Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Xilin Wu" <sophon@radxa.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
	linux-gpio@vger.kernel.org, robh@kernel.org,
	dri-devel@lists.freedesktop.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 4/4] arm64: dts: qcom: sc8280xp: add Radxa Dragon Q8B
Date: Fri, 09 Oct 2026 08:12:51 +0000	[thread overview]
Message-ID: <sashiko-outbox-165058@kernel.org> (raw)
In-Reply-To: <20261009-q8b-dts-v2-4-eda11e5dea8b@radxa.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] arm64: dts: qcom: swapped vdda-phy-supply and vdda-pll-supply in mdss0_dp2_phy
--

commit 1ed6dcf998cee616c10f9c98d191dd8e63e625e3
Author: Xilin Wu <sophon@radxa.com>

arm64: dts: qcom: sc8280xp: add Radxa Dragon Q8B

This commit adds initial device tree support for the Radxa Dragon Q8B
single-board computer. It describes various hardware components including
storage, PCIe, USB-C, HDMI output, audio, and multiple regulators.

> diff --git a/arch/arm64/boot/dts/qcom/sc8280xp-radxa-dragon-q8b.dts b/arch/arm64/boot/dts/qcom/sc8280xp-radxa-dragon-q8b.dts
> new file mode 100644
> index 0000000000000..322b66de6ef68
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/sc8280xp-radxa-dragon-q8b.dts
> @@ -0,0 +1,2102 @@
[ ... ]
> +		vreg_l3b: ldo3 {
> +			regulator-name = "vreg_l3b";
> +			regulator-min-microvolt = <1200000>;
> +			regulator-max-microvolt = <1200000>;
> +			regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> +			regulator-boot-on;
> +			regulator-allow-set-load;
> +			regulator-allowed-modes = <RPMH_REGULATOR_MODE_LPM
> +						   RPMH_REGULATOR_MODE_HPM>;
> +		};
[ ... ]
> +		vreg_l6b: ldo6 {
> +			regulator-name = "vreg_l6b";
> +			regulator-min-microvolt = <880000>;
> +			regulator-max-microvolt = <880000>;
> +			regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> +			regulator-boot-on;
> +			regulator-allow-set-load;
> +			regulator-allowed-modes = <RPMH_REGULATOR_MODE_LPM
> +						   RPMH_REGULATOR_MODE_HPM>;
> +		};
[ ... ]
> +&mdss0_dp2_phy {
> +	vdda-phy-supply = <&vreg_l3b>;
> +	vdda-pll-supply = <&vreg_l6b>;

[Severity: High]
Are the core analog PHY supply and PLL supply swapped here?

The vdda-phy-supply is connected to <&vreg_l3b> (which is configured as 1.2V
above), and vdda-pll-supply is connected to <&vreg_l6b> (configured as 0.88V).
For Qualcomm DisplayPort PHYs, the core analog PHY supply requires the lower
voltage rail (0.88V), and the PLL supply requires the higher voltage rail
(1.2V). 

Could this apply 1.2V to the 0.88V core domain, potentially preventing the PHY
from initializing or causing overvoltage damage? For comparison, usb_0_qmpphy
in this same file correctly uses the lower voltage for vdda-phy-supply and the
higher voltage for vdda-pll-supply.

> +
> +	status = "okay";
> +};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261009-q8b-dts-v2-0-eda11e5dea8b@radxa.com?part=4

  reply	other threads:[~2026-10-09  8:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09  7:55 [PATCH v2 0/4] arm64: dts: qcom: Add support for Radxa Dragon Q8B Xilin Wu
2026-10-09  7:55 ` [PATCH v2 1/4] dt-bindings: display: bridge: simple: document Chrontel CH7218A Xilin Wu
2026-10-09  7:59   ` sashiko-bot
2026-10-09 11:41   ` Krzysztof Kozlowski
2026-10-09  7:55 ` [PATCH v2 2/4] drm/bridge: simple: add " Xilin Wu
2026-10-09  7:58   ` sashiko-bot
2026-10-09  8:23   ` Dmitry Baryshkov
2026-10-09  9:30   ` Neil Armstrong
2026-10-09  7:55 ` [PATCH v2 3/4] dt-bindings: arm: qcom: document Radxa Dragon Q8B Xilin Wu
2026-10-09  7:59   ` sashiko-bot
2026-10-09 11:42   ` Krzysztof Kozlowski
2026-10-09 13:23     ` Dmitry Baryshkov
2026-10-09 13:28       ` Krzysztof Kozlowski
2026-10-09 14:38         ` Krzysztof Kozlowski
2026-10-09  7:55 ` [PATCH v2 4/4] arm64: dts: qcom: sc8280xp: add " Xilin Wu
2026-10-09  8:12   ` sashiko-bot [this message]
2026-10-09  8:29 ` (subset) [PATCH v2 0/4] arm64: dts: qcom: Add support for " Dmitry Baryshkov
2026-10-09 11:43   ` Krzysztof Kozlowski
2026-10-09 13:20     ` Dmitry Baryshkov
2026-10-09 13:23       ` Krzysztof Kozlowski

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=sashiko-outbox-165058@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=sophon@radxa.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