[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Check HAS_PCH_NOP when install or reset dispaly IRQ

2016-12-11 Thread Patchwork
== Series Details == Series: drm/i915: Check HAS_PCH_NOP when install or reset dispaly IRQ URL : https://patchwork.freedesktop.org/series/16678/ State : failure == Summary == Series 16678v1 drm/i915: Check HAS_PCH_NOP when install or reset dispaly IRQ

Re: [Intel-gfx] [PATCH] drm/i915/perf: More documentation hooked to i915.rst

2016-12-11 Thread Daniel Vetter
On Fri, Dec 09, 2016 at 12:41:08PM +, Robert Bragg wrote: > On Thu, Dec 8, 2016 at 3:53 PM, Daniel Vetter wrote: > > On Wed, Dec 07, 2016 at 09:40:33PM +, Robert Bragg wrote: > >> This adds a 'Perf' section to i915.rst with the following sub sections: > >> - Overview > >>

[Intel-gfx] [PATCH v3] drm/i915: Check HAS_PCH_NOP when install or reset dispaly IRQ

2016-12-11 Thread Wang Elaine
From: Elaine Wang Some platforms don't have display. To avoid accessing the non-existent registers, check HAS_PCH_NOP before invoking display IRQ install or reset function. Cc: Chris Wilson Cc: Joonas Lahtinen

[Intel-gfx] ✓ Fi.CI.BAT: success for Add support for Legacy HDMI audio drivers (rev2)

2016-12-11 Thread Patchwork
== Series Details == Series: Add support for Legacy HDMI audio drivers (rev2) URL : https://patchwork.freedesktop.org/series/16254/ State : success == Summary == Series 16254v2 Add support for Legacy HDMI audio drivers https://patchwork.freedesktop.org/api/1.0/series/16254/revisions/2/mbox/

Re: [Intel-gfx] [PATCH] dma-buf: Provide wrappers for reservation's lock

2016-12-11 Thread Daniel Vetter
On Sun, Dec 11, 2016 at 04:05:21PM -0500, Alex Deucher wrote: > On Sun, Dec 11, 2016 at 12:12 PM, Chris Wilson > wrote: > > On Tue, Nov 15, 2016 at 10:43:34PM +0100, Daniel Vetter wrote: > >> On Tue, Nov 15, 2016 at 03:46:42PM +, Chris Wilson wrote: > >> > Joonas

Re: [Intel-gfx] [PATCH v2] drm/i915: Respect num_pipes when install or reset dispaly IRQ

2016-12-11 Thread Wang, Elaine
> On Fri, Dec 09, 2016 at 05:45:56PM +0200, Joonas Lahtinen wrote: > > On pe, 2016-12-09 at 18:01 +0800, Wang Elaine wrote: > > > From: Elaine Wang > > > > > > Some platforms don't have display. To avoid accessing the > > > non-existent registers, check whether num_pipes

Re: [Intel-gfx] [RFC 0/4] Introduce drmfs pseudo filesystem for drm subsystem

2016-12-11 Thread sourab gupta
On Mon, 2016-12-05 at 03:06 -0800, Dhingra, Swati wrote: > From: Swati Dhingra > > Currently, we don't have a stable ABI which can be used for the purpose of > providing output debug/loggging/crc and other such data from DRM. > The ABI in current use (filesystems,

[Intel-gfx] [PATCH 6/7] ALSA: x86: hdmi: Fixup some monitor

2016-12-11 Thread Jerome Anand
This change was given to Canonical apparently to fix an issue with on some monitor brand. It's not clear what this patch does but it doesn't seem to have side effects. Signed-off-by: David Henningsson Signed-off-by: Pierre-Louis Bossart

[Intel-gfx] [PATCH 5/7] ALSA: x86: hdmi: Improve position reporting

2016-12-11 Thread Jerome Anand
Use a hw register to calculate sub-period position reports. This makes PulseAudio happier. Signed-off-by: David Henningsson Signed-off-by: Pierre-Louis Bossart Signed-off-by: Jerome Anand ---

[Intel-gfx] [PATCH 2/7] drm/i915: Add support for audio driver notifications

2016-12-11 Thread Jerome Anand
Notifiations like mode change, hot plug and edid to the audio driver are added. This is inturn used by the audio driver for its functionality. A new interface file capturing the notifications needed by the audio driver is added Signed-off-by: Pierre-Louis Bossart

[Intel-gfx] [PATCH 7/7] ALSA: x86: hdmi: continue playback even when display resolution changes

2016-12-11 Thread Jerome Anand
When the display resolution changes, the drm disables the display pipes due to which audio rendering stops. At this time, we need to ensure the existing audio pointers and buffers are cleared out so that the playback can restarted once the display pipe is enabled with a different N/CTS values

[Intel-gfx] [PATCH 3/7] ALSA: add shell for Intel HDMI LPE audio driver

2016-12-11 Thread Jerome Anand
On Baytrail and Cherrytrail, HDaudio may be fused out or disabled by the BIOS. This driver enables an alternate path to the i915 display registers and DMA. Although there is no hardware path between i915 display and LPE/SST audio clusters, this HDMI capability is referred to in the documentation

[Intel-gfx] [PATCH 4/7] ALSA: x86: hdmi: Add audio support for BYT and CHT

2016-12-11 Thread Jerome Anand
Hdmi audio driver based on the child platform device created by gfx driver is implemented. This audio driver is derived from legacy intel hdmi audio driver. The interfaces for interaction between gfx and audio are updated and the driver implementation updated to derive interrupts in its own

[Intel-gfx] [PATCH 0/7] Add support for Legacy HDMI audio drivers

2016-12-11 Thread Jerome Anand
Legacy (CherryTrail/ Baytrail) HDMI audio drivers added Legacy hdmi audio-Gfx interaction/ interfacing is updated to use irq chip framework Jerome Anand (7): drm/i915: setup bridge for HDMI LPE audio driver drm/i915: Add support for audio driver notifications ALSA: add shell for Intel HDMI

[Intel-gfx] [PATCH 1/7] drm/i915: setup bridge for HDMI LPE audio driver

2016-12-11 Thread Jerome Anand
Enable support for HDMI LPE audio mode on Baytrail and Cherrytrail when HDaudio controller is not detected Setup minimum required resources during i915_driver_load: 1. Create a platform device to share MMIO/IRQ resources 2. Make the platform device child of i915 device for runtime PM. 3. Create

Re: [Intel-gfx] [PATCH] dma-buf: Provide wrappers for reservation's lock

2016-12-11 Thread Alex Deucher
On Sun, Dec 11, 2016 at 12:12 PM, Chris Wilson wrote: > On Tue, Nov 15, 2016 at 10:43:34PM +0100, Daniel Vetter wrote: >> On Tue, Nov 15, 2016 at 03:46:42PM +, Chris Wilson wrote: >> > Joonas complained that writing ww_mutex_lock(>lock, ctx) was too >> > intrusive

Re: [Intel-gfx] [PATCH 1/5] dma-buf: Extract dma-buf.rst

2016-12-11 Thread Jonathan Corbet
On Fri, 9 Dec 2016 19:53:05 +0100 Daniel Vetter wrote: > Just prep work to polish and consolidate all the dma-buf related > documenation. > > Unfortunately I didn't discover a way to both integrate this new file > into the overall toc while keeping it at the current

Re: [Intel-gfx] [PATCH] drm: Simplify GETRESOURCES ioctl

2016-12-11 Thread Chris Wilson
On Sun, Dec 11, 2016 at 08:20:19PM +0100, Daniel Vetter wrote: > Looping twice when we can do it once is silly. Also use a consistent > style. Note that there's a good race with the connector list walking, > since that is no longer protected by mode_config.mutex. But that's for > a later patch to

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/4] drm: Protect master->unique with dev->master_mutex (rev3)

