From: Rob Herring <robh@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Krzysztof Kozlowski" <krzk@kernel.org>,
"Pavel Machek" <pavel@ucw.cz>, "Lee Jones" <lee@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"William Zhang" <william.zhang@broadcom.com>,
"Anand Gore" <anand.gore@broadcom.com>,
"Kursad Oney" <kursad.oney@broadcom.com>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/4] dt-bindings: leds: bcm63138: Add shift register bits
Date: Wed, 2 Oct 2024 14:30:30 -0500 [thread overview]
Message-ID: <20241002193030.GA1195702-robh@kernel.org> (raw)
In-Reply-To: <CACRpkdYqR3N0EaS64gqSfRfezsrSueSKHPbMc4A0g3hHg3y6dw@mail.gmail.com>
On Tue, Oct 01, 2024 at 01:18:29PM +0200, Linus Walleij wrote:
> On Sat, Sep 28, 2024 at 10:05 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
> > On Sat, Sep 28, 2024 at 12:29:47AM +0200, Linus Walleij wrote:
> > > + brcm,serial-shift-bits:
> >
> > bits is an uint32-array, so you need to limit number of items, e.g.
> > items:
> > - minimum: 1
> > maximum: 32
>
> OK this is what I do on the next lines:
>
> > > + minimum: 1
> > > + maximum: 32
>
> Am I doing something wrong here? I see you have a dash
> - minimum in your comment but when I grep through the
> existing bindings for stuff ending with -bits it seems they
> do what I do.
All the unit suffixes started as single values, but then we found some
cases with more than 1 (and even a matrix for opp-hz) and had to extend
them.
I think what you have here is fine. We can imply it's 1 entry given the
scalar constraints.
>
> > default: [0]? or something else?
>
> Since we need to stay compatible with older device trees
> the default is whatever is in the hardware after boot :/
>
> I guess I could write something about it in the description.
>
> Yours,
> Linus Walleij
next prev parent reply other threads:[~2024-10-02 19:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 22:29 [PATCH v2 0/4] leds: bcm63138: Add some new bindings and code Linus Walleij
2024-09-27 22:29 ` [PATCH v2 1/4] dt-bindings: leds: bcm63138: Add shift register bits Linus Walleij
2024-09-28 8:05 ` Krzysztof Kozlowski
2024-10-01 11:18 ` Linus Walleij
2024-10-02 19:30 ` Rob Herring [this message]
2024-09-27 22:29 ` [PATCH v2 2/4] leds: bcm63138: Use scopes and guards Linus Walleij
2024-09-27 22:29 ` [PATCH v2 3/4] leds: bcm63138: Handle shift register config Linus Walleij
2024-09-27 22:29 ` [PATCH v2 4/4] leds: bcm63138: Add some register defines Linus Walleij
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=20241002193030.GA1195702-robh@kernel.org \
--to=robh@kernel.org \
--cc=anand.gore@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=kursad.oney@broadcom.com \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafal@milecki.pl \
--cc=william.zhang@broadcom.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).