From: Jon Hunter <jon-hunter@ti.com>
To: Suman Anna <s-anna@ti.com>
Cc: Benoit Cousson <b-cousson@ti.com>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
device-tree <devicetree-discuss@lists.ozlabs.org>
Subject: Re: [PATCH 1/2] ARM: dts: OMAP5: add PWM capability to timer nodes missing it
Date: Wed, 17 Apr 2013 18:56:06 -0500 [thread overview]
Message-ID: <516F3696.9080008@ti.com> (raw)
In-Reply-To: <1366240995-53538-1-git-send-email-s-anna@ti.com>
On 04/17/2013 06:23 PM, Suman Anna wrote:
> OMAP5 has 6 timers (GPTimers 5, 6, 8 to 11) that are capable of PWM.
> The PWM capability property is missing from the node definitions of
> couple of timers, and this has been fixed.
>
> Signed-off-by: Suman Anna <s-anna@ti.com>
> ---
> arch/arm/boot/dts/omap5.dtsi | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
> index 790bb2a..0d155f5 100644
> --- a/arch/arm/boot/dts/omap5.dtsi
> +++ b/arch/arm/boot/dts/omap5.dtsi
> @@ -422,6 +422,7 @@
> interrupts = <0 41 0x4>;
> ti,hwmods = "timer5";
> ti,timer-dsp;
> + ti,timer-pwm;
> };
>
> timer6: timer@4013a000 {
> @@ -458,6 +459,7 @@
> reg = <0x4803e000 0x80>;
> interrupts = <0 45 0x4>;
> ti,hwmods = "timer9";
> + ti,timer-pwm;
> };
>
> timer10: timer@48086000 {
> @@ -465,6 +467,7 @@
> reg = <0x48086000 0x80>;
> interrupts = <0 46 0x4>;
> ti,hwmods = "timer10";
> + ti,timer-pwm;
> };
>
> timer11: timer@48088000 {
Make sure you copy the linux-arm and device-tree mailing lists.
Acked-by: Jon Hunter <jon-hunter@ti.com>
Thanks!
Jon
next parent reply other threads:[~2013-04-17 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1366240995-53538-1-git-send-email-s-anna@ti.com>
2013-04-17 23:56 ` Jon Hunter [this message]
2013-05-31 22:17 ` [PATCH 1/2] ARM: dts: OMAP5: add PWM capability to timer nodes missing it Anna, Suman
2013-06-03 12:55 ` Benoit Cousson
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=516F3696.9080008@ti.com \
--to=jon-hunter@ti.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=s-anna@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).