From: Joel Fernandes <joelagnelf@nvidia.com>
To: linux-kernel@vger.kernel.org
Cc: Danilo Krummrich <dakr@kernel.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Alexandre Courbot <acourbot@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>,
Shirish Baskaran <sbaskaran@nvidia.com>,
Alistair Popple <apopple@nvidia.com>,
Timur Tabi <ttabi@nvidia.com>, Ben Skeggs <bskeggs@nvidia.com>,
Joel Fernandes <joelagnelf@nvidia.com>
Subject: [PATCH 0/6] Additional documentation for nova-core
Date: Wed, 23 Apr 2025 18:53:56 -0400 [thread overview]
Message-ID: <20250423225405.139613-1-joelagnelf@nvidia.com> (raw)
Hello,
Please find in this series, several clarifications, diagrams and code comments
for various things in the nova-core driver. These are essential to develop an
understanding how nova-core's boot initialization works and aid in development.
These patches are on top of Alex's last posting for GSP WPR2 [1]
[1] https://lore.kernel.org/all/20250420-nova-frts-v1-0-ecd1cca23963@nvidia.com/
Joel Fernandes (6):
nova-core: doc: Add code comments related to devinit
nova-core: doc: Clarify sysmembar operations
nova-core: docs: Document vbios layout
nova-core: docs: Document fwsec operation and layout
gpu: nova-core: Clarify fields in FalconAppifHdrV1
nova-core: docs: Document devinit process
Documentation/gpu/nova/core/devinit.rst | 54 ++++++++
Documentation/gpu/nova/core/fwsec.rst | 173 ++++++++++++++++++++++++
Documentation/gpu/nova/core/vbios.rst | 155 +++++++++++++++++++++
Documentation/gpu/nova/index.rst | 2 +
drivers/gpu/nova-core/devinit.rs | 36 ++++-
drivers/gpu/nova-core/firmware/fwsec.rs | 17 ++-
drivers/gpu/nova-core/gpu.rs | 11 +-
drivers/gpu/nova-core/regs.rs | 17 ++-
8 files changed, 452 insertions(+), 13 deletions(-)
create mode 100644 Documentation/gpu/nova/core/devinit.rst
create mode 100644 Documentation/gpu/nova/core/fwsec.rst
create mode 100644 Documentation/gpu/nova/core/vbios.rst
--
2.43.0
next reply other threads:[~2025-04-23 22:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 22:53 Joel Fernandes [this message]
2025-04-23 22:53 ` [PATCH 1/6] nova-core: doc: Add code comments related to devinit Joel Fernandes
2025-04-23 22:53 ` [PATCH 2/6] nova-core: doc: Clarify sysmembar operations Joel Fernandes
2025-04-23 22:53 ` [PATCH 3/6] nova-core: docs: Document vbios layout Joel Fernandes
2025-04-23 23:12 ` Timur Tabi
2025-04-23 23:30 ` Joel Fernandes
2025-04-23 22:54 ` [PATCH 4/6] nova-core: docs: Document fwsec operation and layout Joel Fernandes
2025-04-23 22:54 ` [PATCH 5/6] gpu: nova-core: Clarify fields in FalconAppifHdrV1 Joel Fernandes
2025-04-24 1:18 ` Alexandre Courbot
[not found] ` <174546399398.876.3516508778193165894@patchwork.local>
2025-04-24 7:45 ` [5/6] " Alexandre Courbot
2025-04-24 13:03 ` Joel Fernandes
2025-04-23 22:54 ` [PATCH 6/6] nova-core: docs: Document devinit process Joel Fernandes
2025-04-24 1:25 ` [PATCH 0/6] Additional documentation for nova-core Alexandre Courbot
2025-04-24 8:10 ` 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=20250423225405.139613-1-joelagnelf@nvidia.com \
--to=joelagnelf@nvidia.com \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=apopple@nvidia.com \
--cc=bskeggs@nvidia.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=sbaskaran@nvidia.com \
--cc=simona@ffwll.ch \
--cc=ttabi@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
all inboxes | Powered by JetHome®