From: Tony Lindgren <tony@atomide.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Keerthy <j-keerthy@ti.com>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH v4 1/2] dt-bindings: timer: Update TI timer to yaml
Date: Wed, 13 Apr 2022 11:42:02 +0300 [thread overview]
Message-ID: <YlaM2rq53q+UsEjG@atomide.com> (raw)
In-Reply-To: <bd861601-1c17-1905-b267-8d8ccb444d8b@linaro.org>
* Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> [220413 08:34]:
> On 13/04/2022 10:10, Tony Lindgren wrote:
> > +allOf:
> > + - if:
> > + not:
> > + properties:
> > + compatible:
> > + contains:
> > + enum:
> > + - ti,omap3430-timer
> > + - ti,omap4430-timer
> > + - ti,omap5430-timer
> > + then:
> > + properties:
> > + reg:
> > + items:
> > + - description: IO address
>
> You can skip the items because they are the same as in properties
> before. Just keep maxItems:1.
OK great.
> > + maxItems: 1
> > + clocks:
> > + items:
> > + - description: Functional clock
>
> The same.
>
> > + maxItems: 1
> > + clock-names:
> > + items:
> > + - const: fck
>
> The same.
>
> > + maxItems: 1
>
> Rest is good.
OK
Thanks,
Tony
next prev parent reply other threads:[~2022-04-13 8:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 8:10 [PATCH v4 0/2] Convert TI dmtimer binding to yaml Tony Lindgren
2022-04-13 8:10 ` [PATCH v4 1/2] dt-bindings: timer: Update TI timer " Tony Lindgren
2022-04-13 8:36 ` Krzysztof Kozlowski
2022-04-13 8:42 ` Tony Lindgren [this message]
2022-04-13 8:10 ` [PATCH v4 2/2] dt-bindings: timer: Add compatible for am6 for TI timer-dm Tony Lindgren
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=YlaM2rq53q+UsEjG@atomide.com \
--to=tony@atomide.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=j-keerthy@ti.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--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).