From: Rob Herring <robh@kernel.org>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/5] dt-bindings: clock: uniphier: Add clock binding for SoC-glue
Date: Wed, 6 Oct 2021 14:49:56 -0500 [thread overview]
Message-ID: <YV395BTH/gqcuDJH@robh.at.kernel.org> (raw)
In-Reply-To: <1633518555-8195-5-git-send-email-hayashi.kunihiko@socionext.com>
On Wed, Oct 06, 2021 at 08:09:14PM +0900, Kunihiko Hayashi wrote:
> Update binding document for clocks implemented in SoC-glue.
>
> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
> ---
> .../bindings/clock/socionext,uniphier-clock.yaml | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/clock/socionext,uniphier-clock.yaml b/Documentation/devicetree/bindings/clock/socionext,uniphier-clock.yaml
> index ee8d16a8019e..05a9d1f89756 100644
> --- a/Documentation/devicetree/bindings/clock/socionext,uniphier-clock.yaml
> +++ b/Documentation/devicetree/bindings/clock/socionext,uniphier-clock.yaml
> @@ -46,6 +46,9 @@ properties:
> - socionext,uniphier-ld20-peri-clock
> - socionext,uniphier-pxs3-peri-clock
> - socionext,uniphier-nx1-peri-clock
> + - description: SoC-glue clock
> + enum:
> + - socionext,uniphier-pro4-sg-clock
>
> "#clock-cells":
> const: 1
> @@ -95,3 +98,16 @@ examples:
>
> // other nodes ...
> };
> +
> + - |
> + soc-glue@5f800000 {
> + compatible = "socionext,uniphier-sysctrl", "simple-mfd", "syscon";
> + reg = <0x5f800000 0x2000>;
> +
> + clock {
> + compatible = "socionext,uniphier-pro4-sg-clock";
> + #clock-cells = <1>;
> + };
> +
> + // other nodes ...
> + };
What's the value of this 2nd example? It's just a different compatible
string.
> --
> 2.7.4
>
>
next prev parent reply other threads:[~2021-10-06 19:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 11:09 [PATCH v2 0/5] clk: uniphier: Introduce some clock features and NX1 support Kunihiko Hayashi
2021-10-06 11:09 ` [PATCH v2 1/5] clk: uniphier: Add audio system and video input clock control for PXs3 Kunihiko Hayashi
2021-10-06 11:09 ` [PATCH v2 2/5] dt-bindings: clock: uniphier: Add NX1 clock binding Kunihiko Hayashi
2021-10-06 11:09 ` [PATCH v2 3/5] clk: uniphier: Add NX1 clock support Kunihiko Hayashi
2021-10-06 11:09 ` [PATCH v2 4/5] dt-bindings: clock: uniphier: Add clock binding for SoC-glue Kunihiko Hayashi
2021-10-06 19:08 ` Rob Herring
2021-10-06 19:49 ` Rob Herring [this message]
2021-10-07 8:50 ` Kunihiko Hayashi
2021-10-08 19:20 ` Rob Herring
2021-10-10 23:55 ` Kunihiko Hayashi
2021-10-06 11:09 ` [PATCH v2 5/5] clk: uniphier: Add SoC-glue clock source selector support for Pro4 Kunihiko Hayashi
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=YV395BTH/gqcuDJH@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mturquette@baylibre.com \
--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).