[Intel-gfx] Can recent i915 support more than 8192x8192 screen?

2018-07-19 Thread Marcin Owsiany
Hello, *TL;DR*: how can I set a 8960x2880 screen (not display) size on a T580? A patch for i915 that I found on the internets does not seem to work. Full story: I'm a rather happy user of ThinkPad T580 which comes with a high-density 3840x2160 LCD, and the following graphics hardware. 00:02.0

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] drm/i915/selftests: Use a full emulation of a user ppgtt context

2018-07-19 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915/selftests: Use a full emulation of a user ppgtt context URL : https://patchwork.freedesktop.org/series/46890/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4516_full -> Patchwork_9722_full = == Summary -

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] drm/i915/selftests: Use a full emulation of a user ppgtt context

2018-07-19 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915/selftests: Use a full emulation of a user ppgtt context URL : https://patchwork.freedesktop.org/series/46890/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4515_full -> Patchwork_9721_full = == Summary -

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Fix psr sink status report. (rev3)

2018-07-19 Thread Patchwork
== Series Details == Series: drm/i915: Fix psr sink status report. (rev3) URL : https://patchwork.freedesktop.org/series/46831/ State : failure == Summary == = CI Bug Log - changes from CI_DRM_4518 -> Patchwork_9726 = == Summary - FAILURE == Serious unknown changes coming with

Re: [Intel-gfx] [PATCH 2/4] i915/dp/dsc: Add DSC PPS register definitions

2018-07-19 Thread Manasi Navare
Anusha, This is not the correct latest patch. This still doesnt have _MMIO for DSCA_ and DSCC registers. On Tue, Jul 17, 2018 at 02:10:59PM -0700, Anusha Srivatsa wrote: > From: "Srivatsa, Anusha" > > Display Stream Compression(DSC) has a set of Picture > Parameter Set(PPS) components that the

Re: [Intel-gfx] [PATCH] drm/i915: Fix psr sink status report.

2018-07-19 Thread Dhinakaran Pandiyan
On Thu, 2018-07-19 at 17:31 -0700, Rodrigo Vivi wrote: > First of all don't try to read dpcd if PSR is not even supported. > > But also, if read failed return -EIO instead of reporting via a > backchannel. > > v2: fix dev_priv: At this level m->private is the connector. (CI/DK) > don't

Re: [Intel-gfx] [PATCH] drm/i915: Remove unused "ret" variable.

2018-07-19 Thread Nathan Ciobanu
On Thu, Jul 19, 2018 at 05:16:03PM -0700, Nathan Ciobanu wrote: > On Thu, Jul 19, 2018 at 04:42:17PM -0700, Rodrigo Vivi wrote: > > Just a small clean-up with no functional change, only > > removing a variable that is never actually used. > > > > Cc: Dhinakaran Pandiyan > > Signed-off-by:

[Intel-gfx] [PATCH] drm/i915: Fix psr sink status report.

