Re: [v2 00/10] arm/arm64: mediatek: Fix mmsys device probing

On Mon, 23 Apr 2018, matthias@kernel.org wrote: > From: Matthias Brugger > > Changes since v1: > - add binding documentation > - ddp: use regmap_update_bits > - ddp: ignore EPROBE_DEFER on clock probing > - mfd: delete mmsys_private > - add Reviewed-by and Acked-by tags

Re: [Xen-devel] [PATCH 0/1] drm/xen-zcopy: Add Xen zero-copy helper DRM driver

On 04/24/2018 01:41 AM, Boris Ostrovsky wrote: On 04/23/2018 08:10 AM, Oleksandr Andrushchenko wrote: On 04/23/2018 02:52 PM, Wei Liu wrote: On Fri, Apr 20, 2018 at 02:25:20PM +0300, Oleksandr Andrushchenko wrote: the gntdev. I think this is generic enough that it could be implemented

Re: [PATCH v11 07/11] drm: Add helper functions to handle aspect-ratio flag bits

On 4/23/2018 3:43 PM, Ville Syrjälä wrote: On Mon, Apr 23, 2018 at 10:55:54AM +0530, Nautiyal, Ankit K wrote: On 4/20/2018 7:42 PM, Ville Syrjälä wrote: On Fri, Apr 20, 2018 at 07:01:47PM +0530, Nautiyal, Ankit K wrote: From: Ankit Nautiyal This patch adds

Re: [PATCH v11 07/11] drm: Add helper functions to handle aspect-ratio flag bits

On 4/23/2018 3:52 PM, Jani Nikula wrote: On Mon, 23 Apr 2018, "Nautiyal, Ankit K" wrote: On 4/20/2018 7:42 PM, Ville Syrjälä wrote: On Fri, Apr 20, 2018 at 07:01:47PM +0530, Nautiyal, Ankit K wrote: From: Ankit Nautiyal +bool

Re: [RFC][PATCH 1/2] drm_hwcomposer: Cleanup gl precompositor init and provide uses_GL flag

Please use "PATCH hwc" for drm_hwcomposer patches. On Mon, Apr 23, 2018 at 7:06 PM, John Stultz wrote: > The drm_hwcomposer has its own GL pre-compositor which is used > to squish layers when there are more layers then planes on the > display hardware. In many ways this

Re: [RESEND PATCH v6 16/27] drm/bridge: analogix_dp: Fix incorrect operations with register ANALOGIX_DP_FUNC_EN_1

On Monday, April 23, 2018 6:50 AM, Enric Balletbo i Serra wrote: > > From: zain wang > > Register ANALOGIX_DP_FUNC_EN_1(offset 0x18), Rockchip is different to > Exynos: > > on Exynos edp phy, > BIT 7 MASTER_VID_FUNC_EN_N > BIT 6 reserved > BIT 5

Re: [RESEND PATCH v6 14/27] drm/bridge: analogix_dp: Don't use ANALOGIX_DP_PLL_CTL to control pll

On Monday, April 23, 2018 6:50 AM, Enric Balletbo i Serra wrote: > > From: zain wang > > There is no register named ANALOGIX_DP_PLL_CTL in Rockchip edp phy reg > list. We should use BIT_4 in ANALOGIX_DP_PD to control the pll power > instead of ANALOGIX_DP_PLL_CTL. > > Cc:

[Bug 106199] Cannot get back into DM after logoff (Linux 4.16.2+)

https://bugs.freedesktop.org/show_bug.cgi?id=106199 Bug ID: 106199 Summary: Cannot get back into DM after logoff (Linux 4.16.2+) Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW

[PATCH v2 3/3] drm/v3d: Introduce a new DRM driver for Broadcom V3D V3.x+

This driver will be used to support Mesa on the Broadcom 7268 and 7278 platforms. V3D 3.3 introduces an MMU, which means we no longer need CMA or vc4's complicated CL/shader validation scheme. This massively changes the GEM behavior, so I've forked off to a new driver. v2: Mark SUBMIT_CL as

[PATCH v2 2/3] dt-bindings: Add a new binding for Broadcom V3D 3.x and newer GPUs.

These OpenGL ES GPUs are present in the 7268 and 7278 set top box chips. Signed-off-by: Eric Anholt --- .../bindings/display/brcm,bcm-v3d.txt | 28 +++ 1 file changed, 28 insertions(+) create mode 100644

[PATCH v2 0/3] V3D DRM driver

Here's v2 of the driver. This is mostly handling danvet's feedback, but there are a couple of other changes: - new core patch for prime vmap/vunmap - kbuild test robot fixes - overflow mem simplification (figured it out over breakfast with keithp) - drm_gem_object_unreference_unlocked() to

[PATCH v2 1/3] drm: Make the prime vmap/vunmap hooks optional.

Some drivers leave these unimplemented, so don't make them have unimplemented stubs. Signed-off-by: Eric Anholt --- drivers/gpu/drm/drm_prime.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/drm_prime.c b/drivers/gpu/drm/drm_prime.c

Re: [RFC][PATCH 2/2] drm_hwcomposer: Fall back to client compositon if the gl precompostior fails

On Mon, Apr 23, 2018 at 5:06 PM, John Stultz wrote: > If the gl precompositor isn't being used, we cannot accept > every layer as a device composited layer. > > Thus this patch adds some extra logic in the validate function > to try to map layers to available device

[RFC][PATCH 1/2] drm_hwcomposer: Cleanup gl precompositor init and provide uses_GL flag

The drm_hwcomposer has its own GL pre-compositor which is used to squish layers when there are more layers then planes on the display hardware. In many ways this duplicates the client-side GL compositing that is done in SurfaceFlinger, but in theory can be more highly optimized for the hardware.

[RFC][PATCH 2/2] drm_hwcomposer: Fall back to client compositon if the gl precompostior fails

If the gl precompositor isn't being used, we cannot accept every layer as a device composited layer. Thus this patch adds some extra logic in the validate function to try to map layers to available device planes, falling back to client side compositing if we run-out of planes. Credit to Rob

[PATCH] Intel: Add a Kaby Lake PCI ID

From: Matt Atwood Signed-off-by: Matt Atwood --- intel/intel_chipset.h | 1 + 1 file changed, 1 insertion(+) diff --git a/intel/intel_chipset.h b/intel/intel_chipset.h index 01d250e..6b8fd1d 100644 --- a/intel/intel_chipset.h +++

Re: [PATCH v2] drm: rcar-du: track dma-buf fences

Hi Emre, Sorry for the late reply. On Wednesday, 4 April 2018 14:03:57 EEST Emre Ucan wrote: > We have to check dma-buf reservation objects > of our framebuffers before we use them. > Otherwise, another driver might be writing > on the same buffer which we are using. > This would cause visible

[Bug 91808] trine1 misrender r600g

https://bugs.freedesktop.org/show_bug.cgi?id=91808 --- Comment #11 from Dave Airlie --- Created attachment 139029 --> https://bugs.freedesktop.org/attachment.cgi?id=139029=edit attempted fix -- You are receiving this mail because: You are the assignee for the

Re: RFC for a render API to support adaptive sync and VRR

On Mon, Apr 23, 2018 at 10:40:06AM -0400, Harry Wentland wrote: > On 2018-04-20 04:32 PM, Manasi Navare wrote: > > On Wed, Apr 18, 2018 at 09:39:02AM +0200, Daniel Vetter wrote: > >> On Wed, Apr 18, 2018 at 5:58 AM, Keith Packard wrote: > >>> Michel Dänzer

Re: [PATCH 8/8] drm: connector: Remove DRM_BUS_FLAG_DATA_* flags

Hi Jacopo, Thank you for the patch. On Thursday, 19 April 2018 12:31:09 EEST Jacopo Mondi wrote: > DRM_BUS_FLAG_DATA_* flags, defined in drm_connector.h header file are > used to swap ordering of LVDS RGB format to accommodate DRM objects > that need to handle LVDS components ordering. > > Now

[Bug 106196] GPU randomly hangs while playing game Rise of the Tomb Rider

https://bugs.freedesktop.org/show_bug.cgi?id=106196 Bug ID: 106196 Summary: GPU randomly hangs while playing game Rise of the Tomb Rider Product: DRI Version: XOrg git Hardware: Other OS: All

Re: [PATCH 5/7] omapfb: omapfb_dss.h: add stubs to build with COMPILE_TEST && DRM_OMAP

On Monday, 23 April 2018 23:09:55 EEST Mauro Carvalho Chehab wrote: > Laurent Pinchart escreveu: > > On Monday, 23 April 2018 17:22:27 EEST Mauro Carvalho Chehab wrote: > > > Em Mon, 23 Apr 2018 15:56:53 +0200 Bartlomiej Zolnierkiewicz escreveu: > > > > On

[Bug 100105] Make Theano OpenCL support work on Clover and RadeonSI

