linux-kernel - Re: [PATCH v4 2/2] arm64: dts: rockchip: Add Radxa ROCK 4D device tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <3568510.6YUMPnJmAY@diego>
Date: Mon, 17 Feb 2025 22:30:40 +0100
From: Heiko Stübner <heiko@...ech.de>
To: Jonas Karlman <jonas@...boo.se>,
 Detlev Casanova <detlev.casanova@...labora.com>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Chris Morgan <macromorgan@...mail.com>,
 Kever Yang <kever.yang@...k-chips.com>, Dragan Simic <dsimic@...jaro.org>,
 Tim Lunn <tim@...thertop.org>, FUKAUMI Naoki <naoki@...xa.com>,
 Michael Riesch <michael.riesch@...fvision.net>,
 Stephen Chen <stephen@...xa.com>, Elon Zhang <zhangzj@...k-chips.com>,
 Alexey Charkov <alchark@...il.com>, devicetree@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, linux-rockchip@...ts.infradead.org,
 kernel@...labora.com, linux-kernel@...r.kernel.org
Subject:
 Re: [PATCH v4 2/2] arm64: dts: rockchip: Add Radxa ROCK 4D device tree

Am Montag, 17. Februar 2025, 22:07:06 MEZ schrieb Detlev Casanova:
> On Monday, 17 February 2025 12:08:47 EST Jonas Karlman wrote:
> > On 2025-02-17 17:34, Detlev Casanova wrote:
> > > +	pmic@23 {
> > > +		compatible = "rockchip,rk806";
> > > +		reg = <0x23>;
> > > +
> > > +		gpio-controller;
> > > +
> > > +		interrupt-parent = <&gpio0>;
> > > +		interrupts = <6 IRQ_TYPE_LEVEL_LOW>;
> > > +
> > > +		pinctrl-names = "default";
> > > +		pinctrl-0 = <&pmic_pins
> > > +			     &rk806_dvs1_null
> > > +			     &rk806_dvs2_null
> > > +			     &rk806_dvs3_null>;
> > > +
> > > +		system-power-controller;
> > > +
> > > +		vcc1-supply = <&vcc_5v0_sys>;
> > > +		vcc2-supply = <&vcc_5v0_sys>;
> > > +		vcc3-supply = <&vcc_5v0_sys>;
> > > +		vcc4-supply = <&vcc_5v0_sys>;
> > > +		vcc5-supply = <&vcc_5v0_sys>;
> > > +		vcc6-supply = <&vcc_5v0_sys>;
> > > +		vcc7-supply = <&vcc_5v0_sys>;
> > > +		vcc8-supply = <&vcc_5v0_sys>;
> > > +		vcc9-supply = <&vcc_5v0_sys>;
> > > +		vcc10-supply = <&vcc_5v0_sys>;
> > > +		vcc11-supply = <&vcc_2v0_pldo_s3>;
> > > +		vcc12-supply = <&vcc_5v0_sys>;
> > > +		vcc13-supply = <&vcc_1v1_nldo_s3>;
> > > +		vcc14-supply = <&vcc_1v1_nldo_s3>;
> > > +		vcca-supply = <&vcc_5v0_sys>;
> > > +
> > > +		#gpio-cells = <2>;
> > 
> > This should probably be sorted next to gpio-controller.
> 
> It's not unusual to put # props at the end. but I can move it up if it is 
> preferred.

That is actually a multi-colored bikeshed ;-)

When sorting alphabetically, do you
- just ignore the "#", this would move #gpio-cells to gpio*  but also
  split up #address-cells and #size-cells
- count "#" as special character and move them to the bottom, but this
  would split #gpio-cells from gpio-controller

--- TL;DR
So far I've not managed to come with a 1-size-fits-all opinion, but for
#gpio* and #clock* properties, readability gets better when they are
together with other gpio* / clock* properties .
----

Also I think you could do away with all the empty lines between properties
above (pinctrl <-> system-power-controller, etc), but of course keep the
empty between the subnodes below :-)


Heiko