From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>,
Kevin Hilman <khilman@ti.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
Arnd Bergmann <arnd@arndb.de>,
devicetree-discuss@lists.ozlabs.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Jeremy Kerr <jeremy.kerr@canonical.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] drivers/amba: probe via device tree
Date: Sun, 22 May 2011 00:47:25 +0100 [thread overview]
Message-ID: <20110521234725.GB17672@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <BANLkTi=8vX1Cs_fzpQXZBuuDuLYLu1FGmg@mail.gmail.com>
On Sat, May 21, 2011 at 11:42:34AM -0600, Grant Likely wrote:
> Russell, it seems to me that the primary behaviour that amba_bus has
> over platform_bus is the clock management, and secondarily
> verification of the type of device by the device id. Am I correct, or
> am I missing something?
It matches by vendor/device ID just like PCI does, and does the bus
clock management and power management in a really nice way, which I
doubt platform devices will ever do.
The way this discussion is going, I'm going to suggest that we also
convert PCI stuff to being platform devices too. I don't see the
point of PCI existing for all the same reasons being given in this
thread.
next prev parent reply other threads:[~2011-05-21 23:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1305829704-11774-1-git-send-email-robherring2@gmail.com>
[not found] ` <20110519233958.GB18181@ponder.secretlab.ca>
[not found] ` <4DD66B8A.5040404@gmail.com>
[not found] ` <201105201621.03801.arnd@arndb.de>
[not found] ` <4DD68614.6090209@gmail.com>
[not found] ` <a42f0c27-2811-4b68-bedf-7dfaa7bff6ff@VA3EHSMHS025.ehs.local>
2011-05-21 17:42 ` Grant Likely
2011-05-21 23:47 ` Russell King - ARM Linux [this message]
2011-05-22 10:00 ` Rafael J. Wysocki
2011-05-22 15:46 ` Rob Herring
2011-05-23 15:23 ` Grant Likely
2011-05-22 10:03 ` Arnd Bergmann
2011-05-25 9:03 ` Linus Walleij
2011-05-23 9:37 ` Kristoffer Glembo
2011-05-23 9:58 ` Russell King - ARM Linux
2011-05-23 15:09 ` Grant Likely
2011-05-24 15:03 ` Rob Herring
2011-05-25 3:02 ` Shawn Guo
2011-05-25 9:07 ` Linus Walleij
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=20110521234725.GB17672@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=arnd@arndb.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=jeremy.kerr@canonical.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=segher@kernel.crashing.org \
--cc=stephen.neuendorffer@xilinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®