From: sashiko-bot@kernel.org
To: "Khristine Andreea Barbulescu" <khristineandreea.barbulescu@oss.nxp.com>
Cc: imx@lists.linux.dev, krzk+dt@kernel.org, conor+dt@kernel.org,
robh@kernel.org, devicetree@vger.kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: s32g: add PIT support for s32g2 and s32g3
Date: Thu, 14 May 2026 16:31:24 +0000 [thread overview]
Message-ID: <20260514163125.69609C2BCB3@smtp.kernel.org> (raw)
In-Reply-To: <20260514070605.996462-2-khristineandreea.barbulescu@oss.nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The Device Tree nodes for the PIT timers are named using the specific IP block name (`pit@...`) instead of the standard generic name (`timer@...`).
--
commit 427ff80913e8247c6a4011dd8722ce9a6b67e322
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 Programmable Interrupt Timer
(PIT0 and PIT1) blocks on S32G2 and S32G3 SoCs.
> diff --git a/arch/arm64/boot/dts/freescale/s32g2.dtsi b/arch/arm64/boot/dts/freescale/s32g2.dtsi
> --- 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 according to the Devicetree Specification (Section
2.2.2 "Generic Names Recommendation"), node names should reflect the
generic function of the device rather than the specific IP block.
Could this node, as well as the pit1 node and the equivalent nodes in
s32g3.dtsi, be named timer@... instead of pit@... to follow standard
Device Tree conventions?
> + compatible = "nxp,s32g2-pit";
> + reg = <0x40188000 0x3000>;
> + interrupts = <GIC_SPI 53 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&clks 61>;
> + clock-names = "pit";
> + status = "disabled";
> + };
> +
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260514070605.996462-1-khristineandreea.barbulescu@oss.nxp.com?part=1
next prev parent reply other threads:[~2026-05-14 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 7:06 [PATCH 0/2] add PIT DTS support for S32G2/S32G3 SoCs Khristine Andreea Barbulescu
2026-05-14 7:06 ` [PATCH 1/2] arm64: dts: s32g: add PIT support for s32g2 and s32g3 Khristine Andreea Barbulescu
2026-05-14 16:31 ` sashiko-bot [this message]
2026-05-14 7:06 ` [PATCH 2/2] dt-bindings: timer: pit: add PIT node example for s32g2/3 platforms Khristine Andreea Barbulescu
2026-05-14 16:53 ` sashiko-bot
2026-05-14 18:14 ` Conor Dooley
2026-05-14 18:38 ` Frank Li
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=20260514163125.69609C2BCB3@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=krzk+dt@kernel.org \
--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