Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org,
	wsa+renesas@sang-engineering.com
Subject: Re: [PATCH net-next v5 3/3] arm64: dts: renesas: r8a779g0: Add gPTP node
Date: Wed, 22 Jul 2026 13:31:09 +0000	[thread overview]
Message-ID: <20260722133109.E658B1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260721132936.1331318-4-niklas.soderlund+renesas@ragnatech.se>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] Device Tree Resource Overlap causes probe failure due to exclusive memory region request
- [High] Hardware Reset State Corruption of shared system gPTP module
--

--- Patch [3]: [PATCH net-next v5 3/3] arm64: dts: renesas: r8a779g0: Add gPTP node ---
commit 4292ed266aa9785a4578e66f92c58f83f6f4bbfd
Author: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>

arm64: dts: renesas: r8a779g0: Add gPTP node

The gPTP module is shared between the RAVB and RTSN Ethernet devices on
the SoC.

> diff --git a/arch/arm64/boot/dts/renesas/r8a779g0.dtsi b/arch/arm64/boot/dts/renesas/r8a779g0.dtsi
> index 82a7278836e57..b9b860ef70351 100644
> --- a/arch/arm64/boot/dts/renesas/r8a779g0.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r8a779g0.dtsi
> @@ -589,6 +589,15 @@ tmu4: timer@ffc00000 {
>  			status = "disabled";
>  		};
>  
> +		gptp: ptp@e6449000 {
> +			compatible = "renesas,r8a779g0-gptp", "renesas,rcar-gen4-gptp";
> +			reg = <0 0xe6449000 0 0x500>;

[Severity: High]
Does this overlap with the existing tsn0 node? 

The existing tsn0 node still claims this identical 0xe6449000 memory region
(size 0x500), which its driver requests exclusively via
devm_ioremap_resource().

Will one of the drivers fail probing entirely, given that request_mem_region()
will reject the second request with -EBUSY?

> +			clocks = <&cpg CPG_MOD 2723>;
> +			power-domains = <&sysc R8A779G0_PD_ALWAYS_ON>;
> +			resets = <&cpg 2723>;

[Severity: High]
Could sharing this reset line cause hardware state corruption?

The tsn0 network driver also maps to the same reset line 2723 and actively
asserts it during interface up/down.

If the tsn0 interface is brought up or down, wouldn't it forcefully reset
the physical gPTP module, wiping out the precision time synchronization
configuration and internal timer values for any other active consumers
(such as RAVB)?

> +			status = "disabled";
> +		};
> +
>  		tsn0: ethernet@e6460000 {
>  			compatible = "renesas,r8a779g0-ethertsn", "renesas,rcar-gen4-ethertsn";
>  			reg = <0 0xe6460000 0 0x7000>,

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260721132936.1331318-1-niklas.soderlund+renesas@ragnatech.se?part=3

      reply	other threads:[~2026-07-22 13:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 13:29 [PATCH net-next v5 0/3] ptp: Add driver for R-Car Gen4 Niklas Söderlund
2026-07-21 13:29 ` [PATCH net-next v5 1/3] dt-bindings: ptp: renesas,rcar-gen4-gptp: Add " Niklas Söderlund
2026-07-21 13:29 ` [PATCH net-next v5 2/3] ptp: Add driver for " Niklas Söderlund
2026-07-21 14:36   ` Vadim Fedorenko
2026-07-22 13:31   ` sashiko-bot
2026-07-21 13:29 ` [PATCH net-next v5 3/3] arm64: dts: renesas: r8a779g0: Add gPTP node Niklas Söderlund
2026-07-22 13:31   ` 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=20260722133109.E658B1F00A3A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=wsa+renesas@sang-engineering.com \
    /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