From: Nick Hu <nick.hu@sifive.com>
To: Conor Dooley <conor@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Samuel Holland <samuel.holland@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Anup Patel <anup@brainfault.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: timer: Add SiFive CLINT2
Date: Fri, 14 Mar 2025 10:15:15 +0800 [thread overview]
Message-ID: <CAKddAkCb+wAT3EcvmpoD57LFYGd8LOOUDEreFvdTnRtDjynD=g@mail.gmail.com> (raw)
In-Reply-To: <20250313-kimono-passport-496a312a849c@spud>
Hi Conor
On Fri, Mar 14, 2025 at 6:34 AM Conor Dooley <conor@kernel.org> wrote:
>
> On Thu, Mar 13, 2025 at 03:58:05PM +0800, Nick Hu wrote:
> > Hi Rob and Conor
> >
> > Thanks to all your feedback.
> >
> > On Wed, Mar 12, 2025 at 4:46 AM Conor Dooley <conor@kernel.org> wrote:
> > >
> > > On Tue, Mar 11, 2025 at 02:59:53PM -0500, Rob Herring wrote:
> > > > On Tue, Mar 11, 2025 at 01:19:03PM +0800, Nick Hu wrote:
> > > > > Add compatible string and property for the SiFive CLINT v2.
> > > > >
> > > > > Signed-off-by: Nick Hu <nick.hu@sifive.com>
> > > > > Reviewed-by: Samuel Holland <samuel.holland@sifive.com>
> > > > > ---
> > > > > .../bindings/timer/sifive,clint.yaml | 19 +++++++++++++++++++
> > > > > 1 file changed, 19 insertions(+)
> > > > >
> > > > > diff --git a/Documentation/devicetree/bindings/timer/sifive,clint.yaml b/Documentation/devicetree/bindings/timer/sifive,clint.yaml
> > > > > index 76d83aea4e2b..93d74c504b5f 100644
> > > > > --- a/Documentation/devicetree/bindings/timer/sifive,clint.yaml
> > > > > +++ b/Documentation/devicetree/bindings/timer/sifive,clint.yaml
> > > > > @@ -36,6 +36,9 @@ properties:
> > > > > - starfive,jh7110-clint # StarFive JH7110
> > > > > - starfive,jh8100-clint # StarFive JH8100
> > > > > - const: sifive,clint0 # SiFive CLINT v0 IP block
> > > >
> > > > Notice that we don't allow clint0 by itself. We shouldn't start now.
> > > >
> > > > > + - items:
> > > >
> > > > If you don't have a specific one yet, then add '- {}' for the first
> > > > entry.
> > > >
> > Do you suggest something like the following?
> > - items:
> > - {}
> > - const: sifive,clint2 # SiFive CLINT v2 IP block
> > description: SiFive CLINT v2 is the HRT that supports the Zicntr
> >
> > > > > + - const: sifive,clint2 # SiFive CLINT v2 IP block
> > > > > + description: SiFive CLINT v2 is the HRT that supports the Zicntr
> > > > > - items:
> > > > > - enum:
> > > > > - allwinner,sun20i-d1-clint
> > > > > @@ -62,6 +65,22 @@ properties:
> > > > > minItems: 1
> > > > > maxItems: 4095
> > > > >
> > > > > + sifive,fine-ctr-bits:
> > > > > + description: The width in bits of the fine counter.
> > > >
> > > > maximum: 15
> > > >
> > > > Unless you know of a different maximum in which case why aren't you
> > > > documenting that too?
> > >
> > You are right. It's my bad. The maximum width should always be 15 in
> > sifive,clint2.
> > I should update to:
> > sifive,fine-ctr-bits:
> > maximum: 15
> > description: The width in bits of the fine counter.
> >
> > if:
> > not:
> > properties:
> > compatible:
> > contains:
> > const: sifive,clint2
> > then:
> > properties:
> > sifive,fine-ctr-bits: false
>
> I think this should be inverted, to
>
> if: properties: compatible: contains: const: sifive,clint2
> then: required: - sifive,fine-counter-bits
> else: sifive,fine-counter-bits: false
>
> since the property has no default.
>
Will update it in the next version. Thanks for the advice.
> >
> > > I'm curious why this is not something that can be discerned from the
> > > compatible. It's max 15, but are there actually versions of this with a
> > > less-than-15-bit width?
> > >
> > The width may be various on different platforms so it is possible to
> > have a less-than-15-bit width.
> >
> > > >
> > > > > +
> > > > > +if:
> > > > > + properties:
> > > > > + compatible:
> > > > > + contains:
> > > > > + const: sifive,clint2
> > > > > +then:
> > > > > + properties:
> > > > > + sifive,fine-ctr-bits:
> > > > > + maximum: 15
> > > > > +else:
> > > > > + properties:
> > > > > + sifive,fine-ctr-bits: false
> > > > > +
> > > > > additionalProperties: false
> > > > >
> > > > > required:
> > > > > --
> > > > > 2.17.1
> > > > >
> >
> > Best Regards,
> > Nick
Best Regards,
Nick
next prev parent reply other threads:[~2025-03-14 2:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 5:19 [PATCH] dt-bindings: timer: Add SiFive CLINT2 Nick Hu
2025-03-11 19:59 ` Rob Herring
2025-03-11 20:46 ` Conor Dooley
2025-03-13 7:58 ` Nick Hu
2025-03-13 22:34 ` Conor Dooley
2025-03-14 2:15 ` Nick Hu [this message]
2025-03-11 20:44 ` Conor Dooley
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='CAKddAkCb+wAT3EcvmpoD57LFYGd8LOOUDEreFvdTnRtDjynD=g@mail.gmail.com' \
--to=nick.hu@sifive.com \
--cc=anup@brainfault.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tglx@linutronix.de \
/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).