[Intel-gfx] [PATCH] drm/i915/psr: disable psr2 for resolution greater than 32X20

skl_psr_setup_su_vsc(intel_dp); > > + skl_psr_setup_su_vsc(intel_dp); > > } > > > > /* > > ___ > Intel-gfx mailing list > Intel-gfx at lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/intel-gfx > -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20170110/b1bb6593/attachment-0001.html>

[Intel-gfx] [PATCH 02/10] drm/i915/psr: program vsc header for psr2

ev_priv->psr.colorimetry_support && > > + dev_priv->psr.y_cord_support) { > > + psr_vsc.sdp_header.HB2 = 0x5; > > + psr_vsc.sdp_header.HB3 = 0x13; > > + } else if (dev_priv->psr.y_cord_support) { > > + psr_vsc.sdp_header.HB2 = 0x4; > > + psr_vsc.sdp_header.HB3 = 0xe; > > + } else { > > + psr_vsc.sdp_header.HB2 = 0x3; > > + psr_vsc.sdp_header.HB3 = 0xc; > > + } > > + > > intel_psr_write_vsc(intel_dp, _vsc); > > } > > > > -- > > 1.9.1 > ___ > Intel-gfx mailing list > Intel-gfx at lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/intel-gfx > -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20170110/9261be42/attachment.html>

[Intel-gfx] [PATCH 01/10] drm : adds Y-coordinate and Colorimetry Format

/ > #define DP_PEER_DEVICE_NONE0x0 > -- > 1.9.1 > > ___ > Intel-gfx mailing list > Intel-gfx at lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/intel-gfx > -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20170110/0a420103/attachment-0001.html>

[PATCH V7 1/4] Documentation/devicetree/bindings: b850v3_lvds_dp

Hi Peter, Thank you for the patch. On Sunday 01 Jan 2017 21:24:29 Peter Senna Tschudin wrote: > Devicetree bindings documentation for the GE B850v3 LVDS/DP++ > display bridge. > > Cc: Martyn Welch > Cc: Martin Donnelly > Cc: Javier Martinez Canillas > Cc: Enric Balletbo i Serra > Cc:

[PATCH V7 1/4] Documentation/devicetree/bindings: b850v3_lvds_dp

Hi Peter, On Saturday 07 Jan 2017 01:29:52 Peter Senna Tschudin wrote: > On 04 January, 2017 21:39 CET, Rob Herring wrote: > > On Tue, Jan 3, 2017 at 5:34 PM, Peter Senna Tschudin wrote: > >> On 03 January, 2017 23:51 CET, Rob Herring wrote: > >>> On Sun, Jan 01, 2017 at 09:24:29PM +0100, Peter

Why does OUT_FENCE_PTR point not to an fd (s32) but to an s64?

Hi Daniel, On Monday 09 Jan 2017 11:23:23 Daniel Vetter wrote: > On Fri, Jan 06, 2017 at 01:04:55PM -0800, Chad Versace wrote: > > Was this a mistake in the API? If so, can we fix this ABI mistake before > > kernel consumers rely on this? > > > > I naïvely expected that OUT_FENCE_PTR would be a

[Bug 97338] Black squares in the Spec Ops: The Line chapter select screen

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

[PATCH 1/4] drm: add vblank hooks to struct drm_crtc_funcs

On Tuesday 10 Jan 2017 11:39:03 Daniel Vetter wrote: > On Mon, Jan 09, 2017 at 07:56:24PM +0800, Shawn Guo wrote: > > From: Shawn Guo > > > > The vblank is mostly CRTC specific and implemented as part of CRTC > > driver. So having vblank hooks in struct drm_crtc_funcs should > > generally help

[PATCH v2] drm: get fbdev size from cmdline mode if it exists

Hi Vincent, On Tuesday 10 Jan 2017 13:33:29 Vincent ABRIOU wrote: > On 01/10/2017 12:39 PM, Daniel Vetter wrote: > > On Tue, Jan 10, 2017 at 12:21:09PM +0100, Vincent Abriou wrote: > >> In case no connector is found while creating the fbdev, gives the > >> possibility to specify the default fbdev

[Bug 99353] Kaveri 7400K shows random colored noise instead of GUI in X or Wayland

. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20170110/84ecb7ad/attachment.html>

[rfc] fix output poll execute lockdep

oftware Engineer, Intel Corporation http://blog.ffwll.ch -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20170110/0394d537/attachment.html>

[Bug 99352] DRM/IMX first primary plane with pixel format DRM_FORMAT_YUV420 the screen is discolored

-devel/attachments/20170110/df7964c2/attachment.html>

[PATCH] drm: disable deep color when EDID violates spec

+ DRM_DEBUG("%s: HDMI sink should do DC_36, but does > >> >> > not!\n", > >> >> > + connector->name); > >> >> > + return; > >> >> > + } > >> >> > + > >> >> > + > >> >> > DRM_DEBUG("%s: Assigning HDMI sink color depth as %d bpc.\n", > >> >> > connector->name, dc_bpc); > >> >> > info->bpc = dc_bpc; > >> >> > + info->edid_hdmi_dc_modes = modes; > >> >> > > >> >> > /* > >> >> >* Deep color support mandates RGB444 support for all video > >> >> > @@ -3823,15 +3842,6 @@ static void drm_parse_hdmi_deep_color_ > info(struct > >> >> > drm_connector *connector, > >> >> > DRM_DEBUG("%s: HDMI sink does YCRCB444 in deep > color.\n", > >> >> > connector->name); > >> >> > } > >> >> > - > >> >> > - /* > >> >> > - * Spec says that if any deep color mode is supported at all, > >> >> > - * then deep color 36 bit must be supported. > >> >> > - */ > >> >> > - if (!(hdmi[6] & DRM_EDID_HDMI_DC_36)) { > >> >> > - DRM_DEBUG("%s: HDMI sink should do DC_36, but does > >> >> > not!\n", > >> >> > - connector->name); > >> >> > - } > >> >> > } > >> >> > > >> >> > static void > >> >> > @@ -3895,6 +3905,7 @@ static void drm_add_display_info(struct > >> >> > drm_connector *connector, > >> >> > /* driver figures it out in this case */ > >> >> > info->bpc = 0; > >> >> > info->color_formats = 0; > >> >> > + info->edid_hdmi_dc_modes = 0; > >> >> > info->cea_rev = 0; > >> >> > info->max_tmds_clock = 0; > >> >> > info->dvi_dual = false; > >> >> > -- > >> >> > 2.11.0 > >> >> > >> >> -- > >> >> Ville Syrjälä > >> >> Intel OTC > >> >> ___ > >> >> dri-devel mailing list > >> >> dri-devel at lists.freedesktop.org > >> >> https://lists.freedesktop.org/mailman/listinfo/dri-devel > >> > > >> > > >> > > >> > ___ > >> > dri-devel mailing list > >> > dri-devel at lists.freedesktop.org > >> > https://lists.freedesktop.org/mailman/listinfo/dri-devel > >> > > > > > -- > > Ville Syrjälä > > Intel OTC > -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20170110/24b33a5e/attachment-0001.html>

[Bug 98984] Hexagonal shapes around lights in Cities: Skylines

next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20170110/26ec2ba3/attachment-0001.html>

[PATCH] drm/i915/psr: disable psr2 for resolution greater than 32X20

Reviewed-by: Rodrigo Vivi On Tue, 2017-01-10 at 12:32 +0530, vathsala nagaraju wrote: > PSR2 is restricted to work with panel resolutions upto 3200x2000, > move the check to intel_psr_match_conditions and fully block psr. > > Cc: Rodrigo Vivi > Cc: Jim Bride > Suggested-by: Rodrigo Vivi >

[PATCH] drm: disable deep color when EDID violates spec

On Tue, Jan 10, 2017 at 12:27:45PM -0500, Alex Deucher wrote: > On Tue, Jan 10, 2017 at 6:33 AM, Ernst Sjöstrand wrote: > > Isn't 10bpc very common among monitors, and 12bpc very rare? Or maybe I'm > > confusing the transport layer with the presentation capabilities...? > > Here are 201 monitors

[Bug 192271] New: kernel 4.9 hangs during shutdown or reboot

https://bugzilla.kernel.org/show_bug.cgi?id=192271 Bug ID: 192271 Summary: kernel 4.9 hangs during shutdown or reboot Product: Drivers Version: 2.5 Kernel Version: 4.9.2 Hardware: x86-64 OS: Linux Tree:

[Bug 99236] System (seems to) completely freeze when interacting with java swing applications.

vel/attachments/20170110/6f8fc808/attachment.html>

[RFC] drm: Parse HDMI 2.0 YCbCr 4:2:0 VDB and VCB

On Tue, Jan 10, 2017 at 05:01:08PM +, Jose Abreu wrote: > Hi Ville, > > > [snip] > > >> Are you going to update all the userspace clients? Exposing HDMI 2.0 > >> modes only for your favorite client doesn't sound like a good plan to > >> me. > >> > >> If we simply compute from a specific

[Bug 191291] [amdgpu] mouse cursor disappearing on X11 (KDE Plasma)

https://bugzilla.kernel.org/show_bug.cgi?id=191291 --- Comment #6 from Johannes Hirte --- Created attachment 251151 --> https://bugzilla.kernel.org/attachment.cgi?id=251151=edit Xorg.0.log-4.10.0-rc3-00029-gbd5d7428f5e5 -- You are receiving this mail because: You are watching the assignee of

[Bug 191291] [amdgpu] mouse cursor disappearing on X11 (KDE Plasma)

https://bugzilla.kernel.org/show_bug.cgi?id=191291 --- Comment #5 from Johannes Hirte --- Created attachment 251141 --> https://bugzilla.kernel.org/attachment.cgi?id=251141=edit dmesg-4.10.0-rc3-00029-gbd5d7428f5e5 -- You are receiving this mail because: You are watching the assignee of the

[Bug 191291] [amdgpu] mouse cursor disappearing on X11 (KDE Plasma)

https://bugzilla.kernel.org/show_bug.cgi?id=191291 --- Comment #4 from Johannes Hirte --- Attaching dmesg and Xorg.log from kernel 4.10.0-rc3-00029-gbd5d7428f5e5 I've booted the sytem, logged into KDE Plasma session logged out and the cursor was gone under sddm. Logs were taken from console

[Bug 191281] [drm:amdgpu_ib_ring_tests] *ERROR* amdgpu: failed testing IB on ring 12 (-110)

https://bugzilla.kernel.org/show_bug.cgi?id=191281 --- Comment #4 from Johannes Hirte --- I can confirm that https://lists.freedesktop.org/archives/amd-gfx/2017-January/004537.html fixes boot for me. Tested on top of linux-4.10.0-rc3-00029-gbd5d7428f5e5 -- You are receiving this mail because:

[PATCH v2 9/9] drm/i915: Add render decompression support

On Mon, Jan 09, 2017 at 11:20:57AM -0800, Jason Ekstrand wrote: > On Thu, Jan 5, 2017 at 7:14 AM, wrote: > > > From: Ville Syrjälä > > > > SKL+ display engine can scan out certain kinds of compressed surfaces > > produced by the render engine. This involved telling the display engine > > the

[Bug 99350] libdrm-2.4.74/xf86drmMode.c:904:15: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]

