From: Jon Hunter <jon-hunter@ti.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>,
device-tree <devicetree-discuss@lists.ozlabs.org>
Subject: Re: [PATCH V2 2/2] ARM: dts: OMAP2+: Add PMU nodes
Date: Fri, 11 Jan 2013 07:59:09 -0600 [thread overview]
Message-ID: <50F01AAD.8020003@ti.com> (raw)
In-Reply-To: <50F01256.7030701@ti.com>
Hi Benoit,
On 01/11/2013 07:23 AM, Benoit Cousson wrote:
> Hi Jon,
>
> On 12/17/2012 06:49 PM, Jon Hunter wrote:
>> Add PMU nodes for OMAP2, OMAP3 and OMAP4460 devices.
>>
>> Please note that the node for OMAP4460 has been placed in a separate
>> header file for OMAP4460, because the node is not compatible with
>> OMAP4430. The node for OMAP4430 is not included because PMU is not
>> currently supported on OMAP4430 due to the absence of a cross-trigger
>> interface driver.
>>
>> Signed-off-by: Jon Hunter <jon-hunter@ti.com>
>
> I've just applied this patch in my for_3.9/dts branch.
>
> I'm wondering if there is any dependency with the previous patch? If
> Tony ack it I can take it as well.
I have been thinking about the best way to handle that. May be best for
you to take both if Tony can ack the first.
Cheers
Jon
next prev parent reply other threads:[~2013-01-11 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 17:49 [PATCH V2 0/2] ARM: dts: Add PMU support for OMAP2+ Jon Hunter
2012-12-17 17:49 ` [PATCH V2 1/2] ARM: OMAP2+: Prepare for device-tree PMU support Jon Hunter
2013-01-11 17:59 ` Tony Lindgren
2012-12-17 17:49 ` [PATCH V2 2/2] ARM: dts: OMAP2+: Add PMU nodes Jon Hunter
2013-01-11 13:23 ` Benoit Cousson
2013-01-11 13:59 ` Jon Hunter [this message]
2013-01-11 17:59 ` Tony Lindgren
[not found] ` <1355766548-5702-1-git-send-email-jon-hunter-l0cyMroinI0@public.gmane.org>
2012-12-17 17:52 ` [PATCH V2 0/2] ARM: dts: Add PMU support for OMAP2+ Jon Hunter
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=50F01AAD.8020003@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=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).