From: Timur Tabi <ttabi@nvidia.com>
To: "airlied@gmail.com" <airlied@gmail.com>
Cc: "nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [Nouveau] [PATCH 3/3] nouveau/gsp: add some basic registry entries.
Date: Tue, 31 Oct 2023 20:02:42 +0000 [thread overview]
Message-ID: <1b84e30b689947e48d14aecb6787944d98699999.camel@nvidia.com> (raw)
In-Reply-To: <CAPM=9twkLVo4aF5exWLXVfRxewcDvb17k9O3L1uB3-KG4g4FMw@mail.gmail.com>
On Wed, 2023-11-01 at 05:29 +1000, Dave Airlie wrote:
> >
> > static const struct nv_gsp_registry_entries r535_registry_entries[] = {
> > { "RMSecBusResetEnable", 1 },
> > { "RMForcePcieConfigSave", 1 },
> > };
> >
> > #define NV_GSP_REG_NUM_ENTRIES ARRAY_SIZE(r535_registry_entries)
>
> Good plan. I'll change that now.
BTW, I looked into these two options. Basically, these options enable
"secondary bus reset", although I'm not exactly sure what that means. It
does enable saving of PCI config registers, so perhaps it preserves those
registers for Nouveau when GSP-RM does a PCI reset.
Also, like I mentioned on IRC earlier, I've got a bunch of patches that
provide mroe robust registry control, including setting options from the
command-line. I'll post those upstream once the dust has settled.
next prev parent reply other threads:[~2023-10-31 20:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 5:18 [Nouveau] nouveau/gsp: move to latest fw and small fixes Dave Airlie
2023-10-31 5:18 ` Dave Airlie
2023-10-31 5:18 ` [Nouveau] [PATCH 1/3] nouveau/gsp: move to 535.113.01 Dave Airlie
2023-10-31 5:18 ` Dave Airlie
2023-10-31 5:18 ` [Nouveau] [PATCH 2/3] nouveau/gsp: fix message signature Dave Airlie
2023-10-31 5:18 ` Dave Airlie
2023-10-31 5:18 ` [Nouveau] [PATCH 3/3] nouveau/gsp: add some basic registry entries Dave Airlie
2023-10-31 5:18 ` Dave Airlie
2023-10-31 15:52 ` [Nouveau] " Timur Tabi
2023-10-31 19:29 ` Dave Airlie
2023-10-31 20:02 ` Timur Tabi [this message]
2023-11-07 18:51 ` Timur Tabi
2023-11-07 18:54 ` Dave Airlie
2023-11-07 19:02 ` Timur Tabi
2023-11-27 20:47 ` Timur Tabi
2023-11-27 21:32 ` Dave Airlie
2023-11-03 2:03 ` [Nouveau] nouveau/gsp: move to latest fw and small fixes 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=1b84e30b689947e48d14aecb6787944d98699999.camel@nvidia.com \
--to=ttabi@nvidia.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=nouveau@lists.freedesktop.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.