tps://lists.freedesktop.org/archives/dri-devel/attachments/20170110/14c47a6b/attachment.html>

[Bug 99236] System (seems to) completely freeze when interacting with java swing applications.

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/20170110/1399c85d/attachment.html>

[RESEND PATCH v14 2/2] drm/i915: Put "cooked" vlank counters in frame CRC lines

On Tue, Jan 10, 2017 at 02:43:05PM +0100, Tomeu Vizoso wrote: > Use drm_accurate_vblank_count so we have the full 32 bit to represent > the frame counter and userspace has a simpler way of knowing when the > counter wraps around. > > Signed-off-by: Tomeu Vizoso > Reviewed-by: Emil Velikov >

[RFC] drm: Parse HDMI 2.0 YCbCr 4:2:0 VDB and VCB

On Tue, Jan 10, 2017 at 05:33:15PM +0200, Ville Syrjälä wrote: > On Tue, Jan 10, 2017 at 12:26:53PM +, Jose Abreu wrote: > > Hi Ville, > > > > > > On 10-01-2017 11:16, Ville Syrjälä wrote: > > > On Thu, Jan 05, 2017 at 02:46:06PM +, Jose Abreu wrote: > > >> > > > > [snip] > > > >

[Bug 99349] Failed to build shader (translation from TGSI)

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

