The Linux Kernel Mailing List
 help / color / mirror / Atom feed
* Re: [PATCH v3 0/2] Add AM62P silicon revision detection via NVMEM
       [not found] <20260209172330.53623-1-jm@ti.com>
@ 2026-05-05 13:59 ` Nishanth Menon
  2026-05-06 11:09 ` Francesco Dolcini
  1 sibling, 0 replies; 3+ messages in thread
From: Nishanth Menon @ 2026-05-05 13:59 UTC (permalink / raw)
  To: Vignesh Raghavendra, Tero Kristo, Rob Herring,
	Krzysztof Kozlowski, Conor Dooley, Santosh Shilimkar,
	Judith Mendez
  Cc: Nishanth Menon, linux-arm-kernel, devicetree, linux-kernel,
	Andrew Davis

Hi Judith Mendez,

On Mon, 09 Feb 2026 11:23:28 -0600, Judith Mendez wrote:
> This series adds support for detecting AM62P silicon revisions using
> the NVMEM framework to read the GP_SW1 register.
> 
> Background:
> ===========
> On AM62P SoCs, the standard JTAGID register does not provide information
> on silicon revision, instead the GP_SW1 register contains the information
> needed for proper device identification.
> 
> [...]

I have applied the following to branch ti-drivers-soc-next on [1].
Thank you!

[1/2] dt-bindings: hwinfo: ti,k3-socinfo: Add nvmem-cells support
      commit: b0ea5175358f0872ffdc9c6073585637dc01815a
[2/2] soc: ti: k3-socinfo: Add support for AM62P variants via NVMEM
      commit: 97cfbd30525ef0df3de0681a4ca04a80a06d4f16

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
https://ti.com/opensource


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH v3 0/2] Add AM62P silicon revision detection via NVMEM
       [not found] <20260209172330.53623-1-jm@ti.com>
  2026-05-05 13:59 ` [PATCH v3 0/2] Add AM62P silicon revision detection via NVMEM Nishanth Menon
@ 2026-05-06 11:09 ` Francesco Dolcini
  2026-05-06 14:09   ` Andrew Davis
  1 sibling, 1 reply; 3+ messages in thread
From: Francesco Dolcini @ 2026-05-06 11:09 UTC (permalink / raw)
  To: Judith Mendez
  Cc: Nishanth Menon, Vignesh Raghavendra, Tero Kristo, Rob Herring,
	Krzysztof Kozlowski, Conor Dooley, Santosh Shilimkar,
	linux-arm-kernel, devicetree, linux-kernel, Andrew Davis

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.

Francesco


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH v3 0/2] Add AM62P silicon revision detection via NVMEM
  2026-05-06 11:09 ` Francesco Dolcini
@ 2026-05-06 14:09   ` Andrew Davis
  0 siblings, 0 replies; 3+ messages in thread
From: Andrew Davis @ 2026-05-06 14:09 UTC (permalink / raw)
  To: Francesco Dolcini, Judith Mendez
  Cc: Nishanth Menon, Vignesh Raghavendra, Tero Kristo, Rob Herring,
	Krzysztof Kozlowski, Conor Dooley, Santosh Shilimkar,
	linux-arm-kernel, devicetree, linux-kernel

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
> 


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-05-06 14:09 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20260209172330.53623-1-jm@ti.com>
2026-05-05 13:59 ` [PATCH v3 0/2] Add AM62P silicon revision detection via NVMEM Nishanth Menon
2026-05-06 11:09 ` Francesco Dolcini
2026-05-06 14:09   ` Andrew Davis

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox