From: <Claudiu.Beznea@microchip.com>
To: <Horatiu.Vultur@microchip.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<Nicolas.Ferre@microchip.com>, <UNGLinuxDriver@microchip.com>
Subject: Re: [PATCH] ARM: dts: lan966x: Add otp support
Date: Wed, 26 Oct 2022 07:42:29 +0000 [thread overview]
Message-ID: <c108d42d-dae8-0852-d89b-160b70b196dc@microchip.com> (raw)
In-Reply-To: <20220916194946.2869510-1-horatiu.vultur@microchip.com>
Hi, Horatiu,
I will postpone this until [1] or [2] is applied.
Thank you,
Claudiu Beznea
[1]
https://lore.kernel.org/all/20220928195112.630351-1-horatiu.vultur@microchip.com/
[2]
https://lore.kernel.org/all/20221025072217.3715634-1-claudiu.beznea@microchip.com/
On 16.09.2022 22:49, Horatiu Vultur wrote:
> Add OTP (one time programmable) support.
> The both lan966x SocS (lan9662 and lan9668) have the same OTP IP.
>
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
> arch/arm/boot/dts/lan966x.dtsi | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm/boot/dts/lan966x.dtsi b/arch/arm/boot/dts/lan966x.dtsi
> index 23665a0429906..784caba369485 100644
> --- a/arch/arm/boot/dts/lan966x.dtsi
> +++ b/arch/arm/boot/dts/lan966x.dtsi
> @@ -163,6 +163,11 @@ port7: port@7 {
> };
> };
>
> + otp: otp@e0021000 {
> + compatible = "microchip,lan9668-otpc", "microchip,lan9662-otpc";
> + reg = <0xe0021000 0x300>;
> + };
> +
> flx0: flexcom@e0040000 {
> compatible = "atmel,sama5d2-flexcom";
> reg = <0xe0040000 0x100>;
next prev parent reply other threads:[~2022-10-26 7:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 19:49 [PATCH] ARM: dts: lan966x: Add otp support Horatiu Vultur
2022-10-26 7:42 ` Claudiu.Beznea [this message]
2022-11-23 10:45 ` Horatiu Vultur - M31836
2022-11-24 15:24 ` Claudiu.Beznea
2022-11-25 9:23 ` Claudiu.Beznea
2022-11-25 10:01 ` Horatiu Vultur - M31836
2022-11-25 11:10 ` Claudiu.Beznea
2022-11-25 11:35 ` Claudiu.Beznea
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=c108d42d-dae8-0852-d89b-160b70b196dc@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Horatiu.Vultur@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.