From: Robin Murphy <robin.murphy@arm.com>
To: Alex Bee <knaerzche@gmail.com>, Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Johan Jonker <jbx6244@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/5] ARM: dts: rockchip: Disable non-required timers for RK3128
Date: Wed, 30 Aug 2023 19:17:15 +0100 [thread overview]
Message-ID: <101f3b88-7151-af5c-3bd4-feb13763228b@arm.com> (raw)
In-Reply-To: <20230829203721.281455-14-knaerzche@gmail.com>
On 2023-08-29 21:37, Alex Bee wrote:
> The Rockchip timer linux driver can handle a maximum of 2 timers and will
> get confused if more of them exist.
Wouldn't it be better to fix that? It looks trivial to do, and frankly
it's a behaviour that doesn't make sense anyway. Of course a system can
have more hardware available than Linux wants to use; that's not an
error, it's just Linux's choice to not use it! See commit a98399cbc1e0
("clocksource/drivers/sp804: Avoid error on multiple instances") for
example.
DTs shouldn't be treated like Linux board files, so curating them around
Linux-specific driver behaviour is inappropriate; FreeBSD or U-Boot or
whatever are perfectly entitled to make use of 5 timers at once if they can.
Thanks,
Robin.
> RK3128 only needs timer0, timer1 and timer5. The latter is the source
> for the arm-timer and it's clock is prevented from being disabled in the
> clock driver so it can get disabled in the device tree, too.
>
> Fixes: a0201bff6259 ("ARM: dts: rockchip: add rk3128 soc dtsi")
> Signed-off-by: Alex Bee <knaerzche@gmail.com>
> ---
> arch/arm/boot/dts/rockchip/rk3128.dtsi | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm/boot/dts/rockchip/rk3128.dtsi b/arch/arm/boot/dts/rockchip/rk3128.dtsi
> index 88a4b0d6d928..f3f0788195d2 100644
> --- a/arch/arm/boot/dts/rockchip/rk3128.dtsi
> +++ b/arch/arm/boot/dts/rockchip/rk3128.dtsi
> @@ -252,6 +252,7 @@ timer2: timer@20044040 {
> interrupts = <GIC_SPI 59 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&cru PCLK_TIMER>, <&cru SCLK_TIMER2>;
> clock-names = "pclk", "timer";
> + status = "disabled";
> };
>
> timer3: timer@20044060 {
> @@ -260,6 +261,7 @@ timer3: timer@20044060 {
> interrupts = <GIC_SPI 60 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&cru PCLK_TIMER>, <&cru SCLK_TIMER3>;
> clock-names = "pclk", "timer";
> + status = "disabled";
> };
>
> timer4: timer@20044080 {
> @@ -268,6 +270,7 @@ timer4: timer@20044080 {
> interrupts = <GIC_SPI 61 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&cru PCLK_TIMER>, <&cru SCLK_TIMER4>;
> clock-names = "pclk", "timer";
> + status = "disabled";
> };
>
> timer5: timer@200440a0 {
> @@ -276,6 +279,7 @@ timer5: timer@200440a0 {
> interrupts = <GIC_SPI 62 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&cru PCLK_TIMER>, <&cru SCLK_TIMER5>;
> clock-names = "pclk", "timer";
> + status = "disabled";
> };
>
> watchdog: watchdog@2004c000 {
next prev parent reply other threads:[~2023-08-30 18:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 20:37 [PATCH v2 0/6] Device tree fixes " Alex Bee
2023-08-29 20:37 ` [PATCH v2 1/5] ARM: dts: rockchip: Fix i2c0 register address " Alex Bee
2023-08-29 20:37 ` [PATCH v2 2/5] ARM: dts: rockchip: Add missing arm timer interrupt " Alex Bee
2023-08-29 20:37 ` [PATCH v2 3/5] ARM: dts: rockchip: Add missing quirk for RK3128's dma engine Alex Bee
2023-08-29 20:37 ` [PATCH v2 4/5] ARM: dts: rockchip: Fix timer clocks for RK3128 Alex Bee
2023-08-29 20:37 ` [PATCH v2 5/5] ARM: dts: rockchip: Disable non-required timers " Alex Bee
2023-08-30 18:17 ` Robin Murphy [this message]
2023-10-05 10:06 ` Alex Bee
2023-10-04 21:32 ` (subset) [PATCH v2 0/6] Device tree fixes " Heiko Stuebner
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=101f3b88-7151-af5c-3bd4-feb13763228b@arm.com \
--to=robin.murphy@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=knaerzche@gmail.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 \
/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
all inboxes | Powered by JetHome®