Hi Krzysztof,

Thank you for the quick response!
On 02/08/2025 11:32, Krzysztof Kozlowski wrote:

On 02/08/2025 10:28, Krzysztof Kozlowski wrote:

quoted

On 01/08/2025 16:36, Andrei Stefanescu wrote:

quoted

Apart from the proposed NVMEM driver, there is also an option of exporting
a syscon regmap for the registers which provide information about the SoC.

I have seen that typically NVMEM drivers export information read from fuses
but I think having a NVMEM driver is nicer way to access the information
instead of using a syscon regmap and manually extracting the needed bits. 

nvmem is not a syscon. Mixing these two means device is something
completely else.

Yes, I don't want to mix them. The driver will either be a NVMEM driver or
a syscon. These registers are read-only. I suggested NVMEM because it's a
an abstraction layer which makes it easier for drivers which want to use
that information without knowing where to actually read it i.e. reg address,
bit mask.

What do think? Which one would be better? Do you have other suggestions?

Best regards,
Andrei

... and yes, I am aware that three FSL/NXP bindings use nvmem as syscon
already. People are mixing hardware description (nvmem) with some
purpose for drivers (syscon) forgetting that syscon are miscellaneous
SoC internal registers, not non-volatile memory.

Best regards,
Krzysztof