From: Daniel Almeida <daniel.almeida@collabora.com>
To: "Onur Özkan" <work@onurozkan.dev>
Cc: linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
dri-devel@lists.freedesktop.org, dakr@kernel.org,
aliceryhl@google.com, airlied@gmail.com, simona@ffwll.ch,
ojeda@kernel.org, boqun@kernel.org, gary@garyguo.net,
bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, tmgross@umich.edu
Subject: Re: [PATCH v4 3/3] drm/tyr: add GPU reset infrastructure
Date: Thu, 13 Aug 2026 20:25:15 -0300 [thread overview]
Message-ID: <D4F91EDE-5FD1-41F8-B5AE-D8C2EA25545D@collabora.com> (raw)
In-Reply-To: <20260813-tyr-reset-impl-v4-3-b36fcd0805b2@onurozkan.dev>
Hi Onur,
Can we move the iomem to the HwGate and get rid of its Arc? This way we
ensure that all hardware access must consider the possibility of an ongoing
reset by having each component that needs hardware access hold an Arc<HwGate>
instead. Perhaps we can even broaden this to "hardware must be powered on" at
some point in the future.
Otherwise, this looks good to me. Let's wait for Alice too.
next prev parent reply other threads:[~2026-08-13 23:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 10:42 [PATCH v4 0/3] drm/tyr: GPU reset infrastructure Onur Özkan
2026-08-13 10:42 ` [PATCH v4 1/3] rust: workqueue: impl Send and Sync for OwnedQueue Onur Özkan
2026-08-13 10:42 ` [PATCH v4 2/3] drm/tyr: clear stale IRQ state before soft reset Onur Özkan
2026-08-13 10:42 ` [PATCH v4 3/3] drm/tyr: add GPU reset infrastructure Onur Özkan
2026-08-13 23:25 ` Daniel Almeida [this message]
2026-08-14 11:20 ` Onur Özkan
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=D4F91EDE-5FD1-41F8-B5AE-D8C2EA25545D@collabora.com \
--to=daniel.almeida@collabora.com \
--cc=a.hindborg@kernel.org \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--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