From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
"Jani Nikula" <jani.nikula@intel.com>,
"Jouni Högander" <jouni.hogander@intel.com>
Subject: Re: [PATCH v2 0/4] drm/i915/dp: Sanitize link capability change handling
Date: Fri, 22 May 2026 21:04:27 +0300 [thread overview]
Message-ID: <ahCaq-j4gNLx8aJR@intel.com> (raw)
In-Reply-To: <20260522160514.2628249-1-imre.deak@intel.com>
On Fri, May 22, 2026 at 07:05:10PM +0300, Imre Deak wrote:
> This is v2 of [1], dropping the addition of helpers to reset the link
> state, addressing Ville's comments in patch 4 and adding Jouni's R-bs.
>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Jouni Högander <jouni.hogander@intel.com>
>
> [1] https://lore.kernel.org/all/20260518112427.2460725-1-imre.deak@intel.com
>
> Imre Deak (4):
> drm/i915/dp: Reset link params after a DPRX capability change
> drm/i915/dp: Add helper to set common link params
> drm/i915/dp: Cache max common lane count
> drm/i915/dp: Detect changes in common link parameters
Series is
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> .../drm/i915/display/intel_display_types.h | 1 +
> drivers/gpu/drm/i915/display/intel_dp.c | 66 +++++++++++++++++--
> 2 files changed, 60 insertions(+), 7 deletions(-)
>
> --
> 2.49.1
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2026-05-22 18:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 16:05 [PATCH v2 0/4] drm/i915/dp: Sanitize link capability change handling Imre Deak
2026-05-22 16:05 ` [PATCH v2 1/4] drm/i915/dp: Reset link params after a DPRX capability change Imre Deak
2026-05-22 16:05 ` [PATCH v2 2/4] drm/i915/dp: Add helper to set common link params Imre Deak
2026-05-22 16:05 ` [PATCH v2 3/4] drm/i915/dp: Cache max common lane count Imre Deak
2026-05-22 16:05 ` [PATCH v2 4/4] drm/i915/dp: Detect changes in common link parameters Imre Deak
2026-05-22 17:27 ` ✓ CI.KUnit: success for drm/i915/dp: Sanitize link capability change handling (rev2) Patchwork
2026-05-22 18:04 ` Ville Syrjälä [this message]
2026-05-22 18:07 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-22 19:19 ` ✓ i915.CI.BAT: success for drm/i915/dp: Sanitize link capability change handling (rev3) Patchwork
2026-05-23 2:03 ` ✓ Xe.CI.FULL: success for drm/i915/dp: Sanitize link capability change handling (rev2) Patchwork
2026-05-24 1:54 ` ✓ i915.CI.Full: success for drm/i915/dp: Sanitize link capability change handling (rev3) Patchwork
2026-05-25 12:15 ` 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=ahCaq-j4gNLx8aJR@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jouni.hogander@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.