From: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
To: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: devicetree-discuss
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
Peter Crosthwaite
<peter.crosthwaite-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
Soren Brinkmann <sorenb-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
Subject: Re: PMU node location
Date: Mon, 14 Jan 2013 09:18:34 +0000 [thread overview]
Message-ID: <20130114091834.GK19765@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <50F18742.5070501-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Sat, Jan 12, 2013 at 03:54:42PM +0000, Rob Herring wrote:
> On 01/10/2013 07:47 AM, Michal Simek wrote:
> > Hi Rob, Mark, Grant and others,
> >
> > I want to check with you the location of ARM pmu node
> > I see that
> > 1) highbank and dbx5x0 have it in soc node
> >
> > 2) vexpress and tegra have no main bus and pmu is in root like all
> > others devices.
> > (Any reason no to have main bus? Does it mean that there is no bus or
> > that all
> > devices are accessible?)
>
> That seems really wrong in general. Any memory mapped device is on a bus
> of some kind. I'm not sure the reasoning. Perhaps Stephen can explain.
>
> > 3) omap2/omap3 have added pmu node to root node(mailing list)
> >
> > 4) Just for completeness no platform has it in the bus.
> >
> >
> > That's why I have obvious question what it is proper location for pmu node?
>
> Obviously, highbank is the true and correct way. ;)
>
> The pmu is part of the cpu, so it could be part of /cpus. That may cause
> problems having non-cpu nodes and it would not get probed (although
> technically that is a Linux problem and should not influence the DT).
If we were going to allow cpu nodes in /cpus, I'd rather we supported a pmu
node in each /cpus/cpuN node. That way the description of heterogeneous
clusters would be intuitive (each pmu node representing a single cpu-affine
unit rather than the collection of all cpu-affine units). That way describing
heterogeneous clusters would become intuitive (cpu affinity would be implicit,
and wouldn't have to be described separately as with my proposed binding [1]).
and I'm not sure how you'd handle PMUs which used the same PPI
> Since it is not on a bus, then putting it at the top level probably
> makes more sense than on a bus.
Agreed. I think this makes the most sense.
>
> Rob
>
> >
> > Thanks,
> > Michal
> >
>
Thanks,
Mark.
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2012-December/137290.html
next prev parent reply other threads:[~2013-01-14 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 13:47 PMU node location Michal Simek
[not found] ` <50EEC672.5050405-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2013-01-12 15:54 ` Rob Herring
[not found] ` <50F18742.5070501-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-01-13 3:10 ` Stephen Warren
[not found] ` <50F225AC.6030407-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-01-19 16:35 ` Rob Herring
2013-01-14 9:18 ` Mark Rutland [this message]
[not found] ` <20130114091834.GK19765-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2013-01-14 9:36 ` Michal Simek
[not found] ` <CAHTX3dLm-LQzPfbRvaPMbOeTg72pBCy2+KqsnftLJKpgFskW9A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-14 10:11 ` Mark Rutland
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=20130114091834.GK19765@e106331-lin.cambridge.arm.com \
--to=mark.rutland-5wv7dgnigg8@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=peter.crosthwaite-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
--cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=sorenb-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.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).