From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Frank Li <Frank.li@nxp.com>
Cc: mbrugger@suse.com, chester62515@gmail.com,
ghennadi.procopciuc@oss.nxp.com, shawnguo@kernel.org,
s.hauer@pengutronix.de, s32@nxp.com, kernel@pengutronix.de,
festevam@gmail.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
imx@lists.linux.dev, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Ghennadi Procopciuc <ghennadi.procopciuc@nxp.com>,
Thomas Fossati <thomas.fossati@linaro.org>
Subject: Re: [PATCH 1/8] arm64: dts: s32g2: Add the STM description
Date: Wed, 30 Jul 2025 23:15:40 +0200 [thread overview]
Message-ID: <5be6d858-01e1-4c2d-bd5c-0e3385251af7@linaro.org> (raw)
In-Reply-To: <aIp+XTCSpNGee2qx@lizhi-Precision-Tower-5810>
Hi Frank,
thanks for the reviews,
On 30/07/2025 22:19, Frank Li wrote:
> On Wed, Jul 30, 2025 at 09:50:14PM +0200, Daniel Lezcano wrote:
>
> I think replace all 'description' with 'node' is easy to read.
Sure
>> The s32g2 has a STM module containing 8 timers. Each timer has a
>> dedicated interrupt and share the same clock.
>>
>> Add the timers STM0->STM6 description for the s32g2 SoC. The STM7 is
>> not added because it is slightly different and needs an extra property
>> which will be added later when supported by the driver.
>>
>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>> Cc: Ghennadi Procopciuc <ghennadi.procopciuc@nxp.com>
>> Cc: Thomas Fossati <thomas.fossati@linaro.org>
>> ---
>> arch/arm64/boot/dts/freescale/s32g2.dtsi | 63 ++++++++++++++++++++++++
>> 1 file changed, 63 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/freescale/s32g2.dtsi b/arch/arm64/boot/dts/freescale/s32g2.dtsi
>> index ea1456d361a3..3e775d030e37 100644
>> --- a/arch/arm64/boot/dts/freescale/s32g2.dtsi
>> +++ b/arch/arm64/boot/dts/freescale/s32g2.dtsi
>> @@ -503,5 +503,68 @@ gic: interrupt-controller@50800000 {
>> interrupt-controller;
>> #interrupt-cells = <3>;
>> };
>> +
>> + stm0: timer@4011c000 {
>
> keep order according to address.
>
> 4011c000 should less than 50800000.
Ah, sure. I'll fix that.
>> + compatible = "nxp,s32g2-stm";
>> + reg = <0x4011c000 0x3000>;
>> + interrupts = <GIC_SPI 24 IRQ_TYPE_LEVEL_HIGH>;
>> + clocks = <&clks 0x3b>, <&clks 0x3c>, <&clks 0x3c>;
>> + clock-names = "counter", "module", "register";
>> + status = "disabled";
>
> why not default enable.
The S32G2 and S32G3 can have different variants with 2, 4, 8 Cortex-A53
and 3 or 4 Cortex-M7. We enable the same number of CPUs present on the
system.
AFAIU:
S32G233A : 2 x Cortex-A53
S32G274A : 4 x Cortex-A53
S32G399A : 8 x Cortex-A53
S32G379A : 4 x Cortex-A53
Otherwise we would have to do the opposite, that is disable the unused
ones in the s32g274a-rdb2.dts, s32g399a-rdb3.dts and other dts which
include the s32g2.dtsi and s32g3.dtsi.
>> + };
>> +
>> + stm1: timer@40120000 {
>> + compatible = "nxp,s32g2-stm";
>> + reg = <0x40120000 0x3000>;
>> + interrupts = <GIC_SPI 25 IRQ_TYPE_LEVEL_HIGH>;
>> + clocks = <&clks 0x3b>, <&clks 0x3c>, <&clks 0x3c>;
>> + clock-names = "counter", "module", "register";
>> + status = "disabled";
>> + };
>> +
>> + stm2: timer@40124000 {
>> + compatible = "nxp,s32g2-stm";
>> + reg = <0x40124000 0x3000>;
>> + interrupts = <GIC_SPI 26 IRQ_TYPE_LEVEL_HIGH>;
>> + clocks = <&clks 0x3b>, <&clks 0x3c>, <&clks 0x3c>;
>> + clock-names = "counter", "module", "register";
>> + status = "disabled";
>> + };
>> +
>> + stm3: timer@40128000 {
>> + compatible = "nxp,s32g2-stm";
>> + reg = <0x40128000 0x3000>;
>> + interrupts = <GIC_SPI 27 IRQ_TYPE_LEVEL_HIGH>;
>> + clocks = <&clks 0x3b>, <&clks 0x3c>, <&clks 0x3c>;
>> + clock-names = "counter", "module", "register";
>> + status = "disabled";
>> + };
>> +
>> + stm4: timer@4021c000 {
>> + compatible = "nxp,s32g2-stm";
>> + reg = <0x4021c000 0x3000>;
>> + clocks = <&clks 0x3b>, <&clks 0x3c>, <&clks 0x3c>;
>> + clock-names = "counter", "module", "register";
>> + interrupts = <GIC_SPI 28 IRQ_TYPE_LEVEL_HIGH>;
>> + status = "disabled";
>> + };
>> +
>> + stm5: timer@40220000 {
>> + compatible = "nxp,s32g2-stm";
>> + reg = <0x40220000 0x3000>;
>> + clocks = <&clks 0x3b>, <&clks 0x3c>, <&clks 0x3c>;
>> + clock-names = "counter", "module", "register";
>> + interrupts = <GIC_SPI 29 IRQ_TYPE_LEVEL_HIGH>;
>> + status = "disabled";
>> + };
>> +
>> + stm6: timer@40224000 {
>> + compatible = "nxp,s32g2-stm";
>> + reg = <0x40224000 0x3000>;
>> + clocks = <&clks 0x3b>, <&clks 0x3c>, <&clks 0x3c>;
>> + clock-names = "counter", "module", "register";
>> + interrupts = <GIC_SPI 30 IRQ_TYPE_LEVEL_HIGH>;
>> + status = "disabled";
>> + };
>> };
>> };
>> --
>> 2.43.0
>>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2025-07-30 21:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 19:50 [PATCH 0/8] Add the STM and the SWT descriptions for the s32g2 and s32g3 Daniel Lezcano
2025-07-30 19:50 ` [PATCH 1/8] arm64: dts: s32g2: Add the STM description Daniel Lezcano
2025-07-30 20:19 ` Frank Li
2025-07-30 21:15 ` Daniel Lezcano [this message]
2025-07-31 23:20 ` Frank Li
2025-08-01 8:35 ` Daniel Lezcano
2025-07-30 19:50 ` [PATCH 2/8] arm64: dts: s32g274-rd2: Enable the STM timers Daniel Lezcano
2025-07-30 20:21 ` Frank Li
2025-07-30 21:15 ` Daniel Lezcano
2025-07-31 23:17 ` Frank Li
2025-08-01 8:23 ` Daniel Lezcano
2025-07-30 19:50 ` [PATCH 3/8] arm64: dts: s32g3: Add the STM descriptions Daniel Lezcano
2025-07-30 19:50 ` [PATCH 4/8] arm64: dts: s32g399a-rdb3: Enable the STM timers Daniel Lezcano
2025-07-30 19:50 ` [PATCH 5/8] arm64: dts: s32g2: Add the Software Timer Watchdog (SWT) description Daniel Lezcano
2025-07-30 20:23 ` Frank Li
2025-07-30 19:50 ` [PATCH 6/8] arm64: dts: s32g274-rd2: Enable the SWT watchdog Daniel Lezcano
2025-07-30 19:50 ` [PATCH 7/8] arm64: dts: s32g3: Add the Software Timer Watchdog (SWT) description Daniel Lezcano
2025-07-30 19:50 ` [PATCH 8/8] arm64: dts: s32g399a-rdb3: Enable the SWT watchdog Daniel Lezcano
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=5be6d858-01e1-4c2d-bd5c-0e3385251af7@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=Frank.li@nxp.com \
--cc=chester62515@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=ghennadi.procopciuc@nxp.com \
--cc=ghennadi.procopciuc@oss.nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbrugger@suse.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=s32@nxp.com \
--cc=shawnguo@kernel.org \
--cc=thomas.fossati@linaro.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;
as well as URLs for NNTP newsgroup(s).