From: Linus Walleij <linus.walleij@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: 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>,
devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-gpio@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/8] pinctrl: renesas: Add R-Car Gen3 fuse support
Date: Fri, 7 Jun 2024 22:45:27 +0200 [thread overview]
Message-ID: <CACRpkdZETWojdSDTT+ownbPtsr4LipT+eDxRA8YjQdGSEmEGdQ@mail.gmail.com> (raw)
In-Reply-To: <a30fa2c5e0d07752692c5a69f5a5fc57ae719c1b.1716974502.git.geert+renesas@glider.be>
On Wed, May 29, 2024 at 11:29 AM Geert Uytterhoeven
<geert+renesas@glider.be> wrote:
> On R-Car Gen3 SoCs, the fuse registers are tightly integrated into the
> Pin Function Controller. Add support for them by providing the
> rcar-fuse driver with all needed info through a platform device and
> platform data.
>
> Note that the number of fuse registers on R-Car V3H and V3H2 differs,
> while their PFC blocks use the same compatible value, hence this is
> handled by checking the top-level compatible value.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Reviewed-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
> ---
> v2:
> - Add Reviewed-by.
Acked-by: Linus Walleij <linus.walleij@linaro.org>
In case this needs to go through some other tree than mine.
Yours,
Linus Walleij
next prev parent reply other threads:[~2024-06-07 20:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 9:29 [PATCH v2 0/8] Add R-Car fuse support Geert Uytterhoeven
2024-05-29 9:29 ` [PATCH v2 1/8] dt-bindings: fuse: Document R-Car E-FUSE / PFC Geert Uytterhoeven
2024-06-03 15:58 ` Rob Herring (Arm)
2024-05-29 9:29 ` [PATCH v2 2/8] dt-bindings: fuse: Document R-Car E-FUSE / OTP_MEM Geert Uytterhoeven
2024-06-03 15:59 ` Rob Herring (Arm)
2024-05-29 9:29 ` [PATCH v2 3/8] soc: renesas: Add R-Car fuse driver Geert Uytterhoeven
2024-05-29 9:29 ` [PATCH v2 4/8] pinctrl: renesas: Add R-Car Gen3 fuse support Geert Uytterhoeven
2024-06-07 20:45 ` Linus Walleij [this message]
2024-05-29 9:29 ` [PATCH v2 5/8] arm64: dts: renesas: r8a779a0: Add E-FUSE node Geert Uytterhoeven
2024-05-29 9:29 ` [PATCH v2 6/8] arm64: dts: renesas: r8a779f0: " Geert Uytterhoeven
2024-05-29 9:29 ` [PATCH v2 7/8] arm64: dts: renesas: r8a779g0: Add OTP_MEM node Geert Uytterhoeven
2024-05-29 9:29 ` [PATCH v2 8/8] arm64: dts: renesas: r8a779h0: " Geert Uytterhoeven
2024-06-24 13:55 ` [PATCH v2 0/8] Add R-Car fuse support Geert Uytterhoeven
2024-06-29 11:35 ` Geert Uytterhoeven
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=CACRpkdZETWojdSDTT+ownbPtsr4LipT+eDxRA8YjQdGSEmEGdQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.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=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;
as well as URLs for NNTP newsgroup(s).