[Intel-gfx] [PATCH] drm/probe-helpers: Drop locking from poll_enable

On Tue, Jan 10, 2017 at 03:17:44PM +, Chris Wilson wrote: > On Tue, Jan 10, 2017 at 03:29:10PM +0100, Daniel Vetter wrote: > > It was only needed to protect the connector_list walking, see > > > > commit 8c4ccc4ab6f64e859d4ff8d7c02c2ed2e956e07f > > Author: Daniel Vetter > > Date: Thu Jul 9

[RFC] drm: Parse HDMI 2.0 YCbCr 4:2:0 VDB and VCB

On Tue, Jan 10, 2017 at 12:26:53PM +, Jose Abreu wrote: > Hi Ville, > > > On 10-01-2017 11:16, Ville Syrjälä wrote: > > On Thu, Jan 05, 2017 at 02:46:06PM +, Jose Abreu wrote: > >> > > [snip] > > >> The pixel clock rate is half of the TMDS character rate in 4:2:0 > >> (in 24 bit),

[Intel-gfx] [RESEND PATCH v14 2/2] drm/i915: Put "cooked" vlank counters in frame CRC lines

On Tue, Jan 10, 2017 at 05:54:57PM +0200, Ville Syrjälä wrote: > On Tue, Jan 10, 2017 at 02:43:05PM +0100, Tomeu Vizoso wrote: > > Use drm_accurate_vblank_count so we have the full 32 bit to represent > > the frame counter and userspace has a simpler way of knowing when the > > counter wraps

[Bug 99349] Failed to build shader (translation from TGSI)

next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20170110/2d119a10/attachment.html>

[Bug 99236] System (seems to) completely freeze when interacting with java swing applications.

ves/dri-devel/attachments/20170110/0801e0c6/attachment.html>

[bug report] drm: kselftest for drm_mm and eviction

Hello Chris Wilson, The patch 560b32842912: "drm: kselftest for drm_mm and eviction" from Dec 22, 2016, leads to the following static checker warning: drivers/gpu/drm/selftests/test-drm_mm.c:1277 evict_everything() warn: calling list_del() inside list_for_each

[Intel-gfx] [PATCH] drm/probe-helpers: Drop locking from poll_enable

On Tue, Jan 10, 2017 at 05:34:08PM +0100, Daniel Vetter wrote: > On Tue, Jan 10, 2017 at 03:17:44PM +, Chris Wilson wrote: > > On Tue, Jan 10, 2017 at 03:29:10PM +0100, Daniel Vetter wrote: > > > -void drm_kms_helper_poll_enable_locked(struct drm_device *dev) > > > +void