2018-07-19 Thread Rodrigo Vivi
First of all don't try to read dpcd if PSR is not even supported. But also, if read failed return -EIO instead of reporting via a backchannel. v2: fix dev_priv: At this level m->private is the connector. (CI/DK) don't convert dpcd read errors to EIO. (DK) Fixes: 5b7b30864d1d ("drm/i915/psr:

[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [v5,2/2] drm/i915/dp: Refactor mav_vswing_tries variable (rev2)

2018-07-19 Thread Patchwork
== Series Details == Series: series starting with [v5,2/2] drm/i915/dp: Refactor mav_vswing_tries variable (rev2) URL : https://patchwork.freedesktop.org/series/46897/ State : failure == Summary == Applying: drm/i915/dp: Refactor mav_vswing_tries variable error: sha1 information is lacking

Re: [Intel-gfx] [PATCH] drm/i915: Remove unused "ret" variable.

2018-07-19 Thread Nathan Ciobanu
On Thu, Jul 19, 2018 at 04:42:17PM -0700, Rodrigo Vivi wrote: > Just a small clean-up with no functional change, only > removing a variable that is never actually used. > > Cc: Dhinakaran Pandiyan > Signed-off-by: Rodrigo Vivi Nice one :) Reviewed-by: > --- >

[Intel-gfx] [PATCH v5] drm/i915/dp: Refactor max_vswing_tries variable

2018-07-19 Thread Nathan Ciobanu
Changes the type and renames the max_vswing_tries variable which was declared as an integer but used as a boolean making it easy to be confused with a counter. Changes in v2: - updated the title and commit message - left the loop exit point in place v3: fix typo in title Cc: Dhinakaran

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Remove unused "ret" variable.

2018-07-19 Thread Patchwork
== Series Details == Series: drm/i915: Remove unused "ret" variable. URL : https://patchwork.freedesktop.org/series/46904/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4517 -> Patchwork_9724 = == Summary - SUCCESS == No regressions found. External URL:

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: GTT remapping for display

2018-07-19 Thread Patchwork
== Series Details == Series: drm/i915: GTT remapping for display URL : https://patchwork.freedesktop.org/series/46886/ State : failure == Summary == = CI Bug Log - changes from CI_DRM_4515_full -> Patchwork_9720_full = == Summary - FAILURE == Serious unknown changes coming with

[Intel-gfx] [PATCH] drm/i915: Remove unused "ret" variable.

2018-07-19 Thread Rodrigo Vivi
Just a small clean-up with no functional change, only removing a variable that is never actually used. Cc: Dhinakaran Pandiyan Signed-off-by: Rodrigo Vivi --- drivers/gpu/drm/i915/intel_dp_mst.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git

Re: [Intel-gfx] [PATCH v2 2/2] drm/i915/mst: Continue state updates even if AUX writes fail.

2018-07-19 Thread Rodrigo Vivi
On Thu, Jul 19, 2018 at 11:51:40AM -0700, Dhinakaran Pandiyan wrote: > On Wed, 2018-07-18 at 22:43 -0700, Rodrigo Vivi wrote: > > On Wed, Jul 18, 2018 at 10:19:43AM -0700, Dhinakaran Pandiyan wrote: > > > > > > We are too late in the enabling sequence to back out cleanly, not > > > updating > > >

Re: [Intel-gfx] [alsa-devel] [PATCH v2 0/3] Make the audio component binding more generic

2018-07-19 Thread Pierre-Louis Bossart
On 7/19/18 1:56 PM, Takashi Iwai wrote: On Thu, 19 Jul 2018 15:05:45 +0200, Pierre-Louis Bossart wrote: On 7/19/18 12:50 AM, Takashi Iwai wrote: On Wed, 18 Jul 2018 22:54:35 +0200, Pierre-Louis Bossart wrote: On 07/17/2018 04:26 AM, Takashi Iwai wrote: Hi, this is a preliminiary patch

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [v3,1/2] drm/i915/icl: move has_resource_streamer to GEN11_FEATURES

2018-07-19 Thread Patchwork
== Series Details == Series: series starting with [v3,1/2] drm/i915/icl: move has_resource_streamer to GEN11_FEATURES URL : https://patchwork.freedesktop.org/series/46884/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4514_full -> Patchwork_9719_full = == Summary -

Re: [Intel-gfx] [PATCH 2/2] drm/i915: implement EXTENDED_RECEIVER_CAPABILITY_FIELD_PRESENT

2018-07-19 Thread Rodrigo Vivi
On Thu, Jul 19, 2018 at 02:47:59PM -0700, Atwood, Matthew S wrote: > On Thu, 2018-07-19 at 14:07 -0700, Rodrigo Vivi wrote: > > On Thu, Jul 19, 2018 at 01:35:49PM -0700, matthew.s.atw...@intel.com > > wrote: > > > From: Matt Atwood > > > > > > According to DP spec (2.9.3.1 of DP 1.4) if > > >

[Intel-gfx] [PATCH v5 2/2] drm/i915/dp: Refactor mav_vswing_tries variable

2018-07-19 Thread Nathan Ciobanu
Changes the type and renames the max_vswing_tries variable which was declared as an integer but used as a boolean making it easy to be confused with a counter. Changes in v2: - updated the title and commit message - left the loop exit point in place Cc: Dhinakaran Pandiyan Cc: Rodrigo

[Intel-gfx] [PATCH v5 1/2] drm/i915/dp: Limit link training clock recovery loop

2018-07-19 Thread Nathan Ciobanu
Limit the link training clock recovery loop to 10 attempts at LANEx_CR_DONE per DP 1.4 spec section 3.5.1.2.2 and 80 attempts for pre-DP 1.4 (4 voltage levels x 4 preemphasis levels x x 5 identical voltages tries). Some faulty USB-C MST hubs can cause us to get stuck in this loop indefinitely

Re: [Intel-gfx] [PATCH 2/2] drm/i915: implement EXTENDED_RECEIVER_CAPABILITY_FIELD_PRESENT

2018-07-19 Thread Atwood, Matthew S
On Thu, 2018-07-19 at 14:07 -0700, Rodrigo Vivi wrote: > On Thu, Jul 19, 2018 at 01:35:49PM -0700, matthew.s.atw...@intel.com > wrote: > > From: Matt Atwood > > > > According to DP spec (2.9.3.1 of DP 1.4) if > > EXTENDED_RECEIVER_CAPABILITY_FIELD_PRESENT is set the addresses in > > DPCD > >

[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/dp: add extended receiver capability field present bit (rev3)

2018-07-19 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/dp: add extended receiver capability field present bit (rev3) URL : https://patchwork.freedesktop.org/series/46743/ State : failure == Summary == Applying: drm/dp: add extended receiver capability field present bit Applying: drm/dp:

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/selftests: Use a full emulation of a user ppgtt context

2018-07-19 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915/selftests: Use a full emulation of a user ppgtt context URL : https://patchwork.freedesktop.org/series/46890/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4516 -> Patchwork_9722 = == Summary - SUCCESS ==

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Cache the error string (rev4)

2018-07-19 Thread Patchwork
== Series Details == Series: drm/i915: Cache the error string (rev4) URL : https://patchwork.freedesktop.org/series/46777/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4513_full -> Patchwork_9718_full = == Summary - WARNING == Minor unknown changes coming with

Re: [Intel-gfx] [PATCH 2/2] drm/i915: implement EXTENDED_RECEIVER_CAPABILITY_FIELD_PRESENT

2018-07-19 Thread Rodrigo Vivi
On Thu, Jul 19, 2018 at 01:35:49PM -0700, matthew.s.atw...@intel.com wrote: > From: Matt Atwood > > According to DP spec (2.9.3.1 of DP 1.4) if > EXTENDED_RECEIVER_CAPABILITY_FIELD_PRESENT is set the addresses in DPCD > 02200h through 0220Fh shall contain the DPRX's true capability. These >

Re: [Intel-gfx] [PATCH 1/2] drm/dp: add extended receiver capability field present bit

2018-07-19 Thread Rodrigo Vivi
On Thu, Jul 19, 2018 at 01:35:48PM -0700, matthew.s.atw...@intel.com wrote: > From: Matt Atwood > > This bit was added to DP Training Aux RD interval sometime between DP > 1.2 and DP 1.3. I understand that some 1.2 version that I had here that caused all the trouble around XXX 1.2, but since

[Intel-gfx] [PATCH 1/2] drm/dp: add extended receiver capability field present bit

2018-07-19 Thread matthew . s . atwood
From: Matt Atwood This bit was added to DP Training Aux RD interval sometime between DP 1.2 and DP 1.3. Via description of the spec this field indicates the panels true capabilities are described in DPCD address space 02200h through 022FFh. v2: version comment update Signed-off-by: Matt Atwood

[Intel-gfx] [PATCH 2/2] drm/i915: implement EXTENDED_RECEIVER_CAPABILITY_FIELD_PRESENT

2018-07-19 Thread matthew . s . atwood
From: Matt Atwood According to DP spec (2.9.3.1 of DP 1.4) if EXTENDED_RECEIVER_CAPABILITY_FIELD_PRESENT is set the addresses in DPCD 02200h through 0220Fh shall contain the DPRX's true capability. These values will match 0h through Fh, except for DPCD_REV, MAX_LINK_RATE,

Re: [Intel-gfx] [PATCH 15/18] drm/i915: Add a new "remapped" gtt_view

2018-07-19 Thread Chris Wilson
Quoting Ville Syrjälä (2018-07-19 21:16:20) > > > > > +} __packed; > > > > > + > > > > > +static inline void assert_intel_remapped_info_is_packed(void) > > > > > +{ > > > > > + BUILD_BUG_ON(sizeof(struct intel_remapped_info) != > > > > > 10*sizeof(unsigned int)); > > Hmm. These assert

[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/selftests: Use a full emulation of a user ppgtt context

2018-07-19 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915/selftests: Use a full emulation of a user ppgtt context URL : https://patchwork.freedesktop.org/series/46890/ State : failure == Summary == = CI Bug Log - changes from CI_DRM_4515 -> Patchwork_9721 = == Summary - FAILURE ==

Re: [Intel-gfx] [PATCH v8] drm/i915: Fix assert_plane() warning on bootup with external display

2018-07-19 Thread Ville Syrjälä
On Thu, Jul 19, 2018 at 08:03:42PM +, Shaikh, Azhar wrote: > > > >-Original Message- > >From: Shaikh, Azhar > >Sent: Friday, July 6, 2018 11:38 AM > >To: intel-gfx@lists.freedesktop.org > >Cc: ville.syrj...@linux.intel.com; Navare, Manasi D > >; Shaikh, Azhar > >Subject: [PATCH v8]

Re: [Intel-gfx] [PATCH 15/18] drm/i915: Add a new "remapped" gtt_view

2018-07-19 Thread Ville Syrjälä
On Thu, Jul 19, 2018 at 08:46:54PM +0100, Chris Wilson wrote: > Quoting Ville Syrjälä (2018-07-19 20:33:57) > > On Thu, Jul 19, 2018 at 07:59:33PM +0100, Chris Wilson wrote: > > > Quoting Ville Syrjala (2018-07-19 19:22:11) > > > > +static struct scatterlist * > > > > +remap_pages(const dma_addr_t

Re: [Intel-gfx] [PATCH v8] drm/i915: Fix assert_plane() warning on bootup with external display

2018-07-19 Thread Shaikh, Azhar
>-Original Message- >From: Shaikh, Azhar >Sent: Friday, July 6, 2018 11:38 AM >To: intel-gfx@lists.freedesktop.org >Cc: ville.syrj...@linux.intel.com; Navare, Manasi D >; Shaikh, Azhar >Subject: [PATCH v8] drm/i915: Fix assert_plane() warning on bootup with >external display > >On KBL,

Re: [Intel-gfx] [PATCH 15/18] drm/i915: Add a new "remapped" gtt_view

2018-07-19 Thread Ville Syrjälä
On Thu, Jul 19, 2018 at 08:46:54PM +0100, Chris Wilson wrote: > Quoting Ville Syrjälä (2018-07-19 20:33:57) > > On Thu, Jul 19, 2018 at 07:59:33PM +0100, Chris Wilson wrote: > > > Quoting Ville Syrjala (2018-07-19 19:22:11) > > > > +static struct scatterlist * > > > > +remap_pages(const dma_addr_t

Re: [Intel-gfx] [PATCH v3 2/2] drm/i915: kill resource streamer

2018-07-19 Thread Rodrigo Vivi
On Thu, Jul 19, 2018 at 12:12:08PM -0700, Lucas De Marchi wrote: > On Thu, Jul 19, 2018 at 10:18 AM Rodrigo Vivi wrote: > > > > On Thu, Jul 19, 2018 at 10:05:57AM -0700, Lucas De Marchi wrote: > > > After disabling resource streamer on ICL (due to it actually not > > > existing there), I got

[Intel-gfx] [PATCH 2/2] drm/i915/selftests: Exercise resetting in the middle of a wait-on-fence

2018-07-19 Thread Chris Wilson
On older HW, gen2/3, fence registers are used for detiling GPU commands and as such changing those registers requires serialisation with the requests on the GPU. Anything running on the GPU is subject to a hang, and so we must be able to recover cleanly in the middle of a stuck wait on a fence

[Intel-gfx] [PATCH 1/2] drm/i915/selftests: Use a full emulation of a user ppgtt context

2018-07-19 Thread Chris Wilson
To test eviction from a ppgtt, we just want a ppgtt i.e. something other than the Global GTT which is shared and used by the kernel for HW features like fencing and scanout. However, we also need it to pass !i915_is_ggtt() and the simplest way is to emulate a full user context rather than the

Re: [Intel-gfx] [PATCH 15/18] drm/i915: Add a new "remapped" gtt_view

2018-07-19 Thread Chris Wilson
Quoting Ville Syrjälä (2018-07-19 20:33:57) > On Thu, Jul 19, 2018 at 07:59:33PM +0100, Chris Wilson wrote: > > Quoting Ville Syrjala (2018-07-19 19:22:11) > > > +static struct scatterlist * > > > +remap_pages(const dma_addr_t *in, unsigned int offset, > > > + unsigned int width,

Re: [Intel-gfx] [PATCH 15/18] drm/i915: Add a new "remapped" gtt_view

2018-07-19 Thread Ville Syrjälä
On Thu, Jul 19, 2018 at 07:59:33PM +0100, Chris Wilson wrote: > Quoting Ville Syrjala (2018-07-19 19:22:11) > > +static struct scatterlist * > > +remap_pages(const dma_addr_t *in, unsigned int offset, > > + unsigned int width, unsigned int height, > > + unsigned int stride, > >

Re: [Intel-gfx] [PATCH 16/18] drm/i915: Overcome display engine stride limits via GTT remapping

2018-07-19 Thread Ville Syrjälä
On Thu, Jul 19, 2018 at 08:01:12PM +0100, Chris Wilson wrote: > Quoting Ville Syrjala (2018-07-19 19:22:12) > > From: Ville Syrjälä > > > > The display engine stride limits are getting in our way. On SKL+ > > we are limited to 8k pixels, which is easily exceeded with three > > 4k displays. To

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: GTT remapping for display

2018-07-19 Thread Patchwork
== Series Details == Series: drm/i915: GTT remapping for display URL : https://patchwork.freedesktop.org/series/46886/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4515 -> Patchwork_9720 = == Summary - SUCCESS == No regressions found. External URL:

Re: [Intel-gfx] [PATCH v3 2/2] drm/i915: kill resource streamer

2018-07-19 Thread Lucas De Marchi
On Thu, Jul 19, 2018 at 10:18 AM Rodrigo Vivi wrote: > > On Thu, Jul 19, 2018 at 10:05:57AM -0700, Lucas De Marchi wrote: > > After disabling resource streamer on ICL (due to it actually not > > existing there), I got feedback that there have been some experimental > > patches for mesa to use RS

Re: [Intel-gfx] [PATCH 16/18] drm/i915: Overcome display engine stride limits via GTT remapping

2018-07-19 Thread Chris Wilson
Quoting Ville Syrjala (2018-07-19 19:22:12) > From: Ville Syrjälä > > The display engine stride limits are getting in our way. On SKL+ > we are limited to 8k pixels, which is easily exceeded with three > 4k displays. To overcome this limitation we can remap the pages > in the GTT to provide the

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: GTT remapping for display

2018-07-19 Thread Patchwork
== Series Details == Series: drm/i915: GTT remapping for display URL : https://patchwork.freedesktop.org/series/46886/ State : warning == Summary == $ dim sparse origin/drm-tip Commit: drm/i915: Fix glk/cnl display w/a #1175 Okay! Commit: drm/i915: s/tile_offset/aligned_offset/ Okay!

Re: [Intel-gfx] [PATCH 15/18] drm/i915: Add a new "remapped" gtt_view

2018-07-19 Thread Chris Wilson
Quoting Ville Syrjala (2018-07-19 19:22:11) > +static struct scatterlist * > +remap_pages(const dma_addr_t *in, unsigned int offset, > + unsigned int width, unsigned int height, > + unsigned int stride, > + struct sg_table *st, struct scatterlist *sg) > +{ > +

Re: [Intel-gfx] [alsa-devel] [PATCH v2 0/3] Make the audio component binding more generic

2018-07-19 Thread Takashi Iwai
On Thu, 19 Jul 2018 15:05:45 +0200, Pierre-Louis Bossart wrote: > > On 7/19/18 12:50 AM, Takashi Iwai wrote: > > On Wed, 18 Jul 2018 22:54:35 +0200, > > Pierre-Louis Bossart wrote: > >> > >> > >> > >> On 07/17/2018 04:26 AM, Takashi Iwai wrote: > >>> Hi, > >>> > >>> this is a preliminiary patch

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: GTT remapping for display

2018-07-19 Thread Patchwork
== Series Details == Series: drm/i915: GTT remapping for display URL : https://patchwork.freedesktop.org/series/46886/ State : warning == Summary == $ dim checkpatch origin/drm-tip 0655c1625b0a drm/i915: Fix glk/cnl display w/a #1175 c95e166cfd63 drm/i915: s/tile_offset/aligned_offset/

Re: [Intel-gfx] [PATCH v3] drm/i915/dp: Give up link training clock recovery after 10 failed attempts

2018-07-19 Thread Nathan Ciobanu
On Thu, Jul 19, 2018 at 10:01:41AM -0700, Rodrigo Vivi wrote: > On Tue, Jul 17, 2018 at 06:05:51PM -0700, Nathan Ciobanu wrote: > > On Tue, Jul 17, 2018 at 03:21:17PM -0700, Dhinakaran Pandiyan wrote: > > > On Mon, 2018-07-16 at 16:51 -0700, Marc Herbert wrote: > > > > > > > > > > > > > > > > >

[Intel-gfx] [PATCH v4 2/2] drm/i915/dp: Remove unneeded mav_vswing_tries variable

2018-07-19 Thread Nathan Ciobanu
max_vswing_tries variable was declared as an int but used as a bool and not even needed because we can just check the return of intel_dp_link_max_vswing_reached. Cc: Dhinakaran Pandiyan Cc: Rodrigo Vivi Cc: Marc Herbert Signed-off-by: Nathan Ciobanu ---

[Intel-gfx] [PATCH v4 1/2] drm/i915/dp: Limit link training clock recovery loop

2018-07-19 Thread Nathan Ciobanu
Limit the link training clock recovery loop to 10 attempts at LANEx_CR_DONE per DP 1.4 spec section 3.5.1.2.2 and 80 attempts for pre-DP 1.4 (4 voltage levels x 4 preemphasis levels x x 5 identical voltages tries). Some faulty USB-C MST hubs can cause us to get stuck in this loop indefinitely

Re: [Intel-gfx] [PATCH v5 01/13] drm/i915/icl: Configure lane sequencing of combo phy transmitter

2018-07-19 Thread Chauhan, Madhav
> -Original Message- > From: Ville Syrjälä [mailto:ville.syrj...@linux.intel.com] > Sent: Thursday, July 19, 2018 9:42 PM > To: Chauhan, Madhav > Cc: intel-gfx@lists.freedesktop.org; Nikula, Jani ; > Zanoni, Paulo R ; Vivi, Rodrigo > > Subject: Re: [Intel-gfx] [PATCH v5 01/13]

Re: [Intel-gfx] [PATCH v2 2/2] drm/i915/mst: Continue state updates even if AUX writes fail.

2018-07-19 Thread Dhinakaran Pandiyan
On Wed, 2018-07-18 at 22:43 -0700, Rodrigo Vivi wrote: > On Wed, Jul 18, 2018 at 10:19:43AM -0700, Dhinakaran Pandiyan wrote: > > > > We are too late in the enabling sequence to back out cleanly, not > > updating > > state tracking variables, like intel_dp->active_mst_links in this > > instance,

[Intel-gfx] [PATCH 12/18] drm/i915: Move display w/a #1175

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä Move the display w/a #1175 to a better place. That place being the new skl+ specific plane->check() hook. This leaves the skl_check_plane_surface() stuff to deal with the gtt offset and src coordinate stuff as originally envisioned. Signed-off-by: Ville Syrjälä ---

[Intel-gfx] [PATCH 09/18] drm/i915: Nuke plane->can_scale/min_downscale

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä We can easily calculate the plane can_scale/min_downscale on demand. And later on we'll probably want to start calculating these dynamically based on the cdclk just as skl already does. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_display.c | 8 +---

[Intel-gfx] [PATCH 02/18] drm/i915: s/tile_offset/aligned_offset/

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä Rename some of the tile_offset() functions to aligned_offset() since they operate on both linear and tiled functions. And we'll include _plane_ in the name of all the variants that take a plane state. Should make it more clear which function to use where. Signed-off-by:

[Intel-gfx] [PATCH 13/18] drm/i915: Move chv rotation checks to plane->check()

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä Move the chv rotation vs. reflections checks to the plane->check() hook, away from the (now) platform agnostic intel_plane_atomic_check_with_state(). Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_atomic_plane.c | 9 -

[Intel-gfx] [PATCH 17/18] drm/i915: Bump gen4+ fb stride limit to 256KiB

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä With gtt remapping plugged in we can simply raise the stride limit on gen4+. Let's just arbitraily pick 256 KiB as the limit. No remapping CCS because the virtual address of each page actually matters due to the new hash mode (WaCompressedResourceDisplayNewHashMode:skl,kbl

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v3,1/2] drm/i915/icl: move has_resource_streamer to GEN11_FEATURES

2018-07-19 Thread Patchwork
== Series Details == Series: series starting with [v3,1/2] drm/i915/icl: move has_resource_streamer to GEN11_FEATURES URL : https://patchwork.freedesktop.org/series/46884/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4514 -> Patchwork_9719 = == Summary - SUCCESS == No

[Intel-gfx] [PATCH 18/18] drm/i915: Bump gen4+ fb size limits to 32kx32k

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä With gtt remapping in place we can use arbitraily large framebuffers. Let's bump the limits as high as we can (32k-1). Going beyond that would require switching out s16.16 src coordinate representation to something with more spare bits. Signed-off-by: Ville Syrjälä ---

[Intel-gfx] [PATCH 15/18] drm/i915: Add a new "remapped" gtt_view

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä To overcome display engine stride limits we'll want to remap the pages in the GTT. To that end we need a new gtt_view type which is just like the "rotated" type except not rotated. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/i915_debugfs.c | 12 +

[Intel-gfx] [PATCH 16/18] drm/i915: Overcome display engine stride limits via GTT remapping

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä The display engine stride limits are getting in our way. On SKL+ we are limited to 8k pixels, which is easily exceeded with three 4k displays. To overcome this limitation we can remap the pages in the GTT to provide the display engine with a view of memory with a smaller

[Intel-gfx] [PATCH 14/18] drm/i915: Extract intel_cursor_check_surface()

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä Extract intel_cursor_check_surface() to better match the code layout of the other plane types. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_display.c | 47 ++-- 1 file changed, 29 insertions(+), 18 deletions(-) diff --git

[Intel-gfx] [PATCH 00/18] drm/i915: GTT remapping for display

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä The display engine has unfortunately low stride limits when compared to modern display resolutions. 2x4k is about as big as we can go currently. This series aims to overcome that by shuffling the pages in the GTT to provide the display engine with a view of memory with a

[Intel-gfx] [PATCH 11/18] drm/i915: Move skl plane fb related checks into a better place

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä Move the skl+ specific framebuffer related checks from intel_plane_atomic_check_with_state() into a new function (skl_plane_check_fb()) which we'll simply call from the skl plane->check() hook. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_atomic_plane.c | 42

[Intel-gfx] [PATCH 01/18] drm/i915: Fix glk/cnl display w/a #1175

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä The workaround was supposed to look at the plane destination coordinates. Currently it's looking at some mixture of src and dst coordinates that doesn't make sense. Fix it up. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_display.c | 7 --- 1 file

[Intel-gfx] [PATCH 07/18] drm/i915: Store ggtt_view in plane_state

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä Stash the gtt_view structure into the plane state. This will become useful when we do GTT remapping as the gtt_view will not come directly from the fb anymore. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_display.c | 16 +---

[Intel-gfx] [PATCH 08/18] drm/i915: s/int plane/int color_plane/

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä To reduce the confusion between a drm plane and the planes of framebuffers let's desiginate the latter as "color plane". Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_display.c | 106 ++- drivers/gpu/drm/i915/intel_drv.h |

[Intel-gfx] [PATCH 10/18] drm/i915: Extract per-platform plane->check() functions

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä Split up intel_check_primary_plane() and intel_check_sprite_plane() into per-platform variants. This way we can get a unified behaviour between the SKL universal planes, and we stop checking for non-SKL specific scaling limits for the "sprite" planes. And we now get a natural

[Intel-gfx] [PATCH 04/18] drm/i915: Use pipe A primary plane .max_stride() as the global stride limit

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä Let's assume that the primary plane for pipe A has the highest max stride of all planes, and we'll use that as the global limit when creating a new framebuffer. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_display.c | 33 ++--- 1

[Intel-gfx] [PATCH 05/18] drm/i915: Rename the plane_state->main/aux to plane_state->color_plane[]

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä Make the main/aux surface stuff a bit more generic by using an array of structures. This will allow us to deal with both the main and aux surfaces with common code. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_display.c | 56

[Intel-gfx] [PATCH 06/18] drm/i915: Store the final plane stride in plane_state

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä Let's store the final plane stride in the plane state. This avoids having to pick betwen the normal vs. rotated stride during hardware programming. And once we get GTT remapping the plane stride will no longer match the fb stride so we'll need a place to store it anyway.

[Intel-gfx] [PATCH 03/18] drm/i915: Add .max_stride() plane hook

2018-07-19 Thread Ville Syrjala
From: Ville Syrjälä Each plane may have different stride limitations. Let's add a new plane function to retutn the maximum stride for each plane. There's going to be some use for this outside the .atomic_check() stuff hence the separate hook. Signed-off-by: Ville Syrjälä ---

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [v3,1/2] drm/i915/icl: move has_resource_streamer to GEN11_FEATURES

2018-07-19 Thread Patchwork
== Series Details == Series: series starting with [v3,1/2] drm/i915/icl: move has_resource_streamer to GEN11_FEATURES URL : https://patchwork.freedesktop.org/series/46884/ State : warning == Summary == $ dim sparse origin/drm-tip Commit: drm/i915/icl: move has_resource_streamer to

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Cache the error string (rev4)

2018-07-19 Thread Patchwork
== Series Details == Series: drm/i915: Cache the error string (rev4) URL : https://patchwork.freedesktop.org/series/46777/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4513 -> Patchwork_9718 = == Summary - SUCCESS == No regressions found. External URL:

Re: [Intel-gfx] [PATCH v3 1/2] drm/i915: remove confusing GPIO vs PCH_GPIO

2018-07-19 Thread De Marchi, Lucas
CC'ing gvt maintainers (and fixing Jani's address in CC). See below On Wed, 2018-07-18 at 13:01 +0300, Ville Syrjälä wrote: > On Tue, Jul 17, 2018 at 03:16:53PM -0700, Lucas De Marchi wrote: > > On Fri, Jul 13, 2018 at 9:10 AM Ville Syrjälä > > wrote: > > > > > > On Fri, Jul 13, 2018 at

Re: [Intel-gfx] [PATCH v3 2/2] drm/i915: kill resource streamer

2018-07-19 Thread Rodrigo Vivi
On Thu, Jul 19, 2018 at 10:05:57AM -0700, Lucas De Marchi wrote: > After disabling resource streamer on ICL (due to it actually not > existing there), I got feedback that there have been some experimental > patches for mesa to use RS years ago, but nothing ever landed or shipped > because there

[Intel-gfx] [PULL] drm-intel-next

2018-07-19 Thread Rodrigo Vivi
-19 for you to fetch changes up to ef821e3f14e868779505bf08f96afb4eade53652: drm/i915: Update DRIVER_DATE to 20180719 (2018-07-19 08:47:59 -0700) On GEM side: - GuC related fixes (Chris, Michal) - GTT read-only pages support (

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Cache the error string (rev4)

2018-07-19 Thread Patchwork
== Series Details == Series: drm/i915: Cache the error string (rev4) URL : https://patchwork.freedesktop.org/series/46777/ State : warning == Summary == $ dim sparse origin/drm-tip Commit: drm/i915: Cache the error string +drivers/gpu/drm/i915/i915_gpu_error.c:846:25: warning: Using plain

[Intel-gfx] [PATCH v3 2/2] drm/i915: kill resource streamer

2018-07-19 Thread Lucas De Marchi
After disabling resource streamer on ICL (due to it actually not existing there), I got feedback that there have been some experimental patches for mesa to use RS years ago, but nothing ever landed or shipped because there was no performance improvement. This removes it from kernel keeping the

[Intel-gfx] [PATCH v3 1/2] drm/i915/icl: move has_resource_streamer to GEN11_FEATURES

2018-07-19 Thread Lucas De Marchi
Resource streamer has been removed on GEN11 so move it to the FEATURES macro. Signed-off-by: Lucas De Marchi Reviewed-by: Daniele Ceraolo Spurio --- drivers/gpu/drm/i915/i915_gem_execbuffer.c | 2 +- drivers/gpu/drm/i915/i915_pci.c| 2 +- 2 files changed, 2 insertions(+), 2

Re: [Intel-gfx] [PATCH v3] drm/i915/dp: Give up link training clock recovery after 10 failed attempts

2018-07-19 Thread Rodrigo Vivi
On Tue, Jul 17, 2018 at 06:05:51PM -0700, Nathan Ciobanu wrote: > On Tue, Jul 17, 2018 at 03:21:17PM -0700, Dhinakaran Pandiyan wrote: > > On Mon, 2018-07-16 at 16:51 -0700, Marc Herbert wrote: > > > > > > > > > > > > > > I think the bug is with this infinite loop which is at the mercy > > > > >

[Intel-gfx] [PATCH v4] drm/i915: Cache the error string

2018-07-19 Thread Chris Wilson
Currently, we convert the error state into a string every time we read from sysfs (and sysfs reads in page size (4KiB) chunks). We do try to window the string and only capture the portion that is being read, but that means that we must always convert up to the window to find the start. For a very

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t] tests/perf_pmu: Restore runtime PM at subtest exit

2018-07-19 Thread Chris Wilson
Quoting Tvrtko Ursulin (2018-07-19 17:37:56) > From: Tvrtko Ursulin > > Restore runtime PM state (via a newly added library function) when the > test which sets it up exit. This was we avoid running all subsequent sub- > tests in the aggressive runtime PM mode. > > Signed-off-by: Tvrtko Ursulin

[Intel-gfx] [PATCH i-g-t] tests/perf_pmu: Restore runtime PM at subtest exit

2018-07-19 Thread Tvrtko Ursulin
From: Tvrtko Ursulin Restore runtime PM state (via a newly added library function) when the test which sets it up exit. This was we avoid running all subsequent sub- tests in the aggressive runtime PM mode. Signed-off-by: Tvrtko Ursulin --- lib/igt_pm.c | 13 - lib/igt_pm.h

Re: [Intel-gfx] [PATCH v5 11/13] drm/i915/icl: Add macros for MMIO of DSI transcoder registers

2018-07-19 Thread Ville Syrjälä
On Tue, Jul 10, 2018 at 03:10:12PM +0530, Madhav Chauhan wrote: > This patch adds _MMIO_DSI and _DSI_TRANS macros for accessing > DSI transcoder registers. > > Credits-to: Jani N > > Cc: Jani Nikula > Signed-off-by: Madhav Chauhan > --- > drivers/gpu/drm/i915/i915_reg.h | 5 + > 1 file

Re: [Intel-gfx] [PATCH v5 09/13] drm/i915/icl: Program TA_TIMING_PARAM registers

2018-07-19 Thread Ville Syrjälä
On Tue, Jul 10, 2018 at 03:10:10PM +0530, Madhav Chauhan wrote: > This patch programs D-PHY timing parameters for the > bus turn around flow(in escape clocks) only if dsi link > frequency <=800 MHz using DPHY_TA_TIMING_PARAM and its > identical register DSI_TA_TIMING_PARAM (inside DSI > Controller

Re: [Intel-gfx] [PATCH v5 07/13] drm/i915/icl: Program DSI clock and data lane timing params

2018-07-19 Thread Ville Syrjälä
On Tue, Jul 10, 2018 at 03:10:08PM +0530, Madhav Chauhan wrote: > This patch programs D-PHY timing parameters for the > clock and data lane (in escape clocks) of DSI > controller (DSI port 0 and 1). > These programmed timings would be used by DSI Controller > to calculate link transition latencies

Re: [Intel-gfx] [PATCH v5 01/13] drm/i915/icl: Configure lane sequencing of combo phy transmitter

2018-07-19 Thread Ville Syrjälä
On Tue, Jul 10, 2018 at 03:10:02PM +0530, Madhav Chauhan wrote: > This patch set the loadgen select and latency optimization for > aux and transmit lanes of combo phy transmitters. It will be > used for MIPI DSI HS operations. > > v2: Rebase > > Signed-off-by: Madhav Chauhan > --- >

Re: [Intel-gfx] [PATCH 1/2] drm/i915/gtt: Enable full-ppgtt by default everywhere

2018-07-19 Thread Chris Wilson
Quoting Kenneth Graunke (2018-07-17 21:02:33) > On Tuesday, July 17, 2018 2:57:50 AM PDT Chris Wilson wrote: > > We should we have all the kinks worked out and full-ppgtt now works > > reliably on gen7 (Ivybridge, Valleyview/Baytrail and Haswell). If we can > > let userspace have full control over

Re: [Intel-gfx] [PATCH v6] drm/i915: Add IOCTL Param to control data port coherency.

2018-07-19 Thread Lis, Tomasz
On 2018-07-19 09:12, Joonas Lahtinen wrote: Quoting Lis, Tomasz (2018-07-18 18:28:32) On 2018-07-18 16:42, Tvrtko Ursulin wrote: On 18/07/2018 14:24, Joonas Lahtinen wrote: Quoting Tomasz Lis (2018-07-16 16:07:16) +++ b/include/uapi/drm/i915_drm.h @@ -1456,6 +1456,13 @@ struct

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/execlists: Move the assertion we have the rpm wakeref down

2018-07-19 Thread Patchwork
== Series Details == Series: drm/i915/execlists: Move the assertion we have the rpm wakeref down URL : https://patchwork.freedesktop.org/series/46837/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4509_full -> Patchwork_9716_full = == Summary - WARNING == Minor unknown

Re: [Intel-gfx] [alsa-devel] [PATCH v2 0/3] Make the audio component binding more generic

2018-07-19 Thread Pierre-Louis Bossart
On 7/19/18 12:50 AM, Takashi Iwai wrote: On Wed, 18 Jul 2018 22:54:35 +0200, Pierre-Louis Bossart wrote: On 07/17/2018 04:26 AM, Takashi Iwai wrote: Hi, this is a preliminiary patch set to convert the existing i915 / HD-audio component binding to be applicable to other drivers like radeon

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/kvmgt: fix an error code in gvt_dma_map_page()

2018-07-19 Thread Patchwork
== Series Details == Series: drm/i915/kvmgt: fix an error code in gvt_dma_map_page() URL : https://patchwork.freedesktop.org/series/46842/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4508_full -> Patchwork_9715_full = == Summary - WARNING == Minor unknown changes

[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [v3,1/5] drm/i915/guc: Fix GuC pin bias and WOPCM initialization order

2018-07-19 Thread Patchwork
== Series Details == Series: series starting with [v3,1/5] drm/i915/guc: Fix GuC pin bias and WOPCM initialization order URL : https://patchwork.freedesktop.org/series/46843/ State : failure == Summary == = CI Bug Log - changes from CI_DRM_4510 -> Patchwork_9717 = == Summary - FAILURE ==

Re: [Intel-gfx] [PATCH] drm/i915/execlists: Move the assertion we have the rpm wakeref down

2018-07-19 Thread Chris Wilson
Quoting Tvrtko Ursulin (2018-07-19 13:14:38) > > On 19/07/2018 12:59, Chris Wilson wrote: > > Quoting Tvrtko Ursulin (2018-07-19 12:49:13) > >> > >> On 19/07/2018 08:50, Chris Wilson wrote: > >>> There's a race between idling the engine and finishing off the last > >>> tasklet (as we may kick the

Re: [Intel-gfx] [PATCH] drm/i915/execlists: Move the assertion we have the rpm wakeref down

2018-07-19 Thread Tvrtko Ursulin
On 19/07/2018 12:59, Chris Wilson wrote: Quoting Tvrtko Ursulin (2018-07-19 12:49:13) On 19/07/2018 08:50, Chris Wilson wrote: There's a race between idling the engine and finishing off the last tasklet (as we may kick the tasklets after declaring an individual engine idle). However, since

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [v3,1/5] drm/i915/guc: Fix GuC pin bias and WOPCM initialization order

2018-07-19 Thread Patchwork
== Series Details == Series: series starting with [v3,1/5] drm/i915/guc: Fix GuC pin bias and WOPCM initialization order URL : https://patchwork.freedesktop.org/series/46843/ State : warning == Summary == $ dim sparse origin/drm-tip Commit: drm/i915/guc: Fix GuC pin bias and WOPCM

Re: [Intel-gfx] [PATCH] drm/i915/execlists: Move the assertion we have the rpm wakeref down

2018-07-19 Thread Chris Wilson
Quoting Tvrtko Ursulin (2018-07-19 12:49:13) > > On 19/07/2018 08:50, Chris Wilson wrote: > > There's a race between idling the engine and finishing off the last > > tasklet (as we may kick the tasklets after declaring an individual > > engine idle). However, since we do not need to access the

Re: [Intel-gfx] [PATCH] drm/i915/execlists: Move the assertion we have the rpm wakeref down

2018-07-19 Thread Tvrtko Ursulin
On 19/07/2018 08:50, Chris Wilson wrote: There's a race between idling the engine and finishing off the last tasklet (as we may kick the tasklets after declaring an individual engine idle). However, since we do not need to access the device until we try to submit to the ELSP register

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/execlists: Move the assertion we have the rpm wakeref down

2018-07-19 Thread Chris Wilson
Quoting Tvrtko Ursulin (2018-07-19 12:42:06) > > On 19/07/2018 09:33, Patchwork wrote: > > == Series Details == > > > > Series: drm/i915/execlists: Move the assertion we have the rpm wakeref down > > URL : https://patchwork.freedesktop.org/series/46837/ > > State : failure > > > > == Summary

  1   2   >