https://bugs.freedesktop.org/show_bug.cgi?id=100105 --- Comment #5 from Jan Vesely --- (In reply to Jan Vesely from comment #4) > Lowering CL requirements combined with the following pull requests: > https://github.com/Theano/libgpuarray/pull/571 >

Re: [PATCH 5/7] omapfb: omapfb_dss.h: add stubs to build with COMPILE_TEST && DRM_OMAP

Hi Mauro, On Monday, 23 April 2018 17:22:27 EEST Mauro Carvalho Chehab wrote: > Em Mon, 23 Apr 2018 15:56:53 +0200 Bartlomiej Zolnierkiewicz escreveu: > > On Monday, April 23, 2018 02:47:28 PM Bartlomiej Zolnierkiewicz wrote: > >> On Friday, April 20, 2018 01:42:51 PM Mauro Carvalho Chehab wrote:

[Bug 105729] AMD Radeon flickering on HiDPI display with Gnome Wayland after wake from suspend

https://bugs.freedesktop.org/show_bug.cgi?id=105729 --- Comment #7 from Jan Vlug --- Created attachment 139027 --> https://bugs.freedesktop.org/attachment.cgi?id=139027=edit dmesg Requested dmesg. -- You are receiving this mail because: You are the assignee for the

[Bug 105729] AMD Radeon flickering on HiDPI display with Gnome Wayland after wake from suspend

https://bugs.freedesktop.org/show_bug.cgi?id=105729 --- Comment #6 from Jan Vlug --- Created attachment 139026 --> https://bugs.freedesktop.org/attachment.cgi?id=139026=edit glxinfo Requested glxinfo. -- You are receiving this mail because: You are the assignee for

[Bug 105729] AMD Radeon flickering on HiDPI display with Gnome Wayland after wake from suspend

https://bugs.freedesktop.org/show_bug.cgi?id=105729 --- Comment #5 from Jan Vlug --- Sorry for my late reply. The interesting thing is that the flickering did not occur any more since comment 4 was added. I was waiting for the flickering to occur again before posting the

Re: [PATCH] MAINTAINERS: drm: fsl-dcu: Update to NXP email address

Hi Stefan, On Fri, Mar 30, 2018 at 2:10 PM, Fabio Estevam wrote: > From: Fabio Estevam > > The freescale.com domain will stop working soon, so use > the nxp.com domain instead. > > Signed-off-by: Fabio Estevam > --- >

Re: [PATCH 4/4] drm/vc4: Add parameter for syncobj support

Stefan Schake writes: > This allows runtime detection of syncobj submission support. > > Signed-off-by: Stefan Schake I think if we move patch 1 after 2+3, then we can just drop this one and use drmGetCap(fd, DRM_CAP_SYNCOBJ, ) in userspace for

Re: [PATCH 3/4] drm/vc4: Export fence through syncobj

Stefan Schake writes: > Allow specifying a syncobj on render job submission where we store the > fence for the job. This gives userland flexible access to the fence. > > Signed-off-by: Stefan Schake > --- > drivers/gpu/drm/vc4/vc4_gem.c | 38

Re: [PATCH 2/4] drm/vc4: Syncobj import support

Stefan Schake writes: > Allow userland to specify a syncobj that is waited on before a render job > starts processing. > > Signed-off-by: Stefan Schake > --- > drivers/gpu/drm/vc4/vc4_drv.h | 2 ++ > drivers/gpu/drm/vc4/vc4_gem.c | 33

Re: [PATCH v4 1/2] drm/vc4: Add CTM support

Stefan Schake writes: > The hardware has a single block for applying a CTM prior to gamma lut. > It can be fed with pixels from one of our CRTC at a time and uses a > matrix with S0.9 scalars. Use private atomic state to reject attempts > from userland to apply CTM for more

[Bug 106006] Kernel 4.16.0+ switch amdgpu.dc=1 causes screen brightness set to 1 to be dimmed by default

https://bugs.freedesktop.org/show_bug.cgi?id=106006 --- Comment #12 from Joel Sass --- Created attachment 139022 --> https://bugs.freedesktop.org/attachment.cgi?id=139022=edit I don't think this is the same file from 2.17. Sorry. -- You are receiving this mail because:

[Bug 106006] Kernel 4.16.0+ switch amdgpu.dc=1 causes screen brightness set to 1 to be dimmed by default

https://bugs.freedesktop.org/show_bug.cgi?id=106006 --- Comment #11 from Joel Sass --- Okay, sadly, I wasn't clear about the kernel I was running. It's located here: https://github.com/M-Bab/linux-kernel-amdgpu and I installed the .deb created by the git contributor here:

Re: [PATCH v2] drm/vc4: Add support for plane alpha

