From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@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: Sat, 12 Jan 2013 20:10:36 -0700 [thread overview]
Message-ID: <50F225AC.6030407@wwwdotorg.org> (raw)
In-Reply-To: <50F18742.5070501-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 01/12/2013 08:54 AM, 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.
I saw no need to have add a bus node (there wasn't one before I started
touching DT on Tegra); the top-level of the DT represents the CPU's
entire view of the address space and has #address-cells/#size-cells, so
devices get probed there just fine, whether they're addressed MMIO
devices or not.
next prev parent reply other threads:[~2013-01-13 3:10 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 [this message]
[not found] ` <50F225AC.6030407-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-01-19 16:35 ` Rob Herring
2013-01-14 9:18 ` Mark Rutland
[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=50F225AC.6030407@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@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 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.