The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Thierry Reding <thierry.reding@kernel.org>,
	 Jonathan Hunter <jonathanh@nvidia.com>,
	Dmitry Osipenko <digetx@gmail.com>
Cc: 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, 15 Jun 2026 08:32:25 -0700	[thread overview]
Message-ID: <ajAa4JAXyssMpr1R@gmail.com> (raw)
In-Reply-To: <20260604-tegra_warn_fix-v1-1-78522c852340@debian.org>


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.

Thanks


      reply	other threads:[~2026-06-15 15:32 UTC|newest]

Thread overview: 2+ 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 [this message]

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