From: Laura Nao <laura.nao@collabora.com>
To: work@onurozkan.dev
Cc: a.hindborg@kernel.org, acourbot@nvidia.com, airlied@gmail.com,
aliceryhl@google.com, bjorn3_gh@protonmail.com, boqun@kernel.org,
dakr@kernel.org, daniel.almeida@collabora.com,
deborah.brouwer@collabora.com, dri-devel@lists.freedesktop.org,
gary@garyguo.net, kernel@collabora.com, laura.nao@collabora.com,
linux-kernel@vger.kernel.org, lossin@kernel.org,
ojeda@kernel.org, rust-for-linux@vger.kernel.org,
simona@ffwll.ch, tamird@kernel.org, tmgross@umich.edu
Subject: Re: [PATCH v2] drm/tyr: add Job IRQ handling
Date: Thu, 30 Jul 2026 11:45:25 +0200 [thread overview]
Message-ID: <20260730094525.245487-1-laura.nao@collabora.com> (raw)
In-Reply-To: <20260729165121.768013-1-work@onurozkan.dev>
Hi Onur,
On 7/29/26 18:51, Onur Özkan wrote:
> On Wed, 29 Jul 2026 11:58:29 +0200
> Laura Nao <laura.nao@collabora.com> wrote:
>
>> +
>> + fn handle(&self, status: u32) {
>> + if JOB_IRQ_RAWSTAT::from_raw(status).glb() {
>> + self.fw_ready.store(true, Ordering::Release);
>> + self.job_irq_wait.wake_up_all();
>> + }
>
> You enable both GLB and CSG above but only handle GLB, is this intentional? This
> means CSG will trigger the handler, do nothing and just get cleared, or am I
> missing something?
>
The series that will later add CSF interface support will likely only
include a firmware readiness check at first, with CSG bit handling
added at a later stage. That's why we're only handling the GLB bit for
now, but I agree unmasking the CSG bits here is premature then. I can
drop this in the next revision, keep only the GLB bit unmasking/handling
and add a TODO comment for the CSG bits.
Thanks!
Laura
prev parent reply other threads:[~2026-07-30 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 9:58 Laura Nao
2026-07-29 12:12 ` Ewan Chorynski
2026-07-29 13:25 ` Laura Nao
2026-07-29 16:51 ` Onur Özkan
2026-07-30 9:45 ` Laura Nao [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=20260730094525.245487-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=lossin@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®