From: Jani Nikula <jani.nikula@intel.com>
To: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Roper, Matthew D" <matthew.d.roper@intel.com>
Subject: Re: [PATCH] drm/xe/mmio: Fix xe_mmio_wait32() to honor delay/sleep maximums
Date: Tue, 15 Sep 2026 19:43:51 +0300 [thread overview]
Message-ID: <f52c0b78ddae61cf668c89708b48ad82ba5f95dc@intel.com> (raw)
In-Reply-To: <145460bc090d7406d03f1335feaadb07172cff20.camel@intel.com>
On Tue, 15 Sep 2026, "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com> wrote:
> On Tue, 2026-09-15 at 10:34 +0300, Nikula, Jani wrote:
>> On Mon, 14 Sep 2026, Alan Previn <alan.previn.teres.alexis@intel.com> wrote:
> alan:snip
>> > int xe_mmio_wait32(struct xe_mmio *mmio, struct xe_reg reg, u32 mask, u32 val, u32 timeout_us,
>> > - u32 *out_val, bool atomic)
>> > + u32 *out_val)
>> > {
>> > - return __xe_mmio_wait32(mmio, reg, mask, val, timeout_us, out_val, atomic, true);
>> > + u32 read;
>> > + int ret;
>> > +
>> > + ret = poll_timeout_us(read = xe_mmio_read32(mmio, reg), (read & mask) == val,
>> > + 10, timeout_us, false);
>>
>> You probably do need to let the callers pass in the wait too. 10 us wait
>> with a long timeout is going to be pretty bad.
>>
>>
> alan: okay - perhaps i can make every caller pass in a polling-wait thats a fraction of their wait time.
> (as a starting point since i dont know what's the expected behavior of every caller).
> so perhaps something like "timeout_us << 4" (i.e. 1/16th) but pass in 10 us if its anything smaller than that
> (i.e. smaller than 16 usec).
I think you need to talk to the xe maintainers, really.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-09-15 16:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 21:57 [PATCH] drm/xe/mmio: Fix xe_mmio_wait32() to honor delay/sleep maximums Alan Previn
2026-09-14 22:16 ` sashiko-bot
2026-09-14 22:40 ` ✓ CI.KUnit: success for drm/xe/mmio: Fix xe_mmio_wait32() to honor delay/sleep maximums (rev4) Patchwork
2026-09-14 23:39 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-15 4:17 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-09-15 7:34 ` [PATCH] drm/xe/mmio: Fix xe_mmio_wait32() to honor delay/sleep maximums Jani Nikula
2026-09-15 16:00 ` Teres Alexis, Alan Previn
2026-09-15 16:43 ` Jani Nikula [this message]
2026-09-15 22:51 ` Rodrigo Vivi
2026-09-16 19:10 ` Teres Alexis, Alan Previn
2026-09-17 0:54 ` Rodrigo Vivi
2026-09-17 2:07 ` Teres Alexis, Alan Previn
2026-09-17 18:49 ` Teres Alexis, Alan Previn
-- strict thread matches above, loose matches on Subject: below --
2026-09-29 19:20 Alan Previn
2026-09-30 3:51 ` Rodrigo Vivi
2026-09-29 15:25 Alan Previn
2026-09-29 16:18 ` sashiko-bot
2026-09-29 19:07 ` Teres Alexis, Alan Previn
2026-09-29 5:44 Alan Previn
2026-09-29 5:49 ` sashiko-bot
2026-09-29 17:51 ` Rodrigo Vivi
2026-09-08 20:33 Alan Previn
2026-09-08 18:56 Alan Previn
2026-09-08 19:03 ` sashiko-bot
2026-09-09 8:00 ` Jani Nikula
2026-09-11 0:05 ` Teres Alexis, Alan Previn
2026-09-07 23:55 Alan Previn
2026-09-08 0:02 ` sashiko-bot
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=f52c0b78ddae61cf668c89708b48ad82ba5f95dc@intel.com \
--to=jani.nikula@intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@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