[PATCH] drm: convert DT component matching to component_match_add_release()

On Thu, Oct 20, 2016 at 04:39:04PM -0400, Sean Paul wrote: > On Wed, Oct 19, 2016 at 6:28 AM, Russell King > wrote: > > Convert DT component matching to use component_match_add_release(). > > > > Signed-off-by: Russell King > > --- >

[Bug 67970] Kernel bugs related to the powersaving features of mobility radeon x1400

was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161020/648aee6a/attachment.html>

[PATCH] dma-buf: Rename struct fence to dma_fence

Hi Chris, Thanks for the patch! On 20 October 2016 at 17:38, Gustavo Padovan wrote: > 2016-10-20 Chris Wilson : > >> I plan to usurp the short name of struct fence for a core kernel struct, >> and so I need to rename the specialised fence/timeline for DMA >> operations to make room. >> >> A

[PATCH] drm: don't override possible_crtcs for primary/cursor planes

On Thu, Oct 20, 2016 at 03:06:06PM -0400, Rob Clark wrote: > It is kind of a pointless restriction. If userspace does silly things > like using crtcA's cursor plane on crtcB, and then setcursor on crtcA, > it will end up with the overlay disabled on crtcB. But userspace is > allowed to shoot

[PATCH v6 11/11] drm/i915: Add a kerneldoc summary for i915_perf.c

In particular this tries to capture for posterity some of the early challenges we had with using the core perf infrastructure in case we ever want to revisit adapting perf for device metrics. Cc: Chris Wilson Signed-off-by: Robert Bragg Reviewed-by: Matthew Auld ---

[PATCH v6 10/11] drm/i915: Add more Haswell OA metric sets

This adds 'compute', 'compute extended', 'memory reads', 'memory writes' and 'sampler balance' metric sets for Haswell. The code is auto generated from an XML description of metric sets, currently maintained in gputop, ref: https://github.com/rib/gputop > gputop-data/oa-*.xml >

[PATCH v6 09/11] drm/i915: add oa_event_min_timer_exponent sysctl

The minimal sampling period is now configurable via a dev.i915.oa_min_timer_exponent sysctl parameter. Following the precedent set by perf, the default is the minimum that won't (on its own) exceed the default kernel.perf_event_max_sample_rate default of 10 samples/s. Signed-off-by: Robert

[PATCH v6 08/11] drm/i915: Add dev.i915.perf_stream_paranoid sysctl option

Consistent with the kernel.perf_event_paranoid sysctl option that can allow non-root users to access system wide cpu metrics, this can optionally allow non-root users to access system wide OA counter metrics from Gen graphics hardware. Signed-off-by: Robert Bragg Reviewed-by: Matthew Auld ---

[PATCH v6 07/11] drm/i915: advertise available metrics via sysfs

Each metric set is given a sysfs entry like: /sys/class/drm/card0/metrics//id This allows userspace to enumerate the specific sets that are available for the current system. The 'id' file contains an unsigned integer that can be used to open the associated metric set via

[PATCH v6 06/11] drm/i915: Enable i915 perf stream for Haswell OA unit

Gen graphics hardware can be set up to periodically write snapshots of performance counters into a circular buffer via its Observation Architecture and this patch exposes that capability to userspace via the i915 perf interface. v2: Make sure to initialize ->specific_ctx_id when opening,

[PATCH v6 05/11] drm/i915: Add 'render basic' Haswell OA unit config

Adds a static OA unit, MUX + B Counter configuration for basic render metrics on Haswell. This is auto generated from an XML description of metric sets, currently maintained in gputop, ref: https://github.com/rib/gputop > gputop-data/oa-*.xml > scripts/i915-perf-kernelgen.py $ make -C

[PATCH v6 04/11] drm/i915: don't whitelist oacontrol in cmd parser

Being able to program OACONTROL from a non-privileged batch buffer is not sufficient to be able to configure the OA unit. This was originally allowed to help enable Mesa to expose OA counters via the INTEL_performance_query extension, but the current implementation based on programming OACONTROL

[PATCH v6 03/11] drm/i915: return EACCES for check_cmd() failures

check_cmd() is checking whether a command adheres to certain restrictions that ensure it's safe to execute within a privileged batch buffer. Returning false implies a privilege problem, not that the command is invalid. The distinction makes the difference between allowing the buffer to be

[PATCH v6 02/11] drm/i915: rename OACONTROL GEN7_OACONTROL

