From: Benoit Cousson <b-cousson@ti.com>
To: Jon Hunter <jon-hunter@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 2/2] ARM: dts: OMAP2+: Add PMU nodes
Date: Mon, 17 Dec 2012 17:04:14 +0100 [thread overview]
Message-ID: <50CF427E.3000804@ti.com> (raw)
In-Reply-To: <50CF411F.4060105@ti.com>
Hi Jon,
On 12/17/2012 04:58 PM, Jon Hunter wrote:
>
> On 12/17/2012 02:16 AM, Benoit Cousson wrote:
>> Hi Jon,
>>
>> On 12/14/2012 10:18 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.
>>
>> But where is the omap4430 node then?
>
> I have left it out deliberately because OMAP4430 is not yet supported by
> PMU as it is dependent on having a driver for the cross-trigger interface.
>
> If you prefer to stick the node in the omap4.dtsi for now then that is
> ok, but I wanted to make it clear that this is for omap4460.
No, that's fine, I was just wondering. You should just add that comment
in the cover letter to make it explicit.
Thanks,
Benoit
WARNING: multiple messages have this Message-ID (diff)
From: b-cousson@ti.com (Benoit Cousson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: OMAP2+: Add PMU nodes
Date: Mon, 17 Dec 2012 17:04:14 +0100 [thread overview]
Message-ID: <50CF427E.3000804@ti.com> (raw)
In-Reply-To: <50CF411F.4060105@ti.com>
Hi Jon,
On 12/17/2012 04:58 PM, Jon Hunter wrote:
>
> On 12/17/2012 02:16 AM, Benoit Cousson wrote:
>> Hi Jon,
>>
>> On 12/14/2012 10:18 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.
>>
>> But where is the omap4430 node then?
>
> I have left it out deliberately because OMAP4430 is not yet supported by
> PMU as it is dependent on having a driver for the cross-trigger interface.
>
> If you prefer to stick the node in the omap4.dtsi for now then that is
> ok, but I wanted to make it clear that this is for omap4460.
No, that's fine, I was just wondering. You should just add that comment
in the cover letter to make it explicit.
Thanks,
Benoit
next prev parent reply other threads:[~2012-12-17 16:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 21:18 [PATCH 0/2] ARM: dts: Add PMU support for OMAP2+ Jon Hunter
2012-12-14 21:18 ` Jon Hunter
2012-12-14 21:18 ` [PATCH 1/2] ARM: OMAP2+: Prepare for device-tree PMU support Jon Hunter
2012-12-14 21:18 ` Jon Hunter
2012-12-14 21:18 ` [PATCH 2/2] ARM: dts: OMAP2+: Add PMU nodes Jon Hunter
2012-12-14 21:18 ` Jon Hunter
2012-12-14 21:24 ` Jon Hunter
2012-12-14 21:24 ` Jon Hunter
2012-12-17 8:16 ` Benoit Cousson
2012-12-17 8:16 ` Benoit Cousson
2012-12-17 15:58 ` Jon Hunter
2012-12-17 15:58 ` Jon Hunter
2012-12-17 16:04 ` Benoit Cousson [this message]
2012-12-17 16:04 ` 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=50CF427E.3000804@ti.com \
--to=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jon-hunter@ti.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.