From: Krzysztof Kozlowski <krzk@kernel.org>
To: Robert Marko <robert.marko@sartura.hr>
Cc: srini@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, horatiu.vultur@microchip.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
daniel.machon@microchip.com, luka.perkov@sartura.hr
Subject: Re: [PATCH 1/2] dt-bindings: nvmem: lan9662-otpc: Add LAN969x series
Date: Mon, 27 Oct 2025 14:42:56 +0100 [thread overview]
Message-ID: <176b8cd1-8c70-4fb8-80c3-69a281dc1d57@kernel.org> (raw)
In-Reply-To: <CA+HBbNGZ3FwrGCtHX=mc8LQR9DCU84jqfhjFRGVDCJWtt+gdkA@mail.gmail.com>
On 27/10/2025 13:23, Robert Marko wrote:
> On Sun, Oct 26, 2025 at 11:10 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On 24/10/2025 21:24, Robert Marko wrote:
>>> LAN969x series also has the same HW block, its just 16KB instead of 8KB
>>> like on LAN966x series.
>>>
>>> So, document compatibles for the LAN969x series.
>>>
>>> Signed-off-by: Robert Marko <robert.marko@sartura.hr>
>>> ---
>>> .../devicetree/bindings/nvmem/microchip,lan9662-otpc.yaml | 7 +++++++
>>> 1 file changed, 7 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/nvmem/microchip,lan9662-otpc.yaml b/Documentation/devicetree/bindings/nvmem/microchip,lan9662-otpc.yaml
>>> index f97c6beb4766..f8c68cf22c1c 100644
>>> --- a/Documentation/devicetree/bindings/nvmem/microchip,lan9662-otpc.yaml
>>> +++ b/Documentation/devicetree/bindings/nvmem/microchip,lan9662-otpc.yaml
>>> @@ -23,8 +23,15 @@ properties:
>>> - items:
>>> - const: microchip,lan9668-otpc
>>> - const: microchip,lan9662-otpc
>>> + - const: microchip,lan9691-otpc
>>> + - const: microchip,lan9692-otpc
>>> + - const: microchip,lan9693-otpc
>>> + - const: microchip,lan9694-otpc
>>> + - const: microchip,lan9696-otpc
>>> + - const: microchip,lan9698-otpc
>>
>> Why are you changing lan9668? Nothing on this is explained in commit
>> msg. Also, list of more than 3 items is not really useful.
>
> I am not chaning lan9668 but rather lan9698.
I clearly see lan9668 being affected here.
> I agree that a list of all possible SoC models is not ideal but I was
> just following the current
> style in the binding.
>
> As far as I know, the whole LAN969x series has identical OTP so just
> using a single
> microchip,lan9691-otpc compatible is enough.
>
>>
>>> - enum:
>>> - microchip,lan9662-otpc
>>> + - microchip,lan9691-otpc
>>
>> Why is it listed twice? First you say lan9662 is compatible with
>> lan9691, now you say it is not.
>
> They differ in OTP size, LAN966x series has 8KB while LAN969x series
> has 16KB of OTP space.
This does not explain how they can be compatible and not compatible the
same time. It's not Shroedinger's cat.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-27 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 19:24 [PATCH 1/2] dt-bindings: nvmem: lan9662-otpc: Add LAN969x series Robert Marko
2025-10-24 19:24 ` [PATCH 2/2] nvmem: lan9662-otp: add support for LAN969x Robert Marko
2025-10-26 10:10 ` [PATCH 1/2] dt-bindings: nvmem: lan9662-otpc: Add LAN969x series Krzysztof Kozlowski
2025-10-27 12:23 ` Robert Marko
2025-10-27 13:42 ` Krzysztof Kozlowski [this message]
2025-10-27 18:22 ` Rob Herring
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=176b8cd1-8c70-4fb8-80c3-69a281dc1d57@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel.machon@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=horatiu.vultur@microchip.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luka.perkov@sartura.hr \
--cc=robert.marko@sartura.hr \
--cc=robh@kernel.org \
--cc=srini@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