[Bug 97879] [amdgpu] Rocket League: long hangs (several seconds) when loading assets (models/textures/shaders?)

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

[RFC] drm: Parse HDMI 2.0 YCbCr 4:2:0 VDB and VCB

Hi Ville, [snip] >> Are you going to update all the userspace clients? Exposing HDMI 2.0 >> modes only for your favorite client doesn't sound like a good plan to >> me. >> >> If we simply compute from a specific modeline whether it needs to be >> transmitted as 4:2:0, I suppose we could simply

[Bug 99330] Severe flickering with Fiji on Wayland

org/archives/dri-devel/attachments/20170110/05406261/attachment.html>

[PATCH] drm: disable deep color when EDID violates spec

On Tue, Jan 10, 2017 at 03:39:42PM +0200, Jani Nikula wrote: > On Tue, 10 Jan 2017, Ville Syrjälä wrote: > > On Thu, Jan 05, 2017 at 05:45:23PM -0600, Nicholas Sielicki wrote: > >> As per the HDMI 1.3 and 1.4 spec, "deep color modes" are color depths > >> greater than 24 bits per pixel. The

[PATCH] drm: disable deep color when EDID violates spec

On 2017-01-10 03:41 PM, Harry Wentland wrote: > On 2017-01-10 03:10 PM, Alex Deucher wrote: >> On Tue, Jan 10, 2017 at 3:02 PM, Ernst Sjöstrand >> wrote: >>> I kindof assume DP is the default connection these days and with >>> Freesync >>> you use >>> DP or course, but this question was

[PATCH 03/10] drm/i915/psr: fix blank screen issue for psr2

On Monday 09 January 2017 10:47 PM, Vivi, Rodrigo wrote: > On Mon, 2017-01-09 at 18:26 +0530, vathsala nagaraju wrote: >> Psr1 and psr2 are mutually exclusive,ie when psr2 is enabled, >> psr1 should be disabled.When psr2 is exited , bit 31 of reg >> PSR2_CTL must be set to 0 but currently bit 31

[PULL] drm-qemu: 4.10 updates

to queue up for 4.11 instead. thanks, Gerd The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8: Linux 4.10-rc3 (2017-01-08 14:18:17 -0800) are available in the git repository at: git://git.kraxel.org/linux tags/drm-qemu-20170110 for you to fetch changes up

[PATCH] drm: disable deep color when EDID violates spec

On 2017-01-10 03:10 PM, Alex Deucher wrote: > On Tue, Jan 10, 2017 at 3:02 PM, Ernst Sjöstrand wrote: >> I kindof assume DP is the default connection these days and with Freesync >> you use >> DP or course, but this question was specifically for HDMI. >> I guess this patch doesn't affect deep

[PATCH] drm: disable deep color when EDID violates spec

On Tue, 10 Jan 2017, Ville Syrjälä wrote: > On Thu, Jan 05, 2017 at 05:45:23PM -0600, Nicholas Sielicki wrote: >> As per the HDMI 1.3 and 1.4 spec, "deep color modes" are color depths >> greater than 24 bits per pixel. The spec explicitly states, "All Deep >> Color modes are optional though if

[PATCH] drm/probe-helpers: Drop locking from poll_enable

It was only needed to protect the connector_list walking, see commit 8c4ccc4ab6f64e859d4ff8d7c02c2ed2e956e07f Author: Daniel Vetter Date: Thu Jul 9 23:44:26 2015 +0200 drm/probe-helper: Grab mode_config.mutex in poll_init/enable Unfortunately the commit message of that patch fails to

[Bug 99330] Severe flickering with Fiji on Wayland

signee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20170110/3b31b7f8/attachment.html>

[PATCH] drm: disable deep color when EDID violates spec

On Tue, Jan 10, 2017 at 12:33:35PM +0100, Ernst Sjöstrand wrote: > Isn't 10bpc very common among monitors, and 12bpc very rare? Or maybe I'm > confusing the transport layer with the presentation capabilities...? > Here are 201 monitors that claim 10bpc: >

[Intel-gfx] [PATCH] drm/probe-helpers: Drop locking from poll_enable

On Tue, Jan 10, 2017 at 03:29:10PM +0100, Daniel Vetter wrote: > It was only needed to protect the connector_list walking, see > > commit 8c4ccc4ab6f64e859d4ff8d7c02c2ed2e956e07f > Author: Daniel Vetter > Date: Thu Jul 9 23:44:26 2015 +0200 > > drm/probe-helper: Grab mode_config.mutex in

[PATCH] drm: disable deep color when EDID violates spec

On Tue, Jan 10, 2017 at 3:02 PM, Ernst Sjöstrand wrote: > I kindof assume DP is the default connection these days and with Freesync > you use > DP or course, but this question was specifically for HDMI. > I guess this patch doesn't affect deep color over DP? > > Anyway, only 17 of those monitors

[PATCH] drm: disable deep color when EDID violates spec

