From: ZhuXiangyu <1194781887@qq.com>
To: "Uwe Kleine-König" <ukleinek@kernel.org>,
"Heiko Stuebner" <heiko@sntech.de>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-pwm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, ZhuXiangyu <1194781887@qq.com>
Subject: [PATCH 2/2] dt-bindings: pwm: rockchip: add RK3506 and RK3576 PWM
Date: Sat, 21 Nov 2026 14:59:36 +0800 [thread overview]
Message-ID: <tencent_85AFCE164FAAD1CCAB95DC7CD804CA9BB309@qq.com> (raw)
In-Reply-To: <20261121065936.1125919-1-1194781887@qq.com>
Document the PWM v4 controllers found on RK3506 and RK3576. They use
the pwm/pclk clocks and may additionally provide the osc and rc
clocks used by the extended features.
Signed-off-by: ZhuXiangyu <1194781887@qq.com>
---
.../devicetree/bindings/pwm/pwm-rockchip.yaml | 54 +++++++++++++++----
1 file changed, 45 insertions(+), 9 deletions(-)
diff --git a/Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml b/Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml
index c8cdfb72..ea6622d9 100644
--- a/Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml
+++ b/Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml
@@ -15,6 +15,8 @@ properties:
- const: rockchip,rk2928-pwm
- const: rockchip,rk3288-pwm
- const: rockchip,rk3328-pwm
+ - const: rockchip,rk3506-pwm
+ - const: rockchip,rk3576-pwm
- const: rockchip,vop-pwm
- items:
- const: rockchip,rk3036-pwm
@@ -42,10 +44,16 @@ properties:
clocks:
minItems: 1
- maxItems: 2
+ maxItems: 4
clock-names:
- maxItems: 2
+ minItems: 1
+ maxItems: 4
+ items:
+ - const: pwm
+ - const: pclk
+ - const: osc
+ - const: rc
"#pwm-cells":
enum: [2, 3]
@@ -66,25 +74,50 @@ allOf:
contains:
enum:
- rockchip,rk3328-pwm
+ - rockchip,rk3506-pwm
+ - rockchip,rk3576-pwm
- rockchip,rv1108-pwm
then:
properties:
clocks:
- items:
- - description: Used to derive the functional clock for the device.
- - description: Used as the APB bus clock.
+ minItems: 2
clock-names:
- items:
- - const: pwm
- - const: pclk
+ minItems: 2
required:
- clocks
- clock-names
- else:
+ - if:
+ properties:
+ compatible:
+ contains:
+ enum:
+ - rockchip,rk3328-pwm
+ - rockchip,rv1108-pwm
+
+ then:
+ properties:
+ clocks:
+ maxItems: 2
+
+ clock-names:
+ maxItems: 2
+
+ - if:
+ not:
+ properties:
+ compatible:
+ contains:
+ enum:
+ - rockchip,rk3328-pwm
+ - rockchip,rk3506-pwm
+ - rockchip,rk3576-pwm
+ - rockchip,rv1108-pwm
+
+ then:
properties:
clocks:
maxItems: 1
@@ -92,6 +125,9 @@ allOf:
Used both to derive the functional clock
for the device and as the bus clock.
+ clock-names:
+ maxItems: 1
+
required:
- clocks
--
2.47.3
next parent reply other threads:[~2026-11-21 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261121065936.1125919-1-1194781887@qq.com>
2026-11-21 6:59 ` ZhuXiangyu [this message]
2026-11-21 13:35 ` [PATCH 2/2] dt-bindings: pwm: rockchip: add RK3506 and RK3576 PWM Heiko Stübner
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=tencent_85AFCE164FAAD1CCAB95DC7CD804CA9BB309@qq.com \
--to=1194781887@qq.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=ukleinek@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