From: Laura Nao <laura.nao@collabora.com>
To: daniel.almeida@collabora.com, aliceryhl@google.com,
dakr@kernel.org, airlied@gmail.com, simona@ffwll.ch,
ojeda@kernel.org
Cc: boqun@kernel.org, gary@garyguo.net, bjorn3_gh@protonmail.com,
a.hindborg@kernel.org, tmgross@umich.edu, tamird@kernel.org,
acourbot@nvidia.com, work@onurozkan.dev,
deborah.brouwer@collabora.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, rust-for-linux@vger.kernel.org,
kernel@collabora.com, Laura Nao <laura.nao@collabora.com>
Subject: [PATCH 0/2] drm/tyr: add Job IRQ handling and GPU event wait support
Date: Tue, 21 Jul 2026 17:14:21 +0200 [thread overview]
Message-ID: <20260721151423.444175-1-laura.nao@collabora.com> (raw)
This series follows up to [1], which adds support for firmware loading
and MCU booting to the Tyr driver. The changes included here were
originally introduced in v4[2], then dropped to reduce the scope of the
series, and have been adjusted to work with the HRT (Higher-Ranked
Lifetime Types) driver architecture recently introduced.
The first commit adds a new Wait type, wrapping a CondVar and a Mutex,
for sleeping until a condition is met or a timeout expires. This can be
used to wait for GPU-driven events.
The second commit adds a threaded IRQ wrapper for the firmware Job
interrupts, used to signal events from the global CSF (GLB) and Command
Stream Group (CSG) interfaces.
These changes will be later used to wait for global CSF interface
readiness after firmware boot, as part of the CSF firmware interfaces
support that will be submitted as a separate series.
This series is based on drm-rust-next and depends on:
- [PATCH v7 0/7] drm/tyr: firmware loading and MCU boot support[1]
- [PATCH v2] rust: irq: make Registration compatible with lifetime-bound drivers[2]
[1] https://lore.kernel.org/rust-for-linux/20260713-fw-boot-b4-v7-0-afd8dc1494dd@collabora.com/#t
[2] https://lore.kernel.org/rust-for-linux/20260719153631.559341-1-dakr@kernel.org/
Deborah Brouwer (1):
drm/tyr: add Wait type for GPU events
Laura Nao (1):
drm/tyr: add Job IRQ handling
drivers/gpu/drm/tyr/driver.rs | 75 ++++++++++++++++++++
drivers/gpu/drm/tyr/fw.rs | 4 ++
drivers/gpu/drm/tyr/fw/irq.rs | 104 ++++++++++++++++++++++++++++
drivers/gpu/drm/tyr/tyr.rs | 1 +
drivers/gpu/drm/tyr/wait.rs | 126 ++++++++++++++++++++++++++++++++++
5 files changed, 310 insertions(+)
create mode 100644 drivers/gpu/drm/tyr/fw/irq.rs
create mode 100644 drivers/gpu/drm/tyr/wait.rs
--
2.39.5
next reply other threads:[~2026-07-21 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 15:14 Laura Nao [this message]
2026-07-21 15:14 ` [PATCH 1/2] drm/tyr: add Wait type for GPU events Laura Nao
2026-07-21 15:32 ` Danilo Krummrich
2026-07-27 9:04 ` Laura Nao
2026-07-21 15:14 ` [PATCH 2/2] drm/tyr: add Job IRQ handling Laura Nao
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=20260721151423.444175-1-laura.nao@collabora.com \
--to=laura.nao@collabora.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=deborah.brouwer@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
/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
all inboxes | Powered by JetHome®