[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <172829154816.179131.15672013040030058967.b4-ty@linaro.org>
Date: Mon, 07 Oct 2024 09:59:08 +0100
From: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Magnus Damm <magnus.damm@...il.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>,
Arnd Bergmann <arnd@...db.de>, Geert Uytterhoeven <geert+renesas@...der.be>
Cc: devicetree@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH v3 resend 0/7] Add Renesas R-Car Gen4 E-FUSE
support
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@...aro.org>
Powered by blists - more mailing lists