Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Imre Deak <imre.deak@intel.com>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH v2 0/2] drm/i915: Fix DP MST DB message timeouts due to PPS delays
Date: Tue, 25 Mar 2025 11:27:04 +0200	[thread overview]
Message-ID: <8734f1a2af.fsf@intel.com> (raw)
In-Reply-To: <20250324180145.142884-1-imre.deak@intel.com>

On Mon, 24 Mar 2025, Imre Deak <imre.deak@intel.com> wrote:
> This is v2 of [1], dropping the change to lock PPS and enable VDD from a
> separate function, as requested by Jani.

Thanks for doing this!

Reviewed-by: Jani Nikula <jani.nikula@intel.com>

>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> [1] https://lore.kernel.org/all/20250321145626.94101-1-imre.deak@intel.com
>
> Imre Deak (2):
>   drm/i915/pps: Let calling intel_pps_vdd_{on,off}_unlocked() w/o PPS
>     lock held
>   drm/i915/dp_mst: Fix side-band message timeouts due to long PPS delays
>
>  drivers/gpu/drm/i915/display/intel_dp_aux.c | 21 ++++++++++++++++++---
>  drivers/gpu/drm/i915/display/intel_pps.c    |  8 ++++----
>  2 files changed, 22 insertions(+), 7 deletions(-)

-- 
Jani Nikula, Intel

  parent reply	other threads:[~2025-03-25  9:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-24 18:01 [PATCH v2 0/2] drm/i915: Fix DP MST DB message timeouts due to PPS delays Imre Deak
2025-03-24 18:01 ` [PATCH v2 1/2] drm/i915/pps: Let calling intel_pps_vdd_{on, off}_unlocked() w/o PPS lock held Imre Deak
2025-03-24 18:01 ` [PATCH v2 2/2] drm/i915/dp_mst: Fix side-band message timeouts due to long PPS delays Imre Deak
2025-03-24 18:35 ` ✓ CI.Patch_applied: success for drm/i915: Fix DP MST DB message timeouts due to " Patchwork
2025-03-24 18:35 ` ✓ CI.checkpatch: " Patchwork
2025-03-24 18:36 ` ✓ CI.KUnit: " Patchwork
2025-03-24 18:53 ` ✓ CI.Build: " Patchwork
2025-03-24 18:55 ` ✓ CI.Hooks: " Patchwork
2025-03-24 18:57 ` ✗ CI.checksparse: warning " Patchwork
2025-03-24 19:21 ` ✓ Xe.CI.BAT: success " Patchwork
2025-03-24 21:53 ` ✓ Xe.CI.Full: " Patchwork
2025-03-25  9:27 ` Jani Nikula [this message]
     [not found] ` <174285700806.75091.7982901296370240968@18a75f3d1eae>
2025-03-25 12:29   ` ✗ i915.CI.Full: failure " Imre Deak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8734f1a2af.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=ville.syrjala@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox