From: Benoit Cousson <bcousson@baylibre.com>
To: Nathan Lynch <Nathan_Lynch@mentor.com>, linux-omap@vger.kernel.org
Cc: tony@atomide.com
Subject: Re: [PATCH] ARM: dts: OMAP5: add pmu node
Date: Wed, 12 Feb 2014 14:00:34 +0100 [thread overview]
Message-ID: <52FB7072.5000005@baylibre.com> (raw)
In-Reply-To: <52FA8498.5050507@mentor.com>
Hi Nathan,
On 11/02/2014 21:14, Nathan Lynch wrote:
> On 01/29/2014 10:56 AM, Nathan Lynch wrote:
>> Expose the PMU on OMAP5.
>>
>> Signed-off-by: Nathan Lynch <nathan_lynch@mentor.com>
>
> OMAP folks, any issues with this patch?
Yes :-)
>> Notes:
>> Briefly tested with perf on OMAP5 UEVM with next-20140124.
>>
>> arch/arm/boot/dts/omap5.dtsi | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
>> index a72813a9663e..fbf4661436e2 100644
>> --- a/arch/arm/boot/dts/omap5.dtsi
>> +++ b/arch/arm/boot/dts/omap5.dtsi
>> @@ -76,6 +76,12 @@
>> <GIC_PPI 10 (GIC_CPU_MASK_RAW(3) | IRQ_TYPE_LEVEL_LOW)>;
>> };
>>
>> + pmu {
>> + compatible = "arm,cortex-a15-pmu";
>> + interrupts = <0 131 4>,
>> + <0 132 4>;
Could you use the macros instead of hard coded value? You have the
example just before your modification in the patch itself.
Thanks,
Benoit
--
Benoît Cousson
BayLibre
Embedded Linux Technology Lab
www.baylibre.com
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-02-12 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 16:56 [PATCH] ARM: dts: OMAP5: add pmu node Nathan Lynch
2014-01-29 16:56 ` Nathan Lynch
2014-02-11 20:14 ` Nathan Lynch
2014-02-12 13:00 ` Benoit Cousson [this message]
2014-02-12 15:02 ` Nathan Lynch
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=52FB7072.5000005@baylibre.com \
--to=bcousson@baylibre.com \
--cc=Nathan_Lynch@mentor.com \
--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.