Re: [PULL] drm-intel-next

[Daniel Vetter]

On Tue, Jul 09, 2024 at 04:27:18PM -0400, Rodrigo Vivi wrote:
> On Fri, Jun 28, 2024 at 05:46:01PM +0300, Jani Nikula wrote:
> > 
> > Hi Dave & Sima -
> > 
> > Another feature pull towards v6.11, hopefully last. This should also fix
> > the 32-bit build issue [1] seen in drm-next.
> 
> Sima, Dave,
> 
> I just noticed that we don't have this one yet in drm-next.
> 
> Anything missing or wrong with this PR?

Nothing, I just made a mess last week processing -next and then lost this
one.

Pulled into drm-next now, and thanks for the ping.
-Sima

> 
> Thanks,
> Rodrigo.
> 
> > 
> > BR,
> > Jani.
> > 
> > 
> > [1] 
> > https://lore.kernel.org/r/CAPM=9tyNGA2wEgnsKdSyjHRGVikywZLdueZj=sytmfyeunz...@mail.gmail.com
> > 
> > 
> > drm-intel-next-2024-06-28:
> > drm/i915 feature pull #2 for v6.11:
> > 
> > Features and functionality:
> > - More eDP Panel Replay enabling (Jouni)
> > - Add async flip and flip done tracepoints (Ville)
> > 
> > Refactoring and cleanups:
> > - Clean up BDW+ pipe interrupt register definitions (Ville)
> > - Prep work for DSB based plane programming (Ville)
> > - Relocate encoder suspend/shutdown helpers (Imre)
> > - Polish plane surface alignment handling (Ville)
> > 
> > Fixes:
> > - Enable more fault interrupts on TGL+/MTL+ (Ville)
> > - Fix CMRR 32-bit build (Mitul)
> > - Fix PSR Selective Update Region Scan Line Capture Indication (Jouni)
> > - Fix cursor fb unpinning (Maarten, Ville)
> > - Fix Cx0 PHY PLL state verification in TBT mode (Imre)
> > - Fix unnecessary MG DP programming on MTL+ Type-C (Imre)
> > 
> > DRM changes:
> > - Rename drm_plane_check_pixel_format() to drm_plane_has_format() and export
> >   (Ville)
> > - Add drm_vblank_work_flush_all() (Maarten)
> > 
> > Xe driver changes:
> > - Call encoder .suspend_complete() hook also on Xe (Imre)
> > 
> > BR,
> > Jani.
> > 
> > The following changes since commit d754ed2821fd9675d203cb73c4afcd593e28b7d0:
> > 
> >   Merge drm/drm-next into drm-intel-next (2024-06-19 11:38:31 +0300)
> > 
> > are available in the Git repository at:
> > 
> >   https://gitlab.freedesktop.org/drm/i915/kernel.git 
> > tags/drm-intel-next-2024-06-28
> > 
> > for you to fetch changes up to 32a120f52a4c0121bca8f2328d4680d283693d60:
> > 
> >   drm/i915/mtl: Skip PLL state verification in TBT mode (2024-06-28 
> > 12:50:52 +0300)
> > 
> > 
> > drm/i915 feature pull #2 for v6.11:
> > 
> > Features and functionality:
> > - More eDP Panel Replay enabling (Jouni)
> > - Add async flip and flip done tracepoints (Ville)
> > 
> > Refactoring and cleanups:
> > - Clean up BDW+ pipe interrupt register definitions (Ville)
> > - Prep work for DSB based plane programming (Ville)
> > - Relocate encoder suspend/shutdown helpers (Imre)
> > - Polish plane surface alignment handling (Ville)
> > 
> > Fixes:
> > - Enable more fault interrupts on TGL+/MTL+ (Ville)
> > - Fix CMRR 32-bit build (Mitul)
> > - Fix PSR Selective Update Region Scan Line Capture Indication (Jouni)
> > - Fix cursor fb unpinning (Maarten, Ville)
> > - Fix Cx0 PHY PLL state verification in TBT mode (Imre)
> > - Fix unnecessary MG DP programming on MTL+ Type-C (Imre)
> > 
> > DRM changes:
> > - Rename drm_plane_check_pixel_format() to drm_plane_has_format() and export
> >   (Ville)
> > - Add drm_vblank_work_flush_all() (Maarten)
> > 
> > Xe driver changes:
> > - Call encoder .suspend_complete() hook also on Xe (Imre)
> > 
> > 
> > Imre Deak (5):
> >   drm/i915: Move encoder suspend/shutdown helpers to intel_encoder.c
> >   drm/i915: Pass intel_display to the encoder suspend/shutdown helpers
> >   drm/xe: Use the encoder suspend helper also used by the i915 driver
> >   drm/i915/display: For MTL+ platforms skip mg dp programming
> >   drm/i915/mtl: Skip PLL state verification in TBT mode
> > 
> > Jouni Högander (12):
> >   drm/i915/psr: Set DP_PSR_SU_REGION_SCANLINE_CAPTURE bit when needed
> >   drm/i915/psr: Check panel ALPM capability for eDP Panel Replay
> >   drm/i915/psr: Inform Panel Replay source support on eDP as well
> >   drm/i915/psr: enable sink for eDP1.5 Panel Replay
> >   drm/i915/psr: Check panel Early Transport capability for eDP PR
> >   drm/i915/psr: 128b/132b Panel Replay is not supported on eDP
> >   drm/i915/psr: HW will not allow PR on eDP when HDCP enabled
> >   drm/i915/alpm: Make crtc_state as const in intel_alpm_compute_params
> >   drm/i915/psr: Perform psr2 checks related to ALPM for Panel Replay
> >   drm/i915/psr: Perform scanline indication check for Panel Replay as 
> > well
> >   drm/i915/psr: Check Early Transport for Panel Replay as well
> >   drm/i915/psr: Modify dg2_activate_panel_replay to support eDP
> > 
> > Maarten Lankhorst (2):
> >   drm: Add drm_vblank_work_flush_all().
> >   drm/i915: Use the same vblank worker for atomic unpin
> > 
> > Mitul Golani (1):
> >   

Re: [PULL] drm-intel-next

[Rodrigo Vivi]

On Fri, Jun 28, 2024 at 05:46:01PM +0300, Jani Nikula wrote:
> 
> Hi Dave & Sima -
> 
> Another feature pull towards v6.11, hopefully last. This should also fix
> the 32-bit build issue [1] seen in drm-next.

Sima, Dave,

I just noticed that we don't have this one yet in drm-next.

Anything missing or wrong with this PR?

Thanks,
Rodrigo.

> 
> BR,
> Jani.
> 
> 
> [1] 
> https://lore.kernel.org/r/CAPM=9tyNGA2wEgnsKdSyjHRGVikywZLdueZj=sytmfyeunz...@mail.gmail.com
> 
> 
> drm-intel-next-2024-06-28:
> drm/i915 feature pull #2 for v6.11:
> 
> Features and functionality:
> - More eDP Panel Replay enabling (Jouni)
> - Add async flip and flip done tracepoints (Ville)
> 
> Refactoring and cleanups:
> - Clean up BDW+ pipe interrupt register definitions (Ville)
> - Prep work for DSB based plane programming (Ville)
> - Relocate encoder suspend/shutdown helpers (Imre)
> - Polish plane surface alignment handling (Ville)
> 
> Fixes:
> - Enable more fault interrupts on TGL+/MTL+ (Ville)
> - Fix CMRR 32-bit build (Mitul)
> - Fix PSR Selective Update Region Scan Line Capture Indication (Jouni)
> - Fix cursor fb unpinning (Maarten, Ville)
> - Fix Cx0 PHY PLL state verification in TBT mode (Imre)
> - Fix unnecessary MG DP programming on MTL+ Type-C (Imre)
> 
> DRM changes:
> - Rename drm_plane_check_pixel_format() to drm_plane_has_format() and export
>   (Ville)
> - Add drm_vblank_work_flush_all() (Maarten)
> 
> Xe driver changes:
> - Call encoder .suspend_complete() hook also on Xe (Imre)
> 
> BR,
> Jani.
> 
> The following changes since commit d754ed2821fd9675d203cb73c4afcd593e28b7d0:
> 
>   Merge drm/drm-next into drm-intel-next (2024-06-19 11:38:31 +0300)
> 
> are available in the Git repository at:
> 
>   https://gitlab.freedesktop.org/drm/i915/kernel.git 
> tags/drm-intel-next-2024-06-28
> 
> for you to fetch changes up to 32a120f52a4c0121bca8f2328d4680d283693d60:
> 
>   drm/i915/mtl: Skip PLL state verification in TBT mode (2024-06-28 12:50:52 
> +0300)
> 
> 
> drm/i915 feature pull #2 for v6.11:
> 
> Features and functionality:
> - More eDP Panel Replay enabling (Jouni)
> - Add async flip and flip done tracepoints (Ville)
> 
> Refactoring and cleanups:
> - Clean up BDW+ pipe interrupt register definitions (Ville)
> - Prep work for DSB based plane programming (Ville)
> - Relocate encoder suspend/shutdown helpers (Imre)
> - Polish plane surface alignment handling (Ville)
> 
> Fixes:
> - Enable more fault interrupts on TGL+/MTL+ (Ville)
> - Fix CMRR 32-bit build (Mitul)
> - Fix PSR Selective Update Region Scan Line Capture Indication (Jouni)
> - Fix cursor fb unpinning (Maarten, Ville)
> - Fix Cx0 PHY PLL state verification in TBT mode (Imre)
> - Fix unnecessary MG DP programming on MTL+ Type-C (Imre)
> 
> DRM changes:
> - Rename drm_plane_check_pixel_format() to drm_plane_has_format() and export
>   (Ville)
> - Add drm_vblank_work_flush_all() (Maarten)
> 
> Xe driver changes:
> - Call encoder .suspend_complete() hook also on Xe (Imre)
> 
> 
> Imre Deak (5):
>   drm/i915: Move encoder suspend/shutdown helpers to intel_encoder.c
>   drm/i915: Pass intel_display to the encoder suspend/shutdown helpers
>   drm/xe: Use the encoder suspend helper also used by the i915 driver
>   drm/i915/display: For MTL+ platforms skip mg dp programming
>   drm/i915/mtl: Skip PLL state verification in TBT mode
> 
> Jouni Högander (12):
>   drm/i915/psr: Set DP_PSR_SU_REGION_SCANLINE_CAPTURE bit when needed
>   drm/i915/psr: Check panel ALPM capability for eDP Panel Replay
>   drm/i915/psr: Inform Panel Replay source support on eDP as well
>   drm/i915/psr: enable sink for eDP1.5 Panel Replay
>   drm/i915/psr: Check panel Early Transport capability for eDP PR
>   drm/i915/psr: 128b/132b Panel Replay is not supported on eDP
>   drm/i915/psr: HW will not allow PR on eDP when HDCP enabled
>   drm/i915/alpm: Make crtc_state as const in intel_alpm_compute_params
>   drm/i915/psr: Perform psr2 checks related to ALPM for Panel Replay
>   drm/i915/psr: Perform scanline indication check for Panel Replay as well
>   drm/i915/psr: Check Early Transport for Panel Replay as well
>   drm/i915/psr: Modify dg2_activate_panel_replay to support eDP
> 
> Maarten Lankhorst (2):
>   drm: Add drm_vblank_work_flush_all().
>   drm/i915: Use the same vblank worker for atomic unpin
> 
> Mitul Golani (1):
>   drm/i915/display: Consider adjusted_pixel_rate to be u64
> 
> Ville Syrjälä (28):
>   drm/i915: Use REG_BIT() for bdw+ pipe interrupts
>   drm/i915: Document bdw+ pipe interrupt bits
>   drm/i915: Sort bdw+ pipe interrupt bits
>   drm/i915: Extend GEN9_PIPE_PLANE_FLIP_DONE() to cover all universal 
> planes
>   drm/i915: Nuke the intermediate pipe fault bitmasks
>   drm/i915: Enable pipeDMC fault interrupts on tgl+
>   drm/i915: 

Re: [PULL] drm-intel-next

[Maxime Ripard]

Hi,

On Wed, Apr 17, 2024 at 09:38:55AM -0400, Rodrigo Vivi wrote:
> Another thing that it is important to highlight is that we have 3 drm level
> patches in this pull request where I didn't see any explicit recorded
> ack from you (drm maintainers) nor from drm-misc maintainers.
> The patches looks good to me and shouldn't cause conflict, so I hope it
> is okay to continue with them here instead of a big removal at this
> point.

Sigh...

I guess it's a good occasion to test
https://gitlab.freedesktop.org/drm/maintainer-tools/-/merge_requests/40

And merge it if it works.

Maxime


signature.asc
Description: PGP signature

Re: [PULL] drm-intel-next

[Jani Nikula]

On Wed, 07 Feb 2024, Jani Nikula  wrote:
> Hi Dave & Sima -
>
> drm-intel-next-2024-02-07:
> drm/i915 feature pull for v6.9:

Ping, this hasn't been merged yet.

BR,
Jani.

-- 
Jani Nikula, Intel

Re: [PULL] drm-intel-next

[Daniel Vetter]

On Thu, Nov 23, 2023 at 09:03:59PM +0200, Jani Nikula wrote:
> 
> Hi Dave & Sima -
> 
> The first i915 feature pull towards v6.8.
> 
> The one thing to single out are the major DP MST, UHBR, and DSC
> bandwidth management improvements from Imre.
> 
> Alas, they also need to be singled out because there are a number of
> updates in drm core and other drivers merged via drm-intel-next that
> will conflict with drm-next. Nothing that wasn't acked or discussed
> before, but maybe this time we erred a bit on the side of too much.
> 
> BR,
> Jani.
> 
> 
> drm-intel-next-2023-11-23:
> drm/i915 feature pull for v6.8:
> 
> Features and functionality:
> - Major DP MST improvements on bandwidth management, DSC (Imre, Stan, Ville)
> - DP panel replay enabling (Animesh, Jouni)
> - MTL C20 phy state verification (Mika)
> - MTL DP DSC fractional bpp support (Ankit, Vandita, Swati, Imre)
> - Audio fastset support (Ville)
> 
> Refactoring and cleanups:
> - Use dma fence interfaces instead of i915_sw_fence (Jouni)
> - Separate gem and display code (Jouni, Juha-Pekka)
> - AUX register macro refactoring (Jani)
> - Separate display module/device parameters from the rest (Jouni)
> - Move display capabilities debugfs under display (Vinod)
> - Makefile cleanup (Jani)
> - Register cleanups (Ville)
> - Enginer iterator cleanups (Tvrtko)
> - Move display lock inits under display/ (Jani)
> - VLV/CHV DPIO PHY register and interface refactoring (Jani)
> - DSI VBT sequence refactoring (Jani, Andy Shevchenko)
> - C10/C20 PHY PLL hardware readout and calculation abstractions (Lucas)
> - DPLL code cleanups (Ville)
> - Cleanup PXP plane protection checks (Jani)
> 
> Fixes:
> - Replace VLV/CHV DSI GPIO direct access with proper GPIO API usage (Andy 
> Shevchenko)
> - Fix VLV/CHV DSI GPIO wrong initial value (Hans de Goede)
> - Fix UHBR data, link M/N/TU and PBN values (Imre)
> - Fix HDCP state on an enable/disable cycle (Suraj)
> - Fix DP MST modeset sequence to be according to spec (Ville)
> - Improved atomicity for multi-pipe commits (Ville)
> - Update URLs in i915 MAINTAINERS entry and code (Jani)
> - Check for VGA converter presence in eDP probe (Ville)
> - Fix surface size checks (Ville)
> - Fix LNL port/phy assignment (Lucas)
> - Reset C10/C20 message bus harder to avoid sporadic failures (Mika)
> - Fix bogus VBT HDMI level shift on BDW (Ville)
> - Add workaround for LNL underruns when enabling FBC (Vinod)
> - DSB refactoring (Animesh)
> - DPT refactoring (Juha-Pekka)
> - Disable DSC on DP MST on ICL (Imre)
> - Fix PSR VSC packet setup timing (Mika)
> - Fix LUT rounding and conversions (Ville)
> 
> DRM core display changes:
> - DP MST fixes, helpers, refactoring to support bandwidth management (Imre)
> - DP MST PBN divider value refactoring and fixes (Imre)
> - DPCD register definitions (Ankit, Imre)
> - Add helper to get DSC bpp precision (Ankit)
> - Fix color LUT rounding (Ville)
> 
> BR,
> Jani.
> 
> The following changes since commit 213c43676beb5f5a63cb27a0c8e8e71035b08445:
> 
>   drm/i915/mtl: Remove the 'force_probe' requirement for Meteor Lake 
> (2023-10-18 06:23:41 +0200)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-2023-11-23

Merged to drm-next, thanks.
-Sima

> 
> for you to fetch changes up to deac453244d309ad7a94d0501eb5e0f9d8d1f1df:
> 
>   drm/i915: Fix glk+ degamma LUT conversions (2023-11-23 15:11:47 +0200)
> 
> 
> drm/i915 feature pull for v6.8:
> 
> Features and functionality:
> - Major DP MST improvements on bandwidth management, DSC (Imre, Stan, Ville)
> - DP panel replay enabling (Animesh, Jouni)
> - MTL C20 phy state verification (Mika)
> - MTL DP DSC fractional bpp support (Ankit, Vandita, Swati, Imre)
> - Audio fastset support (Ville)
> 
> Refactoring and cleanups:
> - Use dma fence interfaces instead of i915_sw_fence (Jouni)
> - Separate gem and display code (Jouni, Juha-Pekka)
> - AUX register macro refactoring (Jani)
> - Separate display module/device parameters from the rest (Jouni)
> - Move display capabilities debugfs under display (Vinod)
> - Makefile cleanup (Jani)
> - Register cleanups (Ville)
> - Enginer iterator cleanups (Tvrtko)
> - Move display lock inits under display/ (Jani)
> - VLV/CHV DPIO PHY register and interface refactoring (Jani)
> - DSI VBT sequence refactoring (Jani, Andy Shevchenko)
> - C10/C20 PHY PLL hardware readout and calculation abstractions (Lucas)
> - DPLL code cleanups (Ville)
> - Cleanup PXP plane protection checks (Jani)
> 
> Fixes:
> - Replace VLV/CHV DSI GPIO direct access with proper GPIO API usage (Andy 
> Shevchenko)
> - Fix VLV/CHV DSI GPIO wrong initial value (Hans de Goede)
> - Fix UHBR data, link M/N/TU and PBN values (Imre)
> - Fix HDCP state on an enable/disable cycle (Suraj)
> - Fix DP MST modeset sequence to be according to spec (Ville)
> - Improved atomicity for multi-pipe commits (Ville)
> - Update URLs in i915 MAINTAINERS 

