[PATCH v2] drm: rcar-du: Arm the page flip event after queuing the page flip

The page flip event is armed in the atomic begin handler, creating a race condition with the frame end interrupt that could send the event before the atomic operation actually completes. To avoid that, arm the event in the atomic flush handler after queuing the page flip. This change doesn't fully

[PATCH] drm: rcar-du: Remove wait field from rcar_du_device structure

The field is a left-over from the switch to the atomic commit helper. It's unused, remove it. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/rcar-du/rcar_du_drv.c | 2 -- drivers/gpu/drm/rcar-du/rcar_du_drv.h | 5 - 2 files changed, 7 deletions(-) diff --git a/drivers/gpu/drm/rcar-du/r

Re: [PATCH v2 1/3] v4l: vsp1: extend VSP1 module API to allow DRM callbacks

Hi Kieran, Thank you for the patch. On Saturday 04 Mar 2017 02:01:17 Kieran Bingham wrote: > To be able to perform page flips in DRM without flicker we need to be > able to notify the rcar-du module when the VSP has completed its > processing. > > We must not have bidirectional dependencies on t

Re: [PATCH v2 2/3] v4l: vsp1: Postpone page flip in event of display list race

Hi Kieran, Thank you for the patch. On Saturday 04 Mar 2017 02:01:18 Kieran Bingham wrote: > If we try to commit the display list while an update is pending, we have > missed our opportunity. The display list manager will hold the commit > until the next interrupt. > > In this event, we inform t

Re: [PATCH v2 3/3] drm: rcar-du: Register a completion callback with VSP1

Hi Kieran, On Saturday 04 Mar 2017 15:07:09 Laurent Pinchart wrote: > On Saturday 04 Mar 2017 02:01:19 Kieran Bingham wrote: > > Currently we process page flip events on every display interrupt, > > however this does not take into consideration the processing time needed > > by the VSP1 utilised i

[Bug 99195] Random GPU lockup on Fedora 25 Wayland & X sessions with Mobility Radeon HD 5650/5750 Opensource drivers

https://bugs.freedesktop.org/show_bug.cgi?id=99195 --- Comment #7 from Tim --- @Michel Dänzer, can you tell in details what i should do to send you details report about this bug? I do everything, just tell. I so disappointed, i silently waited and though this bugs will be fixed very soon. And i f

[Bug 99484] Crusader Kings 2 - Loading bars, siege bars, morale bars, etc. do not render correctly

https://bugs.freedesktop.org/show_bug.cgi?id=99484 --- Comment #9 from Samuel Pitoiset --- A possible fix here https://reviews.llvm.org/D30609. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-dev

Re: docutils borkage (was: [PATCH 2/6] docs-rst: automatically convert Graphviz and SVG images)

On Thu, 2 Mar 2017 16:09:21 -0300 Mauro Carvalho Chehab wrote: > IMHO, the way Python and python libraries break compatibility is crazy. > > Good packaging sense says that, if APIs can break on every single new > release (with seems to be the case of docutils), then a package > depending on such

[Bug 100058] amdgpu/dpm: NULL pointer dereference

https://bugs.freedesktop.org/show_bug.cgi?id=100058 Edward O'Callaghan changed: What|Removed |Added Summary|NULL pointer dereference|amdgpu/dpm: NULL pointer

[PATCH] drm: rcar-du: Arm the page flip event after queuing the page flip.

The page flip event is armed in the atomic begin handler, creating a race condition with the frame end interrupt that could send the event before the atomic operation actually completes. To avoid that, arm the event in the atomic flush handler after queuing the page flip. This change doesn't fully

[Bug 100058] NULL pointer dereference when blacklisting radeon

https://bugs.freedesktop.org/show_bug.cgi?id=100058 Edward O'Callaghan changed: What|Removed |Added Component|General |DRM/AMDgpu Hardware|Othe

[Bug 100058] NULL pointer dereference when blacklisting radeon

https://bugs.freedesktop.org/show_bug.cgi?id=100058 --- Comment #2 from Edward O'Callaghan --- OK so we narrowed the problem down to dpm. (12:17:01 AM) mulander: yep, blacklisted radeon, amdgpu.dpm=0 and booted to X properly without a crash -- You are receiving this mail because: You are the a

[Bug 100058] NULL pointer dereference when blacklisting radeon

https://bugs.freedesktop.org/show_bug.cgi?id=100058 --- Comment #1 from Adam Wolk --- I just tried on a newer kernel from Archlinux [testing]. [mulander@napalm ~]$ uname -a Linux napalm 4.10.1-1-ARCH #1 SMP PREEMPT Sun Feb 26 21:08:53 UTC 2017 x86_64 GNU/Linux Same problem. Here is a photo I man

Re: [PATCH v2 3/3] drm: rcar-du: Register a completion callback with VSP1

Hi Kieran, Thank you for the patch. On Saturday 04 Mar 2017 02:01:19 Kieran Bingham wrote: > Currently we process page flip events on every display interrupt, > however this does not take into consideration the processing time needed > by the VSP1 utilised in the pipeline. > > Register a callbac

[Bug 100058] NULL pointer dereference when blacklisting radeon

https://bugs.freedesktop.org/show_bug.cgi?id=100058 Bug ID: 100058 Summary: NULL pointer dereference when blacklisting radeon Product: DRI Version: XOrg git Hardware: Other OS: Linux (All) Status: NEW Seve

Re: [PATCH 1/5] PCI: Recognize Thunderbolt devices

On Fri, Feb 24, 2017 at 04:17:24PM -0600, Bjorn Helgaas wrote: > On Fri, Feb 24, 2017 at 08:19:45PM +0100, Lukas Wunner wrote: > > Detect on probe whether a PCI device is part of a Thunderbolt controller. [...] > > * If an external Thunderbolt GPU is connected to a dual GPU laptop (Mac > > or not

Re: [PATCH 3/5] drm/nouveau: Don't register Thunderbolt eGPU with vga_switcheroo

On Fri, Feb 24, 2017 at 02:59:44PM -0600, Bjorn Helgaas wrote: > On Fri, Feb 24, 2017 at 1:19 PM, Lukas Wunner wrote: > > An external Thunderbolt GPU can neither drive the laptop's panel nor be > > powered off by the platform, so there's no point in registering it with > > vga_switcheroo. > > > I