The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: Jonathan Hunter <jonathanh@nvidia.com>,
	 Dmitry Osipenko <digetx@gmail.com>,
	Thierry Reding <treding@nvidia.com>,
	linux-tegra@vger.kernel.org,  linux-kernel@vger.kernel.org,
	kernel-team@meta.com
Subject: Re: [PATCH] soc/tegra: fuse: Fix spurious straps warning on SMCCC platforms
Date: Mon, 22 Jun 2026 09:24:03 +0200	[thread overview]
Message-ID: <ajjfgOLpDXuVHpI0@orome> (raw)
In-Reply-To: <ajAa4JAXyssMpr1R@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2977 bytes --]

On Mon, Jun 15, 2026 at 08:32:25AM -0700, Breno Leitao wrote:
> 
> On Thu, Jun 04, 2026 at 03:36:17AM -0700, Breno Leitao wrote:
> > My Grace host started to show this warning:
> >   WARNING: drivers/soc/tegra/fuse/tegra-apbmisc.c:120 at tegra_read_straps
> >    tegra30_fuse_add_randomness
> >    tegra30_fuse_init
> >    tegra_fuse_probe
> > 
> > tegra_read_straps() warns when the static "chipid" cache is still zero,
> > using it as a proxy for "APBMISC has been initialised". However chipid
> > is only ever populated lazily by tegra_read_chipid() when it reads the
> > APBMISC register.
> > 
> > Guard on apbmisc_base instead, which is set unconditionally in
> > tegra_init_apbmisc_resources() for all platforms and is already the
> > sentinel used by tegra_read_chipid().
> > 
> > Fixes: c71f213fa5af ("soc/tegra: fuse: Warn if straps are not ready")
> > Signed-off-by: Breno Leitao <leitao@debian.org>
> > ---
> >  drivers/soc/tegra/fuse/tegra-apbmisc.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/soc/tegra/fuse/tegra-apbmisc.c b/drivers/soc/tegra/fuse/tegra-apbmisc.c
> > index 87ae63a7e52d..7aba7c58bad0 100644
> > --- a/drivers/soc/tegra/fuse/tegra-apbmisc.c
> > +++ b/drivers/soc/tegra/fuse/tegra-apbmisc.c
> > @@ -117,7 +117,7 @@ bool tegra_is_silicon(void)
> >  
> >  u32 tegra_read_straps(void)
> >  {
> > -	WARN(!chipid, "Tegra ABP MISC not yet available\n");
> > +	WARN(!apbmisc_base, "Tegra ABP MISC not yet available\n");
> 
> Hello Thierry,
> 
> Have you had a chance to look at this one? This is showing up in my
> Grace all the time.

Yeah, sorry for the delay. You're right in that we now get the warning
until we end up calling tegra_read_chipid(). However, I don't think the
Fixes: reference is right. I think this started showing up after:

  8b8ee2e56f95 ("soc/tegra: Use ARM SMCCC to get chip ID, revision, and platform info")

I don't think we accounted for tegra_read_straps() in that case and I
suspect that we're not seeing this elsewhere because we do end up
calling tegra_read_chipid() earlier in DT systems whereas for ACPI it
might only get called at a later point, if at all.

There's also this patch:

  https://lore.kernel.org/linux-tegra/20260514051252.2401568-1-kkartik@nvidia.com/

IIUC, that's the only place where tegra_read_straps() gets called on
ACPI systems. Would you mind testing that patch (without the one that
we're currently discussing) to confirm that that's the only callsite?
It doesn't really matter either way, because applying your fix here is
the right thing to do, but it'd still be useful as a data point.

If you don't have any objections, I'm going to replace the Fixes: line,
but otherwise this patch looks good.

Also, I'm going to check if we can get some better coverage in our daily
testing for the ACPI platforms. Do you happen to run any daily tests on
your systems for linux-next?

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-06-22  7:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04 10:36 [PATCH] soc/tegra: fuse: Fix spurious straps warning on SMCCC platforms Breno Leitao
2026-06-15 15:32 ` Breno Leitao
2026-06-22  7:24   ` Thierry Reding [this message]
2026-06-22  9:33     ` Breno Leitao
2026-06-22 13:37     ` Jon Hunter

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=ajjfgOLpDXuVHpI0@orome \
    --to=thierry.reding@kernel.org \
    --cc=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=kernel-team@meta.com \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=treding@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