From: Rob Herring <robh@kernel.org>
To: Vyacheslav Yurkov <V.Yurkov.EXT@bruker.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org,
Vyacheslav Yurkov <uvv.mail@gmail.com>
Subject: Re: [PATCH 2/2] dt-bindings: Add clock guard DT description
Date: Wed, 18 Mar 2026 17:55:10 -0500 [thread overview]
Message-ID: <20260318225510.GA639444-robh@kernel.org> (raw)
In-Reply-To: <20260318-feature-clock-guard-v1-2-6137cb4084b7@bruker.com>
On Wed, Mar 18, 2026 at 05:43:40PM +0000, Vyacheslav Yurkov wrote:
> Describe device tree binding for virtual clock controller guard.
No idea what this means. Please explain how I would identify this h/w.
We generally don't do bindings for virtual devices and we don't do
single clock bindings (other than some we are stuck with).
>
> Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com>
> Signed-off-by: Vyacheslav Yurkov <V.Yurkov.EXT@bruker.com>
> ---
> .../bindings/clock/clock-controller-guard.yaml | 79 ++++++++++++++++++++++
> 1 file changed, 79 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/clock/clock-controller-guard.yaml b/Documentation/devicetree/bindings/clock/clock-controller-guard.yaml
> new file mode 100644
> index 000000000000..71c2d80de1f0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/clock-controller-guard.yaml
> @@ -0,0 +1,79 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/clock/clock-controller-guard.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: Clock Controller Guard
> +
> +maintainers:
> + - Vyacheslav Yurkov <V.Yurkov.EXT@bruker.com>
> +
> +description: |
> + Clock controller that guards upstream clocks and/or GPIO
> + signals and exposes them as a single clock output.
> +
> +properties:
> + compatible:
> + const: clock-controller-guard
> +
> + "#clock-cells":
> + const: 1
> +
> + clocks:
> + description: Input clocks that will be guarded.
> + minItems: 0
> +
> + clock-names: Input clock names.
> + minItems: 0
> +
> + clock-output-names:
> + description: Names of the clock provided by this controller.
> + minItems: 1
> + items:
> + type: string
> +
> + gpios:
> + description: |
> + GPIOs used to control or guard the clocks.
> + minItems: 0
> + maxItems: 32
> +
> + gpio-names:
> + description: Names corresponding to each GPIO.
> + minItems: 0
> + maxItems: 32
> +
> + items:
> + type: string
> +
> +required:
> + - compatible
> + - "#clock-cells"
> +anyOf:
> + - required:
> + - clocks
> + - required:
> + - gpios
> +dependencies:
> + gpio-names: [gpios]
> + clock-names: [clocks]
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + clkctrl: clock-controller {
> + compatible = "clock-controller-guard";
> + #clock-cells = <1>;
> +
> + clocks = <&clk0 0>, <&pll 0>;
> +
> + gpios = <&gpio0 4 GPIO_ACTIVE_HIGH>,
> + <&gpio0 5 GPIO_ACTIVE_HIGH>,
> + <&gpio1 2 GPIO_ACTIVE_LOW>;
> +
> + gpio-names = "gpio0", "gpio1", "gpio2";
> +
> + clock-output-names = "clkout0";
> + };
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2026-03-18 22:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 17:43 [PATCH 0/2] A proposal to add a virtual clock controller guard Vyacheslav Yurkov via B4 Relay
2026-03-18 17:43 ` [PATCH 1/2] clk: Add " Vyacheslav Yurkov via B4 Relay
2026-03-19 8:15 ` kernel test robot
2026-03-18 17:43 ` [PATCH 2/2] dt-bindings: Add clock guard DT description Vyacheslav Yurkov via B4 Relay
2026-03-18 19:33 ` Rob Herring (Arm)
2026-03-18 22:55 ` Rob Herring [this message]
2026-03-19 5:50 ` Vyacheslav Yurkov
2026-03-19 16:50 ` Conor Dooley
2026-03-23 13:52 ` Vyacheslav Yurkov
2026-03-23 20:14 ` Conor Dooley
2026-03-26 9:54 ` Vyacheslav Yurkov
2026-03-26 10:08 ` Krzysztof Kozlowski
2026-03-26 13:39 ` Vyacheslav Yurkov
2026-03-26 13:49 ` Krzysztof Kozlowski
2026-03-26 18:32 ` Conor Dooley
2026-03-28 2:58 ` Vyacheslav Yurkov
2026-03-26 10:44 ` Conor Dooley
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=20260318225510.GA639444-robh@kernel.org \
--to=robh@kernel.org \
--cc=V.Yurkov.EXT@bruker.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=uvv.mail@gmail.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