[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2828868.BjyWNHgNrj@diego>
Date: Tue, 18 Apr 2023 16:12:01 +0200
From: Heiko Stübner <heiko@...ech.de>
To: Johan Jonker <jbx6244@...il.com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Sebastian Reichel <sebastian.reichel@...labora.com>,
Sugar Zhang <sugar.zhang@...k-chips.com>,
Shreeya Patel <shreeya.patel@...labora.com>,
Kever Yang <kever.yang@...k-chips.com>,
Cristian Ciocaltea <cristian.ciocaltea@...labora.com>
Cc: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, kernel@...labora.com
Subject: Re: [PATCH 3/3] arm64: dts: rockchip: Add rk3588 timer
Am Dienstag, 18. April 2023, 13:53:23 CEST schrieb Cristian Ciocaltea:
>
> On 4/18/23 14:29, Johan Jonker wrote:
> >
> >
> > On 4/18/23 11:53, Cristian Ciocaltea wrote:
> >> Add DT node for Rockchip RK3588/RK3588S SoC timer.
> >>
> >> Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@...labora.com>
> >> ---
> >> arch/arm64/boot/dts/rockchip/rk3588s.dtsi | 8 ++++++++
> >> 1 file changed, 8 insertions(+)
> >>
> >> diff --git a/arch/arm64/boot/dts/rockchip/rk3588s.dtsi b/arch/arm64/boot/dts/rockchip/rk3588s.dtsi
> >> index 657c019d27fa..acd89a55374a 100644
> >> --- a/arch/arm64/boot/dts/rockchip/rk3588s.dtsi
> >> +++ b/arch/arm64/boot/dts/rockchip/rk3588s.dtsi
> >> @@ -1400,6 +1400,14 @@ i2c5: i2c@...d0000 {
> >> status = "disabled";
> >> };
> >>
> >
> >> + rktimer: timer@...e0000 {
> >
> > There are multiple timers.
> > Use a label in line with the TRM.
> > Maybe change your label to "timer0" in that trend?
>
> Sure, will use "timer0".
>
> >> + compatible = "rockchip,rk3588-timer", "rockchip,rk3288-timer";
> >> + reg = <0x0 0xfeae0000 0x0 0x20>;
> >
> >> + clocks = <&cru PCLK_BUSTIMER0>, <&cru CLK_BUSTIMER0>;
> >> + clock-names = "pclk", "timer";
> >> + interrupts = <GIC_SPI 289 IRQ_TYPE_LEVEL_HIGH 0>;
> >
> > Heiko's sort rules:
> >
> > compatible
> > reg
> > interrupts
> > [alphabetical]
> > status [if needed]
>
> Thanks for pointing this out! The sort rule was not obvious as there are
> many other nodes that don't conform.
hmm, that is probably an oversight then :-) . Though looking through
rk3588s.dtsi and rk3588.dtsi, it looks like most peripherals follow that
sorting quite nicely.
But there is also a bit of leeway ... aka there can be an argument made
that assigned-clocks might want to live near clocks or regulator-properties
could be sorted somewhat differently.
So general ideal is alphabetically for the random properties to give some
guidance on sorting.
And compatible, regs, interrupts at the top + status at the bottom makes
it way easier to establish a reading pattern, when looking for something
in the file :-) .
Heiko
Powered by blists - more mailing lists