From: "Murthy, Arun R" <arun.r.murthy@intel.com>
To: Simona Vetter <simona@ffwll.ch>,
Jani Nikula <jani.nikula@linux.intel.com>,
<ville.syrjala@linux.intel.com>, <suraj.kandpal@intel.com>,
<imre.deak@intel.com>
Cc: <dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH RFC 0/3] Some updates over DP AUX Transactions
Date: Tue, 10 Mar 2026 14:31:45 +0530 [thread overview]
Message-ID: <a162fe5d-ecd6-4825-b8cf-e117416f0333@intel.com> (raw)
In-Reply-To: <20260309-dp_aux_timeout-v1-0-08c610a63a84@intel.com>
Based on the comment, this merely will not add any impact replacing
write with rmw. Dropping this patchset.
Thanks and Regards,
Arun R Murthy
--------------------
On 09-03-2026 12:59, Arun R Murthy wrote:
> Based on the discussions/comments on the patch
> https://lore.kernel.org/intel-xe/aaVWbdt1vOFxGAb1@ideak-desk.lan/
> in order to address the real HW(DPTX) generated timeout and adress the
> fix, this series is targetted.
> Along with this it was noticed that the the AUX power request bit in the
> port control register is being touched outside the power well framework.
> The limitation due to the way aux port control register was programmed.
> Replacing the aux control register write to read/mask/write thereby
> writing only the required bits.
>
> Note: This is RFC and full round of testing the pending.
>
> Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
> ---
> Arun R Murthy (3):
> drm/display/dp: Export function to wake the sink AUX_CH
> drm/i915/dp: On AUX_CH tx timeout, wake up the sink
> drm/i915/dp: Configure PORT_AUX_CTL and then trigger the tx
>
> drivers/gpu/drm/display/drm_dp_helper.c | 36 +++++++++
> drivers/gpu/drm/i915/display/intel_display_types.h | 6 +-
> drivers/gpu/drm/i915/display/intel_dp_aux.c | 94 +++++++++++++++-------
> drivers/gpu/drm/i915/display/intel_psr.c | 29 ++++---
> include/drm/display/drm_dp_helper.h | 1 +
> 5 files changed, 123 insertions(+), 43 deletions(-)
> ---
> base-commit: 6884fe03ff2bc5a2f501ba4710f950dd4933ac84
> change-id: 20260309-dp_aux_timeout-9d5b1b35a0d8
>
> Best regards,
prev parent reply other threads:[~2026-03-10 9:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 7:29 [PATCH RFC 0/3] Some updates over DP AUX Transactions Arun R Murthy
2026-03-09 7:29 ` [PATCH RFC 1/3] drm/display/dp: Export function to wake the sink AUX_CH Arun R Murthy
2026-03-09 7:29 ` [PATCH RFC 2/3] drm/i915/dp: On AUX_CH tx timeout, wake up the sink Arun R Murthy
2026-03-09 7:29 ` [PATCH RFC 3/3] drm/i915/dp: Configure PORT_AUX_CTL and then trigger the tx Arun R Murthy
2026-03-09 13:09 ` Jani Nikula
2026-03-09 13:20 ` Murthy, Arun R
2026-03-09 8:41 ` ✗ CI.checkpatch: warning for Some updates over DP AUX Transactions Patchwork
2026-03-09 8:42 ` ✓ CI.KUnit: success " Patchwork
2026-03-09 9:21 ` ✗ i915.CI.BAT: failure " Patchwork
2026-03-09 10:08 ` ✗ Xe.CI.BAT: " Patchwork
2026-03-09 13:09 ` ✗ Xe.CI.FULL: " Patchwork
2026-03-10 9:01 ` Murthy, Arun R [this message]
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=a162fe5d-ecd6-4825-b8cf-e117416f0333@intel.com \
--to=arun.r.murthy@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=suraj.kandpal@intel.com \
--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 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.