[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b502d655-5b01-4e23-8100-237f3b38f94a@linaro.org>
Date: Mon, 20 Nov 2023 08:12:58 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Heiko Stuebner <heiko@...ech.de>, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
Arnd Bergmann <arnd@...db.de>,
Bjorn Andersson <andersson@...nel.org>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Michal Simek <michal.simek@....com>,
Neil Armstrong <neil.armstrong@...aro.org>,
Nishanth Menon <nm@...com>, Olof Johansson <olof@...om.net>
Subject: Re: [PATCH] docs: dt-bindings: add DTS Coding Style document
On 16/11/2023 21:33, Heiko Stuebner wrote:
>> regulator-state-mem {
>> regulator-off-in-suspend;
>> };
>>
>> What exactly would be here misordered?
>
> going with the vcc5v0_host regulator of the rk3588-quartzpro64 and
>
> +1. compatible
> +2. reg
> +3. ranges
> +4. All properties with values
> +5. Boolean properties
> +6. status (if applicable)
> +7. Child nodes
>
> we'd end up with
>
> vcc5v0_host: vcc5v0-host-regulator {
> /* 1. */ compatible = "regulator-fixed";
> /* 4. */ gpio = <&gpio4 RK_PB0 GPIO_ACTIVE_HIGH>;
> pinctrl-names = "default";
> pinctrl-0 = <&vcc5v0_host_en>;
> regulator-min-microvolt = <5000000>;
> regulator-max-microvolt = <5000000>;
> regulator-name = "vcc5v0_host";
> vin-supply = <&vcc5v0_usb>;
> /* 5. */ enable-active-high;
> regulator-always-on;
> regulator-boot-on;
> };
>
> which I find somewhat counter-intuitive ;-) .
Yes, good point.
Best regards,
Krzysztof
Powered by blists - more mailing lists