From: "Heiko Stübner" <heiko@sntech.de>
To: Johan Jonker <jbx6244@gmail.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Sugar Zhang <sugar.zhang@rock-chips.com>,
Shreeya Patel <shreeya.patel@collabora.com>,
Kever Yang <kever.yang@rock-chips.com>,
Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH 3/3] arm64: dts: rockchip: Add rk3588 timer
Date: Tue, 18 Apr 2023 16:12:01 +0200 [thread overview]
Message-ID: <2828868.BjyWNHgNrj@diego> (raw)
In-Reply-To: <e2e59d5d-89cb-ba82-f0fc-ecddb9bdfc2a@collabora.com>
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@collabora.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@fead0000 {
> >> status = "disabled";
> >> };
> >>
> >
> >> + rktimer: timer@feae0000 {
> >
> > 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
prev parent reply other threads:[~2023-04-18 14:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 9:53 [PATCH 0/3] Enable rk3588 timer support Cristian Ciocaltea
2023-04-18 9:53 ` [PATCH 1/3] dt-bindings: timer: rockchip: Drop superfluous rk3288 compatible Cristian Ciocaltea
2023-04-18 10:26 ` Heiko Stübner
2023-04-18 10:34 ` Cristian Ciocaltea
2023-04-18 9:53 ` [PATCH 2/3] dt-bindings: timer: rockchip: Add rk3588 compatible Cristian Ciocaltea
2023-04-18 10:26 ` Heiko Stübner
2023-04-18 9:53 ` [PATCH 3/3] arm64: dts: rockchip: Add rk3588 timer Cristian Ciocaltea
2023-04-18 11:29 ` Johan Jonker
2023-04-18 11:53 ` Cristian Ciocaltea
2023-04-18 14:12 ` Heiko Stübner [this message]
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=2828868.BjyWNHgNrj@diego \
--to=heiko@sntech.de \
--cc=cristian.ciocaltea@collabora.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jbx6244@gmail.com \
--cc=kernel@collabora.com \
--cc=kever.yang@rock-chips.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=shreeya.patel@collabora.com \
--cc=sugar.zhang@rock-chips.com \
--cc=tglx@linutronix.de \
/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).