Re: [PULL] drm-intel-next-fixes

[Daniel Vetter]

On Wed, Nov 08, 2023 at 04:04:14PM +0200, Jani Nikula wrote:
> 
> Hi Dave & Daniel -
> 
> I see Dave already sent the pull request for v6.7-rc1 fixes, but here's
> some more.
> 
> drm-intel-next-fixes-2023-11-08:
> drm/i915 fixes for v6.7-rc1:
> - Fix null dereference when perf interface is not available
> - Fix a -Wstringop-overflow warning
> - Fix a -Wformat-truncation warning in intel_tc_port_init
> - Flush WC GGTT only on required platforms
> - Fix MTL HBR3 rate support on C10 phy and eDP
> - Fix MTL notify_guc for multi-GT
> - Bump GLK CDCLK frequency when driving multiple pipes
> - Fix potential spectre vulnerability
> 
> BR,
> Jani.
> 
> The following changes since commit 5258dfd4a6adb5f45f046b0dd2e73c680f880d9d:
> 
>   usb: typec: altmodes/displayport: fixup drm internal api change vs new 
> user. (2023-10-27 07:55:41 +1000)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-intel 
> tags/drm-intel-next-fixes-2023-11-08

Pulled into drm-next, thanks.
-Sima

> 
> for you to fetch changes up to 9506fba463fcbdf8c8b7af3ec9ee34360df843fe:
> 
>   drm/i915/tc: Fix -Wformat-truncation in intel_tc_port_init (2023-11-06 
> 14:42:58 +0200)
> 
> 
> drm/i915 fixes for v6.7-rc1:
> - Fix null dereference when perf interface is not available
> - Fix a -Wstringop-overflow warning
> - Fix a -Wformat-truncation warning in intel_tc_port_init
> - Flush WC GGTT only on required platforms
> - Fix MTL HBR3 rate support on C10 phy and eDP
> - Fix MTL notify_guc for multi-GT
> - Bump GLK CDCLK frequency when driving multiple pipes
> - Fix potential spectre vulnerability
> 
> 
> Arnd Bergmann (1):
>   drm/i915/mtl: avoid stringop-overflow warning
> 
> Chaitanya Kumar Borah (1):
>   drm/i915/mtl: Support HBR3 rate with C10 phy and eDP in MTL
> 
> Harshit Mogalapalli (1):
>   i915/perf: Fix NULL deref bugs with drm_dbg() calls
> 
> Kunwu Chan (1):
>   drm/i915: Fix potential spectre vulnerability
> 
> Nirmoy Das (3):
>   drm/i915: Flush WC GGTT only on required platforms
>   drm/i915/mtl: Apply notify_guc to all GTs
>   drm/i915/tc: Fix -Wformat-truncation in intel_tc_port_init
> 
> Ville Syrjälä (1):
>   drm/i915: Bump GLK CDCLK frequency when driving multiple pipes
> 
>  drivers/gpu/drm/i915/display/intel_cdclk.c  | 12 ++
>  drivers/gpu/drm/i915/display/intel_dp.c |  2 +-
>  drivers/gpu/drm/i915/display/intel_tc.c | 11 ++---
>  drivers/gpu/drm/i915/gem/i915_gem_context.c |  1 +
>  drivers/gpu/drm/i915/gt/intel_ggtt.c| 35 
> -
>  drivers/gpu/drm/i915/gt/intel_rc6.c | 16 -
>  drivers/gpu/drm/i915/i915_debugfs_params.c  |  9 +---
>  drivers/gpu/drm/i915/i915_perf.c| 15 +++--
>  8 files changed, 65 insertions(+), 36 deletions(-)
> 
> -- 
> Jani Nikula, Intel

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

Re: [PULL] drm-intel-next-fixes

[Daniel Vetter]

On Thu, Apr 13, 2023 at 03:12:19PM +0300, Joonas Lahtinen wrote:
> Hi Dave & Daniel,
> 
> Just one Cc:stable fix for indirect sampler state this week on
> drm-intel-next-fixes.
> 
> Regards, Joonas
> 
> ***
> 
> drm-intel-next-fixes-2023-04-13:
> 
> Short summary of fixes pull (less than what git shortlog provides):
> 
> Just one Cc:stable fix for sampler indirect state in bindless heap.
> 
> The following changes since commit 55bf14961db9da61220e6f04bc9919c94b1a6585:
> 
>   Merge tag 'mediatek-drm-next-6.4' of 
> https://git.kernel.org/pub/scm/linux/kernel/git/chunkuang.hu/linux into 
> drm-next (2023-04-11 12:28:10 +0200)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-intel 
> tags/drm-intel-next-fixes-2023-04-13

Pulled, thanks.

> 
> for you to fetch changes up to 81900e3a37750d8c6ad705045310e002f6dd0356:
> 
>   drm/i915: disable sampler indirect state in bindless heap (2023-04-12 
> 11:36:09 +0300)
> 
> 
> Short summary of fixes pull (less than what git shortlog provides):
> 
> Just one Cc:stable fix for sampler indirect state in bindless heap.
> 
> 
> Lionel Landwerlin (1):
>   drm/i915: disable sampler indirect state in bindless heap
> 
>  drivers/gpu/drm/i915/gt/intel_gt_regs.h |  1 +
>  drivers/gpu/drm/i915/gt/intel_workarounds.c | 19 +++
>  2 files changed, 20 insertions(+)

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

Re: [PULL] drm-intel-next

[Daniel Vetter]

On Thu, Apr 06, 2023 at 10:03:51AM -0400, Rodrigo Vivi wrote:
> Hi Daniel,
> 
> Here goes drm-intel-next-2023-04-06:
> 
> - Fix DPT+shmem combo and add i915.enable_dpt modparam (Ville)
> - i915.enable_sagv module parameter (Ville)
> - Correction to QGV related register addresses (Vinod)
> - IPS debugfs per-crtc and new file for false_color (Ville)
> - More clean-up and reorganization of Display code (Jani)
> - DP DSC related fixes and improvements (Stanislav, Ankit, Suraj, Swati)
> - Make utility pin asserts more accurate (Ville)
> - Meteor Lake enabling (Daniele)
> - High refresh rate PSR fixes (Jouni)
> - Cursor and Plane chicken register fixes (Ville)
> - Align the ADL-P TypeC sequences with hardware specification (Imre)
> - Documentation build fixes and improvements to catch bugs earlier (Lee, Jani)
> - PL1 power limit hwmon entry changed to use 0 as disabled state (Ashutosh)
> - DP aux sync fix and improvements (Ville)
> - DP MST fixes and w/a (Stanislav)
> - Limit PXP drm-errors or warning on firmware API failures (Alan)
> 
> Thanks,
> Rodrigo.
> 
> The following changes since commit 46f28427f6f824b6cff06fa025a55350b7de454a:
> 
>   Merge tag 'drm-rcar-next-20230325' of 
> git://git.kernel.org/pub/scm/linux/kernel/git/pinchartl/linux into drm-next 
> (2023-03-27 18:20:20 +0200)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-2023-04-06
> 
> for you to fetch changes up to b358793c3bf231c455c55e0173256a86483997a8:
> 
>   drm/i915/wakeref: fix kernel-doc comment (2023-04-06 15:39:26 +0300)

Pulled, thanks

> 
> 
> - Fix DPT+shmem combo and add i915.enable_dpt modparam (Ville)
> - i915.enable_sagv module parameter (Ville)
> - Correction to QGV related register addresses (Vinod)
> - IPS debugfs per-crtc and new file for false_color (Ville)
> - More clean-up and reorganization of Display code (Jani)
> - DP DSC related fixes and improvements (Stanislav, Ankit, Suraj, Swati)
> - Make utility pin asserts more accurate (Ville)
> - Meteor Lake enabling (Daniele)
> - High refresh rate PSR fixes (Jouni)
> - Cursor and Plane chicken register fixes (Ville)
> - Align the ADL-P TypeC sequences with hardware specification (Imre)
> - Documentation build fixes and improvements to catch bugs earlier (Lee, Jani)
> - PL1 power limit hwmon entry changed to use 0 as disabled state (Ashutosh)
> - DP aux sync fix and improvements (Ville)
> - DP MST fixes and w/a (Stanislav)
> - Limit PXP drm-errors or warning on firmware API failures (Alan)
> 
> 
> Alan Previn (1):
>   drm/i915/pxp: limit drm-errors or warning on firmware API failures
> 
> Ankit Nautiyal (2):
>   drm/dp_helper: Add helper to check DSC support with given o/p format
>   drm/i915/dp: Check if DSC supports the given output_format
> 
> Ashutosh Dixit (1):
>   drm/i915/hwmon: Use 0 to designate disabled PL1 power limit
> 
> Daniele Ceraolo Spurio (1):
>   drm/i915/mtl: Fix MTL stolen memory GGTT mapping
> 
> Imre Deak (29):
>   drm/i915/tc: Group the TC PHY setup/query functions per platform
>   drm/i915/tc: Use the adlp prefix for ADLP TC PHY functions
>   drm/i915/tc: Rename tc_phy_status_complete() to tc_phy_is_ready()
>   drm/i915/tc: Use the tc_phy prefix for all TC PHY functions
>   drm/i915/tc: Move TC port fields to a new intel_tc_port struct
>   drm/i915/tc: Check for TC PHY explicitly in 
> intel_tc_port_fia_max_lane_count()
>   drm/i915/tc: Move the intel_tc_port struct declaration to intel_tc.c
>   drm/i915/tc: Add TC PHY hook to get the PHY HPD live status
>   drm/i915/tc: Add TC PHY hooks to get the PHY ready/owned state
>   drm/i915/tc: Add TC PHY hook to read out the PHY HW state
>   drm/i915/tc: Add generic TC PHY connect/disconnect handlers
>   drm/i915/tc: Factor out tc_phy_verify_legacy_or_dp_alt_mode()
>   drm/i915/tc: Add TC PHY hooks to connect/disconnect the PHY
>   drm/i915/tc: Fix up the legacy VBT flag only in disconnected mode
>   drm/i915/tc: Check TC mode instead of the VBT legacy flag
>   drm/i915/tc: Block/unblock TC-cold in the PHY connect/disconnect hooks
>   drm/i915/tc: Remove redundant wakeref=0 check from unblock_tc_cold()
>   drm/i915/tc: Drop tc_cold_block()/unblock()'s power domain parameter
>   drm/i915/tc: Add TC PHY hook to get the TC-cold blocking power domain
>   drm/i915/tc: Add asserts in TC PHY hooks that the required power is on
>   drm/i915/tc: Add TC PHY hook to init the PHY
>   drm/i915/adlp/tc: Use the DE HPD ISR register for hotplug detection
>   drm/i915/tc: Get power ref for reading the HPD live status register
>   drm/i915/tc: Don't connect the PHY in intel_tc_port_connected()
>   drm/i915/adlp/tc: Align the connect/disconnect PHY sequence with bspec
>   drm/i915: Move shared DPLL disabling into 

Re: [PULL] drm-intel-next

[Daniel Vetter]

On Thu, Mar 23, 2023 at 04:43:22PM -0400, Rodrigo Vivi wrote:
> Hi Daniel,
> 
> Here goes drm-intel-next-2023-03-23:
> 
> Core Changes:
> - drm: Add SDP Error Detection Configuration Register (Arun)
> 
> Driver Changes:
> - Meteor Lake enabling and fixes (RK, Jose, Madhumitha)
> - Lock the fbdev obj before vma pin (Tejas)
> - DSC fixes (Stanislav)
> - Fixes and clean-up on opregion code (Imre)
> - More wm/vblank stuff (Ville)
> - More general display code organization (Jani)
> - DP Fixes (Stanislav, Ville)
> - Introduce flags to ignore long HPD and link training issues \
>   for handling spurious issues on CI (Vinod)
> - Plane cleanups and extra registers (Ville)
> - Update audio keepalive clock values (Clint)
> - Rename find_section to bdb_find_section (Maarten)
> - DP SDP CRC16 for 128b132b link layer (Arun)
> - Fix various issues with noarm register writes (Ville)
> - Fix a few TypeC / MST issues (Imre)
> - Create GSC submission targeting HDCP and PXP usages on MTL+ (Suraj)
> - Enable HDCP2.x via GSC CS (Suraj)
> 
> Thanks,
> Rodrigo.
> 
> The following changes since commit 4b736ed40583631e0cf32c55dbc1e5ec0434a74b:
> 
>   drm/i915: Get rid of the gm45 HPD live state nonsense (2023-03-07 19:09:20 
> +0200)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-2023-03-23

Pulled, thanks.

> 
> for you to fetch changes up to 883631771038d1b0c10c0929e31bbd5ffb5e682c:
> 
>   drm/i915/mtl: Add HDCP GSC interface (2023-03-23 12:17:22 +0530)
> 
> 
> Core Changes:
> - drm: Add SDP Error Detection Configuration Register (Arun)
> 
> Driver Changes:
> - Meteor Lake enabling and fixes (RK, Jose, Madhumitha)
> - Lock the fbdev obj before vma pin (Tejas)
> - DSC fixes (Stanislav)
> - Fixes and clean-up on opregion code (Imre)
> - More wm/vblank stuff (Ville)
> - More general display code organization (Jani)
> - DP Fixes (Stanislav, Ville)
> - Introduce flags to ignore long HPD and link training issues \
>   for handling spurious issues on CI (Vinod)
> - Plane cleanups and extra registers (Ville)
> - Update audio keepalive clock values (Clint)
> - Rename find_section to bdb_find_section (Maarten)
> - DP SDP CRC16 for 128b132b link layer (Arun)
> - Fix various issues with noarm register writes (Ville)
> - Fix a few TypeC / MST issues (Imre)
> - Create GSC submission targeting HDCP and PXP usages on MTL+ (Suraj)
> - Enable HDCP2.x via GSC CS (Suraj)
> 
> 
> Ankit Nautiyal (1):
>   drm/i915/dp: Don't roundup max bpp, while computing compressed bpp
> 
> Anshuman Gupta (1):
>   drm/i915/hdcp: Use generic names for HDCP helpers and structs
> 
> Arun R Murthy (2):
>   drm: Add SDP Error Detection Configuration Register
>   i915/display/dp: SDP CRC16 for 128b132b link layer
> 
> Clint Taylor (1):
>   drm/i915/audio: update audio keepalive clock values
> 
> Imre Deak (18):
>   drm/i915/opregion: Fix opregion setup during system resume on platforms 
> without display
>   drm/i915/opregion: Cleanup opregion after errors during driver loading
>   drm/i915/opregion: Register display debugfs later, after initialization 
> steps
>   drm/i915/opregion: Fix CONFIG_ACPI=n builds adding missing 
> intel_opregion_cleanup() prototype
>   drm/i915/tc: Abort DP AUX transfer on a disconnected TC port
>   drm/i915/tc: Fix TC port link ref init for DP MST during HW readout
>   drm/i915/tc: Fix the ICL PHY ownership check in TC-cold state
>   drm/i915/tc: Fix system resume MST mode restore for DP-alt sinks
>   drm/i915/tc: Wait for IOM/FW PHY initialization of legacy TC ports
>   drm/i915/tc: Factor out helpers converting HPD mask to TC mode
>   drm/i915/tc: Fix target TC mode for a disconnected legacy port
>   drm/i915/tc: Fix TC mode for a legacy port if the PHY is not ready
>   drm/i915/tc: Fix initial TC mode on disabled legacy ports
>   drm/i915/tc: Make the TC mode readout consistent in all PHY states
>   drm/i915/tc: Assume a TC port is legacy if VBT says the port has HDMI
>   drm/i915: Add encoder hook to get the PLL type used by TC ports
>   drm/i915/tc: Factor out a function querying active links on a TC port
>   drm/i915/tc: Check the PLL type used by an enabled TC port
> 
> Jani Nikula (6):
>   drm/i915/debugfs: move IPS debugfs to hsw_ips.c
>   drm/i915/psr: move PSR debugfs to intel_psr.c
>   drm/i915/psr: switch PSR debugfs to struct intel_connector
>   drm/i915/psr: clean up PSR debugfs sink status error handling
>   drm/i915/debugfs: switch crtc debugfs to struct intel_crtc
>   drm/i915/debugfs: add crtc i915_pipe debugfs file
> 
> José Roberto de Souza (1):
>   drm/i915/display/mtl: Program latch to phy reset
> 
> Maarten Lankhorst (1):
>   drm/i915/bios: Rename find_section to find_bdb_section
> 
> Madhumitha 

Re: [PULL] drm-intel-next

[Jani Nikula]

On Mon, 29 Aug 2022, Jani Nikula  wrote:
> Hi Dave & Daniel -
>
> drm-intel-next-2022-08-29:
> drm/i915 feature pull for v6.1:

Hey, I started making another pull request, but realized you haven't
pulled this one yet. Anything the matter, or just fell between the
cracks?

BR,
Jani.