On Tue, Jan 10, 2017 at 12:46 PM, Ville Syrjälä wrote: > On Tue, Jan 10, 2017 at 12:27:45PM -0500, Alex Deucher wrote: >> On Tue, Jan 10, 2017 at 6:33 AM, Ernst Sjöstrand >> wrote: >> > Isn't 10bpc very common among monitors, and 12bpc very rare? Or maybe I'm >> > confusing the transport

DRM range manger test failures

On Tue, Jan 10, 2017 at 12:45:04PM +, Chris Wilson wrote: > On Tue, Jan 10, 2017 at 01:41:54PM +0100, Geert Uytterhoeven wrote: > > Hi Chris, Laurent, > > > > On R-Car Gen2 (Koelsch) and Gen3 (Salvator-X), the new DRM range > > manager selftests fail with: > > > > drm_mm: Testing DRM

[PATCH v1 7/7] ARM: configs: Add STM32 LTDC support in STM32 defconfig

Signed-off-by: Yannick Fertre --- arch/arm/configs/stm32_defconfig | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/configs/stm32_defconfig b/arch/arm/configs/stm32_defconfig index 29068f5..e3974d9 100644 --- a/arch/arm/configs/stm32_defconfig +++

[PATCH v1 6/7] ARM: dts: stm32429i-eval: Enable ltdc & simple panel on Eval board

Enable ltdc & enable am-480272h3tmqw-t01h panel. Signed-off-by: Yannick Fertre --- arch/arm/boot/dts/stm32429i-eval.dts | 58 1 file changed, 58 insertions(+) diff --git a/arch/arm/boot/dts/stm32429i-eval.dts b/arch/arm/boot/dts/stm32429i-eval.dts index

[PATCH v1 5/7] ARM: dts: stm32f429: Add ltdc support

