From: Alex Bee <knaerzche@gmail.com>
To: Heiko Stuebner <heiko@sntech.de>, Rob Herring <robh+dt@kernel.org>
Cc: Johan Jonker <jbx6244@gmail.com>,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Alex Bee <knaerzche@gmail.com>
Subject: [PATCH v2 0/5] Updates for Radxa ROCK Pi 4
Date: Fri, 18 Jun 2021 20:12:51 +0200 [thread overview]
Message-ID: <20210618181256.27992-1-knaerzche@gmail.com> (raw)
Hi list,
This series adds support for 2 new revisions of Radxa's ROCK Pi 4,
namely ROCK Pi 4A+ and ROCK Pi 4B+. While most things are in common
with the previous 4A and 4B revisions, they have OP1 revision of
the SoC and eMMC soldered on board.
Patch 4 and 5 add SPDIF and anlog Codec to the common device tree,
since they are in place in previous revisions as well.
It superseeds
https://lore.kernel.org/linux-rockchip/d4e4e06e-6ddd-4707-232d-b829c1d646e6@gmail.com/
There is no example (which I could find) for Rockchip on how to
deal with "+" revisions - so I looked up other SoCs and the rule
seems to be to use the "+" for the model name (which is the "offical"
name), but use "-plus" for compatible name and device tree files names
(see "Raspberry Pi Model A+", for instance).
A short node for testing ES8316 codec:
The driver disables the headphone jack by default - for testing
one would have to enable it via amixer with:
amixer [card index] 'Right Headphone Mixer Right DAC' on
amixer [card index] 'Left Headphone Mixer Left DAC' on
Alex
Changes in v2:
- added additional compatibles for the new revisions (Heiko)
- renamed ES8316 audio card name to "Analog" (Johan)
- added patch for SPDIF
- aligned spelling of board name(s)
Alex Bee (5):
dt-bindings: Add doc for ROCK Pi 4 A+ and B+
arm64: dts: rockchip: Add RK3399 ROCK Pi 4A+ board
arm64: dts: rockchip: Add RK3399 ROCK Pi 4B+ board
arm64: dts: rockchip: add ES8316 codec for ROCK Pi 4
arm64: dts: rockchip: add SPDIF node for ROCK Pi 4
.../devicetree/bindings/arm/rockchip.yaml | 4 +-
arch/arm64/boot/dts/rockchip/Makefile | 2 +
.../boot/dts/rockchip/rk3399-rock-pi-4.dtsi | 54 +++++++++++++++++++
.../dts/rockchip/rk3399-rock-pi-4a-plus.dts | 14 +++++
.../dts/rockchip/rk3399-rock-pi-4b-plus.dts | 47 ++++++++++++++++
5 files changed, 120 insertions(+), 1 deletion(-)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4a-plus.dts
create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4b-plus.dts
base-commit: 009c9aa5be652675a06d5211e1640e02bbb1c33d
--
2.27.0
next reply other threads:[~2021-06-18 18:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 18:12 Alex Bee [this message]
2021-06-18 18:12 ` [PATCH v2 1/5] dt-bindings: Add doc for ROCK Pi 4 A+ and B+ Alex Bee
2021-07-12 20:07 ` Rob Herring
2021-06-18 18:12 ` [PATCH v2 2/5] arm64: dts: rockchip: Add RK3399 ROCK Pi 4A+ board Alex Bee
2021-06-18 18:12 ` [PATCH v2 3/5] arm64: dts: rockchip: Add RK3399 ROCK Pi 4B+ board Alex Bee
2021-06-18 18:12 ` [PATCH v2 4/5] arm64: dts: rockchip: add ES8316 codec for ROCK Pi 4 Alex Bee
2021-06-18 18:12 ` [PATCH v2 5/5] arm64: dts: rockchip: add SPDIF node " Alex Bee
2021-07-17 21:52 ` [PATCH v2 0/5] Updates for Radxa " 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=20210618181256.27992-1-knaerzche@gmail.com \
--to=knaerzche@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).