>
> Features and functionality:
> - Early Meteorlake (MTL) enabling (José, Radhakrishna, Clint, Imre, Vandita, 
> Ville, Jani)
> - Support more HDMI pixel clock frequencies on DG2 (Clint)
> - Sanity check PCI BARs (Piotr Piórkowski)
> - Enable DC5 on DG2 (Anusha)
> - DG2 DMC firmware version bump to v2.07 (Madhumitha)
> - New ADL-S PCI ID (José)
>
> Refactoring and cleanups:
> - Add display sub-struct to struct drm_i915_private (Jani)
> - Add initial runtime info to device info (Jani)
> - Split out HDCP and backlight registers to separate files (Jani)
>
> Fixes:
> - Skip wm/ddb readout for disabled pipes (Ville)
> - HDMI port timing quirk for GLK ECS Liva Q2 (Diego Santa Cruz)
> - Fix bw init null pointer dereference (Łukasz Bartosik)
> - Disable PPS power hook for DP AUX backlight (Jouni)
> - Avoid warnings on registering multiple backlight devices (Arun)
> - Fix dual-link DSI backlight and CABC ports for display 11+ (Jani)
> - Fix Type-C PHY ownership programming in HDMI legacy mode (Imre)
> - Fix unclaimed register access while loading PIPEDMC-C/D (Imre)
> - Bump up CDCLK for DG2 (Stan)
> - Prune modes that require HDMI 2.1 FRL (Ankit)
> - Disable FBC when PSR1 is enabled in display 12-13 (Matt)
> - Fix TGL+ HDMI transcoder clock and DDI BUF disable order (Imre)
> - Disable PSR before disable pipe (José)
> - Disable DMC handlers during firmware loading/disabling on display 12+ (Imre)
> - Disable clock gating for PIPEDMC-A/B as a workaround (Imre)
>
> Merges:
> - Two drm-next backmerges (Rodrigo, Jani)
>
> BR,
> Jani.
>
> The following changes since commit 2c2d7a67defa198a8b8148dbaddc9e5554efebc8:
>
>   Merge tag 'drm-intel-gt-next-2022-08-24' of 
> git://anongit.freedesktop.org/drm/drm-intel into drm-next (2022-08-26 
> 10:03:43 +1000)
>
> are available in the Git repository at:
>
>   git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-2022-08-29
>
> for you to fetch changes up to 917bda9ab155032a02be1a57ebd4d949ae9e1528:
>
>   Merge drm/drm-next into drm-intel-next (2022-08-29 15:14:59 +0300)
>
> 
> drm/i915 feature pull for v6.1:
>
> Features and functionality:
> - Early Meteorlake (MTL) enabling (José, Radhakrishna, Clint, Imre, Vandita, 
> Ville, Jani)
> - Support more HDMI pixel clock frequencies on DG2 (Clint)
> - Sanity check PCI BARs (Piotr Piórkowski)
> - Enable DC5 on DG2 (Anusha)
> - DG2 DMC firmware version bump to v2.07 (Madhumitha)
> - New ADL-S PCI ID (José)
>
> Refactoring and cleanups:
> - Add display sub-struct to struct drm_i915_private (Jani)
> - Add initial runtime info to device info (Jani)
> - Split out HDCP and backlight registers to separate files (Jani)
>
> Fixes:
> - Skip wm/ddb readout for disabled pipes (Ville)
> - HDMI port timing quirk for GLK ECS Liva Q2 (Diego Santa Cruz)
> - Fix bw init null pointer dereference (Łukasz Bartosik)
> - Disable PPS power hook for DP AUX backlight (Jouni)
> - Avoid warnings on registering multiple backlight devices (Arun)
> - Fix dual-link DSI backlight and CABC ports for display 11+ (Jani)
> - Fix Type-C PHY ownership programming in HDMI legacy mode (Imre)
> - Fix unclaimed register access while loading PIPEDMC-C/D (Imre)
> - Bump up CDCLK for DG2 (Stan)
> - Prune modes that require HDMI 2.1 FRL (Ankit)
> - Disable FBC when PSR1 is enabled in display 12-13 (Matt)
> - Fix TGL+ HDMI transcoder clock and DDI BUF disable order (Imre)
> - Disable PSR before disable pipe (José)
> - Disable DMC handlers during firmware loading/disabling on display 12+ (Imre)
> - Disable clock gating for PIPEDMC-A/B as a workaround (Imre)
>
> Merges:
> - Two drm-next backmerges (Rodrigo, Jani)
>
> 
> Ankit Nautiyal (1):
>   drm/i915/hdmi: Prune modes that require HDMI2.1 FRL
>
> Anusha Srivatsa (3):
>   drm/i915/display: Cleanup intel_phy_is_combo()
>   drm/i915: Pass drm_i915_private struct instead of gt for 
> gen11_gu_misc_irq_handler/ack()
>   drm/i915/dg2: Add support for DC5 state
>
> Arun R Murthy (1):
>   drm/i915/display: avoid warnings when registering dual panel backlight
>
> Bo Liu (1):
>   drm/i915/irq: Fix a "the the" typo
>
> Clint Taylor (1):
>   drm/i915/mtl: Fix rawclk for Meteorlake PCH
>
> Diego Santa Cruz (1):
>   drm/i915/glk: ECS Liva Q2 needs GLK HDMI port timing quirk
>
> Imre Deak (6):
>   drm/i915/tgl+: Fix HDMI transcoder clock vs. DDI BUF disabling order
>   drm/i915/d12+: Disable DMC handlers during loading/disabling the 
> firmware
>   drm/i915/d13: Add Wa_16015201720 disabling clock gating for PIPEDMC-A/B
>   drm/i915/xelpd: Fix unclaimed accesses while loading 

Re: [PULL] drm-intel-next -> drm-intel-gt-next cross-merge sync

[Tvrtko Ursulin]

On 20/05/2022 12:02, Jani Nikula wrote:


Hi all,

This is for Tvrtko to pull to cross-merge sync drm-intel-next to
drm-intel-gt-next.

Dave, Daniel, IIUC this is what you prefer over having topic branches
for all the small things that are needed between drm-intel branches. I
don't think we've done this direct cross-merge before, so decided to
send a pull request for transparency. Do you want us to do it this way
going forward, or can we just do direct merges in git branches without
tagged pull requests?

Looks like drm-intel-next is ahead wrt backmerges too, so this pulls in
some drm-next to drm-intel-gt-next too.


Pulled, thanks Jani for explaining the situation in detail.

Regards,

Tvrtko



BR,
Jani.


PS. For future reference, generated using:
$ dim pull-request drm-intel-next drm-intel/drm-intel-gt-next


The following changes since commit c54b39a565227538c52ead2349eb17d54aadd6f7:

   Merge tag 'drm-intel-next-2022-04-13-1' of 
git://anongit.freedesktop.org/drm/drm-intel into drm-next (2022-04-14 12:03:09 
+1000)

are available in the Git repository at:

   git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-2022-05-20

for you to fetch changes up to 5f38c3fb55ce3814b4353320d7a205068a420e48:

   drm/i915/pcode: Add a couple of pcode helpers (2022-05-20 09:11:45 +0100)


drm/i915 drm-intel-next -> drm-intel-gt-next cross-merge sync


Anshuman Gupta (1):
   drm/i915: Use drm_dbg for rpm logging

Anusha Srivatsa (2):
   drm/i915/dmc: Load DMC on DG2
   drm/i915/dmc: Add MMIO range restrictions

Arunpravin Paneer Selvam (2):
   drm/amdgpu: add drm buddy support to amdgpu
   drm: add a check to verify the size alignment

Ashutosh Dixit (2):
   drm/i915: Introduce has_media_ratio_mode
   drm/i915/pcode: Extend pcode functions for multiple gt's

Biju Das (1):
   drm: bridge: adv7511: Enable DRM_BRIDGE_OP_HPD based on HPD interrupt

Changcheng Deng (1):
   fbcon: use min() to make code cleaner

Chen-Yu Tsai (4):
   dt-bindings: vendor-prefixes: Add prefix for SINO WEALTH Eletronics Ltd.
   dt-bindings: display: ssd1307fb: Add entry for SINO WEALTH SH1106
   drm/ssd130x: Support page addressing mode
   drm/ssd130x: Add support for SINO WEALTH SH1106

Christian König (16):
   dma-buf: add enum dma_resv_usage v4
   dma-buf: specify usage while adding fences to dma_resv obj v7
   dma-buf & drm/amdgpu: remove dma_resv workaround
   dma-buf: add DMA_RESV_USAGE_KERNEL v3
   drm/amdgpu: use DMA_RESV_USAGE_KERNEL
   drm/radeon: use DMA_RESV_USAGE_KERNEL
   RDMA: use DMA_RESV_USAGE_KERNEL
   dma-buf: add DMA_RESV_USAGE_BOOKKEEP v3
   dma-buf: wait for map to complete for static attachments
   drm/i915: drop bo->moving dependency
   drm/ttm: remove bo->moving
   dma-buf: drop seq count based update
   seqlock: drop seqcount_ww_mutex_t
   futex: add missing rtmutex.h include
   drm/ttm: fix logic inversion in ttm_eu_reserve_buffers
   drm/ttm: fix kerneldoc for ttm_lru_bulk_move

Christoph Hellwig (27):
   drm/i915/gvt: remove module refcounting in 
intel_gvt_{,un}register_hypervisor
   drm/i915/gvt: remove enum hypervisor_type
   drm/i915/gvt: rename intel_vgpu_ops to intel_vgpu_mdev_ops
   drm/i915/gvt: move the gvt code into kvmgt.ko
   drm/i915/gvt: remove intel_gvt_ops
   drm/i915/gvt: remove the map_gfn_to_mfn and set_trap_area ops
   drm/i915/gvt: remove the unused from_virt_to_mfn op
   drm/i915/gvt: merge struct kvmgt_vdev into struct intel_vgpu
   drm/i915/gvt: merge struct kvmgt_guest_info into strut intel_vgpu
   drm/i915/gvt: remove vgpu->handle
   drm/i915/gvt: devirtualize ->{read,write}_gpa
   drm/i915/gvt: devirtualize ->{get,put}_vfio_device
   drm/i915/gvt: devirtualize ->set_edid and ->set_opregion
   drm/i915/gvt: devirtualize ->detach_vgpu
   drm/i915/gvt: devirtualize ->inject_msi
   drm/i915/gvt: devirtualize ->is_valid_gfn
   drm/i915/gvt: devirtualize ->gfn_to_mfn
   drm/i915/gvt: devirtualize ->{enable,disable}_page_track
   drm/i915/gvt: devirtualize ->dma_{,un}map_guest_page
   drm/i915/gvt: devirtualize dma_pin_guest_page
   drm/i915/gvt: remove struct intel_gvt_mpt
   drm/i915/gvt: remove the extra vfio_device refcounting for dmabufs
   drm/i915/gvt: streamline intel_vgpu_create
   drm/i915/gvt: pass a struct intel_vgpu to the vfio read/write helpers
   drm/i915/gvt: remove kvmgt_guest_{init,exit}
   drm/i915/gvt: convert to use vfio_register_emulated_iommu_dev
   drm/i915/gvt: merge gvt.c into kvmgvt.c

Colin Ian King (1):
   drm: sti: fix spelling mistake: rejec -> rejection

Dale B Stimson (1):
   drm/i915/pcode: Add a couple of pcode helpers

Daniel Vetter (18):
   fbcon: delete a few unneeded forward decl
 

Re: [PULL] drm-intel-next-fixes

[Daniel Vetter]

On Thu, Jan 13, 2022 at 09:33:03AM +, Tvrtko Ursulin wrote:
> 
> Hi Dave and Daniel,
> 
> A few fixes for the merge window.
> 
> One dealing with runtime PM handling on the PXP unbind path and a few
> regarding the newly added TTM backend support.
> 
> Regards,
> 
> Tvrtko
> 
> ---
> 
> drm-intel-next-fixes-2022-01-13:
> - Hold runtime PM wakelock during PXP unbind (Juston Li)
> - Three fixes for the TTM backend fault handling (Matthew Auld)
> - Make sure to unmap when purging in the TTM backend (Matthew Auld)
> The following changes since commit c65fe9cbbfd61dbc12868f9ed4940c80fcb249e8:
> 
>   drm/i915/fbc: Remember to update FBC state even when not reallocating CFB 
> (2021-12-27 11:46:48 +0200)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-intel 
> tags/drm-intel-next-fixes-2022-01-13

Pulled, thanks.
-Daniel

> 
> for you to fetch changes up to 6ef295e34297433c78ea02dfcf1c649a769050bb:
> 
>   drm/i915/ttm: ensure we unmap when purging (2022-01-10 14:00:47 +)
> 
> 
> - Hold runtime PM wakelock during PXP unbind (Juston Li)
> - Three fixes for the TTM backend fault handling (Matthew Auld)
> - Make sure to unmap when purging in the TTM backend (Matthew Auld)
> 
> 
> Juston Li (1):
>   drm/i915/pxp: Hold RPM wakelock during PXP unbind
> 
> Matthew Auld (4):
>   drm/i915: don't call free_mmap_offset when purging
>   drm/i915/ttm: only fault WILLNEED objects
>   drm/i915/ttm: add unmap_virtual callback
>   drm/i915/ttm: ensure we unmap when purging
> 
>  drivers/gpu/drm/i915/gem/i915_gem_mman.c   |  3 +++
>  drivers/gpu/drm/i915/gem/i915_gem_object_types.h   |  1 +
>  drivers/gpu/drm/i915/gem/i915_gem_pages.c  |  1 -
>  drivers/gpu/drm/i915/gem/i915_gem_ttm.c| 27 
> +-
>  drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c | 18 ---
>  drivers/gpu/drm/i915/pxp/intel_pxp_tee.c   |  5 +++-
>  6 files changed, 38 insertions(+), 17 deletions(-)

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

Re: [PULL] drm-intel-next

[Ville Syrjälä]

On Wed, Jan 27, 2021 at 09:08:22AM -0500, Rodrigo Vivi wrote:
> Hi Dave and Daniel,
> 
> Hopefully this is the last pull request towards 5.12.
> 
> Please notice this contains a drm/framebuffer change needed for
> supporting clear color support for TGL Render Decompression.
> 
> Here goes drm-intel-next-2021-01-27:
> 
...
> - Async flips for all ilk+ platforms (Ville)

Not quite yet. Still missing one rb so couldn't push the full thing.
So still limited to skl+ I'm afraid.

-- 
Ville Syrjälä
Intel
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next

[Daniel Vetter]

On Mon, Jan 04, 2021 at 01:10:18PM -0800, Rodrigo Vivi wrote:
> Hi Dave and Daniel,
> 
> Happy New Year.
> 
> Here goes the first pull request targeting 5.12.
> 
> drm-intel-next-2021-01-04:
> - Display hotplug fix for gen2/gen3 (Chris)
> - Remove trailing semicolon (Tom)
> - Suppress display warnings for old ifwi presend on our CI (Chris)
> - OA/Perf related workaround (Lionel)
> - Replace I915_READ/WRITE per new uncore and display read/write functions 
> (Jani)\
> .
> - PSR improvements (Jose)
> - HDR and other color changes on LSPCON (Uma, Ville)
> - FBC fixes for TGL (Uma)
> - Record plane update times for debugging (Chris)
> - Refactor panel backlight control functions (Dave)
> - Display power improvements (Imre)
> - Add VRR register definition (Manasi)
> - Atomic modeset improvements for bigjoiner pipes (Ville)
> - Switch off the scanout during driver unregister (Chris)
> - Clean-up DP's FEW enable (Manasi)
> - Fix VDSCP slice count (Manasi)
> - Fix and clean up around rc_model_size for DSC (Jani)
> - Remove Type-C noisy debug warn message (Sean)
> - Display HPD code clean-up (Ville)
> - Refactor Intel Display (Dave)
> - Start adding support for Intel's eDP backlight controls (Lyude)

Pulled, thanks.
-Daniel

> 
> Thanks,
> Rodrigo.
> 
> The following changes since commit b3bf99daaee96a141536ce5c60a0d6dba6ec1d23:
> 
>   drm/i915/display: Defer initial modeset until after GGTT is initialised 
> (2020-11-26 11:01:52 +)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-2021-01-04
> 
> for you to fetch changes up to b3304591f14b437b6bccd8dbff06006c11837031:
> 
>   drm/i915/dp: Track pm_qos per connector (2020-12-30 21:22:55 +)
> 
> 
> - Display hotplug fix for gen2/gen3 (Chris)
> - Remove trailing semicolon (Tom)
> - Suppress display warnings for old ifwi presend on our CI (Chris)
> - OA/Perf related workaround (Lionel)
> - Replace I915_READ/WRITE per new uncore and display read/write functions 
> (Jani)\
> .
> - PSR improvements (Jose)
> - HDR and other color changes on LSPCON (Uma, Ville)
> - FBC fixes for TGL (Uma)
> - Record plane update times for debugging (Chris)
> - Refactor panel backlight control functions (Dave)
> - Display power improvements (Imre)
> - Add VRR register definition (Manasi)
> - Atomic modeset improvements for bigjoiner pipes (Ville)
> - Switch off the scanout during driver unregister (Chris)
> - Clean-up DP's FEW enable (Manasi)
> - Fix VDSCP slice count (Manasi)
> - Fix and clean up around rc_model_size for DSC (Jani)
> - Remove Type-C noisy debug warn message (Sean)
> - Display HPD code clean-up (Ville)
> - Refactor Intel Display (Dave)
> - Start adding support for Intel's eDP backlight controls (Lyude)
> 
> 
> Chris Wilson (6):
>   Revert "drm/i915: re-order if/else ladder for hpd_irq_setup"
>   drm/i915/display: Suppress "Combo PHY A HW state changed unexpectedly"
>   drm/i915/display: Record the plane update times for debugging
>   drm/i915/gem: Spring clean debugfs
>   drm/i915: Disable outputs during unregister
>   drm/i915/dp: Track pm_qos per connector
> 
> Dave Airlie (6):
>   drm/i915: refactor panel backlight control functions. (v2)
>   drm/i915/display: move needs_modeset to an inline in header
>   drm/i915/display: move to_intel_frontbuffer to header
>   drm/i915/display: fix misused comma
>   drm/i915: refactor cursor code out of i915_display.c
>   drm/i915: refactor i915 plane code into separate file.
> 
> Imre Deak (10):
>   drm/i915: Use CRTC index consistently during getting/putting CRTC power 
> domains
>   drm/i915: Factor out helpers to get/put a set of tracked power domains
>   drm/i915: Track power references taken for enabled CRTCs
>   drm/i915/ddi: Track power reference taken for encoder DDI IO use
>   drm/i915/ddi: Track power reference taken for encoder main lane AUX use
>   drm/i915: Track power reference taken for eDP VDD
>   drm/i915: Rename power_domains.wakeref to init_wakeref
>   drm/i915: Track power reference taken to disable power well 
> functionality
>   drm/i915: Make intel_display_power_put_unchecked() an internal-only 
> function
>   drm/i915/icl: Fix initing the DSI DSC power refcount during HW readout
> 
> Jani Nikula (15):
>   drm/i915/debugfs: remove RPS autotuning details from i915_rps_boost_info
>   drm/i915: remove last traces of I915_READ_FW() and I915_WRITE_FW()
>   drm/i915/cdclk: prefer intel_de_write() over I915_WRITE()
>   drm/i915/debugfs: remove the i915_cache_sharing debugfs file
>   drm/i915/debugfs: replace I915_READ() with intel_uncore_read()
>   drm/i915/suspend: replace I915_READ()/WRITE() with 
> intel_de_read()/write()
>   drm/i915/pm: replace I915_READ()/WRITE() with 
> intel_uncore_read()/write()
>   