Stefan Schake writes: > The HVS supports mixing fixed alpha with per-pixel alpha or > setting a fixed plane alpha in case there is no per-pixel information. > This allows us to support the generic DRM plane alpha property. > > Signed-off-by: Stefan Schake

Re: [PATCH 16/61] gpu: drm: vc4: simplify getting .drvdata

Wolfram Sang writes: > We should get drvdata from struct device directly. Going via > platform_device is an unneeded step back and forth. > > Signed-off-by: Wolfram Sang Applied to drm-misc-next. Thanks! signature.asc

Re: [PATCH v4 2/8] dt-bindings: display: atmel: optional video-interface of endpoints

On Mon, 23 Apr 2018 09:22:55 +0200 Peter Rosin wrote: > With bus-type/bus-width properties in the endpoint nodes, the video- > interface of the connection can be specified for cases where the > heuristic fails to select the correct output mode. This can happen > e.g. if not all

Re: [PATCH v4 3/8] drm/atmel-hlcdc: support bus-width (12/16/18/24) in endpoint nodes

On Mon, 23 Apr 2018 09:22:56 +0200 Peter Rosin wrote: > This beats the heuristic that the connector is involved in what format > should be output for cases where this fails. > > E.g. if there is a bridge that changes format between the encoder and the > connector, or if some of

[Bug 106194] AMDGPU RIP: dm_update_crtcs_state on kernel 4.17rc2

https://bugs.freedesktop.org/show_bug.cgi?id=106194 Kevin McCormack changed: What|Removed |Added Summary|AMD Fury X system freeze on |AMDGPU RIP:

[Bug 199101] AMDGPU Fury X random screen flicker on Linux kernel 4.16rc5

https://bugzilla.kernel.org/show_bug.cgi?id=199101 --- Comment #22 from Kevin McCormack (wittyma...@yahoo.com) --- Flickering seems to be gone on 4.17rc2! However, there's a new issue :/ https://bugs.freedesktop.org/show_bug.cgi?id=106194 -- You are receiving this mail because: You are

[Bug 106194] AMD Fury X system freeze on kernel 4.17rc2

https://bugs.freedesktop.org/show_bug.cgi?id=106194 Bug ID: 106194 Summary: AMD Fury X system freeze on kernel 4.17rc2 Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity:

Re: [PATCH v8 1/2] drm/bridge: Add Cadence DSI driver

On Sat, 21 Apr 2018 09:08:45 +0200 Boris Brezillon wrote: > Add a driver for Cadence DPI -> DSI bridge. > > This driver only support a subset of Cadence DSI bridge capabilities. > > This driver has been tested/debugged in a simulated environment which > explains

[Bug 106191] FirePro v8800 Failure to recognize DisplayPort signal

https://bugs.freedesktop.org/show_bug.cgi?id=106191 --- Comment #9 from François Jacques --- Created attachment 139017 --> https://bugs.freedesktop.org/attachment.cgi?id=139017=edit dmesg with 4.16.3 backtrace disappears in 4.16.3, still no image. -- You are

[Bug 106191] FirePro v8800 Failure to recognize DisplayPort signal

https://bugs.freedesktop.org/show_bug.cgi?id=106191 --- Comment #8 from François Jacques --- Thank you so much Alex to help out on this! I'll generate another dmesg dump with 4.16.3 -- You are receiving this mail because: You are the assignee for the

[Bug 106191] FirePro v8800 Failure to recognize DisplayPort signal

https://bugs.freedesktop.org/show_bug.cgi?id=106191 --- Comment #7 from François Jacques --- Created attachment 139014 --> https://bugs.freedesktop.org/attachment.cgi?id=139014=edit dmesg with 4.16.2 -- You are receiving this mail because: You are the assignee for

[Bug 106188] Can't successfully set pstates in pp_od_clk_voltage

https://bugs.freedesktop.org/show_bug.cgi?id=106188 --- Comment #3 from tempel.jul...@gmail.com --- I figured out that the cause of the described behavior is that it doesn't allow me to really increase the GPU clock. So I can set "echo "s 7 1194 900" >

[PATCH] drm/tinydrm/mi0283qt: Always set rotation value

The PiTFT (ili9340) has a hardware reset circuit that resets only on power-on and not on each reboot through a gpio like the rpi-display does. As a result, we need to always apply the rotation value regardless of the display "on/off" state. Moved the rotation setting code below out_enable:.

[v2 10/10] MAINTAINERS: update Mediatek Soc entry

