From: sashiko-bot@kernel.org
To: "Bob Hui" <bg9oxa@163.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v12 2/2] arm64: dts: rockchip: Add ALIENTEK QuarkPi-CA2
Date: Mon, 02 Nov 2026 16:01:11 +0000 [thread overview]
Message-ID: <sashiko-outbox-193719@kernel.org> (raw)
In-Reply-To: <20261102-quarkpi-ca2-v12-2-d749d9bb2bf9@163.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] arm64: dts: rockchip: misplaced hp_con pinctrl and duplicate DAPM routes
--
commit 07118101f721e520605d0c72d4bd5b261e3be1ae
Author: Bob Hui <bg9oxa@163.com>
arm64: dts: rockchip: Add ALIENTEK QuarkPi-CA2
This commit adds the device tree for the ALIENTEK QuarkPi-CA2, an RK3588S
based card computer.
> diff --git a/arch/arm64/boot/dts/rockchip/rk3588s-quarkpi-ca2.dts b/arch/arm64/boot/dts/rockchip/rk3588s-quarkpi-ca2.dts
> new file mode 100644
> index 0000000000000..c9cd01ba3869c
> --- /dev/null
> +++ b/arch/arm64/boot/dts/rockchip/rk3588s-quarkpi-ca2.dts
> @@ -0,0 +1,1209 @@
[ ... ]
> + 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", "Headset Mic";
> + simple-audio-card,widgets =
> + "Headphone", "Headphones",
> + "Microphone", "Headset Mic";
> + simple-audio-card,routing =
> + "Headphones", "LOUT1",
> + "Headphones", "ROUT1",
> + "Headphones", "Headphone Power OUTL",
> + "Headphones", "Headphone Power OUTR",
> + "Headphone Power INL", "LOUT1",
> + "Headphone Power INR", "ROUT1",
> + "LINPUT1", "Headset Mic",
> + "RINPUT1", "Headset Mic";
> +
> + sound_codec: simple-audio-card,codec {
> + sound-dai = <&es8388>;
> + system-clock-frequency = <12288000>;
> + };
> +
> + sound_cpu: simple-audio-card,cpu {
> + sound-dai = <&i2s0_8ch>;
> + };
> + };
> +
> + hp_amp: audio-amplifier {
> + compatible = "simple-audio-amplifier";
> + sound-name-prefix = "Headphone Power";
> + enable-gpios = <&gpio1 RK_PC6 GPIO_ACTIVE_HIGH>;
> + };
[Severity: Low]
In analog_sound and hp_amp, hp_con configures gpio1 RK_PC6 with
pcfg_pull_down, which is the enable-gpios pin requested by hp_amp in
simple_amp_probe().
Because pinctrl_bind_pins() applies pinctrl-0 per platform device before
probe(), if hp_amp probes before analog_sound (or while analog_sound defers
waiting for es8388 or i2s0_8ch), hp_con is not bound to hp_amp when
devm_gpiod_get_optional() requests gpio1 RK_PC6. Should hp_con be moved from
analog_sound's pinctrl-0 to hp_amp instead?
Also, in analog_sound's simple-audio-card,routing property, LOUT1 and ROUT1
are routed both directly to Headphones and through the Headphone Power
amplifier widgets (Headphone Power INL/INR -> Headphone Power OUTL/OUTR ->
Headphones), creating parallel direct and amplified paths in the DAPM graph.
Should the direct "Headphones", "LOUT1" and "Headphones", "ROUT1" routes be
dropped so the signal only goes through the headphone amplifier?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261102-quarkpi-ca2-v12-0-d749d9bb2bf9@163.com?part=2
prev parent reply other threads:[~2026-11-02 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 15:40 [PATCH v12 0/2] arm64: dts: rockchip: Add ALIENTEK QuarkPi-CA2 Bob Hui
2026-11-02 15:40 ` [PATCH v12 1/2] dt-bindings: arm: " Bob Hui
2026-11-02 15:40 ` [PATCH v12 2/2] arm64: dts: " Bob Hui
2026-11-02 16:01 ` sashiko-bot [this message]
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-193719@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