From: Zhi Wang <zhiw@nvidia.com>
To: Aaron Kling <webgeek1234@gmail.com>
Cc: Karol Herbst <kherbst@redhat.com>, Lyude Paul <lyude@redhat.com>,
"Danilo Krummrich" <dakr@kernel.org>,
David Airlie <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
Ben Skeggs <bskeggs@redhat.com>,
<dri-devel@lists.freedesktop.org>,
<nouveau@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/nouveau/pmu: Fix gp10b firmware guard
Date: Tue, 18 Feb 2025 10:32:22 +0200 [thread overview]
Message-ID: <20250218103222.0000313b@nvidia.com> (raw)
In-Reply-To: <CALHNRZ99cs=rcR07jqsZE7Q3ndLqteKG8K8zpAm4vaEhsYwTLw@mail.gmail.com>
On Mon, 17 Feb 2025 17:46:41 -0600
Aaron Kling <webgeek1234@gmail.com> wrote:
> On Mon, Feb 17, 2025 at 5:43 PM Aaron Kling via B4 Relay
> <devnull+webgeek1234.gmail.com@kernel.org> wrote:
> >
> > From: Aaron Kling <webgeek1234@gmail.com>
> >
> > Fixes: 989863d7cbe5 ("drm/nouveau/pmu: select implementation based on available firmware")
> > Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> > ---
> > drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gp10b.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gp10b.c b/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gp10b.c
> > index a6f410ba60bc94ec9d52fc78868acddfc6770e19..d393bc540f8628812990dffe4c2f7e9014be07c5 100644
> > --- a/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gp10b.c
> > +++ b/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gp10b.c
> > @@ -75,7 +75,7 @@ gp10b_pmu_acr = {
> > .bootstrap_multiple_falcons = gp10b_pmu_acr_bootstrap_multiple_falcons,
> > };
> >
> > -#if IS_ENABLED(CONFIG_ARCH_TEGRA_210_SOC)
> > +#if IS_ENABLED(CONFIG_ARCH_TEGRA_186_SOC)
> > MODULE_FIRMWARE("nvidia/gp10b/pmu/desc.bin");
> > MODULE_FIRMWARE("nvidia/gp10b/pmu/image.bin");
> > MODULE_FIRMWARE("nvidia/gp10b/pmu/sig.bin");
> >
> > ---
> > base-commit: 2408a807bfc3f738850ef5ad5e3fd59d66168996
> > change-id: 20250217-nouveau-gm10b-guard-a438402b5022
> >
> > Best regards,
> > --
> > Aaron Kling <webgeek1234@gmail.com>
> >
> >
>
> Apologies to the maintainers for the multiple resends. For some reason
> the lists weren't accepting my submissions. Looks like it went through
> with b4, so hopefully I won't have more trouble in the future.
>
It seems like this version doesn't have a comment body. Might need to
double check the b4 setup.
> Sincerely,
> Aaron Kling
>
next prev parent reply other threads:[~2025-02-18 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 23:43 [PATCH] drm/nouveau/pmu: Fix gp10b firmware guard Aaron Kling via B4 Relay
2025-02-17 23:46 ` Aaron Kling
2025-02-18 8:32 ` Zhi Wang [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-30 21:25 Aaron Kling
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=20250218103222.0000313b@nvidia.com \
--to=zhiw@nvidia.com \
--cc=airlied@gmail.com \
--cc=bskeggs@redhat.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kherbst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=simona@ffwll.ch \
--cc=webgeek1234@gmail.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