OACONTROL changes quite a bit for gen8, with some bits split out into a per-context OACTXCONTROL register. Rename now before adding more gen7 OA registers Signed-off-by: Robert Bragg Reviewed-by: Matthew Auld --- drivers/gpu/drm/i915/gvt/handlers.c| 2 +-

[PATCH v6 01/11] drm/i915: Add i915 perf infrastructure

Adds base i915 perf infrastructure for Gen performance metrics. This adds a DRM_IOCTL_I915_PERF_OPEN ioctl that takes an array of uint64 properties to configure a stream of metrics and returns a new fd usable with standard VFS system calls including read() to read typed and sized records; ioctl()

[PATCH v5 4/4] drm/fence: add out-fences support

On Thu, Oct 20, 2016 at 07:34:44PM +0300, Ville Syrjälä wrote: > On Thu, Oct 20, 2016 at 01:55:38PM -0200, Gustavo Padovan wrote: > > 2016-10-20 Ville Syrjälä : > > > > > On Thu, Oct 20, 2016 at 12:50:05PM -0200, Gustavo Padovan wrote: > > > > From: Gustavo Padovan > > > > > > > > Support

[Bug 92248] [KBL/SKL/BYT/BXT] igt/kms_plane_scaling fail

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

[Intel-gfx] linux-next: Tree for Oct 20 (gpu/drm/i915)

On Thu, 20 Oct 2016, Daniel Vetter wrote: > On Thu, Oct 20, 2016 at 7:37 PM, Randy Dunlap > wrote: >> On 10/19/16 20:20, Stephen Rothwell wrote: >>> Hi all, >>> >>> Changes since 20161019: >>> >> >> on i386: when CONFIG_ACPI is not enabled: > > Adding Zhenyu. Might be good to have a fix just

[PATCH 2/3] ARM: bus: da8xx-syscfg: new driver

Hi Kevin, On Thursday 20 Oct 2016 09:57:51 Kevin Hilman wrote: > Laurent Pinchart writes: > > On Wednesday 19 Oct 2016 10:26:57 Bartosz Golaszewski wrote: > >> 2016-10-18 22:49 GMT+02:00 Laurent Pinchart: > >>> On Monday 17 Oct 2016 18:30:49 Bartosz Golaszewski wrote: > Create the driver

[Bug 98361] [BDW /BXT/SKL/SNB] [Regression] drv_hangman subtests parser fail

tps://lists.freedesktop.org/archives/dri-devel/attachments/20161020/949daacf/attachment.html>

[Bug 98361] [BDW /BXT/SKL] [Regression] drv_hangman subtests parser fail

ing 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/20161020/bb2bd4ad/attachment.html>

[Bug 98146] DRI_PRIME=1 and fullscreen issues

. -- 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/20161020/8ce4cf8a/attachment.html>

[Bug 141741] drm:radeon_get_bios [radeon]] *ERROR* Unable to locate a BIOS ROM

https://bugzilla.kernel.org/show_bug.cgi?id=141741 --- Comment #19 from Lukas P --- I did a bisect and it reported the following commit as the first bad one: 30b5b8808c12bcd947dd474980482561b69c1bcb diff --git a/drivers/pci/Kconfig b/drivers/pci/Kconfig index a1f37db..209292e 100644 ---

[Bug 98361] [BDW /BXT/SKL] [Regression] drv_hangman subtests parser fail

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

[PATCH] drm: Complete CEA modedb(VIC 1-107)

Regards Shashank On 10/20/2016 8:00 PM, Alex Deucher wrote: > On Thu, Oct 20, 2016 at 6:28 AM, Shashank Sharma > wrote: >> CEA-861-F specs defines new 4k video modes to be used with >> HDMI 2.0 EDIDs. These modes start at VIC=93 and go all the >> way till VIC=107. >> >> Our existing CEA modedb

[PATCH] drm: Complete CEA modedb(VIC 1-107)

Hello Jose On 10/20/2016 7:19 PM, Jose Abreu wrote: > Hi Shashank, > > > On 20-10-2016 11:25, Sharma, Shashank wrote: >> Adding Jose and Daniel in cc. >> >> Regards >> Shashank >> -Original Message- >> From: Sharma, Shashank >> Sent: Thursday, October 20, 2016 3:58 PM >> To: dri-devel at

[Bug 98146] DRI_PRIME=1 and fullscreen issues

er the web to see if someone had similar issues. Seems like people don't have many problems with switching to DRI3. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.

[Intel-gfx] linux-next: Tree for Oct 20 (gpu/drm/i915)