Re: [PULL] drm-intel-next-fixes

[Daniel Vetter]

On Fri, Dec 18, 2020 at 05:04:09PM +0200, Jani Nikula wrote:
> 
> Hi Dave & Daniel -
> 
> drm-intel-next-fixes-2020-12-18:
> drm/i915 fixes for the merge window

Pulled, thanks a lot.
-Daniel

> 
> 
> BR,
> Jani.
> 
> The following changes since commit efd3043790c6e92f0bbe1fe385db9b544131c59c:
> 
>   Merge tag 'amd-drm-fixes-5.11-2020-12-16' of 
> git://people.freedesktop.org/~agd5f/linux into drm-next (2020-12-16 23:25:51 
> +0100)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-intel 
> tags/drm-intel-next-fixes-2020-12-18
> 
> for you to fetch changes up to 046f70d31ddb2069941aec54966fec5b7fbc7b7b:
> 
>   drm/i915/tgl: Fix REVID macros for TGL to fetch correct stepping 
> (2020-12-18 12:30:10 +0200)
> 
> 
> drm/i915 fixes for the merge window
> 
> 
> Aditya Swarup (1):
>   drm/i915/tgl: Fix REVID macros for TGL to fetch correct stepping
> 
> Chris Wilson (2):
>   Revert "drm/i915: re-order if/else ladder for hpd_irq_setup"
>   drm/i915: Fix mismatch between misplaced vma check and vma insert
> 
> Lionel Landwerlin (1):
>   drm/i915/perf: also include Gen11 in OATAILPTR workaround
> 
>  drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c |  2 +-
>  drivers/gpu/drm/i915/i915_drv.h| 12 ++--
>  drivers/gpu/drm/i915/i915_irq.c| 27 
> ++
>  drivers/gpu/drm/i915/i915_perf.c   |  2 +-
>  4 files changed, 23 insertions(+), 20 deletions(-)
> 
> -- 
> Jani Nikula, Intel Open Source Graphics Center

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next-fixes

[Jani Nikula]

On Mon, 10 Aug 2020, Dave Airlie  wrote:
> Like this stuff has been getting past me for years but I'm not happy
> about it anymore, I'm going to just be grumpy asshole going forward.
> If we introduced scheduler races in linux-next, I want to see reverts,
> and reverts only until we stopped introducing them.

I'll redo the fixes once we have dinq sorted out.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Graphics Center
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next-fixes

[Dave Airlie]

On Fri, 31 Jul 2020 at 02:26, Joonas Lahtinen
 wrote:
>
> Hi Dave & Daniel,
>
> (Covering for Jani here for drm-intel-next-fixes)
>
> 5 new commits over drm-intel-next here.
>
> Fix for KASAN detected race condition and linux-next scheduler
> WARNs. Patch to avoid IRQ spinlock and Cc: stable PMU refcount
> update.
>
> CI machinery needed some kicking, so results didn't appear
> at first. BAT now passed, shards should shortly be availabl
>
> CI_DINF_202 at 
> https://intel-gfx-ci.01.org/tree/drm-intel-next-fixes/combined-alt.html?
>

I've been sitting on this, but I really am having trouble convincing
myself to pull it.

I've pulled it 2-3 times now, looked at it a few times, unpulled it.

drm/i915: Be wary of data races when reading the active execlists

To me reads, like we avoided locking, we tried to fly too close to the
sun, it burned us and we fell back to earth. Instead of not flying too
close to the sun, we just stuck some bandaids on the wings.

drm/i915: Remove i915_request.lock requirement for execution callbacks

at least it stops opencoding an __llist_add function that was likely
dubious to begin with, but I'm having trouble convincing myself this
is a "fix" for anything other than we dug a hole, CI maybe coughed a
bit, keep digging.

drm/i915: Filter wake_flags passed to default_wake_function

I replied to elsewhere, but the whole (pos->func ==
autoremove_wake_function) idiom just seems wrong, I'd probably have to
point it out to Linus to ask what is right, but we already do it
elsewhere in the file, makes me wonder who reviewed this in the first
place.

Like this stuff has been getting past me for years but I'm not happy
about it anymore, I'm going to just be grumpy asshole going forward.
If we introduced scheduler races in linux-next, I want to see reverts,
and reverts only until we stopped introducing them.

drm/i915: Copy default modparams to mock i915_device
drm/i915: Provide the perf pmu.module

are probably acceptable.

Dave.





> Regards, Joonas
>
> ***
>
> drm-intel-next-fixes-2020-07-30-1:
>
> - Fixes for linux-next introduced scheduler races
> - Fix for KASAN race in active execlists
> - Fix for previous breadcrumb breadcrumb code to avoid IRQ spinlock
> - Cc: stable patch for PMU refcount
>
> The following changes since commit d524b87f77364db096855d7eb714ffacec974ddf:
>
>   drm/i915: Update DRIVER_DATE to 20200702 (2020-07-02 21:25:28 +0300)
>
> are available in the Git repository at:
>
>   git://anongit.freedesktop.org/drm/drm-intel 
> tags/drm-intel-next-fixes-2020-07-30-1
>
> for you to fetch changes up to 6bd0b413618ffb50f900ec770283d8c2217d069f:
>
>   drm/i915: Filter wake_flags passed to default_wake_function (2020-07-30 
> 15:33:37 +0300)
>
> 
> - Fixes for linux-next introduced scheduler races
> - Fix for KASAN race in active execlists
> - Fix for previous breadcrumb breadcrumb code to avoid IRQ spinlock
> - Cc: stable patch for PMU refcount
>
> 
> Abdiel Janulgue (2):
>   drm/i915/dg1: add initial DG-1 definitions
>   drm/i915/dg1: Add DG1 PCI IDs
>
> Anshuman Gupta (1):
>   drm/i915/hdcp: Update CP as per the kernel internal state
>
> Anusha Srivatsa (1):
>   drm/i915/dg1: Remove SHPD_FILTER_CNT register programming
>
> Chris Wilson (27):
>   drm/i915/gem: Only revoke the GGTT mmappings on aperture detiling 
> changes
>   drm/i915/gem: Only revoke mmap handlers if active
>   drm/i915/gem: Drop forced struct_mutex from shrinker_taints_mutex
>   drm/i915: Also drop vm.ref along error paths for vma construction
>   drm/i915/gem: Split the context's obj:vma lut into its own mutex
>   drm/i915: Export ppgtt_bind_vma
>   drm/i915/gt: Pin the rings before marking active
>   drm/i915: Update dma-attributes for our sg DMA
>   drm/i915/gem: Unpin idle contexts from kswapd reclaim
>   drm/i915/gt: Replace opencoded i915_gem_object_pin_map()
>   drm/i915: Release shortlived maps of longlived objects
>   drm/i915: Remove i915_gem_object_get_dirty_page()
>   drm/i915/gt: Optimise aliasing-ppgtt allocations
>   drm/i915/selftest: Check that GPR are restored across noa_wait
>   drm/i915/gt: Be defensive in the face of false CS events
>   drm/i915: Pull printing GT capabilities on error to err_print_gt
>   drm/i915/gt: Always reset the engine, even if inactive, on execlists 
> failure
>   drm/i915/gt: Ignore irq enabling on the virtual engines
>   drm/i915/gt: Only swap to a random sibling once upon creation
>   drm/i915: Skip signaling a signaled request
>   drm/i915/gt: Trace placement of timeline HWSP
>   drm/i915/gt: Assert the kernel context is using the HWSP
>   drm/i915: Provide the perf pmu.module
>   drm/i915: Be wary of data races when reading the active execlists
>   drm/i915: Remove i915_request.lock requirement for execution 

Re: [PULL] drm-intel-next

[Daniel Vetter]

On Wed, Jul 15, 2020 at 3:34 PM Jani Nikula  wrote:
>
>
> Argh, failed to mention:
>
> On Wed, 15 Jul 2020, Jani Nikula  wrote:
> > Lee Shawn C (1):
> >   drm/i915/mst: filter out the display mode exceed sink's capability
>
> The above depends on:
>
> > Lyude Paul (1):
> >   drm/probe_helper: Add drm_connector_helper_funcs.mode_valid_ctx
>
> Which has changes outside of i915:
>
> >  drivers/gpu/drm/drm_crtc_helper_internal.h |   7 +-
> >  drivers/gpu/drm/drm_probe_helper.c |  97 +--
>
> and does not have an explicit ack recorded, though drm-misc maintainers
> have been Cc'd. :(
>
> I decided they were benign enough, but needed to be mentioned.

Yeah looks all fine, adding Lyude just as fyi.
-Daniel

>
> BR,
> Jani.
>
>
> --
> Jani Nikula, Intel Open Source Graphics Center



-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next-fixes

[Joonas Lahtinen]

Quoting Joonas Lahtinen (2020-06-10 12:37:00)
> Hi Dave & Daniel,
> 
> Sending this one early for it to hopefully make it in before -rc1.
> 
> Two important fixes: OOPS fix that was missing "Fixes:" tag and
> not picked up earlier. Also fix for a use-after-free in cmdparser.
> 
> Additional fixup to module param types.

Oh, the CI results:

https://intel-gfx-ci.01.org/tree/drm-intel-next-fixes/combined-alt.html?

CI_DINF_195 was drm-next
CI_DINF_197 is this PR

The extra yellow cells due to FIFO underruns are due to a
concurrent CI update that started flagging the issues. So
no regression, just existing long-running issue being
highlighted.

Regards, Joonas

> Regards, Joonas
> 
> ***
> 
> drm-intel-next-fixes-2020-06-10:
> 
> - Avoid use after free in cmdparser
> - Avoid NULL dereference when probing all display encoders
> - Fixup to module parameter type
> 
> The following changes since commit 8d286e2ff4400d313955b4203fc640ca6fd9228b:
> 
>   Merge tag 'drm-intel-next-fixes-2020-06-04' of 
> git://anongit.freedesktop.org/drm/drm-intel into drm-next (2020-06-08 
> 11:59:57 +1000)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-intel 
> tags/drm-intel-next-fixes-2020-06-10
> 
> for you to fetch changes up to 3680c2e9f4254d1f033bf00f540e47a51f8f996b:
> 
>   drm/i915/display: Only query DP state of a DDI encoder (2020-06-09 14:47:05 
> +0300)
> 
> 
> - Avoid use after free in cmdparser
> - Avoid NULL dereference when probing all display encoders
> - Fixup to module parameter type
> 
> 
> Chris Wilson (2):
>   drm/i915/gem: Mark the buffer pool as active for the cmdparser
>   drm/i915/display: Only query DP state of a DDI encoder
> 
> Jani Nikula (1):
>   drm/i915/params: fix i915.reset module param type
> 
>  drivers/gpu/drm/i915/display/intel_dp.c|  3 ++
>  drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 56 
> ++
>  drivers/gpu/drm/i915/i915_params.c |  2 +-
>  3 files changed, 52 insertions(+), 9 deletions(-)
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next

[Joonas Lahtinen]

Quoting Dave Airlie (2020-05-14 04:28:17)
> On Thu, 14 May 2020 at 03:10, Joonas Lahtinen
>  wrote:
> >
> > Ping for merging this? If there are no issues, I'd prefer to pull in
> > next gvt-next and tag the final pull sooner than later.
> 
> Can you check that I'm correct and this isn;'t in patchwork. I've
> checked both the dri-devel and intel-gfx patchworks for it.

We don't have drm-intel-next going to CI separately as it's a point in
time from drm-intel-next-queued. dinq testing seems to be daily today,
but indeed, I do get a for that day 404:

https://intel-gfx-ci.01.org/tree/drm-intel-next-queued/dinq-20200430/combined-alt.html

I could not locate drm-tip results for that DRIVER_DATE update either.

Tomi and Arek, can you take a look?

All drm-intel-next-fixes tags will still get a separate run, so should
be easier to find.

Regards, Joonas

> Dave.
> >
> > Regards, Joonas
> >
> > Quoting Joonas Lahtinen (2020-04-30 15:49:04)
> > > Hi Dave & Daniel,
> > >
> > > Fix for performance regression GitLab #1698: Iris Plus 655 and
> > > 4K screen. Missing workarounds for Tigerlake, and a fix for
> > > DP display audio WA. Unbreaking enable_dpcd_backlight, fixes
> > > to power code for Icelake+.
> > >
> > > Improvements to the soft-RC6 code to improve power efficiency,
> > > a fix for the timestamp corruption on Tigerlake and plenty of
> > > smaller fixes for CI found corner cases.
> > >
> > > Lots of refactoring that prep for upcoming changes, so I expect
> > > the next PR to be quite busy.
> > >
> > > Includes gvt-next-2020-04-22: Removes left non-upstream xen support
> > > bits which will be kept out of tree instead. And several guest
> > > context shadow optimizations.
> > >
> > > Regards, Joonas
> > >
> > > PS. Noticed the ack for locking rules, thanks! Will merge it.
> > >
> > > ***
> > >
> > > drm-intel-next-2020-04-30:
> > >
> > > Driver Changes:
> > >
> > > - Fix GitLab #1698: Performance regression with Linux 5.7-rc1 on
> > >   Iris Plus 655 and 4K screen (Chris)
> > > - Add Wa_14011059788 for Tigerlake (Matt A)
> > > - Add per ctx batchbuffer wa for timestamp for Gen12 (Mika)
> > > - Use indirect ctx bb to load cmd buffer control value
> > >   from context image to avoid corruption (Mika)
> > > - Enable DP Display Audio WA (Uma, Jani)
> > > - Update forcewake firmware ranges for Icelake (Radhakrishna)
> > > - Add missing deinitialization cases of load failure for display (Jose)
> > > - Implement TC cold sequences for Icelake and Tigerlake (Jose)
> > > - Unbreak enable_dpcd_backlight modparam (Lyude)
> > > - Move the late flush_submission in retire to the end (Chris)
> > > - Demote "Reducing compressed framebufer size" message to info (Peter)
> > > - Push MST link retraining to the hotplug work (Ville)
> > > - Hold obj->vma.lock over for_each_ggtt_vma() (Chris)
> > > - Fix timeout handling during TypeC AUX power well enabling for ICL (Imre)
> > > - Fix skl+ non-scaled pfit modes (Ville)
> > > - Prefer soft-rc6 over RPS DOWN_TIMEOUT (Chris)
> > > - Sanitize GT first before poisoning HWSP (Chris)
> > > - Fix up clock RPS frequency readout (Chris)
> > > - Avoid reusing the same logical CCID (Chris)
> > > - Avoid dereferencing a dead context (Chris)
> > > - Always enable busy-stats for execlists (Chris)
> > > - Apply the aggressive downclocking to parking (Chris)
> > > - Restore aggressive post-boost downclocking (Chris)
> > >
> > > - Scrub execlists state on resume (Chris)
> > > - Add debugfs attributes for LPSP (Ansuman)
> > > - Improvements to kernel selftests (Chris, Mika)
> > > - Add tiled blits selftest (Zbigniew)
> > > - Fix error handling in __live_lrc_indirect_ctx_bb() (Dan)
> > > - Add pre/post plane updates for SAGV (Stanislav)
> > > - Add ICL PG3 PW ID for EHL (Anshuman)
> > > - Fix Sphinx build duplicate label warning (Jani)
> > > - Error log non-zero audio power refcount after unbind (Jani)
> > > - Remove object_is_locked assertion from unpin_from_display_plane (Chris)
> > > - Use single set of AUX powerwell ops for gen11+ (Matt R)
> > > - Prefer drm_WARN_ON over WARN_ON (Pankaj)
> > > - Poison residual state [HWSP] across resume (Chris, Tvrtko)
> > > - Convert request-before-CS assertion to debug (Chris)
> > > - Carefully order virtual_submission_tasklet (Chris)
> > > - Check carefully for an idle engine in wait-for-idle (Chris)
> > > - Only close vma we open (Chris)
> > > - Trace RPS events (Chris)
> > > - Use the RPM config register to determine clk frequencies (Chris)
> > > - Drop rq->ring->vma peeking from error capture (Chris)
> > > - Check preempt-timeout target before submit_ports (Chris)
> > > - Check HWSP cacheline is valid before acquiring (Chris)
> > > - Use proper fault mask in interrupt postinstall too (Matt R)
> > > - Keep a no-frills swappable copy of the default context state (Chris)
> > >
> > > - Add atomic helpers for bandwidth (Stanislav)
> > > - Refactor setting dma info to a common helper from device info (Michael)
> > > - Refactor DDI transcoder code for clairty 

Re: [PULL] drm-intel-next

[Dave Airlie]

On Thu, 14 May 2020 at 03:10, Joonas Lahtinen
 wrote:
>
> Ping for merging this? If there are no issues, I'd prefer to pull in
> next gvt-next and tag the final pull sooner than later.

Can you check that I'm correct and this isn;'t in patchwork. I've
checked both the dri-devel and intel-gfx patchworks for it.

