[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250730-striped-free-lionfish-826b70@kuoka>
Date: Wed, 30 Jul 2025 08:58:19 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Jonas Karlman <jonas@...boo.se>
Cc: Erik Beck <xunil@...omasoft.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
Heiko Stuebner <heiko@...ech.de>, devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 2/2] arm64: dts: rockchip: add LinkStar-H68k-1432v1
On Tue, Jul 29, 2025 at 10:30:35PM +0200, Jonas Karlman wrote:
> > +
> > + /* Middle inset/recessed button,
> > + * marked by clockwise arrow/circle
> > + */
> > +
> > + button-reset {
> > + label = "button:system:reset";
> > + gpios = <&gpio0 RK_PA0 GPIO_ACTIVE_LOW>;
> > + linux,code = <KEY_RESTART>;
> > + debounce-interval = <50>;
>
> Please order props alphabetically.
Why the least important property - debounce-interval - would be first?
This is not a readable style.
>
> > + };
> > + };
> > +
> > + gpio-leds {
> > + compatible = "gpio-leds";
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&led_white_pin>, <&led_green_pin>,
> > + <&led_amber_pin>, <&led_blue_pin>;
>
> And here pinctrl-names comes before the pins, this is my personal
> preferred ordering for pinctrl-* props, I will settle for being
> consistent.
This is not the recommended order. Names always are supposed to follow
the property with actual values.
Best regards,
Krzysztof
Powered by blists - more mailing lists