From: Yao Zi <ziyao@disroot.org>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Chris Morgan <macromorgan@hotmail.com>,
Jonas Karlman <jonas@kwiboo.se>, Tim Lunn <tim@feathertop.org>,
Andy Yan <andyshrk@163.com>,
Muhammed Efe Cetin <efectn@protonmail.com>,
Jagan Teki <jagan@edgeble.ai>, Dragan Simic <dsimic@manjaro.org>,
Ondrej Jirman <megi@xff.cz>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org
Cc: Celeste Liu <CoelacanthusHex@gmail.com>,
Yao Zi <ziyao@disroot.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: [PATCH v4 1/4] dt-bindings: serial: snps-dw-apb-uart: Document Rockchip RK3528
Date: Thu, 29 Aug 2024 09:27:02 +0000 [thread overview]
Message-ID: <20240829092705.6241-2-ziyao@disroot.org> (raw)
In-Reply-To: <20240829092705.6241-1-ziyao@disroot.org>
Rockchip RK3528 comes with a snps-dw-apb-uart compatible UART. Document
it in dt-bindings.
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
Signed-off-by: Yao Zi <ziyao@disroot.org>
---
Documentation/devicetree/bindings/serial/snps-dw-apb-uart.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/serial/snps-dw-apb-uart.yaml b/Documentation/devicetree/bindings/serial/snps-dw-apb-uart.yaml
index 4cdb0dcaccf3..4573044be189 100644
--- a/Documentation/devicetree/bindings/serial/snps-dw-apb-uart.yaml
+++ b/Documentation/devicetree/bindings/serial/snps-dw-apb-uart.yaml
@@ -48,6 +48,7 @@ properties:
- rockchip,rk3328-uart
- rockchip,rk3368-uart
- rockchip,rk3399-uart
+ - rockchip,rk3528-uart
- rockchip,rk3568-uart
- rockchip,rk3588-uart
- rockchip,rv1108-uart
--
2.46.0
next prev parent reply other threads:[~2024-08-29 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 9:27 [PATCH v4 0/4] Add initial support for Rockchip RK3528 SoC Yao Zi
2024-08-29 9:27 ` Yao Zi [this message]
2024-08-29 9:27 ` [PATCH v4 2/4] dt-bindings: arm: rockchip: Add Radxa E20C board Yao Zi
2024-08-29 9:27 ` [PATCH v4 3/4] arm64: dts: rockchip: Add base DT for rk3528 SoC Yao Zi
2024-08-29 9:27 ` [PATCH v4 4/4] arm64: dts: rockchip: Add Radxa e20c board Yao Zi
2024-09-17 20:14 ` [PATCH v4 0/4] Add initial support for Rockchip RK3528 SoC Yao Zi
2024-09-17 23:13 ` Heiko Stuebner
2024-09-18 6:21 ` Greg Kroah-Hartman
2024-09-19 10:44 ` Yao Zi
2024-10-12 19:07 ` (subset) " 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=20240829092705.6241-2-ziyao@disroot.org \
--to=ziyao@disroot.org \
--cc=CoelacanthusHex@gmail.com \
--cc=andyshrk@163.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=efectn@protonmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=jagan@edgeble.ai \
--cc=jirislaby@kernel.org \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=macromorgan@hotmail.com \
--cc=megi@xff.cz \
--cc=robh@kernel.org \
--cc=tim@feathertop.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).