On Thu, Oct 20, 2016 at 7:37 PM, Randy Dunlap wrote: > On 10/19/16 20:20, Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20161019: >> > > on i386: when CONFIG_ACPI is not enabled: Adding Zhenyu. Might be good to have a fix just for this that I directly pick up, since I want to tag the

[PATCH v5 4/4] drm/fence: add out-fences support

On Thu, Oct 20, 2016 at 01:55:38PM -0200, Gustavo Padovan wrote: > 2016-10-20 Ville Syrjälä : > > > On Thu, Oct 20, 2016 at 12:50:05PM -0200, Gustavo Padovan wrote: > > > From: Gustavo Padovan > > > > > > Support DRM out-fences by creating a sync_file with a fence for each CRTC > > > that

[PATCH] drm: convert DT component matching to component_match_add_release()

On Thu, Oct 20, 2016 at 5:50 PM, Russell King - ARM Linux wrote: > On Thu, Oct 20, 2016 at 04:39:04PM -0400, Sean Paul wrote: >> On Wed, Oct 19, 2016 at 6:28 AM, Russell King >> wrote: >> > Convert DT component matching to use component_match_add_release(). >> > >>

[PATCH v5 4/4] drm/fence: add out-fences support

Hi Gustavo, I notice your branch has the sync_file refcount change in, but this doesn't seem to take account for that. Will you be dropping that change to match the semantics of fence_array? Couple more comments below. On Thu, Oct 20, 2016 at 12:50:05PM -0200, Gustavo Padovan wrote: >From:

[PATCH v5 4/4] drm/fence: add out-fences support

