From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<srinivas.kandagatla@linaro.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [PATCH 1/2] dt-bindings: lan966x-otpc: document Lan966X OTPC
Date: Mon, 22 Aug 2022 08:04:56 +0200 [thread overview]
Message-ID: <20220822060456.sl343a3a3uifini7@soft-dev3-1.localhost> (raw)
In-Reply-To: <550e652e-4541-c1e6-33a7-d5555f0cb266@linaro.org>
The 08/19/2022 09:52, Krzysztof Kozlowski wrote:
Hi Krzysztof,
>
> On 18/08/2022 19:44, Horatiu Vultur wrote:
> > Document Lan966x OTP controller.
> >
> > +
> > +properties:
> > + compatible:
> > + items:
> > + - const: microchip,lan966x-otpc
>
> No wildcards in compatible (which will also affect the file name as it
> should match the compatible).
Ok, I will replace lan966x with lan966 as the SoC is defined (SOC_LAN966)
>
> > + - const: syscon
>
> Is OTP controller also system controller register region? This is a bit
> odd and looks like hack not to use nvmem subsystem.
That was a copy paste mistake. The OTP controller is not a system
controller register region.
>
> > +
> > + reg:
> > + maxItems: 1
> > +
> > +required:
> > + - compatible
> > + - reg
> > +
> > +unevaluatedProperties: false
> > +
> > +examples:
> > + - |
> > + otpc: otp@e0021000 {
> > + compatible = "microchip,lan966x-otpc", "syscon";
> > + reg = <0xe0021000 0x300>;
> > + };
> > +
> > +...
>
>
> Best regards,
> Krzysztof
--
/Horatiu
next prev parent reply other threads:[~2022-08-22 6:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 16:44 [PATCH 0/2] nvmem: lan966x-otpc: add support Horatiu Vultur
2022-08-18 16:44 ` [PATCH 1/2] dt-bindings: lan966x-otpc: document Lan966X OTPC Horatiu Vultur
2022-08-19 6:52 ` Krzysztof Kozlowski
2022-08-22 6:04 ` Horatiu Vultur [this message]
2022-08-22 18:17 ` Rob Herring
2022-08-22 20:10 ` Horatiu Vultur
2022-08-18 16:44 ` [PATCH 2/2] nvmem: lan966x-otpc: add support Horatiu Vultur
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=20220822060456.sl343a3a3uifini7@soft-dev3-1.localhost \
--to=horatiu.vultur@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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;
as well as URLs for NNTP newsgroup(s).