From: Conor Dooley <conor@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH v2 1/3] dt-bindings: clock: versaclock3: Document clock-output-names
Date: Sat, 19 Aug 2023 09:30:58 +0100 [thread overview]
Message-ID: <20230819-starlit-vixen-ed35a46f065f@spud> (raw)
In-Reply-To: <20230817090810.203900-2-biju.das.jz@bp.renesas.com>
[-- Attachment #1: Type: text/plain, Size: 2712 bytes --]
On Thu, Aug 17, 2023 at 10:08:08AM +0100, Biju Das wrote:
> Document clock-output-names property and fix the "assigned-clock-rates"
> for each clock output in the example based on Table 3. ("Output Source")
> in the 5P35023 datasheet(ie: {REF,SE1,SE2,SE3,DIFF1,DIFF2}).
>
> While at it, replace clocks phandle in the example from x1_x2->x1 as
> X2 is a different 32768 kHz crystal.
>
> Suggested-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Closes: https://lore.kernel.org/all/CAMuHMdUHD+bEco=WYTYWsTAyRt3dTQQt4Xpaejss0Y2ZpLCMNg@mail.gmail.com/
> Fixes: a03d23f860eb ("dt-bindings: clock: Add Renesas versa3 clock generator bindings")
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
> ---
> v1->v2:
> * Updated commit description to make it clear it fixes
> "assigned-clock-rates" in the example based on 5P35023 datasheet.
> ---
> .../devicetree/bindings/clock/renesas,5p35023.yaml | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/clock/renesas,5p35023.yaml b/Documentation/devicetree/bindings/clock/renesas,5p35023.yaml
> index 839648e753d4..db8d01b291dd 100644
> --- a/Documentation/devicetree/bindings/clock/renesas,5p35023.yaml
> +++ b/Documentation/devicetree/bindings/clock/renesas,5p35023.yaml
> @@ -49,6 +49,9 @@ properties:
> $ref: /schemas/types.yaml#/definitions/uint8-array
> maxItems: 37
>
> + clock-output-names:
> + maxItems: 6
> +
> required:
> - compatible
> - reg
> @@ -68,7 +71,7 @@ examples:
> reg = <0x68>;
> #clock-cells = <1>;
>
> - clocks = <&x1_x2>;
> + clocks = <&x1>;
>
> renesas,settings = [
> 80 00 11 19 4c 02 23 7f 83 19 08 a9 5f 25 24 bf
> @@ -76,11 +79,14 @@ examples:
> 80 b0 45 c4 95
> ];
>
> + clock-output-names = "ref", "se1", "se2", "se3",
> + "diff1", "diff2";
> +
> assigned-clocks = <&versa3 0>, <&versa3 1>,
> <&versa3 2>, <&versa3 3>,
> <&versa3 4>, <&versa3 5>;
> - assigned-clock-rates = <12288000>, <25000000>,
> - <12000000>, <11289600>,
> - <11289600>, <24000000>;
> + assigned-clock-rates = <24000000>, <11289600>,
> + <11289600>, <12000000>,
> + <25000000>, <12288000>;
> };
> };
> --
> 2.25.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-08-19 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 9:08 [PATCH v2 0/3] Fix Versa3 clock mapping Biju Das
2023-08-17 9:08 ` [PATCH v2 1/3] dt-bindings: clock: versaclock3: Document clock-output-names Biju Das
2023-08-19 8:30 ` Conor Dooley [this message]
2023-08-21 8:00 ` Geert Uytterhoeven
2023-08-21 8:10 ` Biju Das
2023-08-21 8:32 ` Geert Uytterhoeven
2023-08-17 9:08 ` [PATCH v2 3/3] arm64: dts: renesas: rz-smarc-common: Use versa3 clk for audio mclk Biju Das
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=20230819-starlit-vixen-ed35a46f065f@spud \
--to=conor@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mturquette@baylibre.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--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;
as well as URLs for NNTP newsgroup(s).