From: Rob Herring <robh@kernel.org>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Nishanth Menon <nm@ti.com>,
Tero Kristo <t-kristo@ti.com>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] dt-bindings: clock: Add binding documentation for TI syscon gate clock
Date: Thu, 28 Mar 2019 07:31:42 -0500 [thread overview]
Message-ID: <20190328123142.GA6229@bogus> (raw)
In-Reply-To: <20190312090518.28666-2-vigneshr@ti.com>
On Tue, Mar 12, 2019 at 02:35:17PM +0530, Vignesh Raghavendra wrote:
> Add dt bindings for TI syscon gate clock.
>
> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
> ---
> .../bindings/clock/ti,syscon-gate-clock.txt | 35 +++++++++++++++++++
> 1 file changed, 35 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/ti,syscon-gate-clock.txt
>
> diff --git a/Documentation/devicetree/bindings/clock/ti,syscon-gate-clock.txt b/Documentation/devicetree/bindings/clock/ti,syscon-gate-clock.txt
> new file mode 100644
> index 000000000000..f2bc4281ddba
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/ti,syscon-gate-clock.txt
> @@ -0,0 +1,35 @@
> +TI syscon gate clock
> +
> +The gate clock node must be provided inside a system controller node.
> +
> +Required:
> +- comaptible: Must be "ti,syscon-gate-clock"
> +- reg: Offset of register that controls the clock within syscon regmap
> +- ti,clock-bit-idx: bit index that control gate/ungating of clock
> +- clocks: phandle to the clock parent
> +- #clock-cells: must be <0>
> +
> +Example:
> + ctrlmmr_epwm_ctrl: syscon@104140{
> + compatible = "syscon", "simple-bus";
Can't be both of these...
> + reg = <0x0 0x104140 0x0 0x18>;
> + ranges = <0x0 0x0 0x104140>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + ehrpwm0_tbclk: clk@0 {
> + compatible = "ti,syscon-gate-clock";
> + reg = <0x0>;
> + #clock-cells = <0>;
> + clocks = <&k3_clks 40 0>;
> + ti,clock-bit-idx = <0>;
This would imply you have multiple nodes at one address which is
discouraged.
> + };
We generally don't describe clocks as 1 clock per node. Give the parent
a specific compatible and make it a clock provider.
> +
> + ehrpwm1_tbclk: clk@4 {
> + compatible = "ti,syscon-gate-clock";
> + reg = <0x4>;
> + #clock-cells = <0>;
> + clocks = <&k3_clks 41 0>;
> + ti,clock-bit-idx = <0>;
> + };
> + };
> --
> 2.21.0
>
next prev parent reply other threads:[~2019-03-28 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 9:05 [PATCH 0/2] clk: keystone: Add new driver to handle syscon based clock Vignesh Raghavendra
2019-03-12 9:05 ` [PATCH 1/2] dt-bindings: clock: Add binding documentation for TI syscon gate clock Vignesh Raghavendra
2019-03-28 12:31 ` Rob Herring [this message]
2019-04-03 9:30 ` Tero Kristo
2019-04-09 7:57 ` Vignesh Raghavendra
2019-03-12 9:05 ` [PATCH 2/2] clk: keystone: Add new driver to handle syscon based clock Vignesh Raghavendra
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=20190328123142.GA6229@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nm@ti.com \
--cc=sboyd@kernel.org \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.com \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).