Dave.
>
> Regards, Joonas
>
> Quoting Joonas Lahtinen (2020-04-30 15:49:04)
> > Hi Dave & Daniel,
> >
> > Fix for performance regression GitLab #1698: Iris Plus 655 and
> > 4K screen. Missing workarounds for Tigerlake, and a fix for
> > DP display audio WA. Unbreaking enable_dpcd_backlight, fixes
> > to power code for Icelake+.
> >
> > Improvements to the soft-RC6 code to improve power efficiency,
> > a fix for the timestamp corruption on Tigerlake and plenty of
> > smaller fixes for CI found corner cases.
> >
> > Lots of refactoring that prep for upcoming changes, so I expect
> > the next PR to be quite busy.
> >
> > Includes gvt-next-2020-04-22: Removes left non-upstream xen support
> > bits which will be kept out of tree instead. And several guest
> > context shadow optimizations.
> >
> > Regards, Joonas
> >
> > PS. Noticed the ack for locking rules, thanks! Will merge it.
> >
> > ***
> >
> > drm-intel-next-2020-04-30:
> >
> > Driver Changes:
> >
> > - Fix GitLab #1698: Performance regression with Linux 5.7-rc1 on
> >   Iris Plus 655 and 4K screen (Chris)
> > - Add Wa_14011059788 for Tigerlake (Matt A)
> > - Add per ctx batchbuffer wa for timestamp for Gen12 (Mika)
> > - Use indirect ctx bb to load cmd buffer control value
> >   from context image to avoid corruption (Mika)
> > - Enable DP Display Audio WA (Uma, Jani)
> > - Update forcewake firmware ranges for Icelake (Radhakrishna)
> > - Add missing deinitialization cases of load failure for display (Jose)
> > - Implement TC cold sequences for Icelake and Tigerlake (Jose)
> > - Unbreak enable_dpcd_backlight modparam (Lyude)
> > - Move the late flush_submission in retire to the end (Chris)
> > - Demote "Reducing compressed framebufer size" message to info (Peter)
> > - Push MST link retraining to the hotplug work (Ville)
> > - Hold obj->vma.lock over for_each_ggtt_vma() (Chris)
> > - Fix timeout handling during TypeC AUX power well enabling for ICL (Imre)
> > - Fix skl+ non-scaled pfit modes (Ville)
> > - Prefer soft-rc6 over RPS DOWN_TIMEOUT (Chris)
> > - Sanitize GT first before poisoning HWSP (Chris)
> > - Fix up clock RPS frequency readout (Chris)
> > - Avoid reusing the same logical CCID (Chris)
> > - Avoid dereferencing a dead context (Chris)
> > - Always enable busy-stats for execlists (Chris)
> > - Apply the aggressive downclocking to parking (Chris)
> > - Restore aggressive post-boost downclocking (Chris)
> >
> > - Scrub execlists state on resume (Chris)
> > - Add debugfs attributes for LPSP (Ansuman)
> > - Improvements to kernel selftests (Chris, Mika)
> > - Add tiled blits selftest (Zbigniew)
> > - Fix error handling in __live_lrc_indirect_ctx_bb() (Dan)
> > - Add pre/post plane updates for SAGV (Stanislav)
> > - Add ICL PG3 PW ID for EHL (Anshuman)
> > - Fix Sphinx build duplicate label warning (Jani)
> > - Error log non-zero audio power refcount after unbind (Jani)
> > - Remove object_is_locked assertion from unpin_from_display_plane (Chris)
> > - Use single set of AUX powerwell ops for gen11+ (Matt R)
> > - Prefer drm_WARN_ON over WARN_ON (Pankaj)
> > - Poison residual state [HWSP] across resume (Chris, Tvrtko)
> > - Convert request-before-CS assertion to debug (Chris)
> > - Carefully order virtual_submission_tasklet (Chris)
> > - Check carefully for an idle engine in wait-for-idle (Chris)
> > - Only close vma we open (Chris)
> > - Trace RPS events (Chris)
> > - Use the RPM config register to determine clk frequencies (Chris)
> > - Drop rq->ring->vma peeking from error capture (Chris)
> > - Check preempt-timeout target before submit_ports (Chris)
> > - Check HWSP cacheline is valid before acquiring (Chris)
> > - Use proper fault mask in interrupt postinstall too (Matt R)
> > - Keep a no-frills swappable copy of the default context state (Chris)
> >
> > - Add atomic helpers for bandwidth (Stanislav)
> > - Refactor setting dma info to a common helper from device info (Michael)
> > - Refactor DDI transcoder code for clairty (Ville)
> > - Extend PG3 power well ID to ICL (Anshuman)
> > - Refactor PFIT code for readability and future extensibility (Ville)
> > - Clarify code split between intel_ddi.c and intel_dp.c (Ville)
> > - Move out code to return the digital_port of the aux ch (Jose)
> > - Move rps.enabled/active  and use of RPS interrupts to flags (Chris)
> > - Remove superfluous inlines and dead code (Jani)
> > - Re-disable -Wframe-address from top-level Makefile (Nick)
> > - Static checker and spelling fixes (Colin, Nathan)
> > - Split long lines (Ville)
> >
> > The following changes since commit b06ef327e26367b9286a2079b31cde8d2161c0d8:
> >
> >   drm/i915: Update DRIVER_DATE to 20200417 (2020-04-17 09:35:00 +0300)
> >
> > are 

Re: [PULL] drm-intel-next

[Joonas Lahtinen]

Ping for merging this? If there are no issues, I'd prefer to pull in
next gvt-next and tag the final pull sooner than later.

Regards, Joonas

Quoting Joonas Lahtinen (2020-04-30 15:49:04)
> Hi Dave & Daniel,
> 
> Fix for performance regression GitLab #1698: Iris Plus 655 and
> 4K screen. Missing workarounds for Tigerlake, and a fix for
> DP display audio WA. Unbreaking enable_dpcd_backlight, fixes
> to power code for Icelake+.
> 
> Improvements to the soft-RC6 code to improve power efficiency,
> a fix for the timestamp corruption on Tigerlake and plenty of
> smaller fixes for CI found corner cases.
> 
> Lots of refactoring that prep for upcoming changes, so I expect
> the next PR to be quite busy.
> 
> Includes gvt-next-2020-04-22: Removes left non-upstream xen support
> bits which will be kept out of tree instead. And several guest
> context shadow optimizations.
> 
> Regards, Joonas
> 
> PS. Noticed the ack for locking rules, thanks! Will merge it.
> 
> ***
> 
> drm-intel-next-2020-04-30:
> 
> Driver Changes:
> 
> - Fix GitLab #1698: Performance regression with Linux 5.7-rc1 on
>   Iris Plus 655 and 4K screen (Chris)
> - Add Wa_14011059788 for Tigerlake (Matt A)
> - Add per ctx batchbuffer wa for timestamp for Gen12 (Mika)
> - Use indirect ctx bb to load cmd buffer control value
>   from context image to avoid corruption (Mika)
> - Enable DP Display Audio WA (Uma, Jani)
> - Update forcewake firmware ranges for Icelake (Radhakrishna)
> - Add missing deinitialization cases of load failure for display (Jose)
> - Implement TC cold sequences for Icelake and Tigerlake (Jose)
> - Unbreak enable_dpcd_backlight modparam (Lyude)
> - Move the late flush_submission in retire to the end (Chris)
> - Demote "Reducing compressed framebufer size" message to info (Peter)
> - Push MST link retraining to the hotplug work (Ville)
> - Hold obj->vma.lock over for_each_ggtt_vma() (Chris)
> - Fix timeout handling during TypeC AUX power well enabling for ICL (Imre)
> - Fix skl+ non-scaled pfit modes (Ville)
> - Prefer soft-rc6 over RPS DOWN_TIMEOUT (Chris)
> - Sanitize GT first before poisoning HWSP (Chris)
> - Fix up clock RPS frequency readout (Chris)
> - Avoid reusing the same logical CCID (Chris)
> - Avoid dereferencing a dead context (Chris)
> - Always enable busy-stats for execlists (Chris)
> - Apply the aggressive downclocking to parking (Chris)
> - Restore aggressive post-boost downclocking (Chris)
> 
> - Scrub execlists state on resume (Chris)
> - Add debugfs attributes for LPSP (Ansuman)
> - Improvements to kernel selftests (Chris, Mika)
> - Add tiled blits selftest (Zbigniew)
> - Fix error handling in __live_lrc_indirect_ctx_bb() (Dan)
> - Add pre/post plane updates for SAGV (Stanislav)
> - Add ICL PG3 PW ID for EHL (Anshuman)
> - Fix Sphinx build duplicate label warning (Jani)
> - Error log non-zero audio power refcount after unbind (Jani)
> - Remove object_is_locked assertion from unpin_from_display_plane (Chris)
> - Use single set of AUX powerwell ops for gen11+ (Matt R)
> - Prefer drm_WARN_ON over WARN_ON (Pankaj)
> - Poison residual state [HWSP] across resume (Chris, Tvrtko)
> - Convert request-before-CS assertion to debug (Chris)
> - Carefully order virtual_submission_tasklet (Chris)
> - Check carefully for an idle engine in wait-for-idle (Chris)
> - Only close vma we open (Chris)
> - Trace RPS events (Chris)
> - Use the RPM config register to determine clk frequencies (Chris)
> - Drop rq->ring->vma peeking from error capture (Chris)
> - Check preempt-timeout target before submit_ports (Chris)
> - Check HWSP cacheline is valid before acquiring (Chris)
> - Use proper fault mask in interrupt postinstall too (Matt R)
> - Keep a no-frills swappable copy of the default context state (Chris)
> 
> - Add atomic helpers for bandwidth (Stanislav)
> - Refactor setting dma info to a common helper from device info (Michael)
> - Refactor DDI transcoder code for clairty (Ville)
> - Extend PG3 power well ID to ICL (Anshuman)
> - Refactor PFIT code for readability and future extensibility (Ville)
> - Clarify code split between intel_ddi.c and intel_dp.c (Ville)
> - Move out code to return the digital_port of the aux ch (Jose)
> - Move rps.enabled/active  and use of RPS interrupts to flags (Chris)
> - Remove superfluous inlines and dead code (Jani)
> - Re-disable -Wframe-address from top-level Makefile (Nick)
> - Static checker and spelling fixes (Colin, Nathan)
> - Split long lines (Ville)
> 
> The following changes since commit b06ef327e26367b9286a2079b31cde8d2161c0d8:
> 
>   drm/i915: Update DRIVER_DATE to 20200417 (2020-04-17 09:35:00 +0300)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-2020-04-30
> 
> for you to fetch changes up to 230982d8d8df7f9d9aa216840ea2db1df6ad5d37:
> 
>   drm/i915: Update DRIVER_DATE to 20200430 (2020-04-30 11:13:21 +0300)
> 
> 
> Driver Changes:
> 
> - Fix GitLab 

Re: [PULL] drm-intel-next

[Jani Nikula]

On Tue, 14 Jan 2020, Chris Wilson  wrote:
> Quoting Jani Nikula (2020-01-14 11:43:22)
>> 
>> Hi Dave & Daniel -
>> 
>> Last batch for v5.6, slightly delayed I'm afraid.
>
> I'd like to close https://gitlab.freedesktop.org/drm/intel/issues/738
> for 5.6, otherwise we'll have some more nasty emails from bewildered
> users/devs.
>
> https://patchwork.freedesktop.org/series/71951/

IMO seems small enough to go through drm-intel-next-fixes for v5.6. But
need to close the dinq floodgates already.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next-fixes

[Joonas Lahtinen]

Quoting Joonas Lahtinen (2019-11-20 22:40:35)
> Hi Dave & Daniel,
> 
> NOTE: CI shard results are delayed, bu I'm sending this
> already because I'll travel tomorrow. I'll let you know
> if the results look OK or not. Or you can look up
> CI_DINF_162 results check at:
> 
> https://intel-gfx-ci.01.org/tree/drm-intel-next-fixes/combined-alt.html

The results were not good. I'll send a new PR.

Regards, Joonas
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next

[Rodrigo Vivi]

On Fri, Aug 23, 2019 at 02:23:41PM +0300, Arkadiusz Hiler wrote:
> On Fri, Aug 23, 2019 at 08:46:48PM +1000, Dave Airlie wrote:
> > On Fri, 23 Aug 2019 at 20:08, Arkadiusz Hiler  
> > wrote:
> > >
> > > On Fri, Aug 23, 2019 at 11:50:06AM +1000, Dave Airlie wrote:
> > > > On Fri, 23 Aug 2019 at 05:29, Rodrigo Vivi  
> > > > wrote:
> > > > >
> > > > > Hi Dave and Daniel,
> > > > >
> > > > > Here goes the final pull request targeting 5.4.
> > > >
> > > > For some reason patchwork hasn't picked this up. or if it has I can't
> > > > see it. Not sure whether it was the earlier patch code in it or
> > > > something else malformed.
> > > >
> > > > Dave.
> > >
> > > Hey,
> > >
> > > FDO's Patchwork maintainer here. Feel free to CC me if something like
> > > this happens ever again.
> > >
> > > Seems like the emails was picked up by the patchwork:
> > > https://patchwork.freedesktop.org/patch/325996/
> > >
> > > It appears as a weird mix between a pull request and a regular patch
> > > because of the in-line quoted commit from Stephen. Patchwork doesn't
> > > really know what to do in similar situations.
> > >
> > > Dave, how do you exactly check for new pull requests? I would like to
> > > know which API endpoints/interfaces I should look at. Knowing the
> > > expectations of your tooling would also help.
> > >
> > > There is probably some codepath that just doesn't work right for those
> > > dual-type patches.
> > 
> > I actually should have thought to search a bit deeper for it! I think
> > we've had this happen once before.
> > 
> > I normally just do a search for the keyword pull in the all the patches.
> > https://patchwork.freedesktop.org/project/dri-devel/patches/?submitter===pull==
> 
> Interesting, the original pull as well as the v2 are there now:
> https://hiler.eu/i/fd0401b0.png
> 
> Also the API endpoint seems to show them just fine:
> https://patchwork.freedesktop.org/api/1.0/projects/dri-devel/events/?name=pull-request-new
>  :
>   {
>   "name": "pull-request-new",
>   "event_time": "2019-08-23T08:12:37.601125",
>   "patch": 325996,
>   "parameters": {
>   "pull_url": "git://anongit.freedesktop.org/drm/drm-intel 
> tags/drm-intel-next-2019-08-22"
>   }
>   },
>   {
>   "name": "pull-request-new",
>   "event_time": "2019-08-23T08:08:00.066068",
>   "patch": 325993,
>   "parameters": {
>   "pull_url": "git://anongit.freedesktop.org/drm/drm-intel 
> tags/drm-intel-next-2019-08-22"
>   }
>   }
> 
> FDO's mailing lists had some issues yesteday, I have got few of those
> for the e-mails that I have tried to send:
> 
>   This is an automatically generated Delivery Status Notification.
>   THIS IS A WARNING MESSAGE ONLY.
>   YOU DO NOT NEED TO RESEND YOUR MESSAGE.
> 
>   Delivery to the following recipients has been delayed.
> 
> 
>   The reason for the problem:
>   4.4.2 - Bad connection 'timeout'
> 
> 
> My current guess is that people who were CCed on the pull request got
> the email, checked Patchwork and it wasn't there due to the delivery
> issues.
> 
> In the v2 Rodrigo mentions:
> > for some reason my dim didn't recognized the path apparently
> 
> Rodrigo, can you elaborate? I may be missing/misunderstanding something.

Nevermind. I thought the problem was on my system when generating the
pull since I had seen a git error for being out of the tree.

The second one I generated from inside dinq directory and got it
clean.

So, in summary where are we now here? Do I need to take any action
to help this to get through?

> 
> -- 
> Cheers,
> Arek
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next

[Arkadiusz Hiler]

On Fri, Aug 23, 2019 at 08:46:48PM +1000, Dave Airlie wrote:
> On Fri, 23 Aug 2019 at 20:08, Arkadiusz Hiler  
> wrote:
> >
> > On Fri, Aug 23, 2019 at 11:50:06AM +1000, Dave Airlie wrote:
> > > On Fri, 23 Aug 2019 at 05:29, Rodrigo Vivi  wrote:
> > > >
> > > > Hi Dave and Daniel,
> > > >
> > > > Here goes the final pull request targeting 5.4.
> > >
> > > For some reason patchwork hasn't picked this up. or if it has I can't
> > > see it. Not sure whether it was the earlier patch code in it or
> > > something else malformed.
> > >
> > > Dave.
> >
> > Hey,
> >
> > FDO's Patchwork maintainer here. Feel free to CC me if something like
> > this happens ever again.
> >
> > Seems like the emails was picked up by the patchwork:
> > https://patchwork.freedesktop.org/patch/325996/
> >
> > It appears as a weird mix between a pull request and a regular patch
> > because of the in-line quoted commit from Stephen. Patchwork doesn't
> > really know what to do in similar situations.
> >
> > Dave, how do you exactly check for new pull requests? I would like to
> > know which API endpoints/interfaces I should look at. Knowing the
> > expectations of your tooling would also help.
> >
> > There is probably some codepath that just doesn't work right for those
> > dual-type patches.
> 
> I actually should have thought to search a bit deeper for it! I think
> we've had this happen once before.
> 
> I normally just do a search for the keyword pull in the all the patches.
> https://patchwork.freedesktop.org/project/dri-devel/patches/?submitter===pull==

Interesting, the original pull as well as the v2 are there now:
https://hiler.eu/i/fd0401b0.png

Also the API endpoint seems to show them just fine:
https://patchwork.freedesktop.org/api/1.0/projects/dri-devel/events/?name=pull-request-new
 :
{
"name": "pull-request-new",
"event_time": "2019-08-23T08:12:37.601125",
"patch": 325996,
"parameters": {
"pull_url": "git://anongit.freedesktop.org/drm/drm-intel 
tags/drm-intel-next-2019-08-22"
}
},
{
"name": "pull-request-new",
"event_time": "2019-08-23T08:08:00.066068",
"patch": 325993,
"parameters": {
"pull_url": "git://anongit.freedesktop.org/drm/drm-intel 
tags/drm-intel-next-2019-08-22"
}
}

FDO's mailing lists had some issues yesteday, I have got few of those
for the e-mails that I have tried to send:

This is an automatically generated Delivery Status Notification.
THIS IS A WARNING MESSAGE ONLY.
YOU DO NOT NEED TO RESEND YOUR MESSAGE.

Delivery to the following recipients has been delayed.
  

The reason for the problem:
4.4.2 - Bad connection 'timeout'


My current guess is that people who were CCed on the pull request got
the email, checked Patchwork and it wasn't there due to the delivery
issues.

In the v2 Rodrigo mentions:
> for some reason my dim didn't recognized the path apparently

Rodrigo, can you elaborate? I may be missing/misunderstanding something.

-- 
Cheers,
Arek
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next

[Dave Airlie]

