From: David Yang <mmyangfl@gmail.com>
To: linux-clk@vger.kernel.org
Cc: devicetree@vger.kernel.org, David Yang <mmyangfl@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Subject: [PATCH v2 1/4] dt-bindings: clock: Add simple-clock-controller
Date: Mon, 17 Apr 2023 01:32:57 +0800 [thread overview]
Message-ID: <20230416173302.1185683-2-mmyangfl@gmail.com> (raw)
In-Reply-To: <20230416173302.1185683-1-mmyangfl@gmail.com>
Add DT bindings documentation for simple-clock-controller, mutex
controller for clocks.
Signed-off-by: David Yang <mmyangfl@gmail.com>
---
.../clock/simple-clock-controller.yaml | 50 +++++++++++++++++++
1 file changed, 50 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/simple-clock-controller.yaml
diff --git a/Documentation/devicetree/bindings/clock/simple-clock-controller.yaml b/Documentation/devicetree/bindings/clock/simple-clock-controller.yaml
new file mode 100644
index 000000000000..17835aeddb1d
--- /dev/null
+++ b/Documentation/devicetree/bindings/clock/simple-clock-controller.yaml
@@ -0,0 +1,50 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/clock/simple-clock-controller.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Simple clock controller
+
+maintainers:
+ - David Yang <mmyangfl@gmail.com>
+
+description: |
+ Driver (lock provider) for real clocks.
+
+ Usually one register controls more than one clocks. This controller avoids
+ write conflicts by imposing a write lock, so that two operations on the same
+ register will not happen at the same time.
+
+properties:
+ compatible:
+ items:
+ - oneOf:
+ - const: simple-clock-controller
+ - const: simple-clock-reset-controller
+ - const: syscon
+ - const: simple-mfd
+
+ reg:
+ maxItems: 1
+
+ '#reset-cells':
+ const: 2
+
+patternProperties:
+ "clock@.*":
+ type: object
+ description: Clock nodes.
+
+required:
+ - compatible
+ - reg
+
+additionalProperties: false
+
+examples:
+ - |
+ clock-controller@ffff000 {
+ compatible = "simple-clock-controller", "syscon", "simple-mfd";
+ reg = <0xffff000 0x1000>;
+ };
--
2.39.2
next prev parent reply other threads:[~2023-04-16 17:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 17:32 [PATCH v2 0/4] clk: Add basic register clock controller David Yang
2023-04-16 17:32 ` David Yang [this message]
2023-04-16 17:38 ` [PATCH v2 1/4] dt-bindings: clock: Add simple-clock-controller Krzysztof Kozlowski
2023-04-16 18:22 ` Yangfl
2023-04-16 18:27 ` Krzysztof Kozlowski
2023-04-17 18:08 ` Yangfl
2023-04-16 17:32 ` [PATCH v2 2/4] clk: Add simple clock controller David Yang
2023-04-16 17:33 ` [PATCH v2 3/4] dt-bindings: clock: Add gate-clock David Yang
2023-04-16 17:41 ` Krzysztof Kozlowski
2023-04-16 18:28 ` Yangfl
2023-04-16 18:31 ` Krzysztof Kozlowski
2023-04-16 17:33 ` [PATCH v2 4/4] clk: gate: Add DT binding David Yang
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=20230416173302.1185683-2-mmyangfl@gmail.com \
--to=mmyangfl@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sboyd@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