From: Antonin Malzieu Ridolfi via B4 Relay <devnull+dev.nanonej.com@kernel.org>
To: Danilo Krummrich <dakr@kernel.org>,
Alexandre Courbot <acourbot@nvidia.com>,
Alice Ryhl <aliceryhl@google.com>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
Antonin Malzieu Ridolfi <dev@nanonej.com>
Cc: linux-kernel@vger.kernel.org, nova-gpu@lists.linux.dev,
dri-devel@lists.freedesktop.org, daniel.almeida@collabora.com
Subject: [PATCH 0/5] gpu: nova-core: Move registers definitions
Date: Wed, 17 Jun 2026 01:48:11 +0200 [thread overview]
Message-ID: <20260617-nova-core-regs-split-v1-0-4c7dc4450ea7@nanonej.com> (raw)
Split part of the registers definitions grouped in nova root register file
to belonging modules whom actually use them.
To: Danilo Krummrich <dakr@kernel.org>
To: Alexandre Courbot <acourbot@nvidia.com>
To: Alice Ryhl <aliceryhl@google.com>
To: David Airlie <airlied@gmail.com>
To: Simona Vetter <simona@ffwll.ch>
To: Antonin Malzieu Ridolfi <dev@nanonej.com>
Cc: linux-kernel@vger.kernel.org
Cc: nova-gpu@lists.linux.dev
Cc: dri-devel@lists.freedesktop.org
Cc: daniel.almeida@collabora.com
Suggested-by: Alexandre Courbot <acourbot@nvidia.com>
Suggested-by: Danilo Krummrich <dakr@kernel.org>
Signed-off-by: Antonin Malzieu Ridolfi <dev@nanonej.com>
---
Antonin Malzieu Ridolfi (5):
gpu: nova-core: fb: Move PDISP register definition
gpu: nova-core: gsp: Move PBUS register definition
gpu: nova-core: falcon: Move PFALCON2 register
gpu: nova-core: falcon: Move PRISCV register
gpu: nova-core: falcon: Move PFSP register
drivers/gpu/nova-core/falcon.rs | 71 +++++++++++---------
drivers/gpu/nova-core/falcon/fsp.rs | 14 ++--
drivers/gpu/nova-core/falcon/hal/ga102.rs | 32 +++++----
drivers/gpu/nova-core/falcon/hal/tu102.rs | 8 +--
drivers/gpu/nova-core/falcon/regs.rs | 76 +++++++++++++++++++++
drivers/gpu/nova-core/fb.rs | 4 +-
drivers/gpu/nova-core/fb/regs.rs | 25 +++++++
drivers/gpu/nova-core/gsp/hal/tu102.rs | 12 ++--
drivers/gpu/nova-core/gsp/regs.rs | 11 ++++
drivers/gpu/nova-core/regs.rs | 105 +-----------------------------
10 files changed, 191 insertions(+), 167 deletions(-)
---
base-commit: 5f7410aa26524101d34b627fbe16670b1514962c
change-id: 20260616-nova-core-regs-split-e2a8b22caaf4
Best regards,
--
Antonin Malzieu Ridolfi <dev@nanonej.com>
next reply other threads:[~2026-06-16 23:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 23:48 Antonin Malzieu Ridolfi via B4 Relay [this message]
2026-06-16 23:48 ` [PATCH 1/5] gpu: nova-core: fb: Move PDISP register definition Antonin Malzieu Ridolfi via B4 Relay
2026-06-23 6:18 ` Alexandre Courbot
2026-06-16 23:48 ` [PATCH 2/5] gpu: nova-core: gsp: Move PBUS " Antonin Malzieu Ridolfi via B4 Relay
2026-06-23 6:18 ` Alexandre Courbot
2026-06-16 23:48 ` [PATCH 3/5] gpu: nova-core: falcon: Move PFALCON2 register Antonin Malzieu Ridolfi via B4 Relay
2026-06-23 6:22 ` Alexandre Courbot
2026-06-16 23:48 ` [PATCH 4/5] gpu: nova-core: falcon: Move PRISCV register Antonin Malzieu Ridolfi via B4 Relay
2026-06-16 23:48 ` [PATCH 5/5] gpu: nova-core: falcon: Move PFSP register Antonin Malzieu Ridolfi via B4 Relay
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=20260617-nova-core-regs-split-v1-0-4c7dc4450ea7@nanonej.com \
--to=devnull+dev.nanonej.com@kernel.org \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dev@nanonej.com \
--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®