From: sashiko-bot@kernel.org
To: BG9OXA <bg9oxa@163.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v5 2/2] arm64: dts: rockchip: add ALIENTEK QuarkPi-CA2
Date: Thu, 01 Oct 2026 15:31:13 +0000 [thread overview]
Message-ID: <20261001153113.E4B131F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261001-b4-quarkpi-ca2-v5-2-e19296802978@163.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] dts: gmac1 configuration contradicts commit message regarding RGMII delays
- [Medium] dts: invalid parallel DAPM routing for headphones bypasses the amplifier
--
commit 797f222a3f5a732b55c8373821ac94a17d7cec1f
Author: BG9OXA <bg9oxa@163.com>
arm64: dts: rockchip: add ALIENTEK QuarkPi-CA2
This commit adds device tree support for the ALIENTEK QuarkPi-CA2 single
board computer, defining hardware interfaces including Gigabit Ethernet, USB,
HDMI, PCIe, and an ES8388 audio codec with a headphone amplifier.
> diff --git a/arch/arm64/boot/dts/rockchip/rk3588s-quarkpi-ca2.dts b/arch/arm64/boot/dts/rockchip/rk3588s-quarkpi-ca2.dts
> --- /dev/null
> +++ b/arch/arm64/boot/dts/rockchip/rk3588s-quarkpi-ca2.dts
[ ... ]
> +&gmac1 {
> + phy-mode = "rgmii-id";
> + clock_in_out = "input";
[Severity: Medium]
The commit message states that the RK3588S RGMII delays are applied on the
MAC side using the tx_delay property. However, this node configures the PHY
to apply delays internally via rgmii-id and lacks a tx_delay property.
Does this configuration inadvertently apply delays on the PHY side instead? If
the MAC driver uses a non-zero default delay when the property is missing,
could the TX delay be applied twice, potentially breaking Gigabit Ethernet
transmission?
[ ... ]
> + analog_sound: analog-sound {
> + compatible = "simple-audio-card";
> + pinctrl-names = "default";
> + pinctrl-0 = <&hp_det &hp_con>;
> + simple-audio-card,name = "QuarkPi-CA2 ES8388";
> + simple-audio-card,format = "i2s";
> + simple-audio-card,bitclock-master = <&sound_cpu>;
> + simple-audio-card,frame-master = <&sound_cpu>;
> + simple-audio-card,mclk-fs = <256>;
> + simple-audio-card,aux-devs = <&hp_amp>;
> + simple-audio-card,hp-det-gpios = <&gpio1 RK_PC4 GPIO_ACTIVE_HIGH>;
> + simple-audio-card,pin-switches = "Headphones";
> + simple-audio-card,widgets =
> + "Headphone", "Headphones",
> + "Microphone", "Headset Mic",
> + "Microphone", "Main Mic";
> + simple-audio-card,routing =
> + "Headphones", "LOUT1",
> + "Headphones", "ROUT1",
> + "Headphones", "Headphone Power OUTL",
> + "Headphones", "Headphone Power OUTR",
[Severity: Medium]
The ALSA DAPM routing defines parallel direct paths from the codec (LOUT1 and
ROUT1) to the Headphones widget, alongside the paths passing through the
headphone amplifier (Headphone Power OUTL and OUTR).
Could this parallel direct routing bypass the amplifier logically and confuse
DAPM power management into leaving the external amplifier powered down? DAPM
might see a complete, active path directly from the codec to the headphones,
which could result in no or distorted audio output.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261001-b4-quarkpi-ca2-v5-0-e19296802978@163.com?part=2
next prev parent reply other threads:[~2026-10-01 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 15:19 [PATCH v5 0/2] arm64: dts: rockchip: add ALIENTEK QuarkPi-CA2 BG9OXA
2026-10-01 15:19 ` [PATCH v5 1/2] dt-bindings: arm: " BG9OXA
2026-10-01 15:19 ` [PATCH v5 2/2] arm64: dts: " BG9OXA
2026-10-01 15:31 ` sashiko-bot [this message]
2026-10-04 21:12 ` Andrew Lunn
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=20261001153113.E4B131F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bg9oxa@163.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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