Add LTDC (Lcd-tft Display Controller) support. Signed-off-by: Yannick Fertre --- arch/arm/boot/dts/stm32f429.dtsi | 25 - 1 file changed, 24 insertions(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/stm32f429.dtsi b/arch/arm/boot/dts/stm32f429.dtsi index

[PATCH v1 4/7] drm/panel: simple: Add support for Ampire AM-480272H3TMQW-T01H

Add simple-panel support for the Ampire AM-480272H3TMQW-T01H, which is a 4.3" WQVGA panel. Signed-off-by: Yannick Fertre --- drivers/gpu/drm/panel/panel-simple.c | 29 + 1 file changed, 29 insertions(+) diff --git a/drivers/gpu/drm/panel/panel-simple.c

[PATCH v1 3/7] dt-bindings: Add Ampire AM-480272H3TMQW-T01H panel

Signed-off-by: Yannick Fertre --- .../bindings/display/panel/ampire,am-480272h3tmqw-t01h.txt | 7 +++ 1 file changed, 7 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/panel/ampire,am-480272h3tmqw-t01h.txt diff --git

[PATCH v1 2/7] drm/st: Add STM32 LTDC driver

ael Reulier + * + * License terms: GNU General Public License (GPL), version 2 + */ + +#include +#include + +#include +#include +#include +#include +#include + +#include "drv.h" +#include "ltdc.h" + +#define DRIVER_NAME"st" +#define DRIVER_DESC

[PATCH v1 1/7] dt-bindings: display: add STM32 LTDC driver

Signed-off-by: Yannick Fertre --- .../devicetree/bindings/display/st,ltdc.txt| 57 ++ 1 file changed, 57 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/st,ltdc.txt diff --git a/Documentation/devicetree/bindings/display/st,ltdc.txt

[PATCH v1 0/7] DRM: add LTDC support for STM32F4

The purpose of this set of patches is to add a new driver for stm32f429. This driver was developed and tested on evaluation board stm32429i. Stm32f4 is a MCU platform which don't have MMU so the last patches developed by Benjamin Gaignard regarding "DRM: allow to use mmuless devices" are

[PATCH v2.1 1/7] drm/atomic: Add new iterators over all state, v3.

Add for_each_(old)(new)_(plane,connector,crtc)_in_state iterators to replace the old for_each_xxx_in_state ones. This is useful for >1 flip depth and getting rid of all xxx->state dereferences. This requires extra fixups done when committing a state after duplicating, which in general isn't valid

[RESEND PATCH v14 2/2] drm/i915: Put "cooked" vlank counters in frame CRC lines

Use drm_accurate_vblank_count so we have the full 32 bit to represent the frame counter and userspace has a simpler way of knowing when the counter wraps around. Signed-off-by: Tomeu Vizoso Reviewed-by: Emil Velikov Reviewed-by: Robert Foss --- drivers/gpu/drm/i915/i915_irq.c | 6 +++--- 1

[RESEND PATCH v14 1/2] drm/i915: Use new CRC debugfs API

The core provides now an ABI to userspace for generation of frame CRCs, so implement the ->set_crc_source() callback and reuse as much code as possible with the previous ABI implementation. When handling the pageflip interrupt, we skip 1 or 2 frames depending on the HW because they contain wrong

[RESEND PATCH v14 0/2] New debugfs API for capturing CRC of frames

Hi, here are the last two patches that remain to be merged in this series, rebased on today's drm-tip. Thanks, Tomeu Tomeu Vizoso (2): drm/i915: Use new CRC debugfs API drm/i915: Put "cooked" vlank counters in frame CRC lines drivers/gpu/drm/i915/i915_drv.h | 1 +

[PATCH] drm: Fix error handling in drm_mm eviction kselftest

drivers/gpu/drm/selftests/test-drm_mm.c:1277 evict_everything() warn: calling list_del() inside list_for_each The list_del() inside the error handling in the eviction loop is overkill. We have to undo the eviction scan to return the drm_mm back to a recoverable state, so have to

[bug report] drm: kselftest for drm_mm and eviction

On Tue, Jan 10, 2017 at 05:17:46PM +0300, Dan Carpenter wrote: > Hello Chris Wilson, > > The patch 560b32842912: "drm: kselftest for drm_mm and eviction" from > Dec 22, 2016, leads to the following static checker warning: > > drivers/gpu/drm/selftests/test-drm_mm.c:1277 evict_everything()

[GIT PULL] omapdrm changes for 4.11

--- > drivers/gpu/drm/omapdrm/omap_irq.c | 242 > +++-- > drivers/gpu/drm/omapdrm/omap_plane.c | 24 -- > include/uapi/drm/Kbuild| 1 + > 17 files changed, 441 insertions(+), 481 deletions(-) > ---

DRM range manger test failures

On Tue, Jan 10, 2017 at 02:51:17PM +0100, Daniel Vetter wrote: > On Tue, Jan 10, 2017 at 12:45:04PM +, Chris Wilson wrote: > > On Tue, Jan 10, 2017 at 01:41:54PM +0100, Geert Uytterhoeven wrote: > > > Hi Chris, Laurent, > > > > > > On R-Car Gen2 (Koelsch) and Gen3 (Salvator-X), the new DRM

[PATCH] drm: exynos: Add runtime PM support to MIC driver

This patch adds pm_runtime_get/put calls to notify device core when MIC device is really in use. This is needed to let power domain with this device to be turned off when display is turned off. Signed-off-by: Marek Szyprowski --- drivers/gpu/drm/exynos/exynos_drm_mic.c | 17 - 1

[PATCH] drm: Fix broken VT switch with video=1366x768 option

On Tue, 10 Jan 2017 13:41:42 +0100, Daniel Vetter wrote: > > On Tue, Jan 10, 2017 at 12:36:50PM +0100, Takashi Iwai wrote: > > On Tue, 10 Jan 2017 12:28:36 +0100, > > Ville Syrjälä wrote: > > > > > > On Mon, Jan 09, 2017 at 03:56:14PM +0100, Takashi Iwai wrote: > > > > I noticed that the VT

DRM range manger test failures

Hi Chris, Laurent, On R-Car Gen2 (Koelsch) and Gen3 (Salvator-X), the new DRM range manager selftests fail with: drm_mm: Testing DRM range manger (struct drm_mm), with random_seed=0x83a9b910 max_iterations=8192 max_prime=128 drm_mm: igt_sanitycheck - ok! drm_mm: node has wrong color,

[PATCH] drm: Fix broken VT switch with video=1366x768 option

On Tue, Jan 10, 2017 at 12:36:50PM +0100, Takashi Iwai wrote: > On Tue, 10 Jan 2017 12:28:36 +0100, > Ville Syrjälä wrote: > > > > On Mon, Jan 09, 2017 at 03:56:14PM +0100, Takashi Iwai wrote: > > > I noticed that the VT switch doesn't work any longer with a Dell > > > laptop with 1366x768 eDP

[rfc] fix output poll execute lockdep

On Tue, Jan 10, 2017 at 09:46:26PM +1000, Dave Airlie wrote: > On 10 Jan. 2017 19:50, "Daniel Vetter" wrote: > > On Tue, Jan 10, 2017 at 12:12:30PM +1000, Dave Airlie wrote: > > On runtime resume, nouveau can try and take the mode_config > > mutex in the poll reenable, however a poll can race

[PATCH v2] drm: get fbdev size from cmdline mode if it exists

On 01/10/2017 12:39 PM, Daniel Vetter wrote: > On Tue, Jan 10, 2017 at 12:21:09PM +0100, Vincent Abriou wrote: >> In case no connector is found while creating the fbdev, gives the >> possibility to specify the default fbdev size by firstly checking if the >> command line is defining a preferred

[PATCH] drm: Fix broken VT switch with video=1366x768 option

On Mon, Jan 09, 2017 at 03:56:14PM +0100, Takashi Iwai wrote: > I noticed that the VT switch doesn't work any longer with a Dell > laptop with 1366x768 eDP when the machine is connected with a DP > monitor. It behaves as if VT were switched, but the graphics remain > frozen. Actually the

[RFC] drm: Parse HDMI 2.0 YCbCr 4:2:0 VDB and VCB

On Thu, Jan 05, 2017 at 02:46:06PM +, Jose Abreu wrote: > Hi Ville, > > > On 05-01-2017 11:46, Ville Syrjälä wrote: > > On Thu, Jan 05, 2017 at 10:07:45AM +, Jose Abreu wrote: > >> Hi Ville, > >> > >> > >> On 04-01-2017 16:36, Ville Syrjälä wrote: > >>> On Wed, Jan 04, 2017 at

[PATCH 06/10] drm/i915/psr: set CHICKEN_TRANS for psr2

On Mon, Jan 09, 2017 at 06:38:15PM +0530, vathsala nagaraju wrote: > As per bpsec, CHICKEN_TRANS_EDP bit 12 ,15 must be programmed in > psr2 enable sequence. > Program Transcoder EDP VSC DIP header with a valid setting for PSR2 > and Set CHICKEN_TRANS_EDP(0x420cc) bit 12 for programmable header >

[PATCH] drm: disable deep color when EDID violates spec

On Thu, Jan 05, 2017 at 05:45:23PM -0600, Nicholas Sielicki wrote: > As per the HDMI 1.3 and 1.4 spec, "deep color modes" are color depths > greater than 24 bits per pixel. The spec explicitly states, "All Deep > Color modes are optional though if an HDMI Source or Sink supports any > Deep Color

[Bug 99343] dEQP-GLES31.functional.shaders.builtin_functions.precision.{min, max}.highp_compute.scalar failures

vel/attachments/20170110/daebc924/attachment-0001.html>

DRM range manger test failures

On Tue, Jan 10, 2017 at 01:41:54PM +0100, Geert Uytterhoeven wrote: > Hi Chris, Laurent, > > On R-Car Gen2 (Koelsch) and Gen3 (Salvator-X), the new DRM range > manager selftests fail with: > > drm_mm: Testing DRM range manger (struct drm_mm), with > random_seed=0x83a9b910 max_iterations=8192

[PATCH v2] drm: get fbdev size from cmdline mode if it exists

On Tue, Jan 10, 2017 at 12:21:09PM +0100, Vincent Abriou wrote: > In case no connector is found while creating the fbdev, gives the > possibility to specify the default fbdev size by firstly checking if the > command line is defining a preferred mode. Else go into fallback and set > 1024x768 fbdev

[PATCH] drm: Fix broken VT switch with video=1366x768 option

On Tue, 10 Jan 2017 12:28:36 +0100, Ville Syrjälä wrote: > > On Mon, Jan 09, 2017 at 03:56:14PM +0100, Takashi Iwai wrote: > > I noticed that the VT switch doesn't work any longer with a Dell > > laptop with 1366x768 eDP when the machine is connected with a DP > > monitor. It behaves as if VT

[PATCH] drm: disable deep color when EDID violates spec

ed at all, > > - * then deep color 36 bit must be supported. > > - */ > > - if (!(hdmi[6] & DRM_EDID_HDMI_DC_36)) { > > - DRM_DEBUG("%s: HDMI sink should do DC_36, but does not!\n", > > - connector->name); > > - } > > } > > > > static void > > @@ -3895,6 +3905,7 @@ static void drm_add_display_info(struct > drm_connector *connector, > > /* driver figures it out in this case */ > > info->bpc = 0; > > info->color_formats = 0; > > + info->edid_hdmi_dc_modes = 0; > > info->cea_rev = 0; > > info->max_tmds_clock = 0; > > info->dvi_dual = false; > > -- > > 2.11.0 > > -- > Ville Syrjälä > Intel OTC > ___ > dri-devel mailing list > dri-devel at lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel > -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20170110/22794c37/attachment-0001.html>

[PATCH] drm/i915/psr: disable psr2 for resolution greater than 32X20

PSR2 is restricted to work with panel resolutions upto 3200x2000, move the check to intel_psr_match_conditions and fully block psr. Cc: Rodrigo Vivi Cc: Jim Bride Suggested-by: Rodrigo Vivi Signed-off-by: Vathsala Nagaraju --- drivers/gpu/drm/i915/intel_psr.c | 15 --- 1 file

[PATCH] drm: disable deep color when EDID violates spec

On Tue, Jan 10, 2017 at 6:33 AM, Ernst Sjöstrand wrote: > Isn't 10bpc very common among monitors, and 12bpc very rare? Or maybe I'm > confusing the transport layer with the presentation capabilities...? > Here are 201 monitors that claim 10bpc: >

[RFC] drm: Parse HDMI 2.0 YCbCr 4:2:0 VDB and VCB

Hi Ville, On 10-01-2017 11:16, Ville Syrjälä wrote: > On Thu, Jan 05, 2017 at 02:46:06PM +, Jose Abreu wrote: >> [snip] >> The pixel clock rate is half of the TMDS character rate in 4:2:0 >> (in 24 bit), but for example in deep color 48 bit it will be the >> same rate. There is also a

[PATCH v2] drm: get fbdev size from cmdline mode if it exists

In case no connector is found while creating the fbdev, gives the possibility to specify the default fbdev size by firstly checking if the command line is defining a preferred mode. Else go into fallback and set 1024x768 fbdev size as it was already done. Cc: Tomi Valkeinen Signed-off-by:

[PATCH 2/2] nouveau: wrap the output poll execution and wakeup gpu

From: Dave Airlie This wraps the output poll and fixes a problem where pm resume would try and take the mode config mutex but the output poll thread would already have taken it. I found this while looking for another bug, I've no idea yet if this fixes that problem.

[PATCH 1/2] drm: allow drivers to wrap output poll execution

From: Dave Airlie In order to avoid a lockdep between pm resume and output poll over the mode_config mutex we need to order the wakeup of the device before we take the mode config mutex (as pm resume can also try and take the mode config mutex). This introduces an API for

[rfc] fix output poll execute lockdep

On runtime resume, nouveau can try and take the mode_config mutex in the poll reenable, however a poll can race with this, and take the mutex and get stuck waiting for the runtime to finish completion. These two patches allow the driver to get hooked in before the mutex is taken. I think

[PATCH v2] drm: Schedule the output_poll_work with 1s delay if we have delayed event

On Tue, Jan 10, 2017 at 11:40:59AM +0100, Daniel Vetter wrote: > On Mon, Jan 09, 2017 at 11:50:59AM -0500, Sean Paul wrote: > > On Mon, Jan 9, 2017 at 9:31 AM, Peter Ujfalusi > > wrote: > > > Instead of scheduling the work to handle the initial delayed event, use 1s > > > delay. > > > > > > This

[PATCH v2] drm: Schedule the output_poll_work with 1s delay if we have delayed event

On Mon, Jan 09, 2017 at 11:50:59AM -0500, Sean Paul wrote: > On Mon, Jan 9, 2017 at 9:31 AM, Peter Ujfalusi > wrote: > > Instead of scheduling the work to handle the initial delayed event, use 1s > > delay. > > > > This delay should not be needed, but Optimus/nouveau will fail in a > >

[PATCH 1/4] drm: add vblank hooks to struct drm_crtc_funcs

On Mon, Jan 09, 2017 at 07:56:24PM +0800, Shawn Guo wrote: > From: Shawn Guo > > The vblank is mostly CRTC specific and implemented as part of CRTC > driver. So having vblank hooks in struct drm_crtc_funcs should > generally help to reduce code from client drivers in implementing > drm_driver's

[Intel-gfx] 4.10-rc2 oops in DRM connector code

On Mon, Jan 09, 2017 at 09:42:22AM -0800, Dave Hansen wrote: > On 01/09/2017 08:59 AM, Daniel Vetter wrote: > > On Mon, Jan 9, 2017 at 5:50 PM, Dave Hansen > > wrote: > >> On 01/09/2017 08:41 AM, Daniel Vetter wrote: > >>> On Mon, Jan 9, 2017 at 2:40 PM, Dave Hansen > >>> wrote: > Well,

[PATCH v2 7/7] drm/blend: Use new atomic iterator macros.

Signed-off-by: Maarten Lankhorst --- drivers/gpu/drm/drm_blend.c | 22 +++--- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/drivers/gpu/drm/drm_blend.c b/drivers/gpu/drm/drm_blend.c index 5c45d0852608..78cf9f6cae08 100644 --- a/drivers/gpu/drm/drm_blend.c +++

[PATCH v2 6/7] drm/atomic: Convert get_existing_state callers to get_old/new_state

Signed-off-by: Maarten Lankhorst --- drivers/gpu/drm/drm_atomic.c| 6 +++--- drivers/gpu/drm/drm_atomic_helper.c | 39 + drivers/gpu/drm/drm_blend.c | 3 +-- 3 files changed, 22 insertions(+), 26 deletions(-) diff --git

[PATCH v2 5/7] drm/atomic: Add macros to access existing old/new state

After atomic commit, these macros should be used in place of get_existing_state. Also after commit get_xx_state should no longer be used because it may not have the required locks. Signed-off-by: Maarten Lankhorst --- include/drm/drm_atomic.h | 99

[PATCH v2 4/7] drm/atomic: Fix atomic helpers to use the new iterator macros.

Signed-off-by: Maarten Lankhorst --- drivers/gpu/drm/drm_atomic_helper.c | 293 +++- 1 file changed, 152 insertions(+), 141 deletions(-) diff --git a/drivers/gpu/drm/drm_atomic_helper.c b/drivers/gpu/drm/drm_atomic_helper.c index c468194934a8..b577977322d0

[PATCH v2 3/7] drm/atomic: Use new atomic iterator macros.

Signed-off-by: Maarten Lankhorst --- drivers/gpu/drm/drm_atomic.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/drivers/gpu/drm/drm_atomic.c b/drivers/gpu/drm/drm_atomic.c index 18cdf2c956c6..7b61e0da9ace 100644 --- a/drivers/gpu/drm/drm_atomic.c +++

[PATCH v2 2/7] drm/atomic: Make add_affected_connectors look at crtc_state.

This kills another dereference of connector->state. connector_mask holds all unchanged connectors at least and any changed connectors are already in state anyway. Signed-off-by: Maarten Lankhorst --- drivers/gpu/drm/drm_atomic.c | 11 --- 1 file changed, 8 insertions(+), 3 deletions(-)

  1   2   >