On Thu, Oct 20, 2016 at 12:50:05PM -0200, Gustavo Padovan wrote: > From: Gustavo Padovan > > Support DRM out-fences by creating a sync_file with a fence for each CRTC > that sets the OUT_FENCE_PTR property. I still maintain the out fence should also be per fb (well, per plane since we can't add

[PATCH v5 4/4] drm/fence: add out-fences support

Hi Brian, 2016-10-20 Brian Starkey : > Hi Gustavo, > > I notice your branch has the sync_file refcount change in, but this > doesn't seem to take account for that. Will you be dropping that > change to match the semantics of fence_array? I will drop the fence_get() in the out-fence patch

[PATCH v5 3/4] drm/fence: add fence timeline to drm_crtc

Hi Gustavo, On Thu, Oct 20, 2016 at 12:50:04PM -0200, Gustavo Padovan wrote: >From: Gustavo Padovan > >Create one timeline context for each CRTC to be able to handle out-fences >and signal them. It adds a few members to struct drm_crtc: fence_context, >where we store the context we get from

[Intel-gfx] [PATCH] drm/i915: Add i915 perf infrastructure

On ke, 2016-10-19 at 17:35 +0100, Robert Bragg wrote: > I'll add a default: with MISSING_CASE as that looks like an i915- > specific convention; though it seems like a real shame to defer > missing case issues to runtime errors instead of taking advantage of > the compiler complaining at build

[PATCH v5 3/4] drm/fence: add fence timeline to drm_crtc

2016-10-20 Brian Starkey : > Hi Gustavo, > > On Thu, Oct 20, 2016 at 12:50:04PM -0200, Gustavo Padovan wrote: > > From: Gustavo Padovan > > > > Create one timeline context for each CRTC to be able to handle out-fences > > and signal them. It adds a few members to struct drm_crtc:

[PATCH v2 8/8] ARM: dts: sun6i: hummingbird-a31: Enable display output through VGA bridge

tion/pgp-signature Size: 801 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161020/ea5a402d/attachment.sig>

[PATCH v2 6/8] ARM: dts: sun6i: Add device nodes for first display pipeline

bedded Linux and Kernel engineering http://free-electrons.com -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20

[PATCH v2 7/8] ARM: dts: sun6i: Add A31 LCD0 RGB888 pins

x and Kernel engineering http://free-electrons.com -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161020/f9b10d38/attachment.sig>

[PATCH v2 5/8] drm/sun4i: Add compatible strings for A31/A31s display pipelines

tion/pgp-signature Size: 801 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161020/704f2edd/attachment.sig>

[PATCH v2 4/8] drm/sun4i: Add compatible string for A31/A31s TCON (timing controller)

s.com -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161020/ed0e53ae/attachment-0001.sig>

[PATCH v2 3/8] drm/sun4i: tcon: Move SoC specific quirks to a DT matched data structure

signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161020/b7c51e84/attachment.sig>

[PATCH v2 2/8] drm/sun4i: sun6i-drc: Support DRC on A31 and A31s

not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161020/3f1833e8/attachment.sig>

[PATCH] drm/fb-helper: Don't call dirty callback for untouched clips

On Thu, Oct 20, 2016 at 04:39:52PM +0200, Takashi Iwai wrote: > Since 4.7 kernel, we've seen the error messages like > > kernel: [TTM] Buffer eviction failed > kernel: qxl :00:02.0: object_init failed for (4026540032, 0x0001) > kernel: [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed

[PATCH 4/8] drm: Add encoder_type field to the drm_bridge structure

Hi, On 10/19/2016 07:55 PM, Laurent Pinchart wrote: > The drm_bridge object models on- or off-chip hardware encoders and > provide an abstract control API to display drivers. In order to help > display drivers creating the right kind of drm_encoder object, expose > the type of the hardware

[PATCH] drm/fb-helper: Fix race between deferred_io worker and dirty updater

On Thu, Oct 20, 2016 at 03:36:54PM +0200, Takashi Iwai wrote: > On Thu, 20 Oct 2016 15:28:14 +0200, > Ville Syrjälä wrote: > > > > On Thu, Oct 20, 2016 at 03:20:55PM +0200, Takashi Iwai wrote: > > > Since 4.7 kernel, we've seen the error messages like > > > > > > kernel: [TTM] Buffer eviction

[Bug 93826] 2560x1440 @144Hz graphic glitches and bad refresh rate

URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161020/1de612e1/attachment.html>

[Intel-gfx] i915 monitor hotplug on 4.1/4.4 PREEMPT

Hi, On Thu, Oct 20, 2016 at 3:57 PM, David Weinehall wrote: >> > I get an udev event for unplugging, but there's no event generated for >> > plugging the monitor back in. >> >> Does it work on non-RT? Does it work on v4.8 or v4.9-rc1? > > The second one is relevant though. 4.1 is pre-historic,

[Intel-gfx] i915 monitor hotplug on 4.1/4.4 PREEMPT

On Thu, 20 Oct 2016, David Weinehall wrote: > On Thu, Oct 20, 2016 at 03:28:10PM +0300, Jani Nikula wrote: >> On Thu, 20 Oct 2016, Nicolae Rosia wrote: >> > Monitor hotplugging seems to be broken on latest 4.1/4.4 RT kernel with >> > i915. >> > I have tested this on non-RT kernel and it works.

[PATCH v2] drm/fb-helper: Don't call dirty callback for untouched clips

Since 4.7 kernel, we've seen the error messages like kernel: [TTM] Buffer eviction failed kernel: qxl :00:02.0: object_init failed for (4026540032, 0x0001) kernel: [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO on QXL when switching and accessing on VT. The

[PATCH] drm/fb-helper: Don't call dirty callback for untouched clips

On Thu, 20 Oct 2016 16:56:04 +0200, Ville Syrjälä wrote: > > On Thu, Oct 20, 2016 at 04:39:52PM +0200, Takashi Iwai wrote: > > Since 4.7 kernel, we've seen the error messages like > > > > kernel: [TTM] Buffer eviction failed > > kernel: qxl :00:02.0: object_init failed for (4026540032,

[PATCH 2/4] drm/i2c: tda998x: Remove obsolete drm_connector_register() call

On 10/20/2016 02:45 PM, Russell King - ARM Linux wrote: > On Thu, Oct 20, 2016 at 02:38:25PM +0530, Archit Taneja wrote: >> >> >> On 10/20/2016 01:50 PM, Laurent Pinchart wrote: >>> Hi Russell, >>> >>> On Wednesday 19 Oct 2016 10:35:21 Russell King - ARM Linux wrote: On Wed, Oct 19, 2016 at

[PATCH 10/10] drm/imx: ipuv3-plane: use drm_plane_helper_check_state, clipped coordinates

On Thu, Oct 20, 2016 at 4:41 PM, Ville Syrjälä wrote: > On Thu, Oct 20, 2016 at 03:53:46PM +0800, Ying Liu wrote: >> On Wed, Oct 19, 2016 at 6:21 PM, Philipp Zabel >> wrote: >> > Use drm_plane_helper_check_state to clip raw user coordinates to crtc >> > bounds. This checks for full plane

[PATCH]"drm: change DRM_MIPI_DSI module type from "bool" to "tristate".

On Thu, 20 Oct 2016, Andrzej Hajda wrote: > Hi Jani, > > Forgive me late response. > > On 12.10.2016 16:28, Jani Nikula wrote: >> On Wed, 12 Oct 2016, Emil Velikov wrote: >>> On 11 October 2016 at 10:33, Jani Nikula >>> wrote: On Tue, 11 Oct 2016, "Sun, Jing A" wrote: > It's needed

[PATCH] drm/fb-helper: Don't call dirty callback for untouched clips

Since 4.7 kernel, we've seen the error messages like kernel: [TTM] Buffer eviction failed kernel: qxl :00:02.0: object_init failed for (4026540032, 0x0001) kernel: [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO on QXL when switching and accessing on VT. The

[PATCH] drm: convert DT component matching to component_match_add_release()

On Wed, Oct 19, 2016 at 6:28 AM, Russell King wrote: > Convert DT component matching to use component_match_add_release(). > > Signed-off-by: Russell King > --- > Can we please get this patch from May merged into the drm-misc or >

[PATCH] drm/fb-helper: Fix race between deferred_io worker and dirty updater

On Thu, 20 Oct 2016 16:17:25 +0200, Ville Syrjälä wrote: > > On Thu, Oct 20, 2016 at 03:36:54PM +0200, Takashi Iwai wrote: > > On Thu, 20 Oct 2016 15:28:14 +0200, > > Ville Syrjälä wrote: > > > > > > On Thu, Oct 20, 2016 at 03:20:55PM +0200, Takashi Iwai wrote: > > > > Since 4.7 kernel,

[PATCH] drm/fb-helper: Fix race between deferred_io worker and dirty updater

On Thu, Oct 20, 2016 at 03:36:54PM +0200, Takashi Iwai wrote: > On Thu, 20 Oct 2016 15:28:14 +0200, > Ville Syrjälä wrote: > > > > On Thu, Oct 20, 2016 at 03:20:55PM +0200, Takashi Iwai wrote: > > > Since 4.7 kernel, we've seen the error messages like > > > > > > kernel: [TTM] Buffer eviction

[PATCH] drm/fb-helper: Fix race between deferred_io worker and dirty updater

On Thu, Oct 20, 2016 at 03:20:55PM +0200, Takashi Iwai wrote: > Since 4.7 kernel, we've seen the error messages like > > kernel: [TTM] Buffer eviction failed > kernel: qxl :00:02.0: object_init failed for (4026540032, 0x0001) > kernel: [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed

[PATCH 10/10] drm/imx: ipuv3-plane: use drm_plane_helper_check_state, clipped coordinates

On Thu, Oct 20, 2016 at 04:51:30PM +0800, Ying Liu wrote: > On Thu, Oct 20, 2016 at 4:41 PM, Ville Syrjälä > wrote: > > On Thu, Oct 20, 2016 at 03:53:46PM +0800, Ying Liu wrote: > >> On Wed, Oct 19, 2016 at 6:21 PM, Philipp Zabel > >> wrote: > >> > Use drm_plane_helper_check_state to clip raw

[RFC] drm: add hint to userspace about whether a plane can scale

When you have a mix of planes that can scale and those that cannot scale, userspace really wants to have some hint to know which planes can definitely not scale so it knows to assign them to unscaled layers. I don't think it is fully possible to describe scaling constraints in a generic way, so I

[PATCH v3] drm/imx: ipuv3-plane: use drm_plane_helper_check_state, clipped coordinates

Use drm_plane_helper_check_state to clip raw user coordinates to crtc bounds. This checks for full plane coverage and scaling already, so we can drop some custom checks. Use the clipped coordinates everywhere. Suggested-by: Ville Syrjälä Signed-off-by: Philipp Zabel --- Changes since v2: -

Rename "struct fence" to "struct dma_fence"

On Thu, Oct 20, 2016 at 8:47 AM, Chris Wilson wrote: > I plan to usurp the short name of struct fence for a core kernel struct, > and so I need to rename the specialised fence/timeline for DMA > operations to make room. > > A consensus was reached in >

[PATCH] drm: don't override possible_crtcs for primary/cursor planes

On Thu, Oct 20, 2016 at 3:19 PM, Ville Syrjälä wrote: > On Thu, Oct 20, 2016 at 03:06:06PM -0400, Rob Clark wrote: >> It is kind of a pointless restriction. If userspace does silly things >> like using crtcA's cursor plane on crtcB, and then setcursor on crtcA, >> it will end up with the

[bug report] drm/i915/gvt: vGPU graphics memory virtualization

Hello Zhi Wang, The patch 2707e4446688: "drm/i915/gvt: vGPU graphics memory virtualization" from Mar 28, 2016, leads to the following static checker warnings: drivers/gpu/drm/i915/gvt/gtt.c:1675 intel_vgpu_pin_mm() warn: 'mm->pincount.counter' not decremented on lines: 1670,1675.

[PATCH 2/2] ARM: dts: da850: add a node for the LCD controller

On Thursday 20 October 2016 03:51 PM, Tomi Valkeinen wrote: > On 20/10/16 13:07, Sekhar Nori wrote: > >> Per me, compatible property is an ordered list precisely for the reason >> that things should continue to "work" with as closely matched driver as >> possible. So even if someone is running a

[PATCH] drm: Complete CEA modedb(VIC 1-107)

CEA-861-F specs defines new 4k video modes to be used with HDMI 2.0 EDIDs. These modes start at VIC=93 and go all the way till VIC=107. Our existing CEA modedb contains only 64 modes (VIC=1 to VIC=64). Now to be able to parse 4k modes using the existing techniques, we have to complete the modedb

[PATCH 2/5] dma-buf/fence: make timeout handling in fence_default_wait consistent

On Thu, Oct 20, 2016 at 9:20 AM, Christian König wrote: > From: Christian König > > Kernel functions taking a timeout usually return 1 on success even > when they get a zero timeout. > > Signen-off-by: Christian König > Reviewed-by: Chunming Zhou Adding Sumit. This series is: Reviewed-by:

Rename "struct fence" to "struct dma_fence"

On Thu, Oct 20, 2016 at 10:39:47AM -0400, Sean Paul wrote: > On Thu, Oct 20, 2016 at 2:47 AM, Chris Wilson > wrote: > > I plan to usurp the short name of struct fence for a core kernel struct, > > and so I need to rename the specialised fence/timeline for DMA > > operations to make room. > > > >

[PATCH 10/10] drm/imx: ipuv3-plane: use drm_plane_helper_check_state, clipped coordinates

On Wed, Oct 19, 2016 at 6:21 PM, Philipp Zabel wrote: > Use drm_plane_helper_check_state to clip raw user coordinates to crtc > bounds. This checks for full plane coverage and scaling already, so > we can drop some custom checks. Use the clipped coordinates everywhere. > > Suggested-by: Ville

the dp helper would try to enable the i2c channel for rockchip-edp

On 10/20/2016 03:18 PM, Tomeu Vizoso wrote: > On 19 October 2016 at 15:52, Randy Li wrote: >> Hello, >> >> Recently, I want to use a eDP panel in my RK3288 platform, but I got the >> following message: >> >> [8.935918] i2c i2c-6: of_i2c: modalias failure on /dp at ff97/ports >> [

[PATCH 2/2] ARM: dts: da850: add a node for the LCD controller

On Monday 17 October 2016 07:31 PM, Bartosz Golaszewski wrote: > 2016-10-17 14:29 GMT+02:00 Tomi Valkeinen : >> On 17/10/16 14:40, Laurent Pinchart wrote: >>> Hello, >>> >>> On Monday 17 Oct 2016 10:33:58 Tomi Valkeinen wrote: On 17/10/16 10:12, Sekhar Nori wrote: > On Monday 17 October

[PATCH] drm/fb-helper: Fix race between deferred_io worker and dirty updater

On Thu, 20 Oct 2016 15:28:14 +0200, Ville Syrjälä wrote: > > On Thu, Oct 20, 2016 at 03:20:55PM +0200, Takashi Iwai wrote: > > Since 4.7 kernel, we've seen the error messages like > > > > kernel: [TTM] Buffer eviction failed > > kernel: qxl :00:02.0: object_init failed for (4026540032,

[PATCH v3 3/3] MAINTAINERS: add an entry for ZTE ZX DRM driver

Add myself as the maintainer of ZTE ZX DRM driver. Signed-off-by: Shawn Guo --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 1cd38a7e0064..907dbd3261c5 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -4281,6 +4281,13 @@ S: Maintained

[PATCH v3 2/3] drm: zte: add initial vou drm driver

It adds the initial ZTE VOU display controller DRM driver. There are still some features to be added, like overlay plane, scaling, and more output devices support. But it's already useful with dual CRTCs and HDMI monitor working. Signed-off-by: Shawn Guo --- drivers/gpu/drm/Kconfig |

[PATCH v3 1/3] dt-bindings: add bindings doc for ZTE VOU display controller

It adds initial bindings doc for ZTE VOU display controller. HDMI is the only supported output device right now. Signed-off-by: Shawn Guo Acked-by: Rob Herring --- .../devicetree/bindings/display/zte,vou.txt| 84 ++ 1 file changed, 84 insertions(+) create mode

[PATCH v3 0/3] Add initial ZTE VOU DRM/KMS driver

The series adds the initial ZTE VOU display controller DRM/KMS driver. There are still some features to be added, like overlay plane, scaling, and more output devices support. But it's already useful with dual CRTCs and HDMI display working. Changes for v3: - Rebase to v4.9-rc1 - Update

[PATCH 10/10] drm/imx: ipuv3-plane: use drm_plane_helper_check_state, clipped coordinates

Am Donnerstag, den 20.10.2016, 16:51 +0800 schrieb Ying Liu: > >> Does the clip thing potentially change the user's request by force? > >> For example, the user request an unreasonable big resolution. > > > > The user is allowed to ask for destination coordinates extending outside > > the crtc

i915 monitor hotplug on 4.1/4.4 PREEMPT

On Thu, 20 Oct 2016, Nicolae Rosia wrote: > Monitor hotplugging seems to be broken on latest 4.1/4.4 RT kernel with i915. > I have tested this on non-RT kernel and it works. > I get an udev event for unplugging, but there's no event generated for > plugging the monitor back in. Does it work on

[PATCH 1/5] Revert "drm/amd/dal: Fix underlay pipe and pipe count for Stoney"

Ups my fault. I actually didn't want to send this patch out. Please ignore. Christian. Am 20.10.2016 um 15:20 schrieb Christian König: > From: Harry Wentland > > This reverts commit 4a183f66e543f697271f2ef717fb72aed071e968. > > Change-Id: I331ab0afccf55bd4e50890c64f354249993fb20a > Acked-by:

[PATCH] drm/fb-helper: Fix race between deferred_io worker and dirty updater

On Thu, 20 Oct 2016 15:20:55 +0200, Takashi Iwai wrote: > > Since 4.7 kernel, we've seen the error messages like > > kernel: [TTM] Buffer eviction failed > kernel: qxl :00:02.0: object_init failed for (4026540032, 0x0001) > kernel: [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to

[PATCH 4/4] MAINTAINERS: add drm and drm/i915 irc channels

Signed-off-by: Jani Nikula --- MAINTAINERS | 2 ++ 1 file changed, 2 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 53df9ccc5573..a6bde481170c 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -3954,6 +3954,7 @@ M:David Airlie L: dri-devel at lists.freedesktop.org T:

[PATCH 3/4] MAINTAINERS: Add "C:" for URI for chat where developers hang out

Make it easier to find the developer chat for the subsystem or driver. Signed-off-by: Jani Nikula --- MAINTAINERS | 2 ++ 1 file changed, 2 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 689f7f08a100..53df9ccc5573 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -76,6 +76,8 @@

[PATCH 2/4] MAINTAINERS: add drm and drm/i915 bug filing info

Signed-off-by: Jani Nikula --- MAINTAINERS | 2 ++ 1 file changed, 2 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 4a47ec00a09d..689f7f08a100 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -3951,6 +3951,7 @@ DRM DRIVERS M: David Airlie L: dri-devel at

[PATCH 1/4] MAINTAINERS: Add "B:" for URI where to file bugs

Different subsystems and drivers have different preferences for where to file bugs and what information to include. Add "B:" entry for specifying the URI for the bug tracker directly, a web page for detailed info on filing bugs, or a mailto: URI. Cc: Daniel Vetter Cc: Joe Perches Cc: Andrew

[PATCH] drm: don't override possible_crtcs for primary/cursor planes

On Thu, Oct 20, 2016 at 3:06 PM, Rob Clark wrote: > It is kind of a pointless restriction. If userspace does silly things > like using crtcA's cursor plane on crtcB, and then setcursor on crtcA, > it will end up with the overlay disabled on crtcB. But userspace is > allowed to shoot itself like

[PATCH]"drm: change DRM_MIPI_DSI module type from "bool" to "tristate".

Hi Jani, Forgive me late response. On 12.10.2016 16:28, Jani Nikula wrote: > On Wed, 12 Oct 2016, Emil Velikov wrote: >> On 11 October 2016 at 10:33, Jani Nikula >> wrote: >>> On Tue, 11 Oct 2016, "Sun, Jing A" wrote: It's needed that DRM Driver module could be removed and reloaded

[PATCH] drm/fb-helper: Fix race between deferred_io worker and dirty updater

Since 4.7 kernel, we've seen the error messages like kernel: [TTM] Buffer eviction failed kernel: qxl :00:02.0: object_init failed for (4026540032, 0x0001) kernel: [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO on QXL when switching and accessing on VT. The

[PATCH 5/5] reservation: revert "wait only with non-zero timeout specified (v3)" v2

From: Christian König This reverts commit fb8b7d2b9d80e1e71f379e57355936bd2b024be9. Otherwise signaling might never be activated on the fences. This can result in infinite waiting with hardware which has unreliable interrupts. v2: still return one when the timeout is

[PATCH 4/5] drm/ttm: fix ttm_bo_wait

From: Christian König reservation_object_wait_timeout_rcu() should enable signaling even with a zero timeout, but ttm_bo_wait() can also be called from atomic context and then it is not a good idea to do this. Signed-off-by: Christian König ---

[PATCH 3/5] dma-buf/fence: revert "don't wait when specified timeout is zero"

From: Christian König This reverts commit 847b19a39e4c9b5e74c40f0842c48b41664cb43c. When we don't call the wait function software signaling might never be activated. This can cause infinite polling loops with unreliable interrupt driven hardware. Signed-off-by:

[PATCH 2/5] dma-buf/fence: make timeout handling in fence_default_wait consistent

From: Christian König Kernel functions taking a timeout usually return 1 on success even when they get a zero timeout. Signen-off-by: Christian König Reviewed-by: Chunming Zhou --- drivers/dma-buf/fence.c | 8 +--- 1 file changed, 5 insertions(+), 3

[PATCH 1/5] Revert "drm/amd/dal: Fix underlay pipe and pipe count for Stoney"

From: Harry Wentland This reverts commit 4a183f66e543f697271f2ef717fb72aed071e968. Change-Id: I331ab0afccf55bd4e50890c64f354249993fb20a Acked-by: Alex Deucher Reviewed-by: Andrey Grodzovsky --- drivers/gpu/drm/amd/dal/dc/dce110/dce110_resource.c | 3 +-- 1 file

i915 monitor hotplug on 4.1/4.4 PREEMPT

Hello, Monitor hotplugging seems to be broken on latest 4.1/4.4 RT kernel with i915. I have tested this on non-RT kernel and it works. I get an udev event for unplugging, but there's no event generated for plugging the monitor back in. Any pointers are appreciated. Best regards, Nicolae

[PATCH] drm: don't override possible_crtcs for primary/cursor planes

It is kind of a pointless restriction. If userspace does silly things like using crtcA's cursor plane on crtcB, and then setcursor on crtcA, it will end up with the overlay disabled on crtcB. But userspace is allowed to shoot itself like this. Signed-off-by: Rob Clark --- Note that cursor and

[PATCH v2 1/8] drm/bridge: rgb-to-vga: Support an enable GPIO

vailable URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161020/5175074f/attachment.sig>

[Intel-gfx] i915 monitor hotplug on 4.1/4.4 PREEMPT

On Thu, Oct 20, 2016 at 03:28:10PM +0300, Jani Nikula wrote: > On Thu, 20 Oct 2016, Nicolae Rosia wrote: > > Monitor hotplugging seems to be broken on latest 4.1/4.4 RT kernel with > > i915. > > I have tested this on non-RT kernel and it works. The answer to your first question seems to be here

[PATCH v2] drm/bridge: adv7511: Remove unused code blocks

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/20161020/16049e45/attachment.html>

[PATCH] drm: Complete CEA modedb(VIC 1-107)

Hi Shashank, On 20-10-2016 11:25, Sharma, Shashank wrote: > Adding Jose and Daniel in cc. > > Regards > Shashank > -Original Message- > From: Sharma, Shashank > Sent: Thursday, October 20, 2016 3:58 PM > To: dri-devel at lists.freedesktop.org; intel-gfx at lists.freedesktop.org > Cc:

[bug report] drm/i915/gvt: vGPU command scanner

Hello Zhi Wang, The patch be1da7070aea: "drm/i915/gvt: vGPU command scanner" from May 3, 2016, leads to the following static checker warning: drivers/gpu/drm/i915/gvt/cmd_parser.c:1420 cmd_handler_mi_op_2f() warn: shift has higher precedence than mask

  1   2   >