From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Nanonej Dev" <dev@nanonej.com>
Cc: "Antonin Malzieu Ridolfi via B4 Relay"
<devnull+dev.nanonej.com@kernel.org>,
"Danilo Krummrich" <dakr@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>, <linux-kernel@vger.kernel.org>,
<nova-gpu@lists.linux.dev>, <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 4/4] gpu: nova-core: Extract PFALCON register
Date: Tue, 22 Sep 2026 08:14:06 +0900 [thread overview]
Message-ID: <DLLDJLPUZGMT.1JPALHEPYP3YF@nvidia.com> (raw)
In-Reply-To: <2jQVZV73cgrJOjnRVQ-gT1k4iBhKks2rB7H2doPH0l4zkbumXvnyoLEIFmATkIhpfwxRBwOFClJrf0f_iM7-mHyvYFbgyXt25Aqqp50vm18=@nanonej.com>
On Tue Sep 22, 2026 at 12:13 AM JST, Nanonej Dev wrote:
>
>> > I'd like the method to look at bit less
>> > ad-hoc and more confined. So would you:
>> >
>> > - Move it to `falcon/gsp.rs` and implement it only to `Falcon<Gsp>`, as
>> > that's the only case where we need it so far,
>> > - Make `ctx_dma` a `usize` (it's the caller's problem to provide the
>> > correct type),
>> > - Add the `FalconFbifTarget` and `FalconFbifMemType` as arguments of the
>> > method,
>> > - Maybe rename it to `set_fbif_transcfg`, because the fact we touch
>> > registers is an abstraction detail.
>> >
>> > As a side-note, the series is going to clash heavily with Gary's, and
>> > will need to be rebased on top of it after Gary's series is merged
>> > (which as far as I'm concerned should be the next version).
>>
>
>> Thanks for the review I'll refacto on a v2 like that then and wait for
>> Gary's series to rebase and send it.
>
> I see the patch have been merged [1], so I'll rebase and make a refacto for a v2
>
> [1] https://gitlab.freedesktop.org/drm/rust/kernel/-/commit/ea79a50124315589da68cbcaf518455a142d6d23
Oh yes, I was about to mention it - now is probably a good time. Thanks!
prev parent reply other threads:[~2026-09-21 23:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 23:44 [PATCH 0/4] gpu: nova-core: Extract falcon registers Antonin Malzieu Ridolfi via B4 Relay
2026-08-25 23:44 ` [PATCH 1/4] gpu: nova-core: Extract PFSP register definitions Antonin Malzieu Ridolfi via B4 Relay
2026-08-25 23:44 ` [PATCH 2/4] gpu: nova-core: falcon: Extract PRISCV register Antonin Malzieu Ridolfi via B4 Relay
2026-08-25 23:44 ` [PATCH 3/4] gpu: nova-core: falcon: Extract PFALCON2 register Antonin Malzieu Ridolfi via B4 Relay
2026-08-25 23:44 ` [PATCH 4/4] gpu: nova-core: Extract PFALCON register Antonin Malzieu Ridolfi via B4 Relay
2026-08-28 1:12 ` Alexandre Courbot
2026-08-28 23:30 ` Nanonej Dev
2026-09-21 15:13 ` Nanonej Dev
2026-09-21 23:14 ` Alexandre Courbot [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=DLLDJLPUZGMT.1JPALHEPYP3YF@nvidia.com \
--to=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=dev@nanonej.com \
--cc=devnull+dev.nanonej.com@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nova-gpu@lists.linux.dev \
--cc=simona@ffwll.ch \
/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®