From: John Hubbard <jhubbard@nvidia.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: "Alexandre Courbot" <acourbot@nvidia.com>,
"Joel Fernandes" <joelagnelf@nvidia.com>,
"Timur Tabi" <ttabi@nvidia.com>,
"Alistair Popple" <apopple@nvidia.com>,
"Edwin Peer" <epeer@nvidia.com>, "Zhi Wang" <zhiw@nvidia.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
nouveau@lists.freedesktop.org, rust-for-linux@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] gpu: nova-core: merge the Revision type into the Spec type
Date: Tue, 28 Oct 2025 10:25:33 -0700 [thread overview]
Message-ID: <ce6366ed-4a9a-4a8d-9207-f1da487dca62@nvidia.com> (raw)
In-Reply-To: <DDTYCAZWUZL5.36Y1LKLB8EUD6@kernel.org>
On 10/28/25 5:25 AM, Danilo Krummrich wrote:
> On Tue Oct 28, 2025 at 3:39 AM CET, John Hubbard wrote:
>> -pub(crate) struct Revision {
>> - major: u8,
>> - minor: u8,
>> -}
>> -
>> -impl Revision {
>> - fn from_boot0(boot0: regs::NV_PMC_BOOT_0) -> Self {
>> - Self {
>> - major: boot0.major_revision(),
>> - minor: boot0.minor_revision(),
>> - }
>> - }
>> -}
>> -
>> -impl fmt::Display for Revision {
>> - fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
>> - write!(f, "{:x}.{:x}", self.major, self.minor)
>> - }
>> -}
>> -
>> -/// Structure holding the metadata of the GPU.
>> +/// Structure holding a basic description of the GPU: Architecture, Chipset and Revision.
>> pub(crate) struct Spec {
>> chipset: Chipset,
>> - /// The revision of the chipset.
>> - revision: Revision,
>> + major_revision: u8,
>> + minor_revision: u8,
>> }
>
> Why not keep the Revision type and its Display impl as well?
I just felt like it's not quite pulling its weight. But clearly
that feeling is not widely shared, so I'll put it back in. :)
>
>>
>> impl Spec {
>> @@ -162,11 +142,25 @@ fn new(bar: &Bar0) -> Result<Spec> {
>>
>> Ok(Self {
>> chipset: boot0.chipset()?,
>> - revision: Revision::from_boot0(boot0),
>> + major_revision: boot0.major_revision(),
>> + minor_revision: boot0.minor_revision(),
>> })
>> }
>> }
>>
>> +impl fmt::Display for Spec {
>> + fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
>> + write!(
>> + f,
>> + "Chipset: {}, Architecture: {:?}, Revision: {:x}.{:x}",
>> + self.chipset,
>> + self.chipset.arch(),
>> + self.major_revision,
>> + self.minor_revision
>> + )
>
> This could just be:
>
> write!(
> f,
> "Chipset: {}, Architecture: {:?}, Revision: {}",
> self.chipset,
> self.chipset.arch(),
> self.revision,
> )
>
Yes. That is nicer.
thanks,
John Hubbard
next prev parent reply other threads:[~2025-10-28 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 2:39 [PATCH v2 0/2] gpu: nova: add boot42 support for next-gen GPUs John Hubbard
2025-10-28 2:39 ` [PATCH v2 1/2] gpu: nova-core: merge the Revision type into the Spec type John Hubbard
2025-10-28 12:25 ` Danilo Krummrich
2025-10-28 17:25 ` John Hubbard [this message]
2025-10-28 2:39 ` [PATCH v2 2/2] gpu: nova-core: add boot42 support for next-gen GPUs John Hubbard
2025-10-28 11:42 ` Alexandre Courbot
2025-10-28 17:22 ` John Hubbard
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=ce6366ed-4a9a-4a8d-9207-f1da487dca62@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=epeer@nvidia.com \
--cc=gary@garyguo.net \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=tmgross@umich.edu \
--cc=ttabi@nvidia.com \
--cc=zhiw@nvidia.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