From: Tero Kristo <t-kristo@ti.com>
To: Sourav Poddar <sourav.poddar@ti.com>,
mturquette@linaro.org, tony@atomide.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org, balbi@ti.com
Subject: Re: [PATCH] arm: dts: am43x-clock: add tbclk data for ehrpwm.
Date: Tue, 22 Apr 2014 15:41:24 +0300 [thread overview]
Message-ID: <53566374.3070609@ti.com> (raw)
In-Reply-To: <1398162345-3163-1-git-send-email-sourav.poddar@ti.com>
On 04/22/2014 01:25 PM, Sourav Poddar wrote:
> We need "tblclk" clock data for the functioning of ehrpwm
> module. Hence, populating the required clock information
> in clock dts file.
>
> Signed-off-by: Sourav Poddar <sourav.poddar@ti.com>
> ---
> arch/arm/boot/dts/am43xx-clocks.dtsi | 84 ++++++++++++++++++++++++++++++++++
> drivers/clk/ti/clk-43xx.c | 6 +++
> 2 files changed, 90 insertions(+)
>
> diff --git a/arch/arm/boot/dts/am43xx-clocks.dtsi b/arch/arm/boot/dts/am43xx-clocks.dtsi
> index 142009c..869f9a5 100644
> --- a/arch/arm/boot/dts/am43xx-clocks.dtsi
> +++ b/arch/arm/boot/dts/am43xx-clocks.dtsi
> @@ -87,6 +87,90 @@
> clock-mult = <1>;
> clock-div = <1>;
> };
> +
> + ehrpwm0_gate_tbclk: ehrpwm0_gate_tbclk {
> + #clock-cells = <0>;
> + compatible = "ti,composite-no-wait-gate-clock";
> + clocks = <&dpll_per_m2_ck>;
> + ti,bit-shift = <0>;
> + reg = <0x0664>;
> + };
> +
> + ehrpwm0_tbclk: ehrpwm0_tbclk {
> + #clock-cells = <0>;
> + compatible = "ti,composite-clock";
> + clocks = <&ehrpwm0_gate_tbclk>;
> + };
Why do you use composite-clock type here? I see only add one sub-clock
to the composite, thus the composite part is unused. How about using a
gate-clock type only? Same question applies for the rest of the patch also.
-Tero
> +
> + ehrpwm1_gate_tbclk: ehrpwm1_gate_tbclk {
> + #clock-cells = <0>;
> + compatible = "ti,composite-no-wait-gate-clock";
> + clocks = <&dpll_per_m2_ck>;
> + ti,bit-shift = <1>;
> + reg = <0x0664>;
> + };
> +
> + ehrpwm1_tbclk: ehrpwm1_tbclk {
> + #clock-cells = <0>;
> + compatible = "ti,composite-clock";
> + clocks = <&ehrpwm1_gate_tbclk>;
> + };
> +
> + ehrpwm2_gate_tbclk: ehrpwm2_gate_tbclk {
> + #clock-cells = <0>;
> + compatible = "ti,composite-no-wait-gate-clock";
> + clocks = <&dpll_per_m2_ck>;
> + ti,bit-shift = <2>;
> + reg = <0x0664>;
> + };
> +
> + ehrpwm2_tbclk: ehrpwm2_tbclk {
> + #clock-cells = <0>;
> + compatible = "ti,composite-clock";
> + clocks = <&ehrpwm2_gate_tbclk>;
> + };
> +
> + ehrpwm3_gate_tbclk: ehrpwm3_gate_tbclk {
> + #clock-cells = <0>;
> + compatible = "ti,composite-no-wait-gate-clock";
> + clocks = <&dpll_per_m2_ck>;
> + ti,bit-shift = <2>;
> + reg = <0x0664>;
> + };
> +
> + ehrpwm3_tbclk: ehrpwm3_tbclk {
> + #clock-cells = <0>;
> + compatible = "ti,composite-clock";
> + clocks = <&ehrpwm3_gate_tbclk>;
> + };
> +
> + ehrpwm4_gate_tbclk: ehrpwm4_gate_tbclk {
> + #clock-cells = <0>;
> + compatible = "ti,composite-no-wait-gate-clock";
> + clocks = <&dpll_per_m2_ck>;
> + ti,bit-shift = <2>;
> + reg = <0x0664>;
> + };
> +
> + ehrpwm4_tbclk: ehrpwm4_tbclk {
> + #clock-cells = <0>;
> + compatible = "ti,composite-clock";
> + clocks = <&ehrpwm4_gate_tbclk>;
> + };
> +
> + ehrpwm5_gate_tbclk: ehrpwm5_gate_tbclk {
> + #clock-cells = <0>;
> + compatible = "ti,composite-no-wait-gate-clock";
> + clocks = <&dpll_per_m2_ck>;
> + ti,bit-shift = <2>;
> + reg = <0x0664>;
> + };
> +
> + ehrpwm5_tbclk: ehrpwm5_tbclk {
> + #clock-cells = <0>;
> + compatible = "ti,composite-clock";
> + clocks = <&ehrpwm5_gate_tbclk>;
> + };
> };
> &prcm_clocks {
> clk_32768_ck: clk_32768_ck {
> diff --git a/drivers/clk/ti/clk-43xx.c b/drivers/clk/ti/clk-43xx.c
> index 67c8de5..5413a6a 100644
> --- a/drivers/clk/ti/clk-43xx.c
> +++ b/drivers/clk/ti/clk-43xx.c
> @@ -105,6 +105,12 @@ static struct ti_dt_clk am43xx_clks[] = {
> DT_CLK(NULL, "func_12m_clk", "func_12m_clk"),
> DT_CLK(NULL, "vtp_clk_div", "vtp_clk_div"),
> DT_CLK(NULL, "usbphy_32khz_clkmux", "usbphy_32khz_clkmux"),
> + DT_CLK("48300200.ehrpwm", "tbclk", "ehrpwm0_tbclk"),
> + DT_CLK("48302200.ehrpwm", "tbclk", "ehrpwm1_tbclk"),
> + DT_CLK("48304200.ehrpwm", "tbclk", "ehrpwm2_tbclk"),
> + DT_CLK("48306200.ehrpwm", "tbclk", "ehrpwm0_tbclk"),
> + DT_CLK("48308200.ehrpwm", "tbclk", "ehrpwm1_tbclk"),
> + DT_CLK("4830a200.ehrpwm", "tbclk", "ehrpwm2_tbclk"),
> { .node_name = NULL },
> };
>
>
next prev parent reply other threads:[~2014-04-22 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 10:25 [PATCH] arm: dts: am43x-clock: add tbclk data for ehrpwm Sourav Poddar
2014-04-22 12:41 ` Tero Kristo [this message]
2014-04-25 5:42 ` sourav
2014-04-25 6:49 ` Tero Kristo
2014-04-25 6:51 ` sourav
-- strict thread matches above, loose matches on Subject: below --
2014-04-25 8:55 Sourav Poddar
2014-04-25 12:10 ` Tero Kristo
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=53566374.3070609@ti.com \
--to=t-kristo@ti.com \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=sourav.poddar@ti.com \
--cc=tony@atomide.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).