On Fri, 23 Aug 2019 at 20:08, Arkadiusz Hiler  wrote:
>
> On Fri, Aug 23, 2019 at 11:50:06AM +1000, Dave Airlie wrote:
> > On Fri, 23 Aug 2019 at 05:29, Rodrigo Vivi  wrote:
> > >
> > > Hi Dave and Daniel,
> > >
> > > Here goes the final pull request targeting 5.4.
> >
> > For some reason patchwork hasn't picked this up. or if it has I can't
> > see it. Not sure whether it was the earlier patch code in it or
> > something else malformed.
> >
> > Dave.
>
> Hey,
>
> FDO's Patchwork maintainer here. Feel free to CC me if something like
> this happens ever again.
>
> Seems like the emails was picked up by the patchwork:
> https://patchwork.freedesktop.org/patch/325996/
>
> It appears as a weird mix between a pull request and a regular patch
> because of the in-line quoted commit from Stephen. Patchwork doesn't
> really know what to do in similar situations.
>
> Dave, how do you exactly check for new pull requests? I would like to
> know which API endpoints/interfaces I should look at. Knowing the
> expectations of your tooling would also help.
>
> There is probably some codepath that just doesn't work right for those
> dual-type patches.

I actually should have thought to search a bit deeper for it! I think
we've had this happen once before.

I normally just do a search for the keyword pull in the all the patches.
https://patchwork.freedesktop.org/project/dri-devel/patches/?submitter===pull==

Dave.
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next

[Dave Airlie]

On Fri, 23 Aug 2019 at 05:29, Rodrigo Vivi  wrote:
>
> Hi Dave and Daniel,
>
> Here goes the final pull request targeting 5.4.

For some reason patchwork hasn't picked this up. or if it has I can't
see it. Not sure whether it was the earlier patch code in it or
something else malformed.

Dave.
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next

[Ville Syrjälä]

On Thu, Apr 18, 2019 at 11:04:26AM +0300, Joonas Lahtinen wrote:
> - Suppress spurious combo PHY B warning (Vile)

That's putting it a bit strong :)

-- 
Ville Syrjälä
Intel
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next

[Joonas Lahtinen]

