From: Tianling Shen <cnsztl@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Heiko Stuebner <heiko@sntech.de>,
Jagan Teki <jagan@amarulasolutions.com>,
Peter Geis <pgwipeout@gmail.com>, Andy Yan <andyshrk@163.com>,
Tianling Shen <cnsztl@gmail.com>,
Brian Norris <briannorris@chromium.org>,
Chris Morgan <macromorgan@hotmail.com>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Andrew Lunn <andrew@lunn.ch>,
Michael Riesch <michael.riesch@wolfvision.net>,
Maya Matuszczyk <maccraft123mc@gmail.com>,
Andrew Powers-Holmes <aholmes@omnom.net>,
Sascha Hauer <s.hauer@pengutronix.de>,
Vasily Khoruzhick <anarsoul@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 5/5] arm64: dts: rockchip: remove I2S1 TDM node for the NanoPi R5 series
Date: Sat, 18 Mar 2023 16:37:45 +0800 [thread overview]
Message-ID: <20230318083745.6181-6-cnsztl@gmail.com> (raw)
In-Reply-To: <20230318083745.6181-1-cnsztl@gmail.com>
This is for the audio output which does not exist on the boards.
Also disable regulator-always-on for vccio_acodec since it's only
used by the audio output.
Fixes: c6629b9a6738 ("arm64: dts: rockchip: Add FriendlyElec Nanopi R5S")
Signed-off-by: Tianling Shen <cnsztl@gmail.com>
---
arch/arm64/boot/dts/rockchip/rk3568-nanopi-r5s.dtsi | 6 ------
1 file changed, 6 deletions(-)
diff --git a/arch/arm64/boot/dts/rockchip/rk3568-nanopi-r5s.dtsi b/arch/arm64/boot/dts/rockchip/rk3568-nanopi-r5s.dtsi
index dd9a7907a1c5..58ba328ea782 100644
--- a/arch/arm64/boot/dts/rockchip/rk3568-nanopi-r5s.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3568-nanopi-r5s.dtsi
@@ -330,7 +330,6 @@ regulator-state-mem {
vccio_acodec: LDO_REG4 {
regulator-name = "vccio_acodec";
- regulator-always-on;
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
@@ -441,11 +440,6 @@ &i2s0_8ch {
status = "okay";
};
-&i2s1_8ch {
- rockchip,trcm-sync-tx-only;
- status = "okay";
-};
-
&pcie30phy {
data-lanes = <1 2>;
status = "okay";
--
2.40.0
next prev parent reply other threads:[~2023-03-18 8:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 8:37 [PATCH v2 0/5] arm64: dts: rockchip: improve support for NanoPi R5 series Tianling Shen
2023-03-18 8:37 ` [PATCH v2 1/5] arm64: dts: rockchip: create common dtsi " Tianling Shen
2023-03-18 8:37 ` [PATCH v2 2/5] dt-bindings: Add doc for FriendlyARM NanoPi R5C Tianling Shen
2023-03-18 8:37 ` [PATCH v2 3/5] arm64: dts: rockchip: Add " Tianling Shen
2023-03-18 8:37 ` [PATCH v2 4/5] arm64: dts: rockchip: fix gmac support for NanoPi R5S Tianling Shen
2023-03-18 8:37 ` Tianling Shen [this message]
2023-03-22 23:40 ` [PATCH v2 0/5] arm64: dts: rockchip: improve support for NanoPi R5 series 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=20230318083745.6181-6-cnsztl@gmail.com \
--to=cnsztl@gmail.com \
--cc=aholmes@omnom.net \
--cc=anarsoul@gmail.com \
--cc=andrew@lunn.ch \
--cc=andyshrk@163.com \
--cc=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jagan@amarulasolutions.com \
--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=maccraft123mc@gmail.com \
--cc=macromorgan@hotmail.com \
--cc=michael.riesch@wolfvision.net \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sebastian.reichel@collabora.com \
/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).