Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Pinkesh Vaghela" <pinkesh.vaghela@einfochips.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v4 4/7] riscv: dts: eswin: add hsp bus node
Date: Fri, 14 Aug 2026 07:11:26 +0000	[thread overview]
Message-ID: <20260814071127.434B01F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260814070007.1662455-5-pinkesh.vaghela@einfochips.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] The syscon node is nested under a simple-pm-bus, which relies on child PM runtime to enable its clock, but syscon bypasses PM runtime, leading to unclocked MMIO accesses.
- [Low] The compatible string 'eswin,eic7700-syscfg' is introduced without corresponding device tree binding documentation.
--

--- Patch [4]: [PATCH v4 4/7] riscv: dts: eswin: add hsp bus node ---
commit 478468d2187b14120b83e2c525f0193b36412f11
Author: Pinkesh Vaghela <pinkesh.vaghela@einfochips.com>

riscv: dts: eswin: add hsp bus node

This commit adds an HSP bus node to manage the HSP CFG clock used by HSP
peripherals. This clock is required for accessing both the HSP CSR registers
and the register spaces of HSP peripheral devices.

> diff --git a/arch/riscv/boot/dts/eswin/eic7700.dtsi b/arch/riscv/boot/dts/eswin/eic7700.dtsi
> index b16e3e28632c2..771a88645d835 100644
> --- a/arch/riscv/boot/dts/eswin/eic7700.dtsi
> +++ b/arch/riscv/boot/dts/eswin/eic7700.dtsi
[ ... ]
> @@ -252,6 +252,19 @@ plic: interrupt-controller@c000000 {
>  			#interrupt-cells = <1>;
>  		};
>  
> +		hsp: bus@50400000 {
> +			compatible = "simple-pm-bus";
> +			ranges = <0x0 0x50400000 0x0 0x50400000 0x0 0xa0000>;
> +			clocks = <&clk EIC7700_CLK_GATE_HSP_CFG_CLK>;
> +			#address-cells = <2>;
> +			#size-cells = <2>;
> +
> +			syscon: syscon@50440000 {

[Severity: High]
Will placing the syscon node under a simple-pm-bus lead to unclocked MMIO
accesses and system hangs?

The simple-pm-bus relies on child PM runtime to enable its clock
(EIC7700_CLK_GATE_HSP_CFG_CLK). However, syscon does not instantiate a standard
platform driver. When syscon_node_to_regmap() is called by any dependent
driver, it initializes a regmap with a NULL device and performs raw MMIO
accesses without calling pm_runtime_get_sync().

Because the parent bus is never resumed by the child, the clock remains gated,
which can cause any read/write to the syscon registers to hang the system.

> +				compatible = "eswin,eic7700-syscfg", "syscon";

[Severity: Low]
Is the "eswin,eic7700-syscfg" compatible string missing its device tree
binding documentation?

Without corresponding schema documentation in the bindings tree, this will
cause schema validation warnings during dtbs_check.

> +				reg = <0x0 0x50440000 0x0 0x2000>;
> +			};
> +		};
> +

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260814070007.1662455-1-pinkesh.vaghela@einfochips.com?part=4

  reply	other threads:[~2026-08-14  7:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14  7:00 [PATCH v4 0/7] riscv: eswin: eic7700: Add support for clocks, resets, pinctrl, HSP bus, I2C and watchdog Pinkesh Vaghela
2026-08-14  7:00 ` [PATCH v4 1/7] riscv: dts: eswin: add reset generator for EIC7700 SoC Pinkesh Vaghela
2026-08-14  7:00 ` [PATCH v4 2/7] riscv: dts: eswin: add clock " Pinkesh Vaghela
2026-08-14  7:07   ` sashiko-bot
2026-08-14  7:00 ` [PATCH v4 3/7] riscv: dts: eswin: eic7700: add pinctrl support Pinkesh Vaghela
2026-08-14  7:00 ` [PATCH v4 4/7] riscv: dts: eswin: add hsp bus node Pinkesh Vaghela
2026-08-14  7:11   ` sashiko-bot [this message]
2026-08-14  7:00 ` [PATCH v4 5/7] dt-bindings: i2c: dw: add ESWIN EIC7700 SoC I2C controller Pinkesh Vaghela
2026-08-14  7:00 ` [PATCH v4 6/7] riscv: dts: eswin: add I2C controller support Pinkesh Vaghela
2026-08-14  7:00 ` [PATCH v4 7/7] riscv: dts: eswin: add watchdog support Pinkesh Vaghela
2026-08-14  7:14   ` sashiko-bot

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=20260814071127.434B01F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=pinkesh.vaghela@einfochips.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