From: Miotsuki Mizuno <founder@crepuse.com>
To: "heiko@sntech.de" <heiko@sntech.de>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-rockchip@lists.infradead.org"
<linux-rockchip@lists.infradead.org>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>,
"robh@kernel.org" <robh@kernel.org>
Subject: [PATCH v2 0/1] Enable audio on UNIHIKER M10 V1.2
Date: Mon, 12 Oct 2026 12:17:17 +0000 [thread overview]
Message-ID: <20261012121709.53418-1-founder@crepuse.com> (raw)
Enable the internal codec, I2S2 and onboard microphone route. The board
uses codec revision B; that driver support is already accepted in the
ASoC for-7.4 tree as commit 157f7cba77a9. It is a runtime dependency,
not a change to the existing codec binding.
Changes since v1:
- Normalize author/sender identity and preserve it in the patch body.
- Recheck ordinary and strict checkpatch in the actual Git repository.
Mizuno Miotsuki (1):
arm64: dts: rockchip: Enable audio on DFRobot UNIHIKER M10 V1.2
.../dts/rockchip/rk3308-unihiker-m10-v1.2.dts | 30 +++++++++++++++++++
1 file changed, 30 insertions(+)
base-commit: ae965b9856f033145e292b0c29082a26bcc45efd
--
2.56.0
next reply other threads:[~2026-10-12 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 12:17 Miotsuki Mizuno [this message]
2026-10-12 12:17 ` [PATCH v2 1/1] arm64: dts: rockchip: Enable audio on DFRobot " Miotsuki Mizuno
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=20261012121709.53418-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
all inboxes | Powered by JetHome®