From: Matthias Brugger Mediatek SoCs include several soc specific drivers as well as a mfd device. Add these to the maintainers file. Signed-off-by: Matthias Brugger --- MAINTAINERS | 2 ++ 1 file changed, 2 insertions(+) diff --git a/MAINTAINERS

[v2 07/10] drm/mediatek: Add mfd support for mt8173

From: Matthias Brugger Use the MFD device for SoC mt8173. Probing via devicetree is no longer needed for any SoC, so delete it. Signed-off-by: Matthias Brugger Reviewed-by: Philipp Zabel --- drivers/gpu/drm/mediatek/mtk_drm_drv.c

[v2 08/10] clk: mediatek: mt8173-mm: switch to mfd device

From: Matthias Brugger As the new mfd device is in place, switch probing for the MMSYS to support invocation from the mfd device. Signed-off-by: Matthias Brugger Acked-by: Stephen Boyd --- drivers/clk/mediatek/clk-mt8173.c | 17

[v2 09/10] drm: mediatek: Omit warning on probe defers

From: Matthias Brugger When probe through the MFD, it can happen that the clock drivers wasn't probed before the ddp driver gets invoked. The driver used to omit a warning that the driver failed to get the clocks. Omit this error on the defered probe path. Signed-off-by:

[v2 06/10] mfd: mtk-mmsys: Add mt8173 nodes

From: Matthias Brugger Add devices for the mt8173 SoC. Signed-off-by: Matthias Brugger Reviewed-by: Philipp Zabel --- drivers/mfd/mtk-mmsys.c | 14 ++ 1 file changed, 14 insertions(+) diff --git

[v2 05/10] clk: mediatek: mt2701-mm: switch to mfd device

From: Matthias Brugger As the new mfd device is in place, switch probing for the MMSYS to support invocation from the mfd device. Signed-off-by: Matthias Brugger Acked-by: Stephen Boyd --- drivers/clk/mediatek/clk-mt2701-mm.c | 10

[v2 01/10] dt-bindings: mediatek: mmsys: Add support for mfd

From: Matthias Brugger Add binding description for the mmsys mfd for some Mediatek devices. mmsys has some registers to control clock gates (which is used in the clk driver) and some registers to set the routing and enable the differnet blocks of the display subsystem.

[v2 03/10] mfd: mtk-mmsys: Add mmsys driver

From: Matthias Brugger The MMSYS subsystem includes clocks and drm components. This patch adds a MFD device to probe both drivers from the same device tree compatible. Signed-off-by: Matthias Brugger --- drivers/mfd/Kconfig | 9 ++

[v2 04/10] drm/mediatek: mt2701: switch to mfd probing.

From: Matthias Brugger With the mtk-mmsys MFD device in place, we switch the probing for mt2701 from device-tree to mfd. Signed-off-by: Matthias Brugger --- drivers/gpu/drm/mediatek/mtk_drm_drv.c | 30 +++--- 1 file changed, 23

[v2 02/10] drm/mediatek: Use regmap for register access

From: Matthias Brugger The mmsys memory space is shared between the drm and the clk driver. Use regmap to access it. Signed-off-by: Matthias Brugger Reviewed-by: Philipp Zabel --- drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 4 ++--

[v2 00/10] arm/arm64: mediatek: Fix mmsys device probing

From: Matthias Brugger Changes since v1: - add binding documentation - ddp: use regmap_update_bits - ddp: ignore EPROBE_DEFER on clock probing - mfd: delete mmsys_private - add Reviewed-by and Acked-by tags --- MMSYS in Mediatek SoCs has some registers to control clock gates

[Bug 106188] Can't successfully set pstates in pp_od_clk_voltage

https://bugs.freedesktop.org/show_bug.cgi?id=106188 --- Comment #2 from tempel.jul...@gmail.com --- Thanks for your response. I somehow forgot the missing ">", whoops. I now almost got it working like desired, thanks! However, there is a small problem left: It doesn't switch into pstate 7. I

Re: [PATCH v2 6/8] drm/arm/malidp: Enable/disable the scaling engine interrupts with memory writeback

On Mon, Apr 23, 2018 at 03:50:49PM +0100, Ayan Kumar Halder wrote: > Scaling engine interrupts need to be enabled/disabled as and when memwrite > is enabled and disabled. The reason being scaling engine interrupts are > used only by the memory writeout layer. > > This patch depends on: >

[Bug 106188] Can't successfully set pstates in pp_od_clk_voltage

https://bugs.freedesktop.org/show_bug.cgi?id=106188 --- Comment #1 from Alex Deucher --- (In reply to tempel.julian from comment #0) > Hello, > I specified "amdgpu.ppfeaturemask=0x" as a boot parameter so I could > access

