From: Rob Herring <robh@kernel.org> To: Tero Kristo <t-kristo@ti.com> Cc: linux-clk@vger.kernel.org, mturquette@baylibre.com, sboyd@codeaurora.org, ssantosh@kernel.org, nm@ti.com, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org Subject: Re: [PATCH 1/3] Documentation: dt: Add TI SCI clock driver Date: Sun, 30 Oct 2016 15:41:21 -0500 [thread overview] Message-ID: <20161030204121.qvb5d33dh65awwzx@rob-hp-laptop> (raw) In-Reply-To: <1477053961-27128-2-git-send-email-t-kristo@ti.com> On Fri, Oct 21, 2016 at 03:45:59PM +0300, Tero Kristo wrote: > Add a clock implementation, TI SCI clock, that will hook to the common > clock framework, and allow each clock to be controlled via TI SCI > protocol. > > Signed-off-by: Tero Kristo <t-kristo@ti.com> > --- > .../devicetree/bindings/clock/ti,sci-clk.txt | 37 ++++++++++++++++++++++ > MAINTAINERS | 1 + > 2 files changed, 38 insertions(+) > create mode 100644 Documentation/devicetree/bindings/clock/ti,sci-clk.txt > > diff --git a/Documentation/devicetree/bindings/clock/ti,sci-clk.txt b/Documentation/devicetree/bindings/clock/ti,sci-clk.txt > new file mode 100644 > index 0000000..bfc3ca4 > --- /dev/null > +++ b/Documentation/devicetree/bindings/clock/ti,sci-clk.txt > @@ -0,0 +1,37 @@ > +Texas Instruments TI-SCI Clocks > +=============================== > + > +All clocks on Texas Instruments' SoCs that contain a System Controller, > +are only controlled by this entity. Communication between a host processor > +running an OS and the System Controller happens through a protocol known > +as TI-SCI[1]. This clock implementation plugs into the common clock > +framework and makes use of the TI-SCI protocol on clock API requests. > + > +[1] Documentation/devicetree/bindings/arm/keystone/ti,sci.txt > + > +Required properties: > +------------------- > +- compatible: Must be "ti,k2g-sci-clk" > +- #clock-cells: Shall be 2. > + In clock consumers, this cell represents the device ID and clock ID > + exposed by the PM firmware. The assignments can be found in the header > + files <dt-bindings/genpd/<soc>.h> (which covers the device IDs) and > + <dt-bindings/clock/<soc>.h> (which covers the clock IDs), where <soc> > + is the SoC involved, for example 'k2g'. > + > +Examples: > +-------- > + > +pmmc: pmmc { > + compatible = "ti,k2g-sci"; > + > + k2g_clks: k2g_clks { Use "clocks" for node name instead. > + compatible = "ti,k2g-sci-clk"; I'm starting to think all these child nodes for SCI are pointless. Is there any reason why the parent node can't be the clock provider (along with all the other providers it acks as)? > + #clock-cells = <2>; > + }; > +}; > + > +uart0: serial@2530c00 { > + compatible = "ns16550a"; > + clocks = <&k2g_clks K2G_DEV_UART0 0>; > +};
WARNING: multiple messages have this Message-ID (diff)
From: robh@kernel.org (Rob Herring) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/3] Documentation: dt: Add TI SCI clock driver Date: Sun, 30 Oct 2016 15:41:21 -0500 [thread overview] Message-ID: <20161030204121.qvb5d33dh65awwzx@rob-hp-laptop> (raw) In-Reply-To: <1477053961-27128-2-git-send-email-t-kristo@ti.com> On Fri, Oct 21, 2016 at 03:45:59PM +0300, Tero Kristo wrote: > Add a clock implementation, TI SCI clock, that will hook to the common > clock framework, and allow each clock to be controlled via TI SCI > protocol. > > Signed-off-by: Tero Kristo <t-kristo@ti.com> > --- > .../devicetree/bindings/clock/ti,sci-clk.txt | 37 ++++++++++++++++++++++ > MAINTAINERS | 1 + > 2 files changed, 38 insertions(+) > create mode 100644 Documentation/devicetree/bindings/clock/ti,sci-clk.txt > > diff --git a/Documentation/devicetree/bindings/clock/ti,sci-clk.txt b/Documentation/devicetree/bindings/clock/ti,sci-clk.txt > new file mode 100644 > index 0000000..bfc3ca4 > --- /dev/null > +++ b/Documentation/devicetree/bindings/clock/ti,sci-clk.txt > @@ -0,0 +1,37 @@ > +Texas Instruments TI-SCI Clocks > +=============================== > + > +All clocks on Texas Instruments' SoCs that contain a System Controller, > +are only controlled by this entity. Communication between a host processor > +running an OS and the System Controller happens through a protocol known > +as TI-SCI[1]. This clock implementation plugs into the common clock > +framework and makes use of the TI-SCI protocol on clock API requests. > + > +[1] Documentation/devicetree/bindings/arm/keystone/ti,sci.txt > + > +Required properties: > +------------------- > +- compatible: Must be "ti,k2g-sci-clk" > +- #clock-cells: Shall be 2. > + In clock consumers, this cell represents the device ID and clock ID > + exposed by the PM firmware. The assignments can be found in the header > + files <dt-bindings/genpd/<soc>.h> (which covers the device IDs) and > + <dt-bindings/clock/<soc>.h> (which covers the clock IDs), where <soc> > + is the SoC involved, for example 'k2g'. > + > +Examples: > +-------- > + > +pmmc: pmmc { > + compatible = "ti,k2g-sci"; > + > + k2g_clks: k2g_clks { Use "clocks" for node name instead. > + compatible = "ti,k2g-sci-clk"; I'm starting to think all these child nodes for SCI are pointless. Is there any reason why the parent node can't be the clock provider (along with all the other providers it acks as)? > + #clock-cells = <2>; > + }; > +}; > + > +uart0: serial at 2530c00 { > + compatible = "ns16550a"; > + clocks = <&k2g_clks K2G_DEV_UART0 0>; > +};
next prev parent reply other threads:[~2016-10-30 20:41 UTC|newest] Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-10-21 12:45 [PATCH 0/3] clk: keystone: add sci clock support Tero Kristo 2016-10-21 12:45 ` Tero Kristo 2016-10-21 12:45 ` Tero Kristo 2016-10-21 12:45 ` [PATCH 1/3] Documentation: dt: Add TI SCI clock driver Tero Kristo 2016-10-21 12:45 ` Tero Kristo 2016-10-21 12:45 ` Tero Kristo 2016-10-30 20:41 ` Rob Herring [this message] 2016-10-30 20:41 ` Rob Herring 2016-10-31 12:50 ` Tero Kristo 2016-10-31 12:50 ` Tero Kristo 2016-10-31 12:50 ` Tero Kristo 2016-10-31 20:34 ` Nishanth Menon 2016-10-31 20:34 ` Nishanth Menon 2016-10-31 20:34 ` Nishanth Menon 2016-11-18 17:20 ` Rob Herring 2016-11-18 17:20 ` Rob Herring [not found] ` <CAL_JsqLtSs6ifnMdEOsfXpGoWnmXuGAx83+ziB9yU+zurvob+A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2016-11-21 8:14 ` Tero Kristo 2016-11-21 8:14 ` Tero Kristo 2016-11-21 8:14 ` Tero Kristo 2016-12-02 8:19 ` Tero Kristo 2016-12-02 8:19 ` Tero Kristo 2016-12-02 18:45 ` Rob Herring 2016-12-02 18:45 ` Rob Herring 2016-12-02 18:58 ` Stephen Boyd 2016-12-02 18:58 ` Stephen Boyd [not found] ` <5f146fb6-ec88-b7ee-ef5b-a5ad32c54a74-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2016-12-02 21:07 ` Tero Kristo 2016-12-02 21:07 ` Tero Kristo 2016-12-02 21:07 ` Tero Kristo 2016-10-21 12:46 ` [PATCH 2/3] dt-binding: clock: Add k2g clock definitions Tero Kristo 2016-10-21 12:46 ` Tero Kristo 2016-10-21 12:46 ` Tero Kristo 2017-05-16 15:03 ` Tero Kristo 2017-05-16 15:03 ` Tero Kristo 2016-10-21 12:46 ` [PATCH 3/3] clk: keystone: Add sci-clk driver support Tero Kristo 2016-10-21 12:46 ` Tero Kristo 2016-10-21 12:46 ` Tero Kristo 2016-12-08 0:13 ` Stephen Boyd 2016-12-08 0:13 ` Stephen Boyd 2016-12-08 10:45 ` Tero Kristo 2016-12-08 10:45 ` Tero Kristo 2016-12-08 10:45 ` Tero Kristo 2016-12-08 21:10 ` Stephen Boyd 2016-12-08 21:10 ` Stephen Boyd [not found] ` <20161208211044.GI5423-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2016-12-09 8:05 ` Tero Kristo 2016-12-09 8:05 ` Tero Kristo 2016-12-09 8:05 ` Tero Kristo 2016-12-12 19:38 ` Stephen Boyd 2016-12-12 19:38 ` Stephen Boyd [not found] ` <20161212193800.GL5423-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2016-12-13 9:01 ` Tero Kristo 2016-12-13 9:01 ` Tero Kristo 2016-12-13 9:01 ` Tero Kristo -- strict thread matches above, loose matches on Subject: below -- 2016-08-20 0:33 [PATCH 0/3] ARM: K2G: Add support for TI-SCI Clocks Nishanth Menon 2016-08-20 0:33 ` [PATCH 1/3] Documentation: dt: Add TI SCI clock driver Nishanth Menon 2016-08-20 0:33 ` Nishanth Menon 2016-08-20 0:33 ` Nishanth Menon
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=20161030204121.qvb5d33dh65awwzx@rob-hp-laptop \ --to=robh@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-clk@vger.kernel.org \ --cc=mturquette@baylibre.com \ --cc=nm@ti.com \ --cc=sboyd@codeaurora.org \ --cc=ssantosh@kernel.org \ --cc=t-kristo@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.