From: "Arnd Bergmann" <arnd@arndb.de>
To: "Geert Uytterhoeven" <geert+renesas@glider.be>,
"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Magnus Damm" <magnus.damm@gmail.com>,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>
Cc: devicetree@vger.kernel.org,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 resend 2/7] nvmem: Add R-Car E-FUSE driver
Date: Fri, 04 Oct 2024 13:23:11 +0000 [thread overview]
Message-ID: <5b4afe5b-a7aa-483f-be53-cd6a8de777db@app.fastmail.com> (raw)
In-Reply-To: <563d35a3613c3356536978c0e5dc5ad5e47bbd7d.1727963347.git.geert+renesas@glider.be>
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@glider.be>
> Reviewed-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2024-10-04 13:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 14:04 [PATCH v3 resend 0/7] Add Renesas R-Car Gen4 E-FUSE support Geert Uytterhoeven
2024-10-03 14:04 ` [PATCH v3 resend 1/7] dt-bindings: fuse: Move renesas,rcar-{efuse,otp} to nvmem Geert Uytterhoeven
2024-10-05 17:52 ` Rob Herring (Arm)
2024-10-03 14:04 ` [PATCH v3 resend 2/7] nvmem: Add R-Car E-FUSE driver Geert Uytterhoeven
2024-10-04 13:23 ` Arnd Bergmann [this message]
2024-10-03 14:04 ` [PATCH v3 resend 3/7] arm64: dts: renesas: r8a779a0: Add E-FUSE node Geert Uytterhoeven
2024-10-03 14:04 ` [PATCH v3 resend 4/7] arm64: dts: renesas: r8a779f0: " Geert Uytterhoeven
2024-10-03 14:04 ` [PATCH v3 resend 5/7] arm64: dts: renesas: r8a779f4: Add UFS tuning parameters in E-FUSE Geert Uytterhoeven
2024-10-03 14:04 ` [PATCH v3 resend 6/7] arm64: dts: renesas: r8a779g0: Add OTP_MEM node Geert Uytterhoeven
2024-10-03 14:04 ` [PATCH v3 resend 7/7] arm64: dts: renesas: r8a779h0: " Geert Uytterhoeven
2024-10-07 8:59 ` (subset) [PATCH v3 resend 0/7] Add Renesas R-Car Gen4 E-FUSE support Srinivas Kandagatla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5b4afe5b-a7aa-483f-be53-cd6a8de777db@app.fastmail.com \
--to=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=yoshihiro.shimoda.uh@renesas.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®