From: Nicolas Frattaroli <frattaroli.nicolas@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: Nicolas Frattaroli <frattaroli.nicolas@gmail.com>,
Peter Geis <pgwipeout@gmail.com>,
Michael Riesch <michael.riesch@wolfvision.net>,
Sascha Hauer <s.hauer@pengutronix.de>,
Liang Chen <cl@rock-chips.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] HDMI Audio on RK356x/Quartz64 Model A
Date: Sat, 11 Jun 2022 08:52:58 +0200 [thread overview]
Message-ID: <20220611065300.885212-1-frattaroli.nicolas@gmail.com> (raw)
This enables HDMI audio on Quartz64 Model A, and the RK356x SoC in
general.
i2s0 on the RK356x is connected to HDMI, and only has one DMA. I've
confirmed this with the TRM.
To test this, one needs a video clock, i.e. there is no audio if your
screen is off. The framebuffer console or something else needs to be
running to get audio output.
Changes in v3:
- rebased onto next-20220610
Changes in v2:
- reordered nodes in rk356x.dtsi to conform
- reordered properties in rk356x.dtsi to conform
- add Michael Riesch's Tested-by to rk356x.dtsi
Nicolas Frattaroli (2):
arm64: dts: rockchip: rk356x: Add HDMI audio nodes
arm64: dts: rockchip: Enable HDMI audio on Quartz64 A
.../boot/dts/rockchip/rk3566-quartz64-a.dts | 8 +++++
arch/arm64/boot/dts/rockchip/rk356x.dtsi | 33 +++++++++++++++++++
2 files changed, 41 insertions(+)
--
2.36.1
next reply other threads:[~2022-06-11 6:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 6:52 Nicolas Frattaroli [this message]
2022-06-11 6:52 ` [PATCH v3 1/2] arm64: dts: rockchip: rk356x: Add HDMI audio nodes Nicolas Frattaroli
2022-06-11 6:53 ` [PATCH v3 2/2] arm64: dts: rockchip: Enable HDMI audio on Quartz64 A Nicolas Frattaroli
2022-06-11 13:50 ` [PATCH v3 0/2] HDMI Audio on RK356x/Quartz64 Model A Peter Geis
2022-06-11 15:15 ` 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=20220611065300.885212-1-frattaroli.nicolas@gmail.com \
--to=frattaroli.nicolas@gmail.com \
--cc=cl@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael.riesch@wolfvision.net \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/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®