From: nsekhar@ti•com (Sekhar Nori)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3 2/3] arm: davinci: clock node support for ECAP & EHRPWM
Date: Tue, 2 Apr 2013 13:46:05 +0530 [thread overview]
Message-ID: <515A93C5.4040009@ti.com> (raw)
In-Reply-To: <1364197789-16783-3-git-send-email-avinashphilip@ti.com>
On 3/25/2013 1:19 PM, Philip Avinash wrote:
> Add clock node support for ECAP and EHRPWM modules.
> Also adds TBCLK for EHRWPM TBCLK to comply with pwm-tiehrpwm
> driver.
>
> Signed-off-by: Philip Avinash <avinashphilip@ti•com>
Queuing this for v3.10
Thanks,
Sekhar
next prev parent reply other threads:[~2013-04-02 8:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 7:49 [PATCH v3 0/3] Platform support for EHRPWM & ECAP devices in DAVINCI Philip Avinash
2013-03-25 7:49 ` [PATCH v3 2/3] arm: davinci: clock node support for ECAP & EHRPWM Philip Avinash
2013-04-02 8:16 ` Sekhar Nori [this message]
2013-03-25 7:49 ` [PATCH v3 3/3] ARM: davinci: da850: add EHRPWM & ECAP DT node Philip Avinash
2013-04-02 8:33 ` Sekhar Nori
2013-04-08 9:09 ` Philip, Avinash
2013-04-08 13:09 ` Sekhar Nori
2013-04-09 8:42 ` Philip, Avinash
2013-04-09 11:35 ` Sekhar Nori
2013-04-10 5:30 ` Philip, Avinash
2013-04-10 5:55 ` Sekhar Nori
2013-04-10 6:07 ` Philip, Avinash
2013-03-25 8:14 ` [PATCH v3 0/3] Platform support for EHRPWM & ECAP devices in DAVINCI Sekhar Nori
2013-03-25 8:30 ` Philip, Avinash
2013-03-25 9:37 ` [PATCH v3 1/3] ARM: davinci: clk framework support for enable/disable functionality Philip Avinash
2013-04-01 11:35 ` Sekhar Nori
2013-04-03 3:58 ` Philip, Avinash
2013-04-02 8:35 ` [PATCH v3 0/3] Platform support for EHRPWM & ECAP devices in DAVINCI Sekhar Nori
2013-04-04 4:39 ` Philip, Avinash
2013-04-04 5:49 ` Sekhar Nori
2013-04-04 6:38 ` Philip, Avinash
2013-04-04 10:10 ` Philip, Avinash
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=515A93C5.4040009@ti.com \
--to=nsekhar@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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