From: Rob Herring <robh@kernel.org>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: Mailing List <devicetree-spec@vger.kernel.org>,
devicetree@vger.kernel.org, Stephen Boyd <sboyd@kernel.org>
Subject: Re: [dtschema PATCH] schemas: clock: Add example for 'clock-indices'
Date: Mon, 6 Jun 2022 15:04:45 -0500 [thread overview]
Message-ID: <CAL_JsqK4Z0QBowJrFWbWPyfWZyxqNtDV7_QwfubNYCCuMPVkUQ@mail.gmail.com> (raw)
In-Reply-To: <20220428152719.2263164-1-robh@kernel.org>
On Thu, Apr 28, 2022 at 10:27 AM Rob Herring <robh@kernel.org> wrote:
>
> Add description for assigned-clocks properties from clock-binding.txt in
> the Linux kernel.
>
> This is relicensed from GPL-2.0 (the default) to BSD-2-Clause. The Cc list
> are the original authors.
>
> Cc: Ben Dooks <ben.dooks@codethink.co.uk>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> Please ack the license change.
Ben, need your ack on this please.
>
> dtschema/schemas/clock/clock.yaml | 18 +++++++++++++++---
> 1 file changed, 15 insertions(+), 3 deletions(-)
>
> diff --git a/dtschema/schemas/clock/clock.yaml b/dtschema/schemas/clock/clock.yaml
> index 5299653b80b6..433a858ef31e 100644
> --- a/dtschema/schemas/clock/clock.yaml
> +++ b/dtschema/schemas/clock/clock.yaml
> @@ -94,9 +94,21 @@ properties:
>
> clock-indices:
> $ref: "/schemas/types.yaml#/definitions/uint32-array"
> - description: If the identifying number for the clocks in the node
> - is not linear from zero, then this allows the mapping of identifiers
> - into the clock-output-names array.
> + description: |
> + If the identifying number for the clocks in the node is not linear from
> + zero, then this allows the mapping of identifiers into the
> + clock-output-names array.
> +
> + For example, if we have two clocks <&oscillator 1> and <&oscillator 3>:
> +
> + oscillator {
> + compatible = "myclocktype";
> + #clock-cells = <1>;
> + clock-indices = <1>, <3>;
> + clock-output-names = "clka", "clkb";
> + }
> +
> + This ensures we do not have any empty strings in clock-output-names
>
> # Consumer properties
> clocks:
> --
> 2.34.1
>
prev parent reply other threads:[~2022-06-06 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 15:27 [dtschema PATCH] schemas: clock: Add example for 'clock-indices' Rob Herring
2022-05-19 23:17 ` Stephen Boyd
2022-06-06 20:04 ` Rob Herring [this message]
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=CAL_JsqK4Z0QBowJrFWbWPyfWZyxqNtDV7_QwfubNYCCuMPVkUQ@mail.gmail.com \
--to=robh@kernel.org \
--cc=ben.dooks@codethink.co.uk \
--cc=devicetree-spec@vger.kernel.org \
--cc=devicetree@vger.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;
as well as URLs for NNTP newsgroup(s).