rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Timur Tabi" <ttabi@nvidia.com>,
	"Alexandre Courbot" <acourbot@nvidia.com>,
	"Joel Fernandes" <joelagnelf@nvidia.com>,
	"John Hubbard" <jhubbard@nvidia.com>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Lyude Paul" <lyude@redhat.com>, <nouveau@lists.freedesktop.org>,
	<rust-for-linux@vger.kernel.org>
Cc: "Nouveau" <nouveau-bounces@lists.freedesktop.org>
Subject: Re: [PATCH v3 06/12] gpu: nova-core: add Turing boot registers
Date: Wed, 17 Dec 2025 15:36:26 +0900	[thread overview]
Message-ID: <DF0A8A969D0M.24MRUBP6XTV8S@nvidia.com> (raw)
In-Reply-To: <20251208231801.1786803-7-ttabi@nvidia.com>

On Tue Dec 9, 2025 at 8:17 AM JST, Timur Tabi wrote:
> Define some more GPU registers used to boot GSP-RM on Turing and GA100.
>
> Signed-off-by: Timur Tabi <ttabi@nvidia.com>
> ---
>  drivers/gpu/nova-core/regs.rs | 63 +++++++++++++++++++++++++++++++++++
>  1 file changed, 63 insertions(+)
>
> diff --git a/drivers/gpu/nova-core/regs.rs b/drivers/gpu/nova-core/regs.rs
> index 88bec1d4830b..2143869d27ba 100644
> --- a/drivers/gpu/nova-core/regs.rs
> +++ b/drivers/gpu/nova-core/regs.rs
> @@ -258,6 +258,11 @@ pub(crate) fn vga_workspace_addr(self) -> Option<u64> {
>      6:6     swgen0 as bool;
>  });
>  
> +// Interrupt mask clear register. Writing 1 to a bit clears the corresponding interrupt mask.
> +register!(NV_PFALCON_FALCON_IRQMCLR @ PFalconBase[0x00000014] {
> +    31:0    value as u32;
> +});
> +

This register doesn't appear to be used in this series.

>  register!(NV_PFALCON_FALCON_MAILBOX0 @ PFalconBase[0x00000040] {
>      31:0    value as u32;
>  });
> @@ -266,6 +271,14 @@ pub(crate) fn vga_workspace_addr(self) -> Option<u64> {
>      31:0    value as u32;
>  });
>  
> +// Interface enable register.
> +register!(NV_PFALCON_FALCON_ITFEN @ PFalconBase[0x00000048] {
> +    0:0     ctxen as bool, "Context interface enable";
> +    1:1     mthden as bool, "Method interface enable";
> +    2:2     postwr as bool;
> +    4:4     secwl_cpuctl_alias as bool;
> +});
> +

Neither is this one.

>  // Used to store version information about the firmware running
>  // on the Falcon processor.
>  register!(NV_PFALCON_FALCON_OS @ PFalconBase[0x00000080] {
> @@ -307,6 +320,13 @@ pub(crate) fn mem_scrubbing_done(self) -> bool {
>      7:7     secure_stat as bool;
>  });
>  
> +impl NV_PFALCON_FALCON_DMACTL {
> +    /// Returns `true` if memory scrubbing is completed.
> +    pub(crate) fn mem_scrubbing_done(self) -> bool {
> +        !self.dmem_scrubbing() && !self.imem_scrubbing()
> +    }
> +}
> +
>  register!(NV_PFALCON_FALCON_DMATRFBASE @ PFalconBase[0x00000110] {
>      31:0    base as u32;
>  });
> @@ -353,6 +373,42 @@ pub(crate) fn with_falcon_mem(self, mem: FalconMem) -> Self {
>      1:1     startcpu as bool;
>  });
>  
> +// Config memory base address. Specifies the upper address bits that must be matched
> +// to access the config aperture. The base may not be zero as that would conflict with DMEM.
> +register!(NV_PFALCON2_FALCON_CMEMBASE @ PFalcon2Base[0x00000160] {
> +    31:18     value as u16;
> +});

Or this one.

For the one that remains, please introduce them in the patch that adds
PIO support - that way they are introduced alongside the code that makes
use of them. `regs.rs` is not touched in the PIO patch, so this also
won't complicate review.

  reply	other threads:[~2025-12-17  6:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08 23:17 [PATCH v3 00/12] gpu: nova-core: add Turing support Timur Tabi
2025-12-08 23:17 ` [PATCH v3 01/12] gpu: nova-core: rename Imem to ImemSecure Timur Tabi
2025-12-08 23:17 ` [PATCH v3 02/12] gpu: nova-core: add ImemNonSecure section infrastructure Timur Tabi
2025-12-08 23:17 ` [PATCH v3 03/12] gpu: nova-core: support header parsing on Turing/GA100 Timur Tabi
2025-12-17  6:23   ` Alexandre Courbot
2025-12-08 23:17 ` [PATCH v3 04/12] gpu: nova-core: add support for Turing/GA100 fwsignature Timur Tabi
2025-12-17  6:27   ` Alexandre Courbot
2025-12-08 23:17 ` [PATCH v3 05/12] gpu: nova-core: add NV_PFALCON_FALCON_DMATRFCMD::with_falcon_mem() Timur Tabi
2025-12-08 23:17 ` [PATCH v3 06/12] gpu: nova-core: add Turing boot registers Timur Tabi
2025-12-17  6:36   ` Alexandre Courbot [this message]
2025-12-08 23:17 ` [PATCH v3 07/12] gpu: nova-core: move some functions into the HAL Timur Tabi
2025-12-08 23:17 ` [PATCH v3 08/12] gpu: nova-core: Add basic Turing HAL Timur Tabi
2025-12-17  6:40   ` Alexandre Courbot
2025-12-08 23:17 ` [PATCH v3 09/12] gpu: nova-core: add Falcon HAL method supports_dma() Timur Tabi
2025-12-08 23:17 ` [PATCH v3 10/12] gpu: nova-core: add FalconUCodeDescV2 support Timur Tabi
2025-12-08 23:18 ` [PATCH v3 11/12] gpu: nova-core: align LibosMemoryRegionInitArgument size to page size Timur Tabi
2025-12-17  7:17   ` Alexandre Courbot
2025-12-08 23:18 ` [PATCH v3 12/12] gpu: nova-core: add PIO support for loading firmware images Timur Tabi
2025-12-17  6:37 ` [PATCH v3 00/12] gpu: nova-core: add Turing support Alexandre Courbot

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=DF0A8A969D0M.24MRUBP6XTV8S@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=dakr@kernel.org \
    --cc=jhubbard@nvidia.com \
    --cc=joelagnelf@nvidia.com \
    --cc=lyude@redhat.com \
    --cc=nouveau-bounces@lists.freedesktop.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=rust-for-linux@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).