From: Heiko Stuebner <heiko@sntech.de>
To: lgirdwood@gmail.com, broonie@kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
heiko@sntech.de, marcin.juszkiewicz@linaro.org,
linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: [PATCH 0/3] Fixes for the audio setup on the rk3588-nanopc-t6
Date: Fri, 30 Aug 2024 22:38:16 +0200 [thread overview]
Message-ID: <20240830203819.1972536-1-heiko@sntech.de> (raw)
The Nanopc-T6 board does contain some devicetree errors, that came to
light with recent changes to the board.
clock and port properties need to be part of the codec-binding like used
on other codecs already and one property needs to be removed from the
board.
Heiko Stuebner (3):
ASoC: dt-bindings: realtek,rt5616: document mclk clock
ASoC: dt-bindings: realtek,rt5616: Document audio graph port
arm64: dts: rockchip: drop hp-pin-name property from audio card on
nanopc-t6
.../devicetree/bindings/sound/realtek,rt5616.yaml | 12 ++++++++++++
arch/arm64/boot/dts/rockchip/rk3588-nanopc-t6.dtsi | 1 -
2 files changed, 12 insertions(+), 1 deletion(-)
--
2.43.0
next reply other threads:[~2024-08-30 20:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 20:38 Heiko Stuebner [this message]
2024-08-30 20:38 ` [PATCH 1/3] ASoC: dt-bindings: realtek,rt5616: document mclk clock Heiko Stuebner
2024-08-31 6:46 ` Krzysztof Kozlowski
2024-08-30 20:38 ` [PATCH 2/3] ASoC: dt-bindings: realtek,rt5616: Document audio graph port Heiko Stuebner
2024-08-31 6:47 ` Krzysztof Kozlowski
2024-08-30 20:38 ` [PATCH 3/3] arm64: dts: rockchip: drop hp-pin-name property from audio card on nanopc-t6 Heiko Stuebner
2024-09-04 11:16 ` (subset) [PATCH 0/3] Fixes for the audio setup on the rk3588-nanopc-t6 Mark Brown
2024-09-04 19:06 ` 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=20240830203819.1972536-1-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--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=marcin.juszkiewicz@linaro.org \
--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