From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Aswath Govindraju <a-govindraju@ti.com>,
Grygorii Strashko <grygorii.strashko@ti.com>
Subject: Re: [PATCH v2 2/2] arm64: dts: ti: k3-am625-sk: Enable on board peripherals
Date: Mon, 25 Apr 2022 21:02:01 +0200 [thread overview]
Message-ID: <c50819cb-8234-670f-c7c0-0507af2f96df@linaro.org> (raw)
In-Reply-To: <8517d504-af9c-53f5-a51b-3bcdbb86d09f@ti.com>
On 25/04/2022 11:22, Vignesh Raghavendra wrote:
>>> + /* TPS22918DBVR */
>>> + compatible = "regulator-fixed";
>>> + regulator-name = "vdd_mmc1";
>>> + regulator-min-microvolt = <3300000>;
>>> + regulator-max-microvolt = <3300000>;
>>> + regulator-boot-on;
>>> + enable-active-high;
>>> + vin-supply = <&vcc_3v3_sys>;
>>> + gpio = <&exp1 3 GPIO_ACTIVE_HIGH>;
>>> + };
>>> +
>>> + vdd_sd_dv: gpio-regulator-TLV71033 {
>>
>> The same + do not mix cases, so regulator-1 or regulator-tlv71033
>
> I have fixed this in v3. But had one question though:
>
> Per DT spec, 2.2.3 Path Names seems to indicate node-name-N when N is
> 1,2,3.. So, is it valid to have regulator-tlv71033 as node-name -> does
> not strictly seem to fit into node-name-N format ?
No, "regulator-tlv71033" does not match DT spec. Indeed better to have
some generic suffix, e.g. regulator-vbatt, but strictly speaking DT spec
asks for just "regulator-[0-9]".
However several people prefer such descriptive suffix instead of
"regulator-[0-9]" because it makes their life easier when extending DTSI
(when both DTSI and DTS provide some of such regulators). Therefore I
don't think it's that important to keep with the spec. Rob for example
does not complain here, so probably I am stricter than him.
In any case it would be good to have only suffix or only prefix, e.g.
"regulator-foo-bar" or "foo-bar-regulator", so DT schema can match
against it. Several other types of devices already require such naming.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-04-25 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 6:50 [PATCH v2 0/2] arm64: ti: k3-am62: Introduce DT nodes for basic peripherals Vignesh Raghavendra
2022-04-22 6:50 ` [PATCH v2 1/2] arm64: dts: ti: k3-am62: Add more peripheral nodes Vignesh Raghavendra
2022-04-22 6:50 ` [PATCH v2 2/2] arm64: dts: ti: k3-am625-sk: Enable on board peripherals Vignesh Raghavendra
2022-04-23 10:32 ` Krzysztof Kozlowski
2022-04-25 9:22 ` Vignesh Raghavendra
2022-04-25 19:02 ` Krzysztof Kozlowski [this message]
2022-04-26 18:17 ` Vignesh Raghavendra
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=c50819cb-8234-670f-c7c0-0507af2f96df@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=a-govindraju@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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).