mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Claudiu.Beznea@microchip.com>
To: <Horatiu.Vultur@microchip.com>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<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: Fri, 25 Nov 2022 11:10:22 +0000	[thread overview]
Message-ID: <9302133d-e217-e44e-5372-7bd05865f36a@microchip.com> (raw)
In-Reply-To: <20221125100144.332tizam7tonqqtz@soft-dev3-1>

On 25.11.2022 12:01, Horatiu Vultur - M31836 wrote:
> The 11/25/2022 09:23, Claudiu Beznea - M18063 wrote:
>> Hi, Horatiu,
> 
> Hi Claudiu,
> 
>>
>> 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.
>>
>> If OTP IP is the same for both lan966x is there a reason you've added
>> compatibles for each SoC variants?
> 
> When I was adding the device tree binding, Krzystof mention not to have
> any wilcards in compatible string [0].

I was thinking at having only one of microchip,lan9668-otpc or
microchip,lan9662-otpc whoever was first.

> 
> [0] https://lore.kernel.org/lkml/550e652e-4541-c1e6-33a7-d5555f0cb266@linaro.org/
> 
>>
>> Thank you,
>> Claudiu Beznea
>>
>>>
>>> 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>;
>>
> 


  reply	other threads:[~2022-11-25 11:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 19:49 Horatiu Vultur
2022-10-26  7:42 ` Claudiu.Beznea
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 [this message]
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=9302133d-e217-e44e-5372-7bd05865f36a@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 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®