From: Andrew Davis <afd@ti.com>
To: Francesco Dolcini <francesco@dolcini.it>, Judith Mendez <jm@ti.com>
Cc: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
"Tero Kristo" <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Santosh Shilimkar" <ssantosh@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] Add AM62P silicon revision detection via NVMEM
Date: Wed, 6 May 2026 09:09:37 -0500 [thread overview]
Message-ID: <f5d3795a-32a3-4d86-8813-e74fc8e41725@ti.com> (raw)
In-Reply-To: <20260506110920.GA53971@francesco-nb>
On 5/6/26 6:09 AM, Francesco Dolcini wrote:
> Hello Judith,
>
> On Mon, Feb 09, 2026 at 11:23:28AM -0600, Judith Mendez wrote:
>
> ...
>
>> - NVMEM support is fully optional - the driver continues to work without
>> it and falls back to SR1.0 for AM62P devices
>
> Is this correct? Just wanted to be sure, given the issue we had with TI
> 6.18 kernel on this very specific topic.
>
If you do not define an NVMEM node in DT then this driver falls back to
SR1.0 and continues working. If you do define an NVMEN node but do not
enable the NVMEM driver for that node then you will go into a probe
defer loop as you found. This is a general issue not specific to this
driver that could perhaps be solved by setting limits on probe reattempts,
but that is outside the scope of this series.
Andrew
> Francesco
>
prev parent reply other threads:[~2026-05-06 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 17:23 [PATCH v3 0/2] Add AM62P silicon revision detection via NVMEM Judith Mendez
2026-02-09 17:23 ` [PATCH v3 1/2] dt-bindings: hwinfo: ti,k3-socinfo: Add nvmem-cells support Judith Mendez
2026-02-09 17:23 ` [PATCH v3 2/2] soc: ti: k3-socinfo: Add support for AM62P variants via NVMEM Judith Mendez
2026-05-05 13:59 ` [PATCH v3 0/2] Add AM62P silicon revision detection " Nishanth Menon
2026-05-06 11:09 ` Francesco Dolcini
2026-05-06 14:09 ` Andrew Davis [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=f5d3795a-32a3-4d86-8813-e74fc8e41725@ti.com \
--to=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=francesco@dolcini.it \
--cc=jm@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.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