All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alistair Popple <apopple@nvidia.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: nova-gpu@lists.linux.dev, Alice Ryhl <aliceryhl@google.com>,
	 David Airlie <airlied@gmail.com>,
	Alexandre Courbot <acourbot@nvidia.com>,
	 Benno Lossin <lossin@kernel.org>, Gary Guo <gary@garyguo.net>,
	 Eliot Courtney <ecourtney@nvidia.com>,
	John Hubbard <jhubbard@nvidia.com>,
	linux-kernel@vger.kernel.org,  dri-devel@lists.freedesktop.org,
	rust-for-linux@vger.kernel.org
Subject: Re: [PATCH 3/4] drm: nova: Add GETPARAM parameter to read the GPU chipset
Date: Thu, 9 Jul 2026 11:31:07 +1000	[thread overview]
Message-ID: <ak75iSzu1ZFUcoqM@nvdebian.thelocal> (raw)
In-Reply-To: <DJRP04MWOO7Q.3DD6YF37RS5K2@kernel.org>

On 2026-07-07 at 04:16 +1000, Danilo Krummrich <dakr@kernel.org> wrote...
> On Mon Jul 6, 2026 at 7:34 AM CEST, Alistair Popple wrote:
> > @@ -31,7 +31,6 @@ pub(crate) struct Nova<'bound> {
> >  
> >  /// DRM registration data, accessible from ioctl handlers via the registration guard.
> >  pub(crate) struct DrmRegData<'bound> {
> > -    #[allow(dead_code)]
> 
> Forgot to mention that in the previous patch, please use expect instead.
> 
> > @@ -12,11 +12,11 @@
> >      types::CovariantForLt, //
> >  };
> >  
> > +use crate::gpu::Chipset;
> >  use crate::gpu::Gpu;
> 
> Vertical import style.
> 
> > @@ -25,6 +25,13 @@ extern "C" {
> >   */
> >  #define NOVA_GETPARAM_VRAM_BAR_SIZE	0x1
> >  
> > +/*
> > + * NOVA_GETPARAM_GPU_CHIPSET
> > + *
> > + * Query the GPU chipset architecture/implementation.
> > + */
> > +#define NOVA_GETPARAM_GPU_CHIPSET	0x2
> 
> We could provide an enum for the chipset values and use it in the definition of
> nova-core's Chipset type, which guarantees a single source of truth.
> 
> 	define_chipset!({
> 	    TU102 = uapi::NOVA_CHIPSET_TU102,
> 	    TU104 = uapi::NOVA_CHIPSET_TU104,
> 	    // ...
> 	});

The only downside I can see is it couples nova-core to nova-drm UAPI, but I
don't think that's really a problem so have done this for v2.

 - Alistair

  reply	other threads:[~2026-07-09  1:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06  5:34 [PATCH 0/4] gpu: nova: Export parameters from nova-core to nova-drm Alistair Popple
2026-07-06  5:34 ` [PATCH 1/4] gpu: nova-core: Add public driver API to nova-core Alistair Popple
2026-07-06 17:56   ` Danilo Krummrich
2026-07-06  5:34 ` [PATCH 2/4] gpu: nova: Add DRM registration data Alistair Popple
2026-07-06 18:01   ` Danilo Krummrich
2026-07-09  0:40     ` Alistair Popple
2026-07-06  5:34 ` [PATCH 3/4] drm: nova: Add GETPARAM parameter to read the GPU chipset Alistair Popple
2026-07-06 17:35   ` Timur Tabi
2026-07-06 18:24     ` Danilo Krummrich
2026-07-09  0:16       ` Alistair Popple
2026-07-09  0:49         ` John Hubbard
2026-07-09  4:31           ` Dave Airlie
2026-07-09 10:18           ` Danilo Krummrich
2026-07-06 18:16   ` Danilo Krummrich
2026-07-09  1:31     ` Alistair Popple [this message]
2026-07-06  5:34 ` [PATCH 4/4] drm: nova: Add a GETPARAM parameter to read usable VRAM size Alistair Popple
2026-07-06 18:26   ` Danilo Krummrich

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=ak75iSzu1ZFUcoqM@nvdebian.thelocal \
    --to=apopple@nvidia.com \
    --cc=acourbot@nvidia.com \
    --cc=airlied@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ecourtney@nvidia.com \
    --cc=gary@garyguo.net \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=nova-gpu@lists.linux.dev \
    --cc=rust-for-linux@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.