[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <576c42c4-1256-304d-3513-7bf02cddb220@kernel.org>
Date: Thu, 3 Nov 2022 11:27:09 -0400
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Billy Tsai <billy_tsai@...eedtech.com>,
"jdelvare@...e.com" <jdelvare@...e.com>,
"linux@...ck-us.net" <linux@...ck-us.net>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"joel@....id.au" <joel@....id.au>,
"andrew@...id.au" <andrew@...id.au>,
"lee.jones@...aro.org" <lee.jones@...aro.org>,
"thierry.reding@...il.com" <thierry.reding@...il.com>,
"u.kleine-koenig@...gutronix.de" <u.kleine-koenig@...gutronix.de>,
"p.zabel@...gutronix.de" <p.zabel@...gutronix.de>,
"linux-hwmon@...r.kernel.org" <linux-hwmon@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-aspeed@...ts.ozlabs.org" <linux-aspeed@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-pwm@...r.kernel.org" <linux-pwm@...r.kernel.org>,
BMC-SW <BMC-SW@...eedtech.com>,
"garnermic@...a.com" <garnermic@...a.com>
Subject: Re: [PATCH 1/3] dt-bindings: Add bindings for aspeed pwm-tach.
On 03/11/2022 06:36, Billy Tsai wrote:
>
> On 2022/11/3, 5:20 AM, "Krzysztof Kozlowski" <krzk@...nel.org> wrote:
>
> On 31/10/2022 06:38, Billy Tsai wrote:
> > > +patternProperties:
> > > + "^pwm(@[0-9a-f]+)?$":
> > > + $ref: ../pwm/aspeed,ast2600-pwm.yaml
>
> > Full path, so: /schemas/pwm/aspeed,ast2600-pwm.yaml
>
> > Why unit addresses are optional?
>
> > > +
> > > + "^tach(@[0-9a-f]+)?$":
> > > + $ref: ../hwmon/aspeed,ast2600-tach.yaml
>
> > Ditto
>
> > Why unit addresses are optional?
>
> The pwm_tach is not the bus. I will use
> pwm:
> type: object
> $ref: "/schemas/pwm/aspeed,ast2600-pwm.yaml"
>
> tach:
> type: object
> $ref: "/schemas/hwmon/aspeed,ast2600-tach.yaml"
> to replace it.
>
> > > +
> > > +additionalProperties: false
> > > +
> > > +examples:
> > > + - |
> > > + #include <dt-bindings/clock/ast2600-clock.h>
> > > + pwm_tach: pwm_tach@...10000 {
>
> > Node names should be generic.
> > https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
>
> This is the mfd with pwm and tach, so they are combined as the node name.
>
> > No underscores in node names.
>
> https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#table-1
> I see that the underscore is the valid characters for node names.
> Did I miss any information?
W=2 warnings.
Best regards,
Krzysztof
Powered by blists - more mailing lists