From: Mike Turquette <mturquette@linaro.org>
To: Tero Kristo <t-kristo@ti.com>
Cc: Sourav Poddar <sourav.poddar@ti.com>,
Tony Lindgren <tony@atomide.com>,
devicetree <devicetree@vger.kernel.org>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Felipe Balbi <balbi@ti.com>
Subject: Re: [PATCHv3] arm: dts: am43x-clock: add tbclk data for ehrpwm.
Date: Wed, 28 May 2014 12:15:40 -0700 [thread overview]
Message-ID: <CAPtuhTi59cJSj-_oa49stWzWUsCykk6NMQLVGHeMjj60TniXXg@mail.gmail.com> (raw)
In-Reply-To: <537A0536.1030506@ti.com>
On Mon, May 19, 2014 at 6:20 AM, Tero Kristo <t-kristo@ti.com> wrote:
> On 05/05/2014 10:49 AM, Tero Kristo wrote:
>>
>> On 05/01/2014 10:00 PM, Mike Turquette wrote:
>>>
>>> Quoting Tero Kristo (2014-04-29 07:51:14)
>>>>
>>>> On 04/29/2014 05:15 PM, Sourav Poddar wrote:
>>>>>
>>>>> We need "tbclk" 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>
>>>>
>>>>
>>>> Acked-by: Tero Kristo <t-kristo@ti.com>
>>>
>>>
>>> Looks good to me.
>>>
>>> Tero, just to be clear, are you planning on batching up OMAPish clock
>>> patches and sending a pull request (once they have been reviewed on the
>>> list)?
>>
>>
>> No, I haven't been planning on sending a pull-req, as I believe you
>> still want to ack the TI related clock driver patches yourself also. If
>> you want to change the setup I am of course willing to negotiate the
>> terms. :)
>>
>> -Tero
>
>
> So, based on our discussions, this is now queued for 3.15-rc/clk-dt.
I don't want to cross threads, so we'll work out the details of the
for-3.16 stuff in the "Pending clock and hwmod patches" thread.
However, after this next merge window I am happy to move to a pull
request-based model for OMAP clock patches, since things should slowly
start to settle down.
Regards,
Mike
>
>
> -Tero
>
>>
>>>
>>> Thanks,
>>> Mike
>>>
>>>>
>>>>
>>>>> ---
>>>>> v2->v3
>>>>> - correct bitshifting
>>>>>
>>>>> arch/arm/boot/dts/am43xx-clocks.dtsi | 48
>>>>> ++++++++++++++++++++++++++++++++++
>>>>> drivers/clk/ti/clk-43xx.c | 6 +++++
>>>>> 2 files changed, 54 insertions(+)
>>>>>
>>>>> diff --git a/arch/arm/boot/dts/am43xx-clocks.dtsi
>>>>> b/arch/arm/boot/dts/am43xx-clocks.dtsi
>>>>> index 142009c..42d7b1f 100644
>>>>> --- a/arch/arm/boot/dts/am43xx-clocks.dtsi
>>>>> +++ b/arch/arm/boot/dts/am43xx-clocks.dtsi
>>>>> @@ -87,6 +87,54 @@
>>>>> clock-mult = <1>;
>>>>> clock-div = <1>;
>>>>> };
>>>>> +
>>>>> + ehrpwm0_tbclk: ehrpwm0_tbclk {
>>>>> + #clock-cells = <0>;
>>>>> + compatible = "ti,gate-clock";
>>>>> + clocks = <&dpll_per_m2_ck>;
>>>>> + ti,bit-shift = <0>;
>>>>> + reg = <0x0664>;
>>>>> + };
>>>>> +
>>>>> + ehrpwm1_tbclk: ehrpwm1_tbclk {
>>>>> + #clock-cells = <0>;
>>>>> + compatible = "ti,gate-clock";
>>>>> + clocks = <&dpll_per_m2_ck>;
>>>>> + ti,bit-shift = <1>;
>>>>> + reg = <0x0664>;
>>>>> + };
>>>>> +
>>>>> + ehrpwm2_tbclk: ehrpwm2_tbclk {
>>>>> + #clock-cells = <0>;
>>>>> + compatible = "ti,gate-clock";
>>>>> + clocks = <&dpll_per_m2_ck>;
>>>>> + ti,bit-shift = <2>;
>>>>> + reg = <0x0664>;
>>>>> + };
>>>>> +
>>>>> + ehrpwm3_tbclk: ehrpwm3_tbclk {
>>>>> + #clock-cells = <0>;
>>>>> + compatible = "ti,gate-clock";
>>>>> + clocks = <&dpll_per_m2_ck>;
>>>>> + ti,bit-shift = <4>;
>>>>> + reg = <0x0664>;
>>>>> + };
>>>>> +
>>>>> + ehrpwm4_tbclk: ehrpwm4_tbclk {
>>>>> + #clock-cells = <0>;
>>>>> + compatible = "ti,gate-clock";
>>>>> + clocks = <&dpll_per_m2_ck>;
>>>>> + ti,bit-shift = <5>;
>>>>> + reg = <0x0664>;
>>>>> + };
>>>>> +
>>>>> + ehrpwm5_tbclk: ehrpwm5_tbclk {
>>>>> + #clock-cells = <0>;
>>>>> + compatible = "ti,gate-clock";
>>>>> + clocks = <&dpll_per_m2_ck>;
>>>>> + ti,bit-shift = <6>;
>>>>> + reg = <0x0664>;
>>>>> + };
>>>>> };
>>>>> &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..527a43d 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", "ehrpwm3_tbclk"),
>>>>> + DT_CLK("48308200.ehrpwm", "tbclk", "ehrpwm4_tbclk"),
>>>>> + DT_CLK("4830a200.ehrpwm", "tbclk", "ehrpwm5_tbclk"),
>>>>> { .node_name = NULL },
>>>>> };
>>>>>
>>>>>
>>>>
>>
>
prev parent reply other threads:[~2014-05-28 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 14:15 [PATCHv3] arm: dts: am43x-clock: add tbclk data for ehrpwm Sourav Poddar
2014-04-29 14:51 ` Tero Kristo
2014-05-01 19:00 ` Mike Turquette
2014-05-05 7:49 ` Tero Kristo
2014-05-19 13:20 ` Tero Kristo
2014-05-28 19:15 ` Mike Turquette [this message]
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=CAPtuhTi59cJSj-_oa49stWzWUsCykk6NMQLVGHeMjj60TniXXg@mail.gmail.com \
--to=mturquette@linaro.org \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sourav.poddar@ti.com \
--cc=t-kristo@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).