[PATCH v2 8/8] drm/arm/malidp: Added the late system pm functions

malidp_pm_suspend_late checks if the runtime status is not suspended and if so, invokes malidp_runtime_pm_suspend which disables the display engine/core interrupts and the clocks. It sets the runtime status as suspended. The difference between suspend() and suspend_late() is as follows:- 1.

[PATCH v2 6/8] drm/arm/malidp: Enable/disable the scaling engine interrupts with memory writeback

Scaling engine interrupts need to be enabled/disabled as and when memwrite is enabled and disabled. The reason being scaling engine interrupts are used only by the memory writeout layer. This patch depends on: https://lkml.org/lkml/2017/5/15/695 Signed-off-by: Ayan Kumar Halder

[PATCH v2 4/8] drm/arm/malidp: Split malidp_se_irq_init

Extract the hardware initialisation part from malidp_se_irq_init() into the malidp_se_irq_hw_init() which will be later invoked from malidpxxx_enable_memwrite() when it needs to re-enable the interrupts. Signed-off-by: Ayan Kumar Halder --- Changes in v2:- - Removed the

[PATCH v2 2/8] drm/arm/malidp: Modified the prototype of malidp_se_irq_fini

'struct drm_device' is being replaced with 'struct malidp_hw_device' as the function argument.The reason being the dependency of malidp_se_irq_fini on 'struct drm_device' needs to be removed so as to enable it to call from functions which receives 'struct malidp_hw_device' as argument.

[PATCH v2 5/8] drm/arm/malidp: Enable/disable interrupts in runtime pm

Display engine and core interrupts need to be disabled when the system invokes malidp_runtime_pm_suspend. Consequently, they need to be enabled in malidp_runtime_pm_resume. Signed-off-by: Ayan Kumar Halder --- Changes in v2:- - Removed the change id ---

[PATCH v2 3/8] drm/arm/malidp: Split malidp_de_irq_init

Extract the hardware initialisation part from malidp_de_irq_init() into the malidp_de_irq_hw_init() which will be later invoked from runtime_pm_resume function when it needs to re-enable the interrupts. Signed-off-by: Ayan Kumar Halder --- Changes in v2:- - Removed the

[PATCH v2 7/8] drm/arm/malidp: Set the output_depth register in modeset

One needs to store the value of the OUTPUT_DEPTH that one has parsed from device tree, so that it can be restored on system resume. This value is set in the modeset function as this gets reset when the system suspends. Signed-off-by: Ayan Kumar Halder --- Changes in v2:- -

[PATCH v2 1/8] drm/arm/malidp: Modified the prototype of malidp_de_irq_fini

'struct drm_device' is being replaced with 'struct malidp_hw_device' as the function argument. The reason being the dependency of malidp_de_irq_fini on 'struct drm_device' needs to be removed so as to enable it to call from functions which receives 'struct malidp_hw_device' as argument.

[PATCH v2 0/8] drm/arm/malidp: Enhance support for system and runtime power management on malidp.

This patch series enhances and fixes certain issues relevant to system and runtime power management on malidp. --- Changes in v2: - Removed the change ids and modified some commit messages --- Ayan Kumar Halder (8): drm/arm/malidp: Modified the prototype of malidp_de_irq_fini drm/arm/malidp:

[Bug 106191] FirePro v8800 Failure to recognize DisplayPort signal

https://bugs.freedesktop.org/show_bug.cgi?id=106191 --- Comment #6 from Alex Deucher --- Please attach your full dmesg output. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list

Re: RFC for a render API to support adaptive sync and VRR

On 2018-04-20 04:32 PM, Manasi Navare wrote: > On Wed, Apr 18, 2018 at 09:39:02AM +0200, Daniel Vetter wrote: >> On Wed, Apr 18, 2018 at 5:58 AM, Keith Packard wrote: >>> Michel Dänzer writes: Time-based presentation seems to be the right approach for

[Bug 199319] Flickering screen on AMDGPU and DC with Linux 4.16-2

https://bugzilla.kernel.org/show_bug.cgi?id=199319 --- Comment #20 from har...@gmx.de --- This issues (both, the flickering and the black screen) are obviously fixed with kernel 4.17.0-rc2. Thank you. -- You are receiving this mail because: You are watching the assignee of the bug.

Re: [PATCH 7/7] ARM: dts: sun7i: Add dts file for the A20-linova1-7 HMI

