From: Nishanth Menon <nm@ti.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Alessandro Zummo <a.zummo@towertech.it>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-rtc@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH 1/2] dt-bindings: rtc: Add TI K3 RTC devicetree bindings documentation
Date: Tue, 12 Apr 2022 17:17:43 -0500 [thread overview]
Message-ID: <20220412221743.vbectb4bcghau2b7@confider> (raw)
In-Reply-To: <dee496ce-5e74-4a53-c783-6420b2391387@linaro.org>
On 14:06-20220412, Krzysztof Kozlowski wrote:
> > +properties:
> > + compatible:
> > + items:
>
> No need for items. Just enum under the compatible.
Will fix in next rev. Thanks for catching.
>
> > + - enum:
> > + - ti,am62-rtc
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + interrupts:
> > + maxItems: 1
> > +
> > + clocks:
> > + items:
> > + - description: VBUS Interface clock
> > + - description: 32k Clock source (external or internal).
> > +
> > + clock-names:
> > + items:
> > + - const: "vbus"
> > + - const: "osc32k"
>
> No quotes.
Uggh.. my bad. yup
>
> > +
> > + power-domains:
> > + maxItems: 1
> > +
> > + assigned-clocks:
> > + description: |
> > + override default osc32k parent clock reference to the osc32k clock entry
> > + maxItems: 1
> > +
> > + assigned-clock-parents:
> > + description: |
> > + override default osc32k parent clock phandle of the new parent clock of osc32k
> > + maxItems: 1
>
> Usually assigned-clockXXX are not needed in the bindings. Is here
> something different? They are put only to indicate something special.
I wonder if I should rather use unevaluatedproperties instead? If I use
additionalProperties: False, then the second example below fails.
Thoughts?
>
> > +
> > + wakeup-source: true
> > +
> > +required:
> > + - compatible
> > + - reg
> > + - interrupts
> > + - clocks
> > + - clock-names
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + #include <dt-bindings/interrupt-controller/arm-gic.h>
> > + rtc@2b1f0000 {
> > + compatible = "ti,am62-rtc";
> > + reg = <0x2b1f0000 0x100>;
> > + interrupts = <GIC_SPI 100 IRQ_TYPE_LEVEL_HIGH>;
> > + power-domains = <&bar 0>;
> > + clocks = <&foo 0>, <&foo 1>;
> > + clock-names = "vbus", "osc32k";
> > + wakeup-source;
> > + };
> > +
> > + - |
> > + #include <dt-bindings/interrupt-controller/arm-gic.h>
> > + rtc@2b1f0000 {
> > + compatible = "ti,am62-rtc";
> > + reg = <0x2b1f0000 0x100>;
> > + interrupts = <GIC_SPI 100 IRQ_TYPE_LEVEL_HIGH>;
> > + power-domains = <&bar 0>;
> > + clocks = <&foo 0>, <&foo 1>;
> > + clock-names = "vbus", "osc32k";
> > + wakeup-source;
> > + assigned-clocks = <&foo 1>;
> > + assigned-clock-parents = <&foo 2>;
> > +
>
> Unneeded blank line.
Ack.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-12 22:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 7:31 [PATCH 0/2] rtc: Introduce rtc-ti-k3 Nishanth Menon
2022-04-12 7:31 ` [PATCH 1/2] dt-bindings: rtc: Add TI K3 RTC devicetree bindings documentation Nishanth Menon
2022-04-12 12:06 ` Krzysztof Kozlowski
2022-04-12 22:17 ` Nishanth Menon [this message]
2022-04-13 6:42 ` Krzysztof Kozlowski
2022-04-13 15:45 ` Nishanth Menon
2022-04-14 15:53 ` Rob Herring
2022-04-12 7:31 ` [PATCH 2/2] rtc: Introduce ti-k3-rtc Nishanth Menon
2022-04-14 0:45 ` Andrew Davis
2022-04-15 8:03 ` Vignesh Raghavendra
2022-04-15 8:14 ` Alexandre Belloni
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=20220412221743.vbectb4bcghau2b7@confider \
--to=nm@ti.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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).