From: sashiko-bot@kernel.org
To: "Nicolo Giuliani" <nicolo.giuliani6@studio.unibo.it>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: marvell: Add Sophos XGS 107w NPU board
Date: Sat, 19 Sep 2026 19:50:04 +0000 [thread overview]
Message-ID: <20260919195004.D99D11F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260919-send-dt-v1-3-365615a74ef3@studio.unibo.it>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dt: intentional omission of physical reset-gpios to workaround driver bug
--
commit 3bbda9294c3060f49dfc25ff724a945a54bd4560
Author: Nicolo Giuliani <nicolo.giuliani6@studio.unibo.it>
arm64: dts: marvell: Add Sophos XGS 107w NPU board
This commit adds a device tree for the network processing unit (NPU) of the
Sophos XGS 87/107 desktop firewalls. It describes the Marvell Armada CN9130
SoC, along with the UART, eMMC, SPI NOR flash, SFP cage, and a Marvell
88E6193X switch.
> diff --git a/arch/arm64/boot/dts/marvell/cn9130-sophos-xgs107w.dts b/arch/arm64/boot/dts/marvell/cn9130-sophos-xgs107w.dts
> new file mode 100644
> index 0000000000000..d98d8da10e637
> --- /dev/null
> +++ b/arch/arm64/boot/dts/marvell/cn9130-sophos-xgs107w.dts
[ ... ]
> +&cp0_mdio {
> + status = "okay";
> +
> + switch@2 {
> + compatible = "marvell,mv88e6190";
> + reg = <2>;
> + /*
> + * The reset line of the switch is CP GPIO2 pin 17. It is not
> + * described as reset-gpios: the 88E6193X needs about two
> + * seconds after a reset before it can be used, much longer
> + * than the driver waits, and the probe would time out. The
> + * boot loader resets the switch before starting the kernel.
> + */
[Severity: Medium]
Is it appropriate to deliberately omit the physically present reset-gpios
property to work around a Linux driver timeout limitation?
Device Tree is intended to be an OS-independent description of the hardware
topology. By intentionally omitting this connection in switch@2, the kernel
is unable to reset the switch natively (for instance, during a driver reload
or system reboot).
Would it be better to accurately describe the hardware by including the
reset-gpios property here, and instead fix the timeout in the mv88e6xxx
driver or use standard delay properties like reset-deassert-us to handle
the two-second requirement?
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260919-send-dt-v1-0-365615a74ef3@studio.unibo.it?part=3
next prev parent reply other threads:[~2026-09-19 19:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 19:44 [PATCH 0/3] arm64: dts: marvell: Add Sophos XGS 107w NPU Nicolo Giuliani via B4 Relay
2026-09-19 19:44 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add Sophos Nicolo Giuliani via B4 Relay
2026-09-20 18:26 ` Krzysztof Kozlowski
2026-09-19 19:44 ` [PATCH 2/3] dt-bindings: arm: marvell: Add Sophos XGS 107w NPU Nicolo Giuliani via B4 Relay
2026-09-20 18:27 ` Krzysztof Kozlowski
2026-09-20 19:06 ` R: " Nicolò Giuliani - nicolo.giuliani6@studio.unibo.it
2026-09-19 19:44 ` [PATCH 3/3] arm64: dts: marvell: Add Sophos XGS 107w NPU board Nicolo Giuliani via B4 Relay
2026-09-19 19:50 ` sashiko-bot [this message]
2026-09-19 22:23 ` Andrew Lunn
2026-09-20 8:48 ` R: " Nicolò Giuliani - nicolo.giuliani6@studio.unibo.it
2026-09-20 15:14 ` Andrew Lunn
2026-09-20 17:29 ` R: " Nicolò Giuliani - nicolo.giuliani6@studio.unibo.it
2026-09-20 19:07 ` Nicolò Giuliani - nicolo.giuliani6@studio.unibo.it
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=20260919195004.D99D11F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=nicolo.giuliani6@studio.unibo.it \
--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