Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Khristine Andreea Barbulescu" <khristineandreea.barbulescu@oss.nxp.com>
Cc: Frank.Li@kernel.org, devicetree@vger.kernel.org,
	conor+dt@kernel.org, robh@kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH v2 1/1] arm64: dts: s32g: add PIT support for s32g2 and s32g3
Date: Mon, 18 May 2026 06:46:33 +0000	[thread overview]
Message-ID: <20260518064634.86F5FC2BCB7@smtp.kernel.org> (raw)
In-Reply-To: <20260518063547.2890353-2-khristineandreea.barbulescu@oss.nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The newly added device tree nodes `pit0` and `pit1` are named `pit@...` instead of the generic name `timer@...`.
--

commit 296fdf97d8d5f42b2426eda4d41b0132d74ccbbd
Author: Khristine Andreea Barbulescu <khristineandreea.barbulescu@oss.nxp.com>

arm64: dts: s32g: add PIT support for s32g2 and s32g3

This commit adds device tree nodes for the Periodic Interrupt Timer (PIT0 and
PIT1) blocks on the NXP S32G2 and S32G3 SoCs.

> diff --git a/arch/arm64/boot/dts/freescale/s32g2.dtsi b/arch/arm64/boot/dts/freescale/s32g2.dtsi
> index 51d00dac12deb..57ff97e445075 100644
> --- a/arch/arm64/boot/dts/freescale/s32g2.dtsi
> +++ b/arch/arm64/boot/dts/freescale/s32g2.dtsi
[ ... ]
> @@ -417,6 +417,15 @@ edma0: dma-controller@40144000 {
>  			clock-names = "dmamux0", "dmamux1";
>  		};
>  
> +		pit0: pit@40188000 {

This isn't a bug, but should these nodes use the generic name timer instead of
pit? The Devicetree Specification recommends using generic names that reflect
the primary function of the device rather than specific IP block acronyms.

> +			compatible = "nxp,s32g2-pit";
> +			reg = <0x40188000 0x3000>;
> +			interrupts = <GIC_SPI 53 IRQ_TYPE_LEVEL_HIGH>;
> +			clocks = <&clks 61>;
> +			clock-names = "pit";
> +			status = "disabled";
> +		};
> +
[ ... ]
> @@ -622,6 +631,15 @@ edma1: dma-controller@40244000 {
>  			clock-names = "dmamux0", "dmamux1";
>  		};
>  
> +		pit1: pit@40288000 {

Could this node also be named timer@40288000 for the same reason?

> +			compatible = "nxp,s32g2-pit";
> +			reg = <0x40288000 0x3000>;
> +			interrupts = <GIC_SPI 54 IRQ_TYPE_LEVEL_HIGH>;
> +			clocks = <&clks 61>;
> +			clock-names = "pit";
> +			status = "disabled";
> +		};
[ ... ]
> diff --git a/arch/arm64/boot/dts/freescale/s32g3.dtsi b/arch/arm64/boot/dts/freescale/s32g3.dtsi
> index e314f3c7d61d0..efe5398e12403 100644
> --- a/arch/arm64/boot/dts/freescale/s32g3.dtsi
> +++ b/arch/arm64/boot/dts/freescale/s32g3.dtsi
[ ... ]
> @@ -475,6 +475,15 @@ edma0: dma-controller@40144000 {
>  			clock-names = "dmamux0", "dmamux1";
>  		};
>  
> +		pit0: pit@40188000 {

And similarly, could this node be updated to timer@40188000?

> +			compatible = "nxp,s32g3-pit", "nxp,s32g2-pit";
> +			reg = <0x40188000 0x3000>;
> +			interrupts = <GIC_SPI 53 IRQ_TYPE_LEVEL_HIGH>;
> +			clocks = <&clks 61>;
> +			clock-names = "pit";
> +			status = "disabled";
> +		};
> +
[ ... ]
> @@ -693,6 +702,15 @@ edma1: dma-controller@40244000 {
>  			clock-names = "dmamux0", "dmamux1";
>  		};
>  
> +		pit1: pit@40288000 {

And timer@40288000 here?

> +			compatible = "nxp,s32g3-pit", "nxp,s32g2-pit";
> +			reg = <0x40288000 0x3000>;
> +			interrupts = <GIC_SPI 54 IRQ_TYPE_LEVEL_HIGH>;
> +			clocks = <&clks 61>;
> +			clock-names = "pit";
> +			status = "disabled";
> +		};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260518063547.2890353-2-khristineandreea.barbulescu@oss.nxp.com?part=1

      reply	other threads:[~2026-05-18  6:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18  6:35 [PATCH v2 0/1] add PIT DTS support for S32G2/S32G3 SoCs Khristine Andreea Barbulescu
2026-05-18  6:35 ` [PATCH v2 1/1] arm64: dts: s32g: add PIT support for s32g2 and s32g3 Khristine Andreea Barbulescu
2026-05-18  6:46   ` sashiko-bot [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=20260518064634.86F5FC2BCB7@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=khristineandreea.barbulescu@oss.nxp.com \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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