diff options
| author | Alistair Popple <apopple@nvidia.com> | 2026-09-09 16:44:58 +1000 |
|---|---|---|
| committer | Danilo Krummrich <dakr@kernel.org> | 2026-09-27 14:02:20 +0200 |
| commit | a1678ed1f8a344f1d2e4fc9362226555372d76d4 (patch) | |
| tree | 72ecac7ab98aa9e258405e86025d515fb3e59d1a /tools/lib/python | |
| parent | 342aaa7bb3cc1066ae9055c936b667ecd66de0ec (diff) | |
drm: nova: Add chipid enum to nova-drm UAPI
The chip identifier uniquely identifies a GPU chip and needs to be
exposed to user-space so it can look up chip specific properties that
cannot be derived from the architecture alone. This adds a public enum
to the userspace headers for each chip ID. Nova-core can then use this
enum to define its chipsets.
The values are opaque to user-space. They may be compared against the
enum to identify a chip but user-space must not assume the values carry
any particular meaning or encoding.
This does create a coupling between nova-drm and nova-core whereby
nova-core depends on the values defined by the user-space API for
nova-drm. However this is entirely appropriate as nova-core must be
bound by the UAPI headers as the enum values are read by nova-core and
passed through to user-space.
Note that nova-core currently refers to the chipid as a chipset. This
isn't ideal given that chipid is the preferred and more accurate term
and is what should be exposed via the uAPI. Therefore a future patch
series will be posted that aligns nova-core internals to using chipid
rather than chipset.
Assisted-by: LLM
Signed-off-by: Alistair Popple <apopple@nvidia.com>
Link: https://patch.msgid.link/20260909064506.910162-6-apopple@nvidia.com
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions
