On Thu, 03 Oct 2024 16:04:24 +0200, Geert Uytterhoeven wrote:
> Hi all,
>
> (another rc1, so time for a resend)
>
> R-Car Gen3/Gen4 SoCs contain fuses indicating hardware support or
> hardware parameters. Unfortunately the various SoCs require different
> mechanisms to read the state of the fuses:
> - On R-Car Gen3, the fuse monitor registers are in the middle of the
> Pin Function Controller (PFC) register block,
> - On R-Car V3U and S4-8, the E-FUSE non-volatile memory is accessible
> through a separate register block in the PFC,
> - On R-Car V4H and V4M, the E-FUSE non-volatile memory is accessible
> through the second register block of OTP_MEM.
>
> [...]
Applied, thanks!
[1/7] dt-bindings: fuse: Move renesas,rcar-{efuse,otp} to nvmem
commit: 149e83f1b385661cae3a60cf27271e6ee53ea6e3
[2/7] nvmem: Add R-Car E-FUSE driver
commit: 5ac5933d4e06647b83f6b971b18bc894903a83f2
Best regards,
--
Srinivas Kandagatla <srinivas.kandagatla@xxxxxxxxxx>
