linux-kernel - Re: [PATCH v3 resend 2/7] nvmem: Add R-Car E-FUSE driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <5b4afe5b-a7aa-483f-be53-cd6a8de777db@app.fastmail.com>
Date: Fri, 04 Oct 2024 13:23:11 +0000
From: "Arnd Bergmann" <arnd@...db.de>
To: "Geert Uytterhoeven" <geert+renesas@...der.be>,
 "Srinivas Kandagatla" <srinivas.kandagatla@...aro.org>,
 "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>
Cc: devicetree@...r.kernel.org,
 Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 resend 2/7] nvmem: Add R-Car E-FUSE driver

On Thu, Oct 3, 2024, at 14:04, Geert Uytterhoeven wrote:
> R-Car Gen4 SoCs contain fuses indicating hardware support or hardware
> (e.g. tuning) parameters.  Add a driver to access the state of the
> fuses.  This supports two types of hardware fuse providers:
>   1. E-FUSE non-volatile memory accessible through the Pin Function
>      Controller on R-Car V3U and S4-8,
>   2. E-FUSE non-volatile memory accessible through OTP_MEM on R-Car V4H
>      and V4M.
>
> The state of the cells can be read using the NVMEM framework, either
> from kernel space (e.g. by the Renesas UFSHCD driver), or from
> userspace.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
> Reviewed-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>

Acked-by: Arnd Bergmann <arnd@...db.de>