Quoting Dave Airlie (2019-03-28 04:09:56)
> On Mon, 25 Mar 2019 at 22:49, Joonas Lahtinen
>  wrote:
> >
> > Hi Dave & Daniel,
> >
> > First batch of features for 5.2, tagged last week.
> 
> I asked on irc, but got no answer I saw,
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/i915/i915_gem_context.c:698:12:
> warning: ‘context_barrier_task’ defined but not used
> [-Wunused-function]
>  static int context_barrier_task(struct i915_gem_context *ctx,
> ^~~~
> 
> Is there a fix for this I can throw on top of the merge?
> 
> I don't like warnings in my builds.

As discussed in IRC, I sent a followup PR that has the patches that fix
the build warning.

Regards, Joonas

> 
> Dave.
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next

[Dave Airlie]

On Mon, 25 Mar 2019 at 22:49, Joonas Lahtinen
 wrote:
>
> Hi Dave & Daniel,
>
> First batch of features for 5.2, tagged last week.

I asked on irc, but got no answer I saw,
/home/airlied/devel/kernel/dim/src/drivers/gpu/drm/i915/i915_gem_context.c:698:12:
warning: ‘context_barrier_task’ defined but not used
[-Wunused-function]
 static int context_barrier_task(struct i915_gem_context *ctx,
^~~~

Is there a fix for this I can throw on top of the merge?

I don't like warnings in my builds.

Dave.
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next

[Jani Nikula]

On Mon, 04 Feb 2019, Daniel Vetter  wrote:
> On Mon, Feb 04, 2019 at 10:47:36AM +0200, Joonas Lahtinen wrote:
>> Quoting Dave Airlie (2019-02-04 07:02:07)
>> > On Sat, 2 Feb 2019 at 18:29, Rodrigo Vivi  wrote:
>> > >
>> > > Hi Dave and Daniel,
>> > >
>> > > Here goes another pull request for 5.1.
>> > 
>> > dim complained:
>> > 
>> > Chris committed this without an S-O-B, now because it's all Intel this
>> > probably doesn't matter, so I'll pull it, put please try and let it
>> > not happen again.
>> 
>> It's a tooling issue. It even has the Link: tag, so it is applied with
>> dim, which automatically should apply the S-o-b of committer. The issue
>> should already have a fix.
>> 
>> And we also concluded that as it's all Intel, it should be legally OK,
>> and not worthy force pushing the history (as it was noticed rather
>> late).
>> 
>> But looks like the communication back to you fell short. Apologies for
>> that.
>
> Hm yeah I thought Dave was on cc: but he wasn't. Some I was on cc: for
> that thread though (no idea why that tbh). Also just noticed that we only
> had the private subthread that Jani started, but never replied in public
> (or to sfr or anyone).

Sorry about that, the intention was to sort it out in private first, the
follow-up failed.

BR,
Jani.

> -Daniel
>
>> 
>> Regards, Joonas
>> 
>> > Dave.
>> > 
>> > commit 8e525cb4a622148fbe30134ee3a1a34ad839a43a
>> > Author: Tvrtko Ursulin 
>> > Commit: Chris Wilson 
>> > 
>> > drm/i915/execlists: Move RPCS setup to context pin
>> > 
>> > Configuring RPCS in context image just before pin is sufficient and 
>> > will
>> > come extra handy in one of the following patches.
>> > 
>> > v2:
>> >  * Split image setup a bit differently. (Chris Wilson)
>> > 
>> > v3:
>> >  * Update context image after reset as well - otherwise the application
>> >of pinned default state clears the RPCS.
>> > 
>> > v4:
>> >  * Use local variable throughout the function. (Chris Wilson)
>> > 
>> > Signed-off-by: Tvrtko Ursulin 
>> > Suggested-by: Chris Wilson 
>> > Cc: Chris Wilson 
>> > Reviewed-by: Chris Wilson 
>> > Reviewed-by: Joonas Lahtinen 
>> > Link: 
>> > https://patchwork.freedesktop.org/patch/msgid/20190125023005.1007-1-ch...@chris-wilson.co.uk
>> > 
>> > >
>> > > Maybe I will still send another next week.
>> > >
>> > > This pull also include a GVT one with:
>> > > "
>> > > Here is gvt-next stuff. This includes Coffeelake support for GVT,
>> > > making kvmgt as self load module to have better dependence with
>> > > vfio/mdev, with some const treatment and kernel type change.
>> > > "
>> > >
>> > > And also it includes a drm change for constify drm_color_lut_check.
>> > >
>> > > Rest of details are on the tags below.
>> > >
>> > > drm-intel-next-2019-02-02:
>> > > - Make background color and LUT more robust (Matt)
>> > > - Icelake display fixes (Ville, Imre)
>> > > - Workarounds fixes and reorg (Tvrtko, Talha)
>> > > - Enable fastboot by default on VLV and CHV (Hans)
>> > > - Add another PCI ID for Coffee Lake (Rodrigo)
>> > >
>> > > drm-intel-next-2019-01-29:
>> > > - MOCS table rework for simplification and to add ICL (Lucas, Tomasz)
>> > > - Move RPCS setup to context pin (Tvrtko)
>> > > - Breadcrumb simplification and GPU Reset improvements (Chris)
>> > > - Many fixes for TV modeset (Ville)
>> > > - Clean up on atomic plane checks (Ville)
>> > > - NV12 pich check fix (Raviraj)
>> > > - Disable -Wuninitialized (Nathan)
>> > > - Sanitize DPLL state for broken BIOSes on SNB (Ville)
>> > > - Rework on vma locking and counting and introduce a concept of 
>> > > per-timeline
>> > >   HWSP (Chris)
>> > > - Enable fastboot by default on Skylake and newer platforms (Hans)
>> > > - Fix slk srckey mask bits (Ville)
>> > > - Selftests fixes (Chris)
>> > > - Execlists and preemption improvements and fixes (Chris)
>> > > - drm consitify drm_color_lut_check (Ville)
>> > > - Ice Lake clock fixes (Lucas)
>> > >
>> > > Thanks,
>> > > Rodrigo.
>> > >
>> > > The following changes since commit 
>> > > 85baa5dbf79163026dcb78f742294c522e176432:
>> > >
>> > >   drm/i915: Update DRIVER_DATE to 20190124 (2019-01-24 15:00:59 -0800)
>> > >
>> > > are available in the Git repository at:
>> > >
>> > >   git://anongit.freedesktop.org/drm/drm-intel 
>> > > tags/drm-intel-next-2019-02-02
>> > >
>> > > for you to fetch changes up to 46c0cd8c562bc3e4a99cbaa4ba0904b6871b7b4b:
>> > >
>> > >   drm/i915: Update DRIVER_DATE to 20190202 (2019-02-02 00:14:28 -0800)
>> > >
>> > > 
>> > > - Make background color and LUT more robust (Matt)
>> > > - Icelake display fixes (Ville, Imre)
>> > > - Workarounds fixes and reorg (Tvrtko, Talha)
>> > > - Enable fastboot by default on VLV and CHV (Hans)
>> > > - Add another PCI ID for Coffee Lake (Rodrigo)
>> > >
>> > > 
>> > > Chris Wilson (27):
>> > >   drm/i915: 

Re: [PULL] drm-intel-next

[Daniel Vetter]

On Mon, Feb 04, 2019 at 10:47:36AM +0200, Joonas Lahtinen wrote:
> Quoting Dave Airlie (2019-02-04 07:02:07)
> > On Sat, 2 Feb 2019 at 18:29, Rodrigo Vivi  wrote:
> > >
> > > Hi Dave and Daniel,
> > >
> > > Here goes another pull request for 5.1.
> > 
> > dim complained:
> > 
> > Chris committed this without an S-O-B, now because it's all Intel this
> > probably doesn't matter, so I'll pull it, put please try and let it
> > not happen again.
> 
> It's a tooling issue. It even has the Link: tag, so it is applied with
> dim, which automatically should apply the S-o-b of committer. The issue
> should already have a fix.
> 
> And we also concluded that as it's all Intel, it should be legally OK,
> and not worthy force pushing the history (as it was noticed rather
> late).
> 
> But looks like the communication back to you fell short. Apologies for
> that.

Hm yeah I thought Dave was on cc: but he wasn't. Some I was on cc: for
that thread though (no idea why that tbh). Also just noticed that we only
had the private subthread that Jani started, but never replied in public
(or to sfr or anyone).
-Daniel

> 
> Regards, Joonas
> 
> > Dave.
> > 
> > commit 8e525cb4a622148fbe30134ee3a1a34ad839a43a
> > Author: Tvrtko Ursulin 
> > Commit: Chris Wilson 
> > 
> > drm/i915/execlists: Move RPCS setup to context pin
> > 
> > Configuring RPCS in context image just before pin is sufficient and will
> > come extra handy in one of the following patches.
> > 
> > v2:
> >  * Split image setup a bit differently. (Chris Wilson)
> > 
> > v3:
> >  * Update context image after reset as well - otherwise the application
> >of pinned default state clears the RPCS.
> > 
> > v4:
> >  * Use local variable throughout the function. (Chris Wilson)
> > 
> > Signed-off-by: Tvrtko Ursulin 
> > Suggested-by: Chris Wilson 
> > Cc: Chris Wilson 
> > Reviewed-by: Chris Wilson 
> > Reviewed-by: Joonas Lahtinen 
> > Link: 
> > https://patchwork.freedesktop.org/patch/msgid/20190125023005.1007-1-ch...@chris-wilson.co.uk
> > 
> > >
> > > Maybe I will still send another next week.
> > >
> > > This pull also include a GVT one with:
> > > "
> > > Here is gvt-next stuff. This includes Coffeelake support for GVT,
> > > making kvmgt as self load module to have better dependence with
> > > vfio/mdev, with some const treatment and kernel type change.
> > > "
> > >
> > > And also it includes a drm change for constify drm_color_lut_check.
> > >
> > > Rest of details are on the tags below.
> > >
> > > drm-intel-next-2019-02-02:
> > > - Make background color and LUT more robust (Matt)
> > > - Icelake display fixes (Ville, Imre)
> > > - Workarounds fixes and reorg (Tvrtko, Talha)
> > > - Enable fastboot by default on VLV and CHV (Hans)
> > > - Add another PCI ID for Coffee Lake (Rodrigo)
> > >
> > > drm-intel-next-2019-01-29:
> > > - MOCS table rework for simplification and to add ICL (Lucas, Tomasz)
> > > - Move RPCS setup to context pin (Tvrtko)
> > > - Breadcrumb simplification and GPU Reset improvements (Chris)
> > > - Many fixes for TV modeset (Ville)
> > > - Clean up on atomic plane checks (Ville)
> > > - NV12 pich check fix (Raviraj)
> > > - Disable -Wuninitialized (Nathan)
> > > - Sanitize DPLL state for broken BIOSes on SNB (Ville)
> > > - Rework on vma locking and counting and introduce a concept of 
> > > per-timeline
> > >   HWSP (Chris)
> > > - Enable fastboot by default on Skylake and newer platforms (Hans)
> > > - Fix slk srckey mask bits (Ville)
> > > - Selftests fixes (Chris)
> > > - Execlists and preemption improvements and fixes (Chris)
> > > - drm consitify drm_color_lut_check (Ville)
> > > - Ice Lake clock fixes (Lucas)
> > >
> > > Thanks,
> > > Rodrigo.
> > >
> > > The following changes since commit 
> > > 85baa5dbf79163026dcb78f742294c522e176432:
> > >
> > >   drm/i915: Update DRIVER_DATE to 20190124 (2019-01-24 15:00:59 -0800)
> > >
> > > are available in the Git repository at:
> > >
> > >   git://anongit.freedesktop.org/drm/drm-intel 
> > > tags/drm-intel-next-2019-02-02
> > >
> > > for you to fetch changes up to 46c0cd8c562bc3e4a99cbaa4ba0904b6871b7b4b:
> > >
> > >   drm/i915: Update DRIVER_DATE to 20190202 (2019-02-02 00:14:28 -0800)
> > >
> > > 
> > > - Make background color and LUT more robust (Matt)
> > > - Icelake display fixes (Ville, Imre)
> > > - Workarounds fixes and reorg (Tvrtko, Talha)
> > > - Enable fastboot by default on VLV and CHV (Hans)
> > > - Add another PCI ID for Coffee Lake (Rodrigo)
> > >
> > > 
> > > Chris Wilson (27):
> > >   drm/i915: Measure the required reserved size for request emission
> > >   drm/i915: Remove manual breadcumb counting
> > >   drm/i915: Compute the HWS offsets explicitly
> > >   drm/i915: Make all GPU resets atomic
> > >   drm/i915/guc: Disable global reset
> > >   drm/i915: 

Re: [PULL] drm-intel-next

[Dave Airlie]

On Sat, 2 Feb 2019 at 18:29, Rodrigo Vivi  wrote:
>
> Hi Dave and Daniel,
>
> Here goes another pull request for 5.1.

dim complained:

Chris committed this without an S-O-B, now because it's all Intel this
probably doesn't matter, so I'll pull it, put please try and let it
not happen again.

Dave.

commit 8e525cb4a622148fbe30134ee3a1a34ad839a43a
Author: Tvrtko Ursulin 
Commit: Chris Wilson 

drm/i915/execlists: Move RPCS setup to context pin

Configuring RPCS in context image just before pin is sufficient and will
come extra handy in one of the following patches.

v2:
 * Split image setup a bit differently. (Chris Wilson)

v3:
 * Update context image after reset as well - otherwise the application
   of pinned default state clears the RPCS.

v4:
 * Use local variable throughout the function. (Chris Wilson)

Signed-off-by: Tvrtko Ursulin 
Suggested-by: Chris Wilson 
Cc: Chris Wilson 
Reviewed-by: Chris Wilson 
Reviewed-by: Joonas Lahtinen 
Link: 
https://patchwork.freedesktop.org/patch/msgid/20190125023005.1007-1-ch...@chris-wilson.co.uk

>
> Maybe I will still send another next week.
>
> This pull also include a GVT one with:
> "
> Here is gvt-next stuff. This includes Coffeelake support for GVT,
> making kvmgt as self load module to have better dependence with
> vfio/mdev, with some const treatment and kernel type change.
> "
>
> And also it includes a drm change for constify drm_color_lut_check.
>
> Rest of details are on the tags below.
>
> drm-intel-next-2019-02-02:
> - Make background color and LUT more robust (Matt)
> - Icelake display fixes (Ville, Imre)
> - Workarounds fixes and reorg (Tvrtko, Talha)
> - Enable fastboot by default on VLV and CHV (Hans)
> - Add another PCI ID for Coffee Lake (Rodrigo)
>
> drm-intel-next-2019-01-29:
> - MOCS table rework for simplification and to add ICL (Lucas, Tomasz)
> - Move RPCS setup to context pin (Tvrtko)
> - Breadcrumb simplification and GPU Reset improvements (Chris)
> - Many fixes for TV modeset (Ville)
> - Clean up on atomic plane checks (Ville)
> - NV12 pich check fix (Raviraj)
> - Disable -Wuninitialized (Nathan)
> - Sanitize DPLL state for broken BIOSes on SNB (Ville)
> - Rework on vma locking and counting and introduce a concept of per-timeline
>   HWSP (Chris)
> - Enable fastboot by default on Skylake and newer platforms (Hans)
> - Fix slk srckey mask bits (Ville)
> - Selftests fixes (Chris)
> - Execlists and preemption improvements and fixes (Chris)
> - drm consitify drm_color_lut_check (Ville)
> - Ice Lake clock fixes (Lucas)
>
> Thanks,
> Rodrigo.
>
> The following changes since commit 85baa5dbf79163026dcb78f742294c522e176432:
>
>   drm/i915: Update DRIVER_DATE to 20190124 (2019-01-24 15:00:59 -0800)
>
> are available in the Git repository at:
>
>   git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-2019-02-02
>
> for you to fetch changes up to 46c0cd8c562bc3e4a99cbaa4ba0904b6871b7b4b:
>
>   drm/i915: Update DRIVER_DATE to 20190202 (2019-02-02 00:14:28 -0800)
>
> 
> - Make background color and LUT more robust (Matt)
> - Icelake display fixes (Ville, Imre)
> - Workarounds fixes and reorg (Tvrtko, Talha)
> - Enable fastboot by default on VLV and CHV (Hans)
> - Add another PCI ID for Coffee Lake (Rodrigo)
>
> 
> Chris Wilson (27):
>   drm/i915: Measure the required reserved size for request emission
>   drm/i915: Remove manual breadcumb counting
>   drm/i915: Compute the HWS offsets explicitly
>   drm/i915: Make all GPU resets atomic
>   drm/i915/guc: Disable global reset
>   drm/i915: Remove GPU reset dependence on struct_mutex
>   drm/i915/selftests: Trim struct_mutex duration for set-wedged selftest
>   drm/i915: Issue engine resets onto idle engines
>   drm/i915: Wait for a moment before forcibly resetting the device
>   drm/i915: Stop tracking MRU activity on VMA
>   drm/i915: Pull VM lists under the VM mutex.
>   drm/i915: Move vma lookup to its own lock
>   drm/i915: Always allocate an object/vma for the HWSP
>   drm/i915: Move list of timelines under its own lock
>   drm/i915: Introduce concept of per-timeline (context) HWSP
>   drm/i915: Enlarge vma->pin_count
>   drm/i915: Allocate a status page for each timeline
>   drm/i915: Share per-timeline HWSP using a slab suballocator
>   drm/i915: Track the context's seqno in its own timeline HWSP
>   drm/i915: Track active timelines
>   drm/i915/selftests: Apply a subtest filter
>   drm/i915: Identify active requests
>   drm/i915: Rename execlists->queue_priority to queue_priority_hint
>   drm/i915/execlists: Suppress preempting self
>   drm/i915: Remove the intel_engine_notify tracepoint
>   drm/i915: Replace global breadcrumbs with per-context interrupt tracking
>   drm/i915: Drop fake 

Re: [PULL] drm-intel-next-fixes

[Daniel Vetter]

On Fri, Oct 19, 2018 at 12:38 PM Joonas Lahtinen
 wrote:
>
> Hi Dave,
>
> Here are the promised MST fixes that were missing due to being
> in i915 tree, yet outside i915 directory.
>
> Further explanation in the previous PR's thread.

fwiw, lgtm.

Cheers, Daniel
>
> Regards, Joonas
>
> ***
>
> drm-intel-next-fixes-2018-10-19:
> - The missing 4 MST patches that tooling didn't pick from drm core/nouveau
> The following changes since commit f2bfc71aee75feff33ca659322b72ffeed5a243d:
>
>   Merge tag 'drm-intel-next-fixes-2018-10-18' of 
> git://anongit.freedesktop.org/drm/drm-intel into drm-next (2018-10-19 
> 14:28:11 +1000)
>
> are available in the Git repository at:
>
>   git://anongit.freedesktop.org/drm/drm-intel 
> tags/drm-intel-next-fixes-2018-10-19
>
> for you to fetch changes up to 7b0f61e91b6056c71649efa3204112a4b6cf5fc8:
>
>   drm/nouveau: Fix nv50_mstc->best_encoder() (2018-10-19 11:46:46 +0300)
>
> 
> - The missing 4 MST patches that tooling didn't pick from drm core/nouveau
>
> 
> Lyude Paul (4):
>   drm/atomic_helper: Disallow new modesets on unregistered connectors
>   drm/atomic_helper: Allow DPMS On<->Off changes for unregistered 
> connectors
>   drm/atomic_helper: Stop modesets on unregistered connectors harder
>   drm/nouveau: Fix nv50_mstc->best_encoder()
>
>  drivers/gpu/drm/drm_atomic_helper.c | 21 +-
>  drivers/gpu/drm/drm_connector.c | 11 ++---
>  drivers/gpu/drm/i915/intel_dp_mst.c |  8 ++--
>  drivers/gpu/drm/nouveau/dispnv50/disp.c | 14 ++-
>  include/drm/drm_connector.h | 71 
> -
>  5 files changed, 103 insertions(+), 22 deletions(-)



-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next-fixes

[Joonas Lahtinen]

Quoting Daniel Vetter (2018-10-19 10:05:32)
> On Fri, Oct 19, 2018 at 8:59 AM Joonas Lahtinen
>  wrote:
> >
> > Quoting Daniel Vetter (2018-10-18 22:32:00)
> > > On Thu, Oct 18, 2018 at 6:57 PM Joonas Lahtinen
> > >  wrote:
> > > >
> > > > Hi Dave,
> > > >
> > > > Here comes the final set of fixes under -next-fixes umbrella.
> > > > Next one will be then from -fixes, assuming a release next Sun.
> > > >
> > > > Fixes for bunch of display related issues reported by users, then the
> > > > MST fixes that were dropped from Rodrigos PR + further Icelake fixes
> > > > and proactive improvements picked by tooling.
> > > >
> > > > Excuse for the slight accumulation as I skipped last week due to
> > > > travel like I warned.
> > > >
> > > > Regards, Joonas
> > > >
> > > > ***
> > > >
> > > > drm-intel-next-fixes-2018-10-18:
> > > > - Fix GPU hang on MacBook2,1 when booting in EFI mode (Bugzilla #105637)
> > > > - Fix garbled console on Y tiled BIOS framebuffer configs (Bugzilla 
> > > > #108264)
> > > > - Fix black screen on certain eDP panels eg. Dell XPS 9350 (Bugzilla 
> > > > #107489 and #105338)
> > > > - MST fixes that Rodrigo dropped from drm-intel-fixes and bunch of 
> > > > Icelake fixes
> > >
> > > This won't work because it doesn't contain Lyude's core fix (+ the 2
> > > fixups). You either need to cherry-pick all of them (and then probably
> > > include the nouveau one), or none of them. Did the cherry-pick script
> > > not propose them, or something else? They're all cc: stable.
> >
> > cherry-pick-next-fixes did not propose more. I did specifically ask
> > Rodrigo to drop the relevant stuff from drm-intel-fixes so that the
> > tooling would pick it up. What is there that is missing?
> 
> dim cherry-pick-branch is limited to drivers/gpu/drm/i915 :-(
> 
> Remove that (well at least only filter drm/) and you should see them.
> Ideally you put the core patch + 2 core fixups before the i915/nouveau
> patches.
> 
> I guess putting core patches that are bugfixes through drm-intel.git
> really isn't a good idea with our process ...

I've now done this now. Removal of the filter adding two patches, but I
had to track down the further Fixes: to Fixes: manually. Thanks to
Daniel for the assistance in pointing the missing patches.

As you already pulled this PR, the core fixes will end up after
the i915 fixes. If you end up wanting to rebase the order, note that
the Fixes: annotations will be wrecked. I'll send a further fixup PR.

I also amended the Fixes: tags to point to cherry-picked fixes, to
decrease the likelihood of falling through automated tooling (while
appending Cc: stable to one patch missing it).

So you want to avoid rebasing the patches in all circumstances (or
you have to update/remove the Fixes: lines beyond the line "(cherry
picked from ...".

Lovely thing to do on Friday :) Hopefully next week will be less
of a hassle.

Regards, Joonas

> -Daniel
> 
> >
> > Regards, Joonas
> >
> > > -Daniel
> > >
> > > > - Then assorted proactive code fixes caught by CI or developers
> > > >
> > > > The following changes since commit 
> > > > ca4b869240d5810ebac6b1570ad7beffcfbac2f5:
> > > >
> > > >   Merge branch 'drm-next-4.20' of 
> > > > git://people.freedesktop.org/~agd5f/linux into drm-next (2018-10-11 
> > > > 14:53:45 +1000)
> > > >
> > > > are available in the Git repository at:
> > > >
> > > >   git://anongit.freedesktop.org/drm/drm-intel 
> > > > tags/drm-intel-next-fixes-2018-10-18
> > > >
> > > > for you to fetch changes up to 835fe6d75d14c1513910ed7f5665127fee12acc8:
> > > >
> > > >   firmware/dmc/icl: Add missing MODULE_FIRMWARE() for Icelake. 
> > > > (2018-10-18 10:36:10 +0300)
> > > >
> > > > 
> > > > - Fix GPU hang on MacBook2,1 when booting in EFI mode (Bugzilla #105637)
> > > > - Fix garbled console on Y tiled BIOS framebuffer configs (Bugzilla 
> > > > #108264)
> > > > - Fix black screen on certain eDP panels eg. Dell XPS 9350 (Bugzilla 
> > > > #107489 and #105338)
> > > > - MST fixes that Rodrigo dropped from drm-intel-fixes and bunch of 
> > > > Icelake fixes
> > > > - Then assorted proactive code fixes caught by CI or developers
> > > >
> > > > 
> > > > Anusha Srivatsa (1):
> > > >   firmware/dmc/icl: Add missing MODULE_FIRMWARE() for Icelake.
> > > >
> > > > Chris Wilson (3):
> > > >   drm/i915: Only reset seqno if actually idle
> > > >   drm/i915/selftests: Disable shrinker across mmap-exhaustion
> > > >   drm/i915: Large page offsets for pread/pwrite
> > > >
> > > > Imre Deak (1):
> > > >   drm/i915/gen9+: Fix initial readout for Y tiled framebuffers
> > > >
> > > > Lyude Paul (3):
> > > >   drm/i915: Don't unset intel_connector->mst_port
> > > >   drm/i915: Skip vcpi allocation for MSTB ports that are gone
> > > >   drm/i915: Fix intel_dp_mst_best_encoder()
> > > >
> > > > Mahesh Kumar (2):
> > > >   drm/i915/icl: 

Re: [PULL] drm-intel-next-fixes

[Daniel Vetter]

On Thu, Oct 18, 2018 at 6:57 PM Joonas Lahtinen
 wrote:
>
> Hi Dave,
>
> Here comes the final set of fixes under -next-fixes umbrella.
> Next one will be then from -fixes, assuming a release next Sun.
>
> Fixes for bunch of display related issues reported by users, then the
> MST fixes that were dropped from Rodrigos PR + further Icelake fixes
> and proactive improvements picked by tooling.
>
> Excuse for the slight accumulation as I skipped last week due to
> travel like I warned.
>
> Regards, Joonas
>
> ***
>
> drm-intel-next-fixes-2018-10-18:
> - Fix GPU hang on MacBook2,1 when booting in EFI mode (Bugzilla #105637)
> - Fix garbled console on Y tiled BIOS framebuffer configs (Bugzilla #108264)
> - Fix black screen on certain eDP panels eg. Dell XPS 9350 (Bugzilla #107489 
> and #105338)
> - MST fixes that Rodrigo dropped from drm-intel-fixes and bunch of Icelake 
> fixes

This won't work because it doesn't contain Lyude's core fix (+ the 2
fixups). You either need to cherry-pick all of them (and then probably
include the nouveau one), or none of them. Did the cherry-pick script
not propose them, or something else? They're all cc: stable.
-Daniel

> - Then assorted proactive code fixes caught by CI or developers
>
> The following changes since commit ca4b869240d5810ebac6b1570ad7beffcfbac2f5:
>
>   Merge branch 'drm-next-4.20' of git://people.freedesktop.org/~agd5f/linux 
> into drm-next (2018-10-11 14:53:45 +1000)
>
> are available in the Git repository at:
>
>   git://anongit.freedesktop.org/drm/drm-intel 
> tags/drm-intel-next-fixes-2018-10-18
>
> for you to fetch changes up to 835fe6d75d14c1513910ed7f5665127fee12acc8:
>
>   firmware/dmc/icl: Add missing MODULE_FIRMWARE() for Icelake. (2018-10-18 
> 10:36:10 +0300)
>
> 
> - Fix GPU hang on MacBook2,1 when booting in EFI mode (Bugzilla #105637)
> - Fix garbled console on Y tiled BIOS framebuffer configs (Bugzilla #108264)
> - Fix black screen on certain eDP panels eg. Dell XPS 9350 (Bugzilla #107489 
> and #105338)
> - MST fixes that Rodrigo dropped from drm-intel-fixes and bunch of Icelake 
> fixes
> - Then assorted proactive code fixes caught by CI or developers
>
> 
> Anusha Srivatsa (1):
>   firmware/dmc/icl: Add missing MODULE_FIRMWARE() for Icelake.
>
> Chris Wilson (3):
>   drm/i915: Only reset seqno if actually idle
>   drm/i915/selftests: Disable shrinker across mmap-exhaustion
>   drm/i915: Large page offsets for pread/pwrite
>
> Imre Deak (1):
>   drm/i915/gen9+: Fix initial readout for Y tiled framebuffers
>
> Lyude Paul (3):
>   drm/i915: Don't unset intel_connector->mst_port
>   drm/i915: Skip vcpi allocation for MSTB ports that are gone
>   drm/i915: Fix intel_dp_mst_best_encoder()
>
> Mahesh Kumar (2):
>   drm/i915/icl: create function to identify combophy port
>   drm/i915/icl: Fix DDI/TC port clk_off bits
>
> Manasi Navare (1):
>   drm/i915/dp: Link train Fallback on eDP only if fallback link BW can 
> fit panel's native mode
>
> Rodrigo Vivi (1):
>   drm/i915/icl: Fix signal_levels
>
> Ville Syrjälä (3):
>   drm/i915: Check fb stride against plane max stride
>   drm/i915: Restore vblank interrupts earlier
>   drm/i915: Use the correct crtc when sanitizing plane mapping
>
>  drivers/gpu/drm/i915/i915_debugfs.c  |   2 +-
>  drivers/gpu/drm/i915/i915_gem.c  |  12 +-
>  drivers/gpu/drm/i915/i915_reg.h  |   3 +
>  drivers/gpu/drm/i915/intel_csr.c |   1 +
>  drivers/gpu/drm/i915/intel_ddi.c |  36 --
>  drivers/gpu/drm/i915/intel_display.c | 151 
> ---
>  drivers/gpu/drm/i915/intel_dp.c  |  32 -
>  drivers/gpu/drm/i915/intel_dp_link_training.c|  26 ++--
>  drivers/gpu/drm/i915/intel_dp_mst.c  |  41 +++---
>  drivers/gpu/drm/i915/intel_drv.h |   2 +
>  drivers/gpu/drm/i915/intel_sprite.c  |  22 
>  drivers/gpu/drm/i915/selftests/i915_gem_object.c |   3 +
>  12 files changed, 227 insertions(+), 104 deletions(-)



-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next

[Rodrigo Vivi]

On Mon, Jun 18, 2018 at 09:12:55AM +0200, Daniel Vetter wrote:
> On Tue, Jun 12, 2018 at 9:59 AM, Jani Nikula
>  wrote:
> > On Tue, 12 Jun 2018, Dave Airlie  wrote:
> >> On 12 June 2018 at 02:27, Rodrigo Vivi  wrote:
> >>> Hi Dave,
> >>>
> >>> This is the first round targeting 4.19.
> >>>
> >> Does this tree feed into linux-next already?
> >>
> >> Since we shouldn't have new stuff for linux-next feeding into it until
> >> after rc1.

The timing was wrong but the pull is valid now that rc1 is out there.

Sorry for the early noise.

> >
> > I think we'll feed it to linux-next only after merge window closes
> > i.e. rc1.
> >
> >> I won't be pulling this until after rc1 anyways.
> >
> > Seems fair; this doesn't conflict with tagging manageable sized batches
> > in dinq like Rodrigo has done here. So we're good.
> 
> The scripts don't require to send out a pull request when only
> tagging, I guess this pull here was just a fumble?

not actually. I had tagged that on the week before.

It was my mistake on setting my own todo list...

instead accounting for the merge window and wait for -rc1
I mistakenly account release date + 1 week when adding the task
to my todo list here and end up sending that too early.

> -Daniel
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
> ___
> dim-tools mailing list
> dim-tools@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dim-tools
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next

[Daniel Vetter]

On Tue, Jun 12, 2018 at 9:59 AM, Jani Nikula
 wrote:
> On Tue, 12 Jun 2018, Dave Airlie  wrote:
>> On 12 June 2018 at 02:27, Rodrigo Vivi  wrote:
>>> Hi Dave,
>>>
>>> This is the first round targeting 4.19.
>>>
>> Does this tree feed into linux-next already?
>>
>> Since we shouldn't have new stuff for linux-next feeding into it until
>> after rc1.
>
> I think we'll feed it to linux-next only after merge window closes
> i.e. rc1.

dim indeed takes care of that, but only if the
drm-intel-fixes/next-fixes branches are handled correctly. Which is
why fast-forwarding them according to the documentation is paramount,
for otherwise we upset everyone using linux-next :-)
-Daniel

>
>> I won't be pulling this until after rc1 anyways.
>
> Seems fair; this doesn't conflict with tagging manageable sized batches
> in dinq like Rodrigo has done here. So we're good.
>
> BR,
> Jani.
>
> --
> Jani Nikula, Intel Open Source Graphics Center



-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next

[Daniel Vetter]

On Tue, Jun 12, 2018 at 9:59 AM, Jani Nikula
 wrote:
> On Tue, 12 Jun 2018, Dave Airlie  wrote:
>> On 12 June 2018 at 02:27, Rodrigo Vivi  wrote:
>>> Hi Dave,
>>>
>>> This is the first round targeting 4.19.
>>>
>> Does this tree feed into linux-next already?
>>
>> Since we shouldn't have new stuff for linux-next feeding into it until
>> after rc1.
>
> I think we'll feed it to linux-next only after merge window closes
> i.e. rc1.
>
>> I won't be pulling this until after rc1 anyways.
>
> Seems fair; this doesn't conflict with tagging manageable sized batches
> in dinq like Rodrigo has done here. So we're good.

The scripts don't require to send out a pull request when only
tagging, I guess this pull here was just a fumble?
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next

[Jani Nikula]

On Tue, 12 Jun 2018, Dave Airlie  wrote:
> On 12 June 2018 at 02:27, Rodrigo Vivi  wrote:
>> Hi Dave,
>>
>> This is the first round targeting 4.19.
>>
> Does this tree feed into linux-next already?
>
> Since we shouldn't have new stuff for linux-next feeding into it until
> after rc1.

I think we'll feed it to linux-next only after merge window closes
i.e. rc1.

> I won't be pulling this until after rc1 anyways.

Seems fair; this doesn't conflict with tagging manageable sized batches
in dinq like Rodrigo has done here. So we're good.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Graphics Center
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools

Re: [PULL] drm-intel-next

[Jani Nikula]

Agreed. Zhi, don't worry about it.

I think the main takeaways here are:

1) We need to improve the dim checks on git pulls. This is both for us
pulling gvt, and now that Dave's experimenting with dim, for him pulling
all the trees.

2) The GVT maintainers should consider using dim too. It would probably
require some tweaking for their needs, but I'm pretty sure the
safeguards would prove helpful.


BR,
Jani.


On Tue, 15 May 2018, Daniel Vetter  wrote:
> Imo we should take this as a personal failure of anyone, things
> happen. Instead this is a good opportunity to improve our scripts, to
> make sure we catch this in the future.
>
> Cheers, Daniel
>
> On Tue, May 15, 2018 at 3:16 PM, Wang, Zhi A  wrote:
>> Hi:
>>
>> I am truly sorry for the mess. It's actual my fault of solving a patch 
>> dependency by rebasing. Jani was trying to help me to catch the deadline, I 
>> am very appreciated for Jani's help and I am quite sorry for letting Jani 
>> experience this failure. He tried to help but I fail him. As a new guy of 
>> managing the pull request and maintenance, I need to learn more and improve 
>> our working flow to prevent this happen in future. Sorry for the 
>> inconvenience.
>>
>> Thanks,
>> Zhi.
>>
>> -Original Message-
>> From: Nikula, Jani
>> Sent: Tuesday, May 15, 2018 12:56 PM
>> To: Dave Airlie 
>> Cc: Daniel Vetter ; Jani Nikula 
>> ; Joonas Lahtinen 
>> ; Vivi, Rodrigo ; 
>> Sean Paul ; Gustavo Padovan ; 
>> Maarten Lankhorst ; 
>> dri-de...@lists.freedesktop.org; intel-...@lists.freedesktop.org; 
>> dim-tools@lists.freedesktop.org; Wang, Zhi A ; Zhenyu 
>> Wang ; Srinivas, Vidya 
>> Subject: [PULL] drm-intel-next
>>
>>
>> Hi Dave -
>>
>> So this one contains the problematic pull from gvt. It's got both a 
>> backmerge and a rebase. I spotted the rebase, but intentionally let it slide 
>> due to the deadline closing, and then completely missed the backmerge. I 
>> don't know what I was thinking. My bad, sorry.
>>
>> We'll need to improve our workflows with the gvt team.
>>
>> Anyway, here's the pull, wrinkles and all, as discussed on IRC. Let us know 
>> if you can tolerate it, or if we need to rewrite history.
>>
>> BR,
>> Jani.
>>
>>
>> PS. Regarding the changelog, Vidya Srinivas  had a 
>> huge role in the NV12 work, but alas I failed to give proper credit because 
>> the patches were based on earlier work by Chandra.
>>
>>
>> drm-intel-next-2018-05-14:
>> Last drm/i915 changes for v4.18:
>>
>> - NV12 enabling (Chandra, Maarten)
>> - ICL workarounds (Oscar)
>> - ICL basic DPLL enabling (Paulo)
>> - GVT updates
>> - DP link config refactoring (Jani)
>> - Module parameter to override DMC firmware (Jani)
>> - PSR updates (José, DK, Daniel, Ville)
>> - ICL DP vswing programming (Manasi)
>> - ICL DBuf slice updates (Mahesh)
>> - Selftest fixes and updates (Chris, Matthew, Oscar)
>> - Execlist fixes and updates (Chris)
>> - Stolen memory first 4k fix (Hans de Goede)
>> - wait_for fixes (Mika)
>> - Tons of GEM improvements (Chris)
>> - Plenty of other fixes and improvements (Everyone)
>> - Crappy changelog (Me)
>>
>> BR,
>> Jani.
>>
>> The following changes since commit 0ab390262c4920f26f8202063a268d5fc829728e:
>>
>>   Merge tag 'drm-misc-next-2018-04-26' of 
>> git://anongit.freedesktop.org/drm/drm-misc into drm-next (2018-04-30 
>> 09:32:43 +1000)
>>
>> are available in the git repository at:
>>
>>   git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-2018-05-14
>>
>> for you to fetch changes up to 01f83786f9ab9c8883ce634cb9a0de51086ad7ea:
>>
>>   drm/i915: Update DRIVER_DATE to 20180514 (2018-05-14 15:28:05 +0300)
>>
>> 
>> Last drm/i915 changes for v4.18:
>>
>> - NV12 enabling (Chandra, Maarten)
>> - ICL workarounds (Oscar)
>> - ICL basic DPLL enabling (Paulo)
>> - GVT updates
>> - DP link config refactoring (Jani)
>> - Module parameter to override DMC firmware (Jani)
>> - PSR updates (José, DK, Daniel, Ville)
>> - ICL DP vswing programming (Manasi)
>> - ICL DBuf slice updates (Mahesh)
>> - Selftest fixes and updates (Chris, Matthew, Oscar)
>> - Execlist fixes and updates (Chris)
>> - Stolen memory first 4k fix (Hans de Goede)
>> - wait_for fixes (Mika)
>> - Tons of GEM improvements (Chris)
>> - Plenty of other fixes and improvements (Everyone)
>> - Crappy changelog (Me)
>>
>> 
>> Abhay Kumar (1):
>>   drm/i915/audio: set minimum CD clock to twice the BCLK
>>
>> Andy Shevchenko (1):
>>   i915: Convert to use match_string() helper
>>
>> Anusha Srivatsa (1):
>>   drm/i915/firmware: 

RE: [PULL] drm-intel-next

[Wang, Zhi A]

Hi:

I am truly sorry for the mess. It's actual my fault of solving a patch 
dependency by rebasing. Jani was trying to help me to catch the deadline, I am 
very appreciated for Jani's help and I am quite sorry for letting Jani 
experience this failure. He tried to help but I fail him. As a new guy of 
managing the pull request and maintenance, I need to learn more and improve our 
working flow to prevent this happen in future. Sorry for the inconvenience.

Thanks,
Zhi.

-Original Message-
From: Nikula, Jani 
Sent: Tuesday, May 15, 2018 12:56 PM
To: Dave Airlie 
Cc: Daniel Vetter ; Jani Nikula 
; Joonas Lahtinen 
; Vivi, Rodrigo ; Sean 
Paul ; Gustavo Padovan ; Maarten 
Lankhorst ; dri-de...@lists.freedesktop.org; 
intel-...@lists.freedesktop.org; dim-tools@lists.freedesktop.org; Wang, Zhi A 
; Zhenyu Wang ; Srinivas, Vidya 

Subject: [PULL] drm-intel-next


Hi Dave -

So this one contains the problematic pull from gvt. It's got both a backmerge 
and a rebase. I spotted the rebase, but intentionally let it slide due to the 
deadline closing, and then completely missed the backmerge. I don't know what I 
was thinking. My bad, sorry.

We'll need to improve our workflows with the gvt team.

Anyway, here's the pull, wrinkles and all, as discussed on IRC. Let us know if 
you can tolerate it, or if we need to rewrite history.

BR,
Jani.


PS. Regarding the changelog, Vidya Srinivas  had a 
huge role in the NV12 work, but alas I failed to give proper credit because the 
patches were based on earlier work by Chandra.


drm-intel-next-2018-05-14:
Last drm/i915 changes for v4.18:

- NV12 enabling (Chandra, Maarten)
- ICL workarounds (Oscar)
- ICL basic DPLL enabling (Paulo)
- GVT updates
- DP link config refactoring (Jani)
- Module parameter to override DMC firmware (Jani)
- PSR updates (José, DK, Daniel, Ville)
- ICL DP vswing programming (Manasi)
- ICL DBuf slice updates (Mahesh)
- Selftest fixes and updates (Chris, Matthew, Oscar)
- Execlist fixes and updates (Chris)
- Stolen memory first 4k fix (Hans de Goede)
- wait_for fixes (Mika)
- Tons of GEM improvements (Chris)
- Plenty of other fixes and improvements (Everyone)
- Crappy changelog (Me)

BR,
Jani.

The following changes since commit 0ab390262c4920f26f8202063a268d5fc829728e:

  Merge tag 'drm-misc-next-2018-04-26' of 
git://anongit.freedesktop.org/drm/drm-misc into drm-next (2018-04-30 09:32:43 
+1000)

are available in the git repository at:

  git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-2018-05-14

for you to fetch changes up to 01f83786f9ab9c8883ce634cb9a0de51086ad7ea:

  drm/i915: Update DRIVER_DATE to 20180514 (2018-05-14 15:28:05 +0300)


Last drm/i915 changes for v4.18:

- NV12 enabling (Chandra, Maarten)
- ICL workarounds (Oscar)
- ICL basic DPLL enabling (Paulo)
- GVT updates
- DP link config refactoring (Jani)
- Module parameter to override DMC firmware (Jani)
- PSR updates (José, DK, Daniel, Ville)
- ICL DP vswing programming (Manasi)
- ICL DBuf slice updates (Mahesh)
- Selftest fixes and updates (Chris, Matthew, Oscar)
- Execlist fixes and updates (Chris)
- Stolen memory first 4k fix (Hans de Goede)
- wait_for fixes (Mika)
- Tons of GEM improvements (Chris)
- Plenty of other fixes and improvements (Everyone)
- Crappy changelog (Me)


Abhay Kumar (1):
  drm/i915/audio: set minimum CD clock to twice the BCLK

Andy Shevchenko (1):
  i915: Convert to use match_string() helper

Anusha Srivatsa (1):
  drm/i915/firmware: Correct URL for firmware

Chandra Konduru (3):
  drm/i915: Add NV12 support to intel_framebuffer_init
  drm/i915: Add NV12 as supported format for primary plane
  drm/i915: Add NV12 as supported format for sprite plane

Changbin Du (1):
  drm/i915/gvt: Remove disable_warn_untrack and print untracked mmio with 
debug level

Chris Wilson (53):
  drm/i915: Check whitelist registers across resets
  drm/i915: Call i915_perf_fini() on init_hw error unwind
  drm/i915: Move the priotree struct to its own headers
  drm/i915: Rename priotree to sched
  drm/i915: Pack params to engine->schedule() into a struct
  drm/i915: Build request info on stack before printk
  drm/i915: Don't dump umpteen thousand requests
  drm/i915: Skip printing global offsets for per-engine scratch pages
  drm/i915/breadcrumbs: Keep the fake irq armed across reset
  drm/i915: Use memset64() to align the ring with MI_NOOP
  drm/i915: Remove obsolete min/max freq setters from debugfs
  drm/i915: Compile out engine debug for release
  

RE: [PULL] drm-intel-next

[Srinivas, Vidya]

> -Original Message-
> From: Nikula, Jani
> Sent: Tuesday, May 15, 2018 3:26 PM
> To: Dave Airlie 
> Cc: Daniel Vetter ; Jani Nikula
> ; Joonas Lahtinen
> ; Vivi, Rodrigo ;
> Sean Paul ; Gustavo Padovan
> ; Maarten Lankhorst
> ; dri-de...@lists.freedesktop.org;
> intel-...@lists.freedesktop.org; dim-tools@lists.freedesktop.org; Wang, Zhi
> A ; Zhenyu Wang ;
> Srinivas, Vidya 
> Subject: [PULL] drm-intel-next
> 
> 
> Hi Dave -
> 
> So this one contains the problematic pull from gvt. It's got both a backmerge
> and a rebase. I spotted the rebase, but intentionally let it slide due to the
> deadline closing, and then completely missed the backmerge. I don't know
> what I was thinking. My bad, sorry.
> 
> We'll need to improve our workflows with the gvt team.
> 
> Anyway, here's the pull, wrinkles and all, as discussed on IRC. Let us know if
> you can tolerate it, or if we need to rewrite history.
> 
> BR,
> Jani.
> 
> 
> PS. Regarding the changelog, Vidya Srinivas  had a
> huge role in the NV12 work, but alas I failed to give proper credit because 
> the
> patches were based on earlier work by Chandra.

No problem at all :) Sincerely, Thank you so much. It was based on Chandra's 
original work and without Maarten
It would never reach the merge stage :)

> 
> 
> drm-intel-next-2018-05-14:
> Last drm/i915 changes for v4.18:
> 
> - NV12 enabling (Chandra, Maarten)
> - ICL workarounds (Oscar)
> - ICL basic DPLL enabling (Paulo)
> - GVT updates
> - DP link config refactoring (Jani)
> - Module parameter to override DMC firmware (Jani)
> - PSR updates (José, DK, Daniel, Ville)
> - ICL DP vswing programming (Manasi)
> - ICL DBuf slice updates (Mahesh)
> - Selftest fixes and updates (Chris, Matthew, Oscar)
> - Execlist fixes and updates (Chris)
> - Stolen memory first 4k fix (Hans de Goede)
> - wait_for fixes (Mika)
> - Tons of GEM improvements (Chris)
> - Plenty of other fixes and improvements (Everyone)
> - Crappy changelog (Me)
> 
> BR,
> Jani.
> 
> The following changes since commit
> 0ab390262c4920f26f8202063a268d5fc829728e:
> 
>   Merge tag 'drm-misc-next-2018-04-26' of
> git://anongit.freedesktop.org/drm/drm-misc into drm-next (2018-04-30
> 09:32:43 +1000)
> 
> are available in the git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-2018-05-
> 14
> 
> for you to fetch changes up to 01f83786f9ab9c8883ce634cb9a0de51086ad7ea:
> 
>   drm/i915: Update DRIVER_DATE to 20180514 (2018-05-14 15:28:05 +0300)
> 
> 
> Last drm/i915 changes for v4.18:
> 
> - NV12 enabling (Chandra, Maarten)
> - ICL workarounds (Oscar)
> - ICL basic DPLL enabling (Paulo)
> - GVT updates
> - DP link config refactoring (Jani)
> - Module parameter to override DMC firmware (Jani)
> - PSR updates (José, DK, Daniel, Ville)
> - ICL DP vswing programming (Manasi)
> - ICL DBuf slice updates (Mahesh)
> - Selftest fixes and updates (Chris, Matthew, Oscar)
> - Execlist fixes and updates (Chris)
> - Stolen memory first 4k fix (Hans de Goede)
> - wait_for fixes (Mika)
> - Tons of GEM improvements (Chris)
> - Plenty of other fixes and improvements (Everyone)
> - Crappy changelog (Me)
> 
> 
> Abhay Kumar (1):
>   drm/i915/audio: set minimum CD clock to twice the BCLK
> 
> Andy Shevchenko (1):
>   i915: Convert to use match_string() helper
> 
> Anusha Srivatsa (1):
>   drm/i915/firmware: Correct URL for firmware
> 
> Chandra Konduru (3):
>   drm/i915: Add NV12 support to intel_framebuffer_init
>   drm/i915: Add NV12 as supported format for primary plane
>   drm/i915: Add NV12 as supported format for sprite plane
> 
> Changbin Du (1):
>   drm/i915/gvt: Remove disable_warn_untrack and print untracked mmio
> with debug level
> 
> Chris Wilson (53):
>   drm/i915: Check whitelist registers across resets
>   drm/i915: Call i915_perf_fini() on init_hw error unwind
>   drm/i915: Move the priotree struct to its own headers
>   drm/i915: Rename priotree to sched
>   drm/i915: Pack params to engine->schedule() into a struct
>   drm/i915: Build request info on stack before printk
>   drm/i915: Don't dump umpteen thousand requests
>   drm/i915: Skip printing global offsets for per-engine scratch pages
>   drm/i915/breadcrumbs: Keep the fake irq armed across reset
>   drm/i915: Use memset64() to align the ring with MI_NOOP
>   drm/i915: Remove obsolete min/max freq setters from debugfs
>   drm/i915: Compile out engine debug for release
>   drm/i915/selftests: Wait for idle between idle resets as well
>   

Re: [PULL] drm-intel-next

[Dave Airlie]

On 4 May 2018 at 10:29, Dave Airlie  wrote:
> On 4 May 2018 at 10:19, Dave Airlie  wrote:
>> On 2 May 2018 at 17:03, Jani Nikula  wrote:
>>>
>>> Hi Dave -
>>>
>>> drm-intel-next-2018-04-13:
>>> First drm/i915 feature batch heading for v4.18:
>>>
>>> - drm-next backmerge to fix build (Rodrigo)
>>> - GPU documentation improvements (Kevin)
>>> - GuC and HuC refactoring, host/GuC communication, logging, fixes, and more
>>>   (mostly Michal and Michał, also Jackie, Michel and Piotr)
>>> - PSR and PSR2 enabling and fixes (DK, José, Rodrigo and Chris)
>>> - Selftest updates (Chris, Daniele)
>>> - DPLL management refactoring (Lucas)
>>> - DP MST fixes (Lyude and DK)
>>> - Watermark refactoring and changes to support NV12 (Mahesh)
>>> - NV12 prep work (Chandra)
>>> - Icelake Combo PHY enablers (Manasi)
>>> - Perf OA refactoring and ICL enabling (Lionel)
>>> - ICL enabling (Oscar, Paulo, Nabendu, Mika, Kelvin, Michel)
>>> - Workarounds refactoring (Oscar)
>>> - HDCP fixes and improvements (Ramalingam, Radhakrishna)
>>> - Power management fixes (Imre)
>>> - Various display fixes (Maarten, Ville, Vidya, Jani, Gaurav)
>>> - debugfs for FIFO underrun clearing (Maarten)
>>> - Execlist improvements (Chris)
>>> - Reset improvements (Chris)
>>> - Plenty of things here and there I overlooked and/or didn't understand... 
>>> (Everyone)
>>>
>>
>> Just FYI I've started using dim for managing the drm-next tree (step
>> one to a possible group),
>>
>> This pull gets rejected by dim apply-pull for two reasons,
>>
>> One the driver date bump isn't reviewed, and one patch in here the SOB
>> line is different
>> name than the committer, even though they appear to be same person.
>>
>> I've pulled it anyways, but just logging the dim issues for prosperity.
>
> Actually I haven't pulled it, but I think dim just doesn't handle my
> use case very well.
> I do
> dim -f apply-pull < pullreq
>
> It gets merge conflicts and ask me to solve them, but there doesn't seem
> to be a dim apply-pull --resolved type of interface to say, keep going
> and finish the
> dim stuff you were doing before we hit conflicts.
>

I manually did
git commit --amend -s --no-edit
dim add-link drm-next < pullreq

but it would be nice to have a continue or resolved.

Dave.
___
dim-tools mailing list
dim-tools@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dim-tools