2016-12-11 Thread Patchwork
== Series Details == Series: series starting with [1/4] drm: Protect master->unique with dev->master_mutex (rev3) URL : https://patchwork.freedesktop.org/series/16661/ State : success == Summary == Series 16661v3 Series without cover letter

Re: [Intel-gfx] [PATCH 0/5] sphinxification for dma-buf docs

2016-12-11 Thread Jonathan Corbet
On Sun, 11 Dec 2016 18:35:42 +0100 Daniel Vetter wrote: > > Here's a thought, though: how about if we slip in a little version of > > dma-buf.rst now with a "coming soon, don't miss it!!" message? Then the > > rest of the set could go through your tree without touching >

[Intel-gfx] [PATCH] drm: Simplify GETRESOURCES ioctl

2016-12-11 Thread Daniel Vetter
Looping twice when we can do it once is silly. Also use a consistent style. Note that there's a good race with the connector list walking, since that is no longer protected by mode_config.mutex. But that's for a later patch to fix. v2: Actually try to not blow up, somehow I lost the hunk that

[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] lockdep: Markup callers of might_lock() as potential sleepers

2016-12-11 Thread Patchwork
== Series Details == Series: series starting with [1/2] lockdep: Markup callers of might_lock() as potential sleepers URL : https://patchwork.freedesktop.org/series/16667/ State : failure == Summary == Series 16667v1 Series without cover letter

[Intel-gfx] [PATCH 1/2] lockdep: Markup callers of might_lock() as potential sleepers

