From: Miotsuki Mizuno <founder@crepuse.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Mark Brown <broonie@kernel.org>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-rockchip@lists.infradead.org"
<linux-rockchip@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>
Subject: [PATCH] arm64: dts: rockchip: Enable audio on DFRobot UNIHIKER M10 V1.2
Date: Fri, 9 Oct 2026 11:27:55 +0000 [thread overview]
Message-ID: <20261009112754.60770-1-founder@crepuse.com> (raw)
Enable the internal RK3308 codec and its I2S2 interface, and add a
simple-audio-card. Route the onboard microphone to MIC1 and supply it
from MICBIAS1, with the bias set to 85 percent of AVDD as used during
board bring-up.
The board does not expose a speaker interface, so no speaker routing
is added.
The board uses codec revision B. Support has been accepted in the ASoC
for-7.4 branch as commit 157f7cba77a9 ("ASoC: codecs: rk3308: add support
for codec revision B"). This is a runtime dependency; the DTS uses the
existing codec compatible and bindings.
Signed-off-by: Mizuno Miotsuki <founder@crepuse.com>
---
Based on Heiko's v7.4-armsoc/dts64 branch. The codec revision-B driver
support is in Mark Brown's ASoC for-7.4 branch (157f7cba77a9); there is
no build-time or binding dependency on that change.
The same microphone route and 85-percent bias setting were used during
V1.2 bring-up. Codec registration and onboard microphone capture were
verified then, with the recording confirmed by listening. PCM/DAPM
checks were also performed with the preceding codec candidate; physical
LINEOUT and HPOUT audio were not tested. The final accepted codec
shared-output implementation was compile-tested only.
Validation of this patch:
- Target DTB build: PASS (arm64 defconfig, aarch64-linux-gnu-gcc).
- Target dtbs_check against all bindings: PASS, no diagnostics
(dtschema 2026.9, CHECK_DTBS=y).
- Strict checkpatch: PASS, 0 errors, 0 warnings, 0 checks.
.../dts/rockchip/rk3308-unihiker-m10-v1.2.dts | 30 +++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3308-unihiker-m10-v1.2.dts b/arch/arm64/boot/dts/rockchip/rk3308-unihiker-m10-v1.2.dts
index 270ea970c95a..7adef454ea89 100644
--- a/arch/arm64/boot/dts/rockchip/rk3308-unihiker-m10-v1.2.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3308-unihiker-m10-v1.2.dts
@@ -54,6 +54,26 @@ sdio_pwrseq: sdio-pwrseq {
reset-gpios = <&gpio0 RK_PA2 GPIO_ACTIVE_LOW>;
};
+ sound {
+ compatible = "simple-audio-card";
+ simple-audio-card,name = "UNIHIKER M10 RK3308 codec";
+ simple-audio-card,format = "i2s";
+ simple-audio-card,mclk-fs = <256>;
+ simple-audio-card,widgets =
+ "Microphone", "Internal Microphone";
+ simple-audio-card,routing =
+ "Internal Microphone", "MICBIAS1",
+ "MIC1", "Internal Microphone";
+
+ simple-audio-card,cpu {
+ sound-dai = <&i2s_8ch_2>;
+ };
+
+ simple-audio-card,codec {
+ sound-dai = <&codec>;
+ };
+ };
+
vcc_1v8: regulator-vcc-1v8 {
compatible = "regulator-fixed";
regulator-name = "vcc_1v8";
@@ -117,6 +137,11 @@ vdd_core: regulator-vdd-core {
};
};
+&codec {
+ rockchip,micbias-avdd-percent = <85>;
+ status = "okay";
+};
+
&cpu0 {
cpu-supply = <&vdd_core>;
};
@@ -131,6 +156,11 @@ &emmc {
status = "okay";
};
+&i2s_8ch_2 {
+ #sound-dai-cells = <0>;
+ status = "okay";
+};
+
&io_domains {
vccio0-supply = <&vcc_io>;
vccio1-supply = <&vcc_io>;
base-commit: f204f28bd1fa9b4cf3e47488ba3ba25251aba18a
--
2.56.0
reply other threads:[~2026-10-09 11:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261009112754.60770-1-founder@crepuse.com \
--to=founder@crepuse.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=robh@kernel.org \
/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