Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Hrushiraj Gandhi" <hrushirajg23@gmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 1/2] arm64: dts: rockchip: add Vicharak Axon board
Date: Mon, 01 Jun 2026 13:42:17 +0000	[thread overview]
Message-ID: <20260601134217.C666F1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260601132529.139172-2-hrushirajg23@gmail.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] The `enable-gpios` property is invalid for the `rockchip,rk3588-dw-hdmi-qp` compatible binding and is ignored by the driver, leaving the HDMI ports unpowered.
- [High] The `rk806_dvs1_null` pinctrl node incorrectly configures `gpio_pwrctrl2` instead of `gpio_pwrctrl1` due to a copy-paste error.
--

commit 9e5cc3349cf78765922014a014dd0a775c777bef
Author: Hrushiraj Gandhi <hrushirajg23@gmail.com>

arm64: dts: rockchip: add Vicharak Axon board

Add initial support for the Vicharak Axon single-board computer based on
the Rockchip RK3588 SoC.

> diff --git a/arch/arm64/boot/dts/rockchip/rk3588-vicharak-axon.dts b/arch/arm64/boot/dts/rockchip/rk3588-vicharak-axon.dts
> new file mode 100644
> index 0000000000000..fecd13a52e88a
> --- /dev/null
> +++ b/arch/arm64/boot/dts/rockchip/rk3588-vicharak-axon.dts
[ ... ]
> +&hdmi0 {
> +	enable-gpios = <&gpio1 RK_PB0 GPIO_ACTIVE_HIGH>;
[Severity: High]
The dw-hdmi-qp binding does not support the enable-gpios property, so the
driver will not parse this.

If this GPIO controls power to the HDMI port, will the port remain unpowered
and non-functional? If this is meant to enable FRL, should this use the
frl-enable-gpios property instead?

> +	status = "okay";
> +};
[ ... ]
> +&hdmi1 {
> +	enable-gpios = <&gpio1 RK_PA7 GPIO_ACTIVE_HIGH>;
[Severity: High]
Similarly to hdmi0 above, does this enable-gpios property need to be changed
since it is not parsed by the dw-hdmi-qp driver?

> +	status = "okay";
> +};
[ ... ]
> +	pmic@0 {
> +		reg = <0>;
> +		compatible = "rockchip,rk806";
[ ... ]
> +		rk806_dvs1_null: rk806_dvs1_null {
> +			pins = "gpio_pwrctrl2";
[Severity: High]
Is this pins assignment correct? It configures gpio_pwrctrl2 instead of
gpio_pwrctrl1 for rk806_dvs1_null, which looks like a copy-paste error.

This could leave the actual DVS1 pin unconfigured and susceptible to
unintentional voltage scaling from floating signals.

> +			function = "pin_fun0";
> +		};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260601132529.139172-1-hrushirajg23@gmail.com?part=1

  reply	other threads:[~2026-06-01 13:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01 13:25 [PATCH v2 0/2] arm64: dts: rockchip: add Vicharak Axon board support Hrushiraj Gandhi
2026-06-01 13:25 ` [PATCH v2 1/2] arm64: dts: rockchip: add Vicharak Axon board Hrushiraj Gandhi
2026-06-01 13:42   ` sashiko-bot [this message]
2026-06-01 13:25 ` [PATCH v2 2/2] dt-bindings: arm: " Hrushiraj Gandhi
2026-06-01 14:01   ` Heiko Stuebner

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=20260601134217.C666F1F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hrushirajg23@gmail.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