2016-12-11 Thread Chris Wilson
If might_lock() is called on a mutex, it may also potentially sleep. Call might_sleep() in this case so that the caller is checked for both. This is similar to the might_sleep() that is checked by the real mutex_lock(). Signed-off-by: Chris Wilson Cc: Peter Zijlstra

[Intel-gfx] [PATCH 2/2] kref: Annotate kref_put_mutex() with might_lock()

2016-12-11 Thread Chris Wilson
As kref_put_mutex() may take the mutex (on the final unreference), mark it up with might_lock() so that the caller is unconditionally checked by lockdep. Signed-off-by: Chris Wilson Cc: Peter Zijlstra --- include/linux/kref.h | 1 + 1 file

Re: [Intel-gfx] [PATCH 0/5] sphinxification for dma-buf docs

2016-12-11 Thread Daniel Vetter
On Sun, Dec 11, 2016 at 4:11 PM, Jonathan Corbet wrote: > On Sun, 11 Dec 2016 13:35:49 +0100 > Daniel Vetter wrote: > >> > It seems like just the sort of thing we want to be doing to pull the docs >> > together in a more rational way. >> >> Ok if we pull

Re: [Intel-gfx] [PATCH] dma-buf: Provide wrappers for reservation's lock

2016-12-11 Thread Chris Wilson
On Tue, Nov 15, 2016 at 10:43:34PM +0100, Daniel Vetter wrote: > On Tue, Nov 15, 2016 at 03:46:42PM +, Chris Wilson wrote: > > Joonas complained that writing ww_mutex_lock(>lock, ctx) was too > > intrusive compared to reservation_object_lock(resv, ctx); > > > > Signed-off-by: Chris Wilson

Re: [Intel-gfx] [PATCH 0/5] sphinxification for dma-buf docs

2016-12-11 Thread Jonathan Corbet
On Sun, 11 Dec 2016 13:35:49 +0100 Daniel Vetter wrote: > > It seems like just the sort of thing we want to be doing to pull the docs > > together in a more rational way. > > Ok if we pull this in through gfx trees? Will miss 4.10 though, that's > already finished and

Re: [Intel-gfx] [PATCH] drm: Simplify GETRESOURCES ioctl

2016-12-11 Thread Chris Wilson
On Sun, Dec 11, 2016 at 01:39:15PM +0100, Daniel Vetter wrote: > + count = 0; > + fb_id = u64_to_user_ptr(card_res->fb_id_ptr); > + list_for_each_entry(fb, _priv->fbs, filp_head) { > + count++; > + if (count > card_res->count_fbs) > +

[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/4] drm: Protect master->unique with dev->master_mutex (rev2)

2016-12-11 Thread Patchwork
== Series Details == Series: series starting with [1/4] drm: Protect master->unique with dev->master_mutex (rev2) URL : https://patchwork.freedesktop.org/series/16661/ State : failure == Summary == Series 16661v2 Series without cover letter

[Intel-gfx] [PATCH] drm: Simplify GETRESOURCES ioctl

2016-12-11 Thread Daniel Vetter
Looping twice when we can do it once is silly. Also use a consistent style. Note that there's a good race with the connector list walking, since that is no longer protected by mode_config.mutex. But that's for a later patch to fix. v2: Actually try to not blow up, somehow I lost the hunk that

Re: [Intel-gfx] [PATCH 0/5] sphinxification for dma-buf docs

2016-12-11 Thread Daniel Vetter
On Fri, Dec 9, 2016 at 10:15 PM, Jonathan Corbet wrote: > On Fri, 9 Dec 2016 19:53:04 +0100 > Daniel Vetter wrote: > >> Not yet everything in this area, I still want to sprinkle nice docs around >> all >> the fence code. Especially some text to explain

Re: [Intel-gfx] [PATCH 0/5] sphinxification for dma-buf docs

2016-12-11 Thread Sumit Semwal
Hi Daniel, On 10 December 2016 at 02:45, Jonathan Corbet wrote: > On Fri, 9 Dec 2016 19:53:04 +0100 > Daniel Vetter wrote: > >> Not yet everything in this area, I still want to sprinkle nice docs around >> all >> the fence code. Especially some text to

Re: [Intel-gfx] [PATCH 4/4] drm: Simplify GETRESOURCES ioctl

2016-12-11 Thread Daniel Vetter
On Sat, Dec 10, 2016 at 11:04 PM, Chris Wilson wrote: >> + list_for_each_entry(fb, _priv->fbs, filp_head) { >> + count++; >> + if (count > card_res->count_fbs) >> + continue; >> + >> + if (put_user(fb->base.id,