[Bug 96492] Running Opera web-browser with forced hardware rendering cause GPU lockup

for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161220/8d31b457/attachment.html>

[Bug 99078] Desktop icons oversaturated with red after December 11 2016 update

... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161220/8a008f56/attachment-0001.html>

[PATCH] drm/nouveau/dma: use rb_entry()

To make the code clearer, use rb_entry() instead of container_of() to deal with rbtree. Signed-off-by: Geliang Tang --- drivers/gpu/drm/nouveau/nvkm/engine/dma/base.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/dma/base.c

[Bug 98897] Macbook pro 11,5 screen flicker when AC adapter plugged in

are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161220/3da80e57/attachment.html>

[Bug 93649] [radeonsi] Graphics lockup while playing tf2

part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161220/25783faa/attachment.html>

[PATCH v2] drm: zte: add overlay plane support

From: Shawn Guo It enables VOU VL (Video Layer) to support overlay plane with scaling function. VL0 has some quirks on scaling support. We chose to skip it and only adds VL1 and VL2 into DRM core for now. Signed-off-by: Shawn Guo --- Changes for v2: - Use clipped

[PATCH] drm: zte: add overlay plane support

Hi Ville, On Thu, Dec 08, 2016 at 05:57:55PM +0200, Ville Syrjälä wrote: > On Thu, Dec 08, 2016 at 11:12:41AM +0800, Shawn Guo wrote: > > > +static void zx_vl_plane_atomic_update(struct drm_plane *plane, > > + struct drm_plane_state *old_state) > > +{ > > +

[pull] amdgpu drm-next-4.10

Hi Dave, Fixes for 4.10. Highlights: - fix display regression on DCE6/8 - Powergating fixes for GFX8 - amdgpu SI fixes (golden settings, proper rev id setup, etc.) The following changes since commit 2cf026ae85c42f253feb9f420d1b4bc99bd5503d: Merge branch 'linux-4.10' of

[Bug 99136] Blood Effects Total War: Warhammer

nee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161220/885bb11f/attachment.html>

[PATCH 1/2] drm: Add new DRM_IOCTL_MODE_GETPLANE2

On Tue, Dec 20, 2016 at 7:12 PM, Kristian H. Kristensen wrote: > diff --git a/include/uapi/drm/drm_mode.h b/include/uapi/drm/drm_mode.h > index ce7efe2..cea3de3 100644 > --- a/include/uapi/drm/drm_mode.h > +++ b/include/uapi/drm/drm_mode.h > @@ -209,6 +209,33 @@ struct drm_mode_get_plane { >

[Bug 99163] Radeon HDMI audio lost after resuming from suspend on kernel >4.2

. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161220/515390aa/attachment.html>

[PATCH v2 2/2] drm: Add Content Protection properties to drm

On Thu, Dec 4, 2014 at 8:03 PM, Sean Paul wrote: > Add new standard connector properties to track whether content protection > (ex: hdcp) is desired by userspace. There are two properties involved, > "Content Protection" and "Content Protection KSV". > > The "Content Protection" property allows

[PATCH v2 2/2] drm: parse hf-vsdb

HDMI 2.0 / CEA-861-F specs define a new CEA extension data block, called hdmi-forum vendor specific data block (HF-VSDB). This block contains information about sink's support for HDMI 2.0 compliant features. These features are: - Deep color YUV 420 support and BPC - 3D flags for -

[PATCH v2 1/2] drm: Create new structure for HDMI info

This patch creates a new structure drm_hdmi_info (inspired from drm_display_info). Driver will parse HDMI sink's advance capabilities from HF-VSDB and populate this structure. This structure will be kept and used as a sub-class within drm_display_info. We are adding parsing of HF-VSDB In the next

[Bug 107001] Radeon HDMI audio lost after resuming from suspend

https://bugzilla.kernel.org/show_bug.cgi?id=107001 --- Comment #4 from Timo Valtoaho --- ...and with 4.9.0. Sadly this has been bothering for over a year now. Anybody else suffering from this? -- You are receiving this mail because: You are watching the assignee of the bug.

[PATCH] drivers/gpu/drm/ast: Support reading configuration values from device tree

The ast driver configures a window to enable access into BMC memory space in order to read some configuration registers. If this window is disabled, which it can be from the BMC side, the ast driver can't function. Closing this window is a necessity for security if a machine's host side and BMC

[PATCH 2/2] drm: Get atomic property value even if DRIVER_ATOMIC is not set

i915 does not set DRIVER_ATOMIC by default yet but uses atomic_check and atomic_commit. drm_object_property_get_value() does not read the correct value of atomic properties if DRIVER_ATOMIC is not set. Checking whether the driver uses atomic modeset is a better check instead as the property values

[PATCH 1/2] drm: Wrap the check for atomic_commit implementation

This check is useful for drivers that do not have DRIVER_ATOMIC set but have atomic modesetting internally implemented. Wrap the check into a function since this is used in many places and as a bonus, the function name helps to document what the check is for. Suggested-by: Daniel Vetter Cc:

[PATCH 2/2] rnndb: mdp5: Update mdp5_pipe

Update mdp5_pipe to incorporate SSPP_NONE and SSPP_CURSORx pipes Signed-off-by: Archit Taneja --- rnndb/mdp/mdp5.xml | 25 ++--- 1 file changed, 14 insertions(+), 11 deletions(-) diff --git a/rnndb/mdp/mdp5.xml b/rnndb/mdp/mdp5.xml index 49aa207..a5ae1e3 100644 ---

[PATCH 1/2] rnndb: mdp5: Add missing bitfields for MDP5_LM_BLEND_COLOR_OUT

Signed-off-by: Archit Taneja --- rnndb/mdp/mdp5.xml | 4 1 file changed, 4 insertions(+) diff --git a/rnndb/mdp/mdp5.xml b/rnndb/mdp/mdp5.xml index de9560b..49aa207 100644 --- a/rnndb/mdp/mdp5.xml +++ b/rnndb/mdp/mdp5.xml @@ -451,6 +451,10 @@

[PATCH 0/2] rnndb: mdp5: Cursor related reg updates

Some cursor SSPP related updates. Archit Taneja (2): rnndb: mdp5: Add missing bitfields for MDP5_LM_BLEND_COLOR_OUT rnndb: mdp5: Update mdp5_pipe rnndb/mdp/mdp5.xml | 29 ++--- 1 file changed, 18 insertions(+), 11 deletions(-) -- The Qualcomm Innovation Center,

[PATCH 2/2] modetest: Teach modetest about format info

From: "Kristian H. Kristensen" BUG=chrome-os-partner:56407 TEST=modetest on a KMS driver that exposes modifiers should print those Change-Id: I91b2a408b1c8f112d7ba5d0998119b3c800b199c --- tests/modetest/modetest.c | 40 1 file

[PATCH 1/2] Add DRM_IOCTL_MODE_GETPLANE2 ioctl wrapper

From: "Kristian H. Kristensen" This adds support for the new DRM_IOCTL_MODE_GETPLANE2 ioctl. For older kernels drmModeGetPlane2() falls back to DRM_IOCTL_MODE_GETPLANE and return the new, bigger drmModePlaneRec, reporting 0 modifiers. BUG=chrome-os-partner:56407

[PATCH 2/2] i915: Add format modifiers for Intel

Signed-off-by: Kristian H. Kristensen --- drivers/gpu/drm/i915/intel_display.c | 35 --- drivers/gpu/drm/i915/intel_sprite.c | 36 +++- 2 files changed, 67 insertions(+), 4 deletions(-) diff --git

[PATCH 1/2] drm: Add new DRM_IOCTL_MODE_GETPLANE2

From: "Kristian H. Kristensen" This new ioctl exctends DRM_IOCTL_MODE_GETPLANE, by returning information about the modifiers that will work with each format. Signed-off-by: Kristian H. Kristensen --- drivers/gpu/drm/arm/hdlcd_crtc.c| 1 +

[PATCH v3 1/4] DRM: add help to get ELD speaker allocation

On Mon, 19 Dec 2016, Arnaud Pouliquen wrote: > Add helper to allow users to retrieve the speaker allocations without > knowledge of the ELD structure. > > Signed-off-by: Arnaud Pouliquen I've already replied with my Reviewed-by, please take care to include them. Reviewed-by: Jani Nikula >

[PATCH v2 17/29] drm: bridge: dw-hdmi: Refactor PHY power handling

Hi Russell, Thank you for the review. On Tuesday 20 Dec 2016 11:45:53 Russell King - ARM Linux wrote: > On Tue, Dec 20, 2016 at 03:33:48AM +0200, Laurent Pinchart wrote: > > Instead of spreading version-dependent PHY power handling code around, > > group it in two functions to power the PHY on

[PATCH v2 04/13] drm: Add data mirror bus flag

Hi Stefan, Thank you for the review. On Tuesday 20 Dec 2016 14:01:46 Stefan Agner wrote: > On 2016-12-18 21:31, Laurent Pinchart wrote: > > Hi Stefan and Thierry, > > > > As the author and suggester of the other bus flags, could you please > > review this patch ? > > It looks to me like an

[PATCH] fbdev: remove current maintainer

t -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161220/c71b35da/attachment.sig>

[PATCH v2 16/29] drm: bridge: dw-hdmi: Detect PHY type at runtime

Hi Jose, On Tuesday 20 Dec 2016 11:39:21 Jose Abreu wrote: > On 20-12-2016 01:33, Laurent Pinchart wrote: > > Detect the PHY type and use it to handle the PHY type-specific SVSRET > > signal. > > > > Signed-off-by: Laurent Pinchart > > > > --- > >

[PATCH v2 16/29] drm: bridge: dw-hdmi: Detect PHY type at runtime

Hi Laurent, On 20-12-2016 13:11, Laurent Pinchart wrote: > Hi Jose, > > On Tuesday 20 Dec 2016 11:39:21 Jose Abreu wrote: >> On 20-12-2016 01:33, Laurent Pinchart wrote: >>> Detect the PHY type and use it to handle the PHY type-specific SVSRET >>> signal. >>> >>> Signed-off-by: Laurent Pinchart

[PATCH] drm/mediatek: Support UYVY and YUYV format for overlay

Hi Bibby, On Wed, 2016-12-14 at 13:14 +0800, Bibby Hsieh wrote: > MT8173 overlay can support UYVY and YUYV format, > we add the format in DRM driver. > > Signed-off-by: Bibby Hsieh > --- > drivers/gpu/drm/mediatek/mtk_disp_ovl.c | 6 ++ > drivers/gpu/drm/mediatek/mtk_drm_plane.c | 2 ++ >

[Bug 99158] vdpau segfaults and gpu locks with kodi on R9285

-- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161220/c0f7b262/attachment.html>

[RFC 8/9] HACK: drm/msm/mdp5: Add support for legacy cursor updates

Op 20-12-16 om 07:23 schreef Archit Taneja: > > > On 12/19/2016 06:20 PM, Maarten Lankhorst wrote: >> Op 19-12-16 om 13:08 schreef Archit Taneja: >>> This code has been more or less picked up from the vc4 and intel >>> implementations of update_plane() funcs for cursor planes. >>> >>> The

[PATCH v2 2/2] drm: parse hf-vsdb

Hi Shashank, On 20-12-2016 13:47, Shashank Sharma wrote: > HDMI 2.0 / CEA-861-F specs define a new CEA extension data block, > called hdmi-forum vendor specific data block (HF-VSDB). This block > contains information about sink's support for HDMI 2.0 compliant > features. These features are: >

[PATCH v2 04/13] drm: Add data mirror bus flag

On 2016-12-20 14:21, Laurent Pinchart wrote: > Hi Stefan, > > Thank you for the review. > > On Tuesday 20 Dec 2016 14:01:46 Stefan Agner wrote: >> On 2016-12-18 21:31, Laurent Pinchart wrote: >> > Hi Stefan and Thierry, >> > >> > As the author and suggester of the other bus flags, could you

[Bug 99143] r9 390: Hardware cursor invisible after hibernate/resume

bed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161220/bf0bdf6e/attachment.html>

[PATCH v3] drm: Improve drm_mm search (and fix topdown allocation) with rbtrees

The drm_mm range manager claimed to support top-down insertion, but it was neither searching for the top-most hole that could fit the allocation request nor fitting the request to the hole correctly. In order to search the range efficiently, we create a secondary index for the holes using either

[PATCH v2 1/2] drm: Create new structure for HDMI info

Hi Shashank, On 20-12-2016 13:47, Shashank Sharma wrote: > This patch creates a new structure drm_hdmi_info (inspired from > drm_display_info). Driver will parse HDMI sink's advance capabilities > from HF-VSDB and populate this structure. This structure will be kept > and used as a sub-class

[PATCH v2 04/13] drm: Add data mirror bus flag

Hi Laurent, On 2016-12-18 21:31, Laurent Pinchart wrote: > Hi Stefan and Thierry, > > As the author and suggester of the other bus flags, could you please review > this patch ? It looks to me like an appropriate use case for the flag. One remark below: > > On Saturday 19 Nov 2016 05:28:04

[PATCH v2 17/29] drm: bridge: dw-hdmi: Refactor PHY power handling

Hi Russell, On 20-12-2016 11:45, Russell King - ARM Linux wrote: > On Tue, Dec 20, 2016 at 03:33:48AM +0200, Laurent Pinchart wrote: >> Instead of spreading version-dependent PHY power handling code around, >> group it in two functions to power the PHY on and off and use them >> through the

[PATCH] drm/ttm: use designated initializers

On Sun, Dec 18, 2016 at 10:53 PM, Alexander Stein wrote: > Hello Kees, > > While understanding what your patches (I've seen the other ones as well) do > themself, I still don't get what your intention is, e.g. why you need this? > Apart from a better readability. > > On Friday 16 December 2016

[RFC 8/9] HACK: drm/msm/mdp5: Add support for legacy cursor updates

On 12/19/2016 06:20 PM, Maarten Lankhorst wrote: > Op 19-12-16 om 13:08 schreef Archit Taneja: >> This code has been more or less picked up from the vc4 and intel >> implementations of update_plane() funcs for cursor planes. >> >> The update_plane() func is usually the

i915 regression in kernel 4.10

On Tue, Dec 20, 2016 at 09:42:46AM -0500, Konrad Rzeszutek Wilk wrote: > On Mon, Dec 19, 2016 at 03:16:44PM +0100, Juergen Gross wrote: > > On 19/12/16 13:29, Chris Wilson wrote: > > > On Mon, Dec 19, 2016 at 12:39:16PM +0100, Juergen Gross wrote: > > >> With recent 4.10 kernel the graphics isn't

[PATCH v2 17/29] drm: bridge: dw-hdmi: Refactor PHY power handling

On Tue, Dec 20, 2016 at 03:33:48AM +0200, Laurent Pinchart wrote: > Instead of spreading version-dependent PHY power handling code around, > group it in two functions to power the PHY on and off and use them > through the driver. > > Powering off the PHY at the beginning of the setup phase is

[RFC 0/4] Introduce drmfs pseudo filesystem for drm subsystem

On Tue, 20 Dec 2016, Laurent Pinchart wrote: > Hi Swati, > > On Monday 19 Dec 2016 16:12:22 swati.dhingra at intel.com wrote: >> From: Swati Dhingra >> >> Currently, we don't have a stable ABI which can be used for the purpose of >> providing output debug/loggging/crc and other such data from

[PATCH v2 16/29] drm: bridge: dw-hdmi: Detect PHY type at runtime

Hi Laurent, On 20-12-2016 01:33, Laurent Pinchart wrote: > Detect the PHY type and use it to handle the PHY type-specific SVSRET > signal. > > Signed-off-by: Laurent Pinchart > --- > drivers/gpu/drm/bridge/dw-hdmi.c | 68 >

[PATCH] drm: remove immutable flag from suggested X/Y connector properties

The suggested X and Y connector properties are intended as a way for drivers for virtual machine GPUs to provide information about the layout of the host system windows (or whatever) corresponding to given guest connectors. The intention is for the guest system to lay out screens in the virtual

[PATCH v2 15/29] drm: bridge: dw-hdmi: Handle overflow workaround based on device version

Hi Laurent, On 20-12-2016 01:33, Laurent Pinchart wrote: > Use the device version queried at runtime instead of the device type > provided through platform data to handle the overflow workaround. This > will make support of other SoCs integrating the same HDMI TX controller > version easier. > >

[Bug 99158] vdpau segfaults and gpu locks with kodi on R9285

art -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161220/bfd64ae0/attachment.html>

[Bug 99158] vdpau segfaults and gpu locks with kodi on R9285

ail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161220/0cf2cdc8/attachment.html>

[PATCH] drm/amdgpu: use designated initializers

On Fri, Dec 16, 2016 at 8:02 PM, Kees Cook wrote: > Prepare to mark sensitive kernel structures for randomization by making > sure they're using designated initializers. These were identified during > allyesconfig builds of x86, arm, and arm64, with most initializer fixes > extracted from

[Bug 99143] r9 390: Hardware cursor invisible after hibernate/resume

into this. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161220/bf8e0671/attachment.html>

[PATCH] drm/i915/debugfs: use rb_entry()

On Mon, Dec 19, 2016 at 10:43:49PM +0800, Geliang Tang wrote: > To make the code clearer, use rb_entry() instead of container_of() to > deal with rbtree. > > Signed-off-by: Geliang Tang Not sure a direct alias for container_of is all that useful, but we have list_entry too ... Queued up for

[PATCH v2 14/29] drm: bridge: dw-hdmi: Detect AHB audio DMA using correct register

Hi Laurent, On 20-12-2016 01:33, Laurent Pinchart wrote: > Bit 0 in CONFIG1_ID tells whether the IP core uses an AHB slave > interface for control. The correct way to identify AHB audio DMA support > is through bit 1 in CONFIG3_ID. > > Signed-off-by: Laurent Pinchart

[PATCH v2 13/29] drm: bridge: dw-hdmi: Reject invalid product IDs

Hi Laurent, On 20-12-2016 01:33, Laurent Pinchart wrote: > The DWC HDMI TX can be recognized by the two product identification > registers. If the registers don't read as expect the IP will be very > different than what the driver has been designed for, or will be > misconfigured in a way that

[PATCH v2 12/29] drm: bridge: dw-hdmi: Rename CONF0 SPARECTRL bit to SVSRET

Hi Laurent, On 20-12-2016 01:33, Laurent Pinchart wrote: > The bit is documented in a Rockchip BSP as > > #define m_SVSRET_SIG (1 << 5) /* depend on PHY_MHL_COMB0=1 */ > > This is confirmed by a Renesas platform, which uses a 2.0 DWC HDMI TX as > the RK3288. Rename the bit accordingly.

[Intel-gfx] [PATCH 0/2] drm: link status property and DP link training failure handling

On Mon, Dec 19, 2016 at 11:15:40PM +, Pandiyan, Dhinakaran wrote: > On Sun, 2016-12-18 at 14:43 +0100, Daniel Vetter wrote: > > On Sat, Dec 17, 2016 at 05:47:56AM +, Pandiyan, Dhinakaran wrote: > > > On Fri, 2016-12-16 at 16:47 +0200, Jani Nikula wrote: > > > > On Fri, 16 Dec 2016, Daniel

[PATCH v2 6/6] drm/i915: Add a cursor hack to allow converting legacy page flip to atomic, v3.

On Mon, Dec 12, 2016 at 11:34:55AM +0100, Maarten Lankhorst wrote: > Do something similar to vc4, only allow updating the cursor state > in-place through a fastpath when the watermarks are unaffected. This > will allow cursor movement to be smooth, but changing cursor size or > showing/hiding

[RFC 0/4] Introduce drmfs pseudo filesystem for drm subsystem

On Tue, Dec 20, 2016 at 4:44 AM, Jani Nikula wrote: > On Tue, 20 Dec 2016, Laurent Pinchart > wrote: >> Hi Swati, >> >> On Monday 19 Dec 2016 16:12:22 swati.dhingra at intel.com wrote: >>> From: Swati Dhingra >>> >>> Currently, we don't have a stable ABI which can be used for the purpose of

i915 regression in kernel 4.10

On Mon, Dec 19, 2016 at 03:16:44PM +0100, Juergen Gross wrote: > On 19/12/16 13:29, Chris Wilson wrote: > > On Mon, Dec 19, 2016 at 12:39:16PM +0100, Juergen Gross wrote: > >> With recent 4.10 kernel the graphics isn't coming up under Xen. First > >> failure message is: > >> > >> [ 46.656649]

[Nouveau] [PATCH] drm/nouveau: fix unknown chipset for GTX 1060

we already have that included in 4.10 2016-12-12 12:26 GMT+01:00 Chris Chiu : > Nouveau driver shows unknown chipset (136000a1) for GTX 1060, so it > only gives VGA resolution on screen. Use the same chipset as nv134 > then it shows FullHD. This commit copies fields from nv134_chipset > to

[PATCH 3/3] drm/msm: Verify that MSM_SUBMIT_BO_FLAGS are set

For every submission buffer object one of MSM_SUBMIT_BO_WRITE and MSM_SUBMIT_BO_READ must be set (and nothing else). If we allowed zero then the buffer object would never get queued to be unreferenced. Signed-off-by: Jordan Crouse --- drivers/gpu/drm/msm/msm_gem_submit.c | 3 ++- 1 file

[PATCH 2/3] drm/msm: Put back the vaddr in submit_reloc()

The error cases in submit_reloc() need to put back the virtual address of the bo before failling. Add a single failure path for the function. Signed-off-by: Jordan Crouse --- drivers/gpu/drm/msm/msm_gem_submit.c | 15 +-- 1 file changed, 9 insertions(+), 6 deletions(-) diff --git

[PATCH 1/3] drm/msm: Ensure that the hardware write pointer is valid

Currently the value written to CP_RB_WPTR is calculated on the fly as (rb->next - rb->start). But as the code is designed rb->next is wrapped before writing the commands so if a series of commands happened to fit perfectly in the ringbuffer, rb->next would end up being equal to rb->size / 4 and

[PATCH 0/3] drm/msm: 4.10 fixes

Here is a short trio of drm/msm fixes suitable for 4.10. The first fixes a hang that occurs when the ring is completely filled, the other two can be triggered through the API and cause mild distress. Jordan Crouse (3): drm/msm: Ensure that the hardware write pointer is valid drm/msm: Put

[PATCH v3 0/4] Generic HDMI codec: Add channel mapping control

Hi, On Dec 19 2016 20:08, Arnaud Pouliquen wrote: > Aim of this patch is to add 'Playback Channel Map' control to export > audio capabilities in term of HDMI sink speakers allocation. > > V3: > - "ASoC: hdmi-codec: add channel mapping control": > => Minor fixes: > - select stereo

[PATCH v2 29/29] arm64: dts: r8a7795: salvator-x: Add DU1 and DU2 external dot clocks

The DU1 and DU2 external dot clocks are fixed frequency clock generators running at 33MHz. Signed-off-by: Laurent Pinchart --- arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts | 23 ++ 1 file changed, 23 insertions(+) diff

[PATCH v2 28/29] arm64: dts: r8a7795: salvator-x: Enable HDMI outputs

From: Koji Matsuoka Instantiate the HDMI connectors and enable the encoders. Signed-off-by: Koji Matsuoka Signed-off-by: Ulrich Hecht Signed-off-by: Laurent Pinchart ---

[PATCH v2 27/29] arm64: dts: r8a7795: Add HDMI encoder support

From: Ulrich Hecht Add DT nodes for the two HDMI encoders in disabled state. Based on work by Koji Matsuoka. Signed-off-by: Ulrich Hecht Signed-off-by: Laurent Pinchart ---

[PATCH v2 26/29] drm: rcar-du: Add HDMI outputs to R8A7795 device description

From: Koji Matsuoka Update the device description with the two available HDMI outputs. Signed-off-by: Koji Matsuoka Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/rcar-du/rcar_du_crtc.h | 4 +++-

[PATCH v2 25/29] drm: rcar-du: Add DPLL support

From: Koji Matsuoka The implementation hardcodes a workaround for the H3 ES1.x SoC regardless of the SoC revision, as the workaround can be safely applied on all devices in the Gen3 family without any side effect. Signed-off-by: Koji Matsuoka Signed-off-by: Ulrich

[PATCH v2 24/29] drm: rcar-du: Skip disabled outputs

When a DT node connected to a DU output is disabled no bridge will ever be instantiated for it. Skip the output in that case. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/rcar-du/rcar_du_kms.c | 7 +++ 1 file changed, 7 insertions(+)

[PATCH v2 23/29] drm: rcar-du: Add Gen3 HDMI encoder support

From: Koji Matsuoka The R-Car Gen3 SoCs include on-chip DesignWare HDMI encoders. Support them with a platform driver to provide platform glue data to the dw-hdmi driver. The driver is a complete rewrite of code coming from the Renesas BSP, save for the values in

[PATCH v2 22/29] dt-bindings: display: renesas: Add R-Car Gen3 HDMI TX DT bindings

The Renesas R-Car Gen3 SoCs use a Synopsys DWC HDMI TX encoder IP. Add corresponding device tree bindings based on the DWC HDMI TX bindings model. Signed-off-by: Laurent Pinchart Acked-by: Rob Herring ---

[PATCH v2 21/29] dt-bindings: display: dw-hdmi: Clean up DT bindings documentation

Make it clear that the core bridge/dw_hdmi.txt document isn't a device tree binding by itself but is meant to be referenced by platform device tree bindings, and update the Rockchip and Freescale DWC HDMI TX bindings to reference it. Signed-off-by: Laurent Pinchart

[PATCH v2 20/29] drm: bridge: dw-hdmi: Remove device type from platform data

From: Kieran Bingham The device type isn't used anymore now that workarounds and PHY-specific operations are performed based on version information read at runtime. Remove it. Signed-off-by: Kieran Bingham

[PATCH v2 19/29] drm: bridge: dw-hdmi: Add support for custom PHY configuration

From: Kieran Bingham The DWC HDMI TX controller interfaces with a companion PHY. While Synopsys provides multiple standard PHYs, SoC vendors can also integrate a custom PHY. Modularize PHY configuration to support vendor PHYs through platform data. The

[PATCH v2 18/29] drm: bridge: dw-hdmi: Move CSC configuration out of PHY code

The color space converter isn't part of the PHY, move its configuration out of PHY code. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/bridge/dw-hdmi.c | 25 ++--- 1 file changed, 10 insertions(+), 15 deletions(-) diff

[PATCH v2 17/29] drm: bridge: dw-hdmi: Refactor PHY power handling

Instead of spreading version-dependent PHY power handling code around, group it in two functions to power the PHY on and off and use them through the driver. Powering off the PHY at the beginning of the setup phase is currently split in two locations for first and second generation PHYs, group

[PATCH v2 16/29] drm: bridge: dw-hdmi: Detect PHY type at runtime

Detect the PHY type and use it to handle the PHY type-specific SVSRET signal. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/bridge/dw-hdmi.c | 68 ++-- include/drm/bridge/dw_hdmi.h | 10 ++ 2 files

[PATCH v2 15/29] drm: bridge: dw-hdmi: Handle overflow workaround based on device version

Use the device version queried at runtime instead of the device type provided through platform data to handle the overflow workaround. This will make support of other SoCs integrating the same HDMI TX controller version easier. Among the supported platforms only i.MX6DL and i.MX6Q have been

[PATCH v2 14/29] drm: bridge: dw-hdmi: Detect AHB audio DMA using correct register

Bit 0 in CONFIG1_ID tells whether the IP core uses an AHB slave interface for control. The correct way to identify AHB audio DMA support is through bit 1 in CONFIG3_ID. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/bridge/dw-hdmi.c | 6 +++---

[PATCH v2 13/29] drm: bridge: dw-hdmi: Reject invalid product IDs

The DWC HDMI TX can be recognized by the two product identification registers. If the registers don't read as expect the IP will be very different than what the driver has been designed for, or will be misconfigured in a way that makes it non-operational (invalid memory address, incorrect clocks,

[PATCH v2 12/29] drm: bridge: dw-hdmi: Rename CONF0 SPARECTRL bit to SVSRET

The bit is documented in a Rockchip BSP as #define m_SVSRET_SIG (1 << 5) /* depend on PHY_MHL_COMB0=1 */ This is confirmed by a Renesas platform, which uses a 2.0 DWC HDMI TX as the RK3288. Rename the bit accordingly. Signed-off-by: Laurent Pinchart

[PATCH v2 11/29] drm: bridge: dw-hdmi: Remove PHY configuration resolution parameter

From: Kieran Bingham The current code hard codes the call of hdmi_phy_configure() to be 8bpp and provides extraneous error checking to verify that this hardcoded value is correct. Simplify the implementation by removing the argument. Signed-off-by:

[PATCH v2 10/29] drm: bridge: dw-hdmi: Implement DRM bridge registration

As an option for drivers not based on the component framework, register the bridge with the DRM core with the DRM bridge API. Existing drivers based on dw_hdmi_bind() and dw_hdmi_unbind() are not affected as those functions are preserved with their current behaviour. Signed-off-by: Laurent

[PATCH v2 09/29] drm: bridge: dw-hdmi: Create connector in the bridge attach operation

The DRM device is not guaranteed by the bridge API to be available before the attach callback. The driver performs properly at the moment as it doesn't use the drm_bridge_add() registration method. As this will be changed later, move connector creation to attach time to ensure compatibility with

[PATCH v2 08/29] drm: bridge: dw-hdmi: Reorder functions to prepare for next commit

The next commit will reference structures and functions in a way that currently requires forward declarations. Reorder the functions to avoid that. No functional change to the code is performed. Signed-off-by: Laurent Pinchart Reviewed-by: Jose Abreu

[PATCH v2 07/29] drm: bridge: dw-hdmi: Move IRQ and IO resource allocation to common code

There's no need to duplicate identical code in multiple drivers (two at the moment, one more to come soon). Move it to the dw-hdmi core where it can be shared. If resource allocation ever becomes device-specific later we'll always have the option of splitting it out again. While it at pass the

[PATCH v2 06/29] drm: bridge: dw-hdmi: Don't forward HPD events to DRM core before attach

Hotplug events should only be forwarded to the DRM core by the interrupt handler when the bridge has been attached, otherwise the DRM device pointer will be NULL, resulting in a crash. Signed-off-by: Laurent Pinchart Reviewed-by: Jose Abreu ---

[PATCH v2 05/29] drm: bridge: dw-hdmi: Remove encoder field from struct dw_hdmi

The field isn't needed, remove it. Signed-off-by: Laurent Pinchart Reviewed-by: Jose Abreu --- drivers/gpu/drm/bridge/dw-hdmi.c | 9 +++-- 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/drivers/gpu/drm/bridge/dw-hdmi.c

[PATCH v2 04/29] drm: bridge: dw-hdmi: Embed drm_bridge in struct dw_hdmi

The drm_bridge instance is always needed, there's no point in allocating it separately. Signed-off-by: Laurent Pinchart Reviewed-by: Jose Abreu --- drivers/gpu/drm/bridge/dw-hdmi.c | 13 +++-- 1 file changed, 3 insertions(+), 10

[PATCH v2 03/29] drm: bridge: dw-hdmi: Remove unused function parameter

From: Kieran Bingham The 'prep' parameter passed to hdmi_phy_configure() is useless. It is hardcoded as 0, and if set, simply prevents the configure function from executing. Remove it. Signed-off-by: Kieran Bingham

[PATCH v2 02/29] drm: bridge: dw-hdmi: Remove unneeded arguments to bind/unbind functions

The master argument isn't used. The data argument, a void pointer, is used by the bind function only where it's cast to a drm_device pointer, which can easily be obtained from the encoder argument instead. Remove them. Signed-off-by: Laurent Pinchart

[PATCH v2 01/29] drm: bridge: dw-hdmi: Merge __hdmi_phy_i2c_write and hdmi_phy_i2c_write

The latter is just an int wrapper around the former void function that unconditionally returns 0. As the return value is never checked, merge the two functions into one. Signed-off-by: Laurent Pinchart Reviewed-by: Jose Abreu ---

[PATCH v2 00/29] R-Car Gen3 HDMI output support

Hello, This patch series implements support for the HDMI output on Renesas R-Car Gen3 SoCs, and more specifically on the R-Car H3. R-Car Gen3 SoCs include one or multiple Synopsys DWC HDMI TX controllers. The series thus starts with 20 cleanup or feature patches for the dw-hdmi driver. Patches

[PATCH] fbdev: remove current maintainer

Hi Daniel, On Thursday 08 Dec 2016 11:04:47 Daniel Vetter wrote: > On Thu, Dec 08, 2016 at 10:34:12AM +0200, Tomi Valkeinen wrote: > > Remove Tomi Valkeinen from fbdev maintainer and mark fbdev as orphan. > > > > Signed-off-by: Tomi Valkeinen > > --- > > > > I just don't have time to even

[RFC 0/4] Introduce drmfs pseudo filesystem for drm subsystem

Hi Swati, On Monday 19 Dec 2016 16:12:22 swati.dhingra at intel.com wrote: > From: Swati Dhingra > > Currently, we don't have a stable ABI which can be used for the purpose of > providing output debug/loggging/crc and other such data from DRM. > The ABI in current use (filesystems, ioctls, et

[Bug 97980] [amdgpu] New kernel warning during shutdown

|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161220/17e89216/attachment.html>

  1   2   >