Hi, Il 22/03/2018 19:05, Maxime Ripard ha scritto: On Wed, Mar 21, 2018 at 09:03:13PM +0100, Giulio Benetti wrote: The A20-Linova1-7 HMI, also called Q027_2_F which is printed on production label, is an industrial Human Machine Interface. It features: - 512MB DDR RAM - 1 Sd-card >= 4GB - 1 Usb

[Bug 199475] AMDGPU Failed to blank

https://bugzilla.kernel.org/show_bug.cgi?id=199475 --- Comment #5 from DCWizard (andreas...@gmail.com) --- No i don't have any display problem. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing

[Bug 199475] AMDGPU Failed to blank

https://bugzilla.kernel.org/show_bug.cgi?id=199475 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC|

[Bug 106193] When positioning a monitor output above or below initial configuration with xrandr, hard freeze with graphics artifacts 4.16.2+

https://bugs.freedesktop.org/show_bug.cgi?id=106193 --- Comment #3 from Harry Wentland --- If the patch doesn't help are you able to capture the dmesg log and post it? -- You are receiving this mail because: You are the assignee for the

[Bug 106193] When positioning a monitor output above or below initial configuration with xrandr, hard freeze with graphics artifacts 4.16.2+

https://bugs.freedesktop.org/show_bug.cgi?id=106193 --- Comment #2 from Harry Wentland --- Created attachment 139013 --> https://bugs.freedesktop.org/attachment.cgi?id=139013=edit [PATCH] drm/amd/display: Disallow enabling CRTC without primary plane with FB Does this

[Bug 106193] When positioning a monitor output above or below initial configuration with xrandr, hard freeze with graphics artifacts 4.16.2+

https://bugs.freedesktop.org/show_bug.cgi?id=106193 --- Comment #1 from Joel Sass --- Created attachment 139012 --> https://bugs.freedesktop.org/attachment.cgi?id=139012=edit A picture of the monitor output on failure. -- You are receiving this mail because: You are the

[Bug 106192] 4.16.2+ lightdm logon screen will not unblank after monitors fall asleep

https://bugs.freedesktop.org/show_bug.cgi?id=106192 Michel Dänzer changed: What|Removed |Added Attachment #139011|application/x-trash |text/plain

[Bug 106192] 4.16.2+ lightdm logon screen will not unblank after monitors fall asleep

https://bugs.freedesktop.org/show_bug.cgi?id=106192 Michel Dänzer changed: What|Removed |Added Attachment #139009|text/x-log |text/plain

[Bug 106192] 4.16.2+ lightdm logon screen will not unblank after monitors fall asleep

https://bugs.freedesktop.org/show_bug.cgi?id=106192 Michel Dänzer changed: What|Removed |Added Attachment #139008|application/x-trash |text/plain

[PATCH 1/4] drm/panel: otm8009a: fix backlight updates

Backlight updates was not working anymore since the good implementation of the dsi lpm mode in the dsi host driver. After a longer analysis, the backlight updates in dsi video mode require the dsi hs mode. Note: it is important to keep the dsi lpm mode for the rest of the driver as init sequence,

Re: [PATCH 5/7] omapfb: omapfb_dss.h: add stubs to build with COMPILE_TEST && DRM_OMAP

On 23/04/18 16:56, Bartlomiej Zolnierkiewicz wrote: > Ideally we should be able to build both drivers in the same kernel > (especially as modules). > > I was hoping that it could be fixed easily but then I discovered > the root source of the problem: > > drivers/gpu/drm/omapdrm/dss/display.o:

[PATCH 4/4] drm/panel: otm8009a: use new backlight api

Use the new backlight api. Signed-off-by: Philippe Cornu --- drivers/gpu/drm/panel/panel-orisetech-otm8009a.c | 26 1 file changed, 9 insertions(+), 17 deletions(-) diff --git a/drivers/gpu/drm/panel/panel-orisetech-otm8009a.c

[PATCH 2/4] drm/panel: otm8009a: fix glitches by moving backlight enable to otm8009a_enable()

The backlight 1st update was in the otm8009a_prepare() function for a bad reason: backlight was not working in video mode and the otm8009a_prepare() is in command mode for the init sequence. As the backlight is now fixed (no lpm), it is good to put it back in the otm8009a_enable() function,

[PATCH 3/4] drm/panel: otm8009a: no message if probe success

Remove the message in case of probe success. This comes from a suggestion followed in the recent integration of the raydium rm68200 panel. Signed-off-by: Philippe Cornu --- drivers/gpu/drm/panel/panel-orisetech-otm8009a.c | 11 ++- 1 file changed, 2 insertions(+),

