drivers/gpu/drm/drm_crtc.c:1995:5: sparse: symbol 'get_properties' was not
declared. Should it be static?
Signed-off-by: Fengguang Wu
---
drm_crtc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c
index dcfd64e5..a80
tree: git://people.freedesktop.org/~robclark/linux atomic-properties
head: 4e73d9848e88a1bdd90c2506457dc4e7583c2f58
commit: d9224ddf063bb89803a3f4cce2dfd3d2afcb4906 [5/12] drm: refactor
getproperties/getconnector
reproduce:
# apt-get install sparse
git checkout d9224ddf063bb89803a3f4cce2df
Hi Russell,
On 12/17/2014 06:40 PM, Russell King - ARM Linux wrote:
> On Wed, Dec 17, 2014 at 05:44:33PM +0800, Liu Ying wrote:
>> Hi Thierry,
>>
>> Sorry for the late response.
>> I tried to address almost all your comments locally first.
>> More feedback below.
>>
>> On 12/10/2014 09:16 PM, Thie
> -Original Message-
> From: Thierry Reding [mailto:thierry.reding at gmail.com]
> Sent: Wednesday, December 17, 2014 16:13
> To: Cheng, Yao
> Cc: Daniel Vetter; intel-gfx at lists.freedesktop.org; dri-
> devel at lists.freedesktop.org; daniel.vetter at ffwll.ch; Kelley, Sean V;
> Chehab,
https://bugzilla.kernel.org/show_bug.cgi?id=85421
--- Comment #23 from Michel Dänzer ---
(In reply to Hin-Tak Leung from comment #22)
> My crash-free days with 10.3.x/10.4.0 are measured in days if not hours, but
> with 10.2.x is in weeks. I'll continue to switch to a newer mesa as it comes
> ou
Hi,
This series addressed almost all comments from Thierry Redding and Russell
on v1.
This series adds support for i.MX MIPI DSI DRM driver.
Currently, the MIPI DSI driver only supports the burst with sync pulse mode.
This series also includes a DRM panel driver for the Truly TFT480800-16-E pane
If no best divider is normally found, we will try to use the maximum divider.
We should not set the parent clock rate to be 1Hz by force for being rounded.
Instead, we should take the maximum divider as a base and calculate a correct
parent clock rate for being rounded.
Signed-off-by: Liu Ying
--
Signed-off-by: Liu Ying
---
v1->v2:
* None.
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/bindings/vendor-prefixes.txt
index 78efebb..3cee528 100644
---
Signed-off-by: Liu Ying
---
v1->v2:
* None.
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/bindings/vendor-prefixes.txt
index 3cee528..8257f3a 100644
---
This patch supports the video_27m clock which is a fixed factor
clock of the pll3_pfd1_540m clock.
Signed-off-by: Liu Ying
---
v1->v2:
* None.
arch/arm/mach-imx/clk-imx6q.c | 1 +
include/dt-bindings/clock/imx6qdl-clock.h | 3 ++-
2 files changed, 3 insertions(+), 1 deletion(-)
di
This patch adds a macro to define the GPR3 MIPI muxing control register field
shift bits.
Signed-off-by: Liu Ying
---
v1->v2:
* None.
include/linux/mfd/syscon/imx6q-iomuxc-gpr.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/mfd/syscon/imx6q-iomuxc-gpr.h
b/include/linux/mfd
The MIPI DSI node contains some ports which represent possible DRM CRTCs
it can connect with. Each port has a 'reg' property embedded. This
property will be wrongly interpretted by the MIPI DSI bus driver, because
the driver will take each subnode which contains a 'reg' property as a
DSI peripher
Signed-off-by: Liu Ying
---
v1->v2:
* Thierry Reding suggested that the mipi_dsi_pixel_format_to_bpp() function
could be placed at the common DRM MIPI DSI driver.
This patch is newly added.
include/drm/drm_mipi_dsi.h | 14 ++
1 file changed, 14 insertions(+)
diff --git a/incl
This patch adds i.MX MIPI DSI host controller driver support.
Currently, the driver supports the burst with sync pulses mode only.
Signed-off-by: Liu Ying
---
v1->v2:
* Address almost all comments from Thierry Reding and Russell.
* Update the DT documentation to remove the display-timings node
This patch adds support for Himax HX8369A MIPI DSI panel.
Signed-off-by: Liu Ying
---
v1->v2:
* Address almost all comments from Thierry Reding.
* Remove several DT properties as they can be implied by the compatible string.
* Add the HIMAX/himax prefixes to the driver's Kconfig name and drive
The TRULY TFT480800-16-E panel is driven by the Himax HX8369A driver IC.
The driver IC supports several display/control interface modes, including
the MIPI DSI video mode and command mode.
Signed-off-by: Liu Ying
---
v1->v2:
* To address Thierry Reding's comments, remove several unnecessary
p
This patch adds support for MIPI DSI host controller.
Signed-off-by: Liu Ying
---
v1->v2:
* None.
arch/arm/boot/dts/imx6qdl.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/imx6qdl.dtsi b/arch/arm/boot/dts/imx6qdl.dtsi
index 96bf2a0..bfc39fd 100644
--- a/arch/a
The new imx_v6_v7_defconfig is generated in this way:
* make ARCH=arm imx_v6_v7_defconfig
* make ARCH=arm savedefconfig
* cp defconfig arch/arm/configs/imx_v6_v7_defconfig
Signed-off-by: Liu Ying
---
v1->v2:
* None.
arch/arm/configs/imx_v6_v7_defconfig | 15 +++
1 file changed, 7 i
This patch adds support for MIPI DSI host controller.
The new imx_v6_v7_defconfig is generated in this way:
* make ARCH=arm imx_v6_v7_defconfig
* make ARCH=arm menuconfig and manually choose to build in
the MIPI DSI host controller driver
* make ARCH=arm savedefconfig
* cp defconfig arch/arm/con
This patch adds support for Himax HX8369A panel.
The new imx_v6_v7_defconfig is generated in this way:
* make ARCH=arm imx_v6_v7_defconfig
* make ARCH=arm menuconfig and manually choose to build in
the Himax HX8369A panel driver
* make ARCH=arm savedefconfig
* cp defconfig arch/arm/configs/imx_v
L;
Same here.
> +static int hdmi_audio_infoframe_unpack(struct hdmi_audio_infoframe *frame,
> +void *buffer)
> +{
> + u8 *ptr = buffer;
> + int ret;
> +
> + if (ptr[0] != HDMI_INFOFRAME_TYPE_AUDIO ||
> + ptr[1] != 1 ||
> + ptr[2] != HDMI_AUDIO_INFOFRAME_SIZE) {
> + return -EINVAL;
> + }
> +
> + if (hdmi_infoframe_checksum(buffer, HDMI_INFOFRAME_SIZE(AUDIO)) != 0)
> + return -EINVAL;
And here.
> +static int
> +hdmi_vendor_any_infoframe_unpack(union hdmi_vendor_any_infoframe *frame,
> + void *buffer)
> +{
[...]
> + /* HDMI OUI */
> + if ((ptr[0] != 0x03) ||
> + (ptr[1] != 0x0c) ||
> + (ptr[2] != 0x00))
> + return -EINVAL;
It'd be nice if this would actually use the HDMI_IEEE_OUI constant. The
_pack() function hardcodes this too, so I guess it's fine and something
that could be cleaned up later on if somebody cares enough.
Thierry
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141218/4a9a740c/attachment.sig>
ook it through the media git tree, especially since
patch 3/3 clearly belongs there.
If we ever need to resolve dependencies between this and new work in DRM
we could set up a stable branch containing patches 1/3 and 2/3 which can
be merged into both trees.
Thierry
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141218/fa756f27/attachment-0001.sig>
https://bugzilla.kernel.org/show_bug.cgi?id=84771
Gary van der Merwe changed:
What|Removed |Added
CC||garyvdm at gmail.com
--- Comment #3
On 12/18/14 09:24, Thierry Reding wrote:
> On Thu, Dec 11, 2014 at 09:57:54AM +0100, Hans Verkuil wrote:
>> Hi Thierry,
>>
>> On 12/02/14 13:08, Hans Verkuil wrote:
>>> This patch series adds new HDMI 2.0/CEA-861-F defines to hdmi.h and
>>> adds unpacking and logging functions to hdmi.c. It also us
The qemu stdvga can be configured with a wide range of video memory,
from 1 MB to 256 MB (default is 16 MB). In case it is configured
with only 1 or 2 MB it isn't really usable with bochsdrm, due to
depths other than 32bpp not being supported so that isn't enough
memory for a reasonable sized fram
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/qxl/qxl_fb.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/qxl/qxl_fb.c b/drivers/gpu/drm/qxl/qxl_fb.c
index 3d7c1d0..18ef31a 100644
--- a/drivers/gpu/drm/qxl/qxl_fb.c
+++ b/drivers/gpu/drm/qxl/qxl_fb.c
@@ -521,6 +521,9 @@
orm_device_add() to a workqueue would be the best
option here.
Thierry
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141218/2f671650/attachment.sig>
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141218/c124b51a/attachment.html>
HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141218/37b7d5d8/attachment.html>
Am Donnerstag, den 18.12.2014, 15:11 +0800 schrieb Liu Ying:
> This patch supports the video_27m clock which is a fixed factor
> clock of the pll3_pfd1_540m clock.
>
> Signed-off-by: Liu Ying
> ---
> v1->v2:
> * None.
>
> arch/arm/mach-imx/clk-imx6q.c | 1 +
> include/dt-bindings/c
Am Donnerstag, den 18.12.2014, 15:11 +0800 schrieb Liu Ying:
> The MIPI DSI node contains some ports which represent possible DRM CRTCs
> it can connect with. Each port has a 'reg' property embedded. This
> property will be wrongly interpretted by the MIPI DSI bus driver, because
> the driver wil
On Thu, Dec 18, 2014 at 11:04 AM, Thierry Reding
wrote:
>> I double checked the symptom and found it was a deadlock on drm_global_mutex.
>> When i915_driver_load() registers the platform device while ipvr module is
>> in the system, ipvr's probe() function tries to lock drm_global_mutex which
>>
Am Donnerstag, den 18.12.2014, 15:11 +0800 schrieb Liu Ying:
> This patch adds i.MX MIPI DSI host controller driver support.
> Currently, the driver supports the burst with sync pulses mode only.
>
> Signed-off-by: Liu Ying
> ---
> v1->v2:
> * Address almost all comments from Thierry Reding and
was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141218/07f55c19/attachment.html>
facts too.
And then I have no idea if this is the correct place here at radeonsi.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attach
From: Gustavo Padovan
Hi,
In this series:
- fix to FIMD pageflips, only finish pageflips if START == START_S.
- remove struct exynos_drm_overlay and struct exynos_drm_manager.
exynos_drm_overlay was merged with exynos_drm_plane and exynos_drm_manager
with exynos_drm_crtc removing two extra
From: Daniel Kurtz
A framebuffer gets committed to FIMD's default window like this:
exynos_drm_crtc_update()
exynos_plane_commit()
fimd_win_commit()
fimd_win_commit() programs BUF_START[0]. At each vblank, FIMD hardware
copies the value from BUF_START to BUF_START_S (BUF_START's shadow
re
From: Gustavo Padovan
With this change we allow other pieces of the code to use this macro.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 3 ---
drivers/gpu/drm/exynos/exynos_drm_drv.h | 3 +++
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/driv
From: Gustavo Padovan
Let other pieces of the driver access struct exynos_drm_crtc as well.
struct exynos_drm_manager will be merged into struct exynos_drm_crtc, in
the sense we will move all its members to exynos_drm_crtc, so to start
this conversion exynos_drm_crtc need to be exposed as well.
From: Gustavo Padovan
This functions were doing nothing but calling a manager op function,
so remove them and call the manager directly.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 33 ---
drivers/gpu/drm/exynos/exynos_drm_plane.c
From: Gustavo Padovan
We set it in the beginning of the function, thus no need to set it at
initialization.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_fimd.c
From: Gustavo Padovan
struct exynos_drm_overlay has no practical advantage nor serves as
important piece of the exynos API design. The only place it was used
was inside the struct exynos_plane which was just causing a extra
access overhead. Users had to access the overlay first and just then
get
From: Gustavo Padovan
vidi_commit does nothing, remove it and its callers.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_vidi.c | 12
1 file changed, 12 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_vidi.c
b/drivers/gpu/drm/exynos/exynos_drm_
From: Gustavo Padovan
DPMS settings should only be changed by a full modeset.
exynos_plane_update() should only care about updating the planes itself
and nothing else.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_plane.c | 1 -
1 file changed, 1 deletion(-)
diff --git
From: Gustavo Padovan
DPMS only makes sense when the mode changes, for plane update changes do
not perform any dpms operation.
This move places the win_commit() and commit() calls directly in the code
instead of calling exynos_drm_crtc_commit() thus avoiding DPMS operations.
Signed-off-by: Gust
From: Gustavo Padovan
It's doing nothing but calling exynos_crtc->ops->win_commit(), so let's
call this directly to avoid extra layers of abstraction.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 4 +++-
drivers/gpu/drm/exynos/exynos_drm_plane.c | 15 +---
From: Gustavo Padovan
We can safely use the exynos_update_plane() to update the plane
framebuffer for both the overlay and primary planes.
Note that this patch removes a call to manager->ops->commit() in
exynos_drm_crtc_mode_set_commit(). The commit() call is used only by the
fimd driver to set
From: Gustavo Padovan
Avoid an extra call to exynos_drm_crtc_mode_set_commit() that only calls
exynos_update_plane().
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/exynos/e
From: Gustavo Padovan
This was just as extra chain in the call stack. We just rename it to
_set_base() and let it do everything alone.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/drivers/
From: Gustavo Padovan
'base' is more widely used name in the drm subsystem for the base object.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 4 ++--
drivers/gpu/drm/exynos/exynos_drm_drv.h | 7 +++
2 files changed, 5 insertions(+), 6 deletions(-)
diff --g
From: Gustavo Padovan
Get the pipe value from a parameter instead of getting it from
manager->pipe. We are removing manager->pipe.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 8
drivers/gpu/drm/exynos/exynos_drm_crtc.h | 2 +-
drivers/gpu/drm/exynos/e
From: Gustavo Padovan
It is not longer used. This is part of the process of removing
struct exynos_drm_manager entirely.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 2 +-
drivers/gpu/drm/exynos/exynos_drm_drv.h | 2 --
drivers/gpu/drm/exynos/exynos_drm_fimd.c
From: Gustavo Padovan
'type' is now part of the struct exynos_drm_crtc. This is just another
step in the struct exynos_drm_manager removal.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 6 --
drivers/gpu/drm/exynos/exynos_drm_crtc.h | 3 ++-
drivers/gpu/drm/
From: Gustavo Padovan
manager-drm_dev is only accessed by exynos_drm_crtc_create() so this patch
pass drm_dev as argument on exynos_drm_crtc_create() and remove it from
struct exynos_drm_manager.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 9 +
drivers
From: Gustavo Padovan
exynos_drm_manager was just a redundant struct to represent the crtc as
well. In this commit we merge exynos_drm_manager into exynos_drm_crtc to
remove an unnecessary level of indirection easing the understand of the
flow on exynos.
Signed-off-by: Gustavo Padovan
---
driv
From: Gustavo Padovan
Split update plane in two parts, an initial check part that can fail
and the update part that can't fail.
This is a important step for the upcoming atomic modesetting support.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 11 --
d
From: Gustavo Padovan
We can safely use the mode stored in the crtc.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 5 -
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 12 +---
2 files changed, 1 insertion(+), 16 deletions(-)
diff --git a/drivers/gpu/dr
From: Gustavo Padovan
It is no longer used anywhere.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_drv.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_drv.h
b/drivers/gpu/drm/exynos/exynos_drm_drv.h
index 4c930d0..d490b49 100644
From: Gustavo Padovan
Rip out the check from exynos_update_plane() and create
exynos_check_plane() for the check phase enabling use to use
the atomic helpers to call our check and update phases when updating
planes.
Update all users of exynos_update_plane() accordingly to call
exynos_check_plane
From: Gustavo Padovan
The atomic helper to disable planes also uses exynos_update_plane() to
disable plane so we had to adapt it to both commit and disable planes.
A check for NULL CRTC was added to exynos_plane_mode_set() since planes
to be disabled have plane_state->crtc set to NULL.
Also win
From: Gustavo Padovan
It is not used outside of the plane scope anymore.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_plane.c | 11 ++-
drivers/gpu/drm/exynos/exynos_drm_plane.h | 5 -
2 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/drivers/
From: Gustavo Padovan
The new atomic infrastructure needs the .mode_set_nofb() callback to
update CRTC timings before setting any plane.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 61
1 file changed, 14 insertions(+), 47 delet
From: Gustavo Padovan
Add CRTC callbacks .atomic_begin() .atomic_flush(). On exynos they
unprotect the windows before the commit and protects it after based on
a plane mask tha store which plane will be updated.
For that we create two new exynos_crtc callbacks: .win_protect() and
.win_unprotect(
From: Gustavo Padovan
Use drm_atomic_set_fb_for_plane() in the legacy page_flip path to keep
track of the framebuffer pointer and reference.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/exyno
From: Gustavo Padovan
Set CRTC, planes and connectors to use the default implementations from
the atomic helper library. The helpers will work to keep track of state
for each DRM object.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/bridge/ptn3460.c | 4
drivers/gpu/drm/
bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141218/512eb629/attachment.html>
On Thu, Dec 18, 2014 at 11:58:51AM -0200, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> The atomic helper to disable planes also uses exynos_update_plane() to
> disable plane so we had to adapt it to both commit and disable planes.
>
> A check for NULL CRTC was added to exynos_plane_mode_se
Shanghai AVIC Optoelectronics Co., Ltd. is a subsidiary of Tianma
Microelectronics Co., Ltd. and designs and manufactures TFT LCDs.
Signed-off-by: Philipp Zabel
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/
The Shanghai AVIC Optoelectronics TM070DDH03 is a 7" 1024x600 TFT LCD
panel connecting to a 24-bit RGB LVDS interface.
Signed-off-by: Philipp Zabel
---
.../devicetree/bindings/panel/avic,tm070ddh03.txt | 7 +
drivers/gpu/drm/panel/panel-simple.c | 31 ++
2
Hi all,
Here's the atomic dpms I've promised. Still a few things open that I need to
look at once Rob's series has landed and I can rebase:
- Not sure whether we should expose crtc_state->active or not as atomic prop. I
guess it won't hurt to do so, so I'll do that.
- Some of the sanity checks n
This is the infrastructure for DPMS ported to the atomic world.
Fundamental changes compare to legacy DPMS are:
- No more per-connector dpms state, instead there's just one per each
display pipeline. So if you clone either you have to unclone first
if you only want to switch off one screen, or
This builds on top of the crtc->active infrastructure to implement
legacy DPMS. My choice of semantics is somewhat arbitrary, but the
entire pipe is enabled as along as one output is still enabled.
Of course it also clamps everything that's not ON to OFF.
Signed-off-by: Daniel Vetter
---
driver
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141218/b642052c/attachment.html>
From: Jeff McGee
Update kernel interface with new I915_GETPARAM ioctl entries for
slice total, subslice total, EU total, and threads per EU. Add a
wrapping function for each parameter.
The motivation for this change is that fusing can be used to create
multiple slice, subslice, and EU configurat
From: Jeff McGee
The motivation for this change is that fusing can be used to create
multiple slice, subslice, and EU configuration within the same PCI
ID. CHV is the first such device to do this and thus make an ID-based
lookup table approach unreliable. The best solution is for the kernel
to de
https://bugzilla.kernel.org/show_bug.cgi?id=89661
--- Comment #17 from Bernd Steinhauser ---
Ok, it does now boot and seems to work.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=85421
--- Comment #24 from Hin-Tak Leung ---
I had a quick look about 10.2.x vs 10.3.x (specifically, just doing "git log
mesa-10.2.8..mesa-10.3.3 | grep '^commit' | wc -l" and vice versa), and it is
more like they diverged from their most recent common
re the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141218/f06ee7c6/attachment.html>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141218/5bd93095/attachment.html>
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141218/42436522/attachment.html>
mime type||
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141218/6d7426f5/attachment.html>
Hi Daniel,
On Monday 15 December 2014 08:33:10 Daniel Vetter wrote:
> On Fri, Dec 12, 2014 at 10:56:53PM +0200, Laurent Pinchart wrote:
> > On Wednesday 10 December 2014 18:30:10 Daniel Vetter wrote:
> > > On Wed, Dec 10, 2014 at 12:17:51PM -0500, Rob Clark wrote:
> > > > In DRM/KMS we are lacking
Welcome to v2 of the atomic-properties series. This is the part where
we start exposing atomic to userspace. This patchset applies on top
of the topic/atomic-core branch. A few patches from v1 of the patchset
have already been picked up on topic/atomic-core (and are not re-sent).
The first step
As we add properties for all the standard plane/crtc/connector
attributes (in preperation for the atomic ioctl), we are going to want
to handle core state in core (rather than per driver). Intercepting the
core properties will be easier if the atomic_set_property vfuncs are not
called directly, bu
Since we won't be using the obj->properties->values[] array to shadow
property values for atomic drivers, we are going to need a vfunc for
getting prop values. Add that along w/ mandatory wrapper fxns.
v2: more comments and copypasta comment typo fix
Signed-off-by: Rob Clark
Reviewed-by: Sean P
We need to hold connection_mutex as we read the properties. Easiest
thing is just widen the scope where connection_mutex is held.
Signed-off-by: Rob Clark
Reviewed-by: Sean Paul
Reviewed-by: Daniel Vetter
---
drivers/gpu/drm/drm_crtc.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-
Both need to iterate a mode objects properties. Split that out into a
helper shared by both ioctl handlers, since this is going to become more
complicated when we add atomic properties (which will need filtering
from legacy userspace).
Signed-off-by: Rob Clark
Reviewed-by: Sean Paul
Reviewed-by
Once a driver is using atomic helpers for modeset, the next step is to
switch over to atomic properties. To do this, make sure that any
modeset objects have their ->atomic_{get,set}_property() vfuncs suitably
populated if they have custom properties (you did already remember to
plug in atomic-help
Add functions to check core plane/crtc state.
v2: comments, int-overflow checks, call from core rather than
helpers to be sure drivers can't find a way to bypass core
checks
Signed-off-by: Rob Clark
Reviewed-by: Sean Paul
Reviewed-by: Daniel Vetter
---
drivers/gpu/drm/drm_atomic.c
Getting ready to add a lot more standard properties for atomic.
Signed-off-by: Rob Clark
Reviewed-by: Sean Paul
Reviewed-by: Daniel Vetter
---
drivers/gpu/drm/drm_crtc.c | 27 +--
1 file changed, 17 insertions(+), 10 deletions(-)
diff --git a/drivers/gpu/drm/drm_crtc.c
Expose the core plane state as properties, so they can be updated via
atomic ioctl.
v2: atomic property flag
Signed-off-by: Rob Clark
Reviewed-by: Sean Paul
Reviewed-by: Daniel Vetter
---
Documentation/DocBook/drm.tmpl | 74 -
drivers/gpu/drm/drm_atomic.c | 69
Expose the core connector state as properties so it can be updated via
atomic ioctl.
Signed-off-by: Rob Clark
Reviewed-by: Sean Paul
Reviewed-by: Daniel Vetter
---
Documentation/DocBook/drm.tmpl | 11 +--
drivers/gpu/drm/drm_atomic.c | 9 +++--
drivers/gpu/drm/drm_crtc.c | 1
Not too much to do, as we haven't exposed any driver custom properties
yet, so all we need to do is plug in the helpers and set the feature
flag.
Signed-off-by: Rob Clark
Reviewed-by: Sean Paul
Reviewed-by: Daniel Vetter
---
drivers/gpu/drm/msm/hdmi/hdmi_connector.c | 1 +
drivers/gpu
The atomic modeset ioctl can be used to push any number of new values
for object properties. The driver can then check the full device
configuration as single unit, and try to apply the changes atomically.
The ioctl simply takes a list of object IDs and property IDs and their
values.
Originally b
Hi Dave,
A few msm fixes for 3.19:
* hdmi regulators fix
* hdmi fix for spurious HPD interrupts
* fix for sync atomic update after async update (which could show
up with a setcrtc following a pageflip)
* couple little Coccinelle cleanups
The following changes since commit 4e0cd68115620bc32
On Thu, Dec 18, 2014 at 10:54:14PM +0200, Laurent Pinchart wrote:
> Hi Daniel,
>
> On Monday 15 December 2014 08:33:10 Daniel Vetter wrote:
> > On Fri, Dec 12, 2014 at 10:56:53PM +0200, Laurent Pinchart wrote:
> > > On Wednesday 10 December 2014 18:30:10 Daniel Vetter wrote:
> > > > On Wed, Dec 10
This is just a bit fallout from patch polishing and moving the
get_prop logic fully into the core:
- Drop EXPORT_SYMBOL and make the helpers static.
- Drop kerneldoc since not used by drivers.
- Move the cross-file function declarations only used by drm.ko
internally to an internal header.
v2: k
On Thu, Dec 18, 2014 at 5:03 PM, Kertesz Laszlo
wrote:
> On Tue, 2014-10-28 at 09:41 -0400, Alex Deucher wrote:
>> On Tue, Oct 28, 2014 at 8:13 AM, Laszlo Kertesz
>> wrote:
>> > Hello,
>> > i have an issue with Skype lately (i compile mesa, kernel, drm, xserver
>> > from
>> > git periodically an
On Thu, Dec 18, 2014 at 4:22 PM, Daniel Vetter wrote:
>> > > > > TODO move definition of tokens to drm_fourcc.h?
>> > > >
>> > > > Seems orthogonal imo. Another todo is to add checking to all drivers to
>> > > > reject it if it's not 0 with -EINVAL. Otherwise we have yet another
>> > > > case
>>
+--+++---+
| | 7552e7dd95 | 7bf2844ed1 |
next-20141218 |
+--+++---+
| boot_successes | 60 | 0 | 0
1 - 100 of 113 matches
Mail list logo
