From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: "Murthy, Arun R" <arun.r.murthy@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] Revert "drm/i915/dp: change aux_ctl reg read to polling read"
Date: Thu, 20 Nov 2025 16:11:10 +0200 [thread overview]
Message-ID: <aR8hfrY3EjxL8Loq@intel.com> (raw)
In-Reply-To: <220fd18a4d5d0ce5fb8c4c61041c968f6b42cd43@intel.com>
On Thu, Nov 20, 2025 at 03:08:12PM +0200, Jani Nikula wrote:
> On Thu, 20 Nov 2025, "Murthy, Arun R" <arun.r.murthy@intel.com> wrote:
> >> -----Original Message-----
> >> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Ville
> >> Syrjala
> >> Sent: Thursday, November 20, 2025 12:23 AM
> >> To: intel-gfx@lists.freedesktop.org
> >> Cc: intel-xe@lists.freedesktop.org
> >> Subject: [PATCH 2/2] Revert "drm/i915/dp: change aux_ctl reg read to polling
> >> read"
> >>
> >> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >>
> >> This reverts commit 5a9b0c7418448ed3766f61ba0a71d08f259c3181.
> >>
> >> The switch from AUX interrupts to pollign was very hand-wavy.
> >> Yes, there have been some situations in CI on a few platforms where the AUX
> >> hardware seemingly forgets to signal the timeout, but those have been
> >> happening after we switched to polling as well. So I don't think we have any
> >> conclusive evidence that polling actually helps here.
> >>
> >> Someone really should root cause the actual problem, and see if there is a
> >> proper workaround we could implemnt (eg. disabling clock gating/etc.). In the
> >> meantime just go back to using the interrupt for AUX completion.
> >>
> >> If the hardware fails to signal the timeout we will just hit the
> >> wait_event_timeout() software timeout instead. I suppose we could try to tune
> >> the software timeout to more closely match the expected hardware timeout.
> >> Might need to use
> >> wait_event_hrtimeout() or something to avoid jiffies granularity issues...
> >>
> >> The AUX polling is also a hinderance towards using poll_timeout_us() because
> >> we have a very long timeout, but would need a fairly short polling interval to
> >> keep AUX transfer reasonably fast. Someone would need to come up with good
> >> numbers in a somewhat scientific way.
> >>
> > Upon multiple rounds of validation based on the results polling had improvements when compared with the interrupt mechanism. We can optimize more by using poll_timeout, I am afraid that reverting back to interrupts may end up with more failures.
What exactly do you mean by failures? IIRC the only thing we've
seen is the software timeout firing instead of the hw timeout,
which shouldn't be a problem really. Eiter way the AUX transfer
failed.
>
> I'm not sure the issues were root caused properly.
At least the commit message is completely useless in explaining any
of it. No explanation of what the actual issue seen was, no test
resutls, no mention of what other workarounds were attempted,
no root cause...
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-11-20 14:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 18:53 [PATCH 0/2] drm/i915: Go back to using AUX interrupts Ville Syrjala
2025-11-19 18:53 ` [PATCH 1/2] drm/i915: Enable DDI A/B AUX interrupts on LNL+ Ville Syrjala
2025-11-19 18:53 ` [PATCH 2/2] Revert "drm/i915/dp: change aux_ctl reg read to polling read" Ville Syrjala
2025-11-20 3:40 ` Murthy, Arun R
2025-11-20 13:08 ` Jani Nikula
2025-11-20 14:11 ` Ville Syrjälä [this message]
2025-11-19 20:24 ` ✓ CI.KUnit: success for drm/i915: Go back to using AUX interrupts Patchwork
2025-11-19 20:46 ` ✗ CI.checksparse: warning " Patchwork
2025-11-19 21:40 ` ✓ Xe.CI.BAT: success " Patchwork
2025-11-20 1:35 ` ✗ Xe.CI.Full: failure " Patchwork
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=aR8hfrY3EjxL8Loq@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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;
as well as URLs for NNTP newsgroup(s).