[PATCH 0/4] drm/panel: otm8009a: backlight fixes & improvements

This patch serie fixes 2 backlight issues and adds the new backlight api support. Philippe Cornu (4): drm/panel: otm8009a: fix backlight updates drm/panel: otm8009a: fix glitches by moving backlight enable to otm8009a_enable() drm/panel: otm8009a: no message if probe success

[Bug 106193] When positioning a monitor output above or below initial configuration with xrandr, hard freeze with graphics artifacts 4.16.2+

https://bugs.freedesktop.org/show_bug.cgi?id=106193 Bug ID: 106193 Summary: When positioning a monitor output above or below initial configuration with xrandr, hard freeze with graphics artifacts 4.16.2+ Product: DRI

RE: [PATCH] drm: Don't pass the index to drm_property_add_enum()

Acked-by: Stanislav Lisovskiy Best Regards, Lisovskiy Stanislav Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo> From: Ville Syrjala [ville.syrj...@linux.intel.com] Sent: Friday, March 16,

Re: [PATCH 5/7] omapfb: omapfb_dss.h: add stubs to build with COMPILE_TEST && DRM_OMAP

On Monday, April 23, 2018 02:47:28 PM Bartlomiej Zolnierkiewicz wrote: > On Friday, April 20, 2018 01:42:51 PM Mauro Carvalho Chehab wrote: > > Add stubs for omapfb_dss.h, in the case it is included by > > some driver when CONFIG_FB_OMAP2 is not defined, with can > > happen on ARM when DRM_OMAP is

[Bug 106192] 4.16.2+ lightdm logon screen will not unblank after monitors fall asleep

https://bugs.freedesktop.org/show_bug.cgi?id=106192 --- Comment #3 from Joel Sass --- Created attachment 139011 --> https://bugs.freedesktop.org/attachment.cgi?id=139011=edit Xorg.conf from frozen screen 0 -- You are receiving this mail because: You are the assignee for

[Bug 106192] 4.16.2+ lightdm logon screen will not unblank after monitors fall asleep

https://bugs.freedesktop.org/show_bug.cgi?id=106192 --- Comment #2 from Joel Sass --- Created attachment 139010 --> https://bugs.freedesktop.org/attachment.cgi?id=139010=edit Dmesg shows kernel error after freezing. Had to acquire with ssh. Looks like a kernel bug issue.

[Bug 106192] 4.16.2+ lightdm logon screen will not unblank after monitors fall asleep

https://bugs.freedesktop.org/show_bug.cgi?id=106192 --- Comment #1 from Joel Sass --- Created attachment 139009 --> https://bugs.freedesktop.org/attachment.cgi?id=139009=edit Xorg failure when screen was blanked in lightdm -- You are receiving this mail because: You are

[Bug 106192] 4.16.2+ lightdm logon screen will not unblank after monitors fall asleep

https://bugs.freedesktop.org/show_bug.cgi?id=106192 Bug ID: 106192 Summary: 4.16.2+ lightdm logon screen will not unblank after monitors fall asleep Product: DRI Version: unspecified Hardware: Other OS: All

RE: [Intel-gfx] [PATCH v7 1/2] drm: content-type property for HDMI connector

Ping From: Intel-gfx [intel-gfx-boun...@lists.freedesktop.org] on behalf of StanLis [stanislav.lisovs...@intel.com] Sent: Monday, April 23, 2018 10:34 AM To: dri-devel@lists.freedesktop.org Cc: intel-...@lists.freedesktop.org Subject: [Intel-gfx] [PATCH v7

[Bug 106191] FirePro v8800 Failure to recognize DisplayPort signal

https://bugs.freedesktop.org/show_bug.cgi?id=106191 François Jacques changed: What|Removed |Added Summary|Failure to recognize|FirePro

[Bug 106191] Failure to recognize DisplayPort signal

https://bugs.freedesktop.org/show_bug.cgi?id=106191 François Jacques changed: What|Removed |Added Keywords|

[Bug 106191] Failure to recognize DisplayPort signal

https://bugs.freedesktop.org/show_bug.cgi?id=106191 --- Comment #5 from François Jacques --- If there's anything else I can provide that would help further diagnosing this issue, I'll gladly try. Steps I'm thinking about taking for further experiments, in the

[Bug 103769] Unity based games do not start

https://bugs.freedesktop.org/show_bug.cgi?id=103769 --- Comment #15 from letha...@gmail.com --- it seems the segfaults have improved lately... Much less, the games do start more often -- You are receiving this mail because: You are the assignee for the

  1   2   >