From: wcohen@redhat.com (William Cohen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Add the Performance Monitoring Unit to the Trimslice device tree
Date: Thu, 26 Apr 2012 14:28:19 -0400 [thread overview]
Message-ID: <4F9993C3.8050008@redhat.com> (raw)
In-Reply-To: <4F9970AD.6090501@wwwdotorg.org>
On 04/26/2012 11:58 AM, Stephen Warren wrote:
> On 04/26/2012 09:22 AM, Will Deacon wrote:
>> On Thu, Apr 26, 2012 at 04:16:27PM +0100, William Cohen wrote:
>>> On 04/23/2012 01:56 PM, William Cohen wrote:
>>>> Has this patch been pulled into the git tree? -Will (Cohen)
>>>
>>>
>>> This patch pretty much duplicates what is already done for in board-seaboard.c:
>>>
>>> http://lxr.linux.no/#linux+v3.3.3/arch/arm/mach-tegra/board-seaboard.c#L147
>>>
>>> I have tested the patch out with oprofile, papi, and perf. Things seem to function properly with the patch on a trimslice.
>>
>> Right, that sounds good to me. This should go via the tegra/arm-soc tree.
>> For some reason, I can't find the original patch in the list archives so
>> perhaps you could repost it to linux-arm-kernel and CC Olof and Arnd?
>
> Is there actually any reason to proceed with this patch? When booting
> Tegra using device tree (i.e. CONFIG_OF rather than the way the phrase
> is used in the email subject), the ARM PMU is enabled on all boards. So,
> I'd recommend switching to DT rather than continuing to patch up the
> board files, which will hopefully be removed in the nearish future.
>
> (BTW, best to cc linux-tegra at vger.kernel.org too)
Hi Stephen,
The fedora 17 arm kernels are not yet using the DT. That is the motivations to get this fix into the upstream kernel so that people could use performance monitoring hardware.
Has the pmu support been verified to work on Nvidia Tegra when using the DT? In the past I was not successful in getting the trimslice to boot up using device tree. Are there some clear instructions somewhere on how to do this?
-Will
next prev parent reply other threads:[~2012-04-26 18:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1330740413-29260-1-git-send-email-wcohen@redhat.com>
2012-03-05 10:32 ` [PATCH] Add the Performance Monitoring Unit to the Trimslice device tree Will Deacon
2012-04-23 17:56 ` William Cohen
2012-04-26 15:16 ` William Cohen
2012-04-26 15:22 ` Will Deacon
2012-04-26 15:58 ` Stephen Warren
2012-04-26 18:28 ` William Cohen [this message]
2012-04-26 18:57 ` Stephen Warren
2012-04-26 20:09 ` William Cohen
2012-04-27 21:44 ` Stephen Warren
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=4F9993C3.8050008@redhat.com \
--to=wcohen@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).