public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>,
	Rob Herring <robherring2@gmail.com>,
	devicetree-discuss@lists.ozlabs.org,
	Jeremy Kerr <jeremy.kerr@canonical.com>,
	linux-arm-kernel@lists.infradead.org,
	"Rafael J. Wysocki" <rjw@sisk.pl>, Kevin Hilman <khilman@ti.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PATCH 2/2] drivers/amba: probe via device tree
Date: Sun, 22 May 2011 12:03:03 +0200	[thread overview]
Message-ID: <201105221203.03970.arnd@arndb.de> (raw)
In-Reply-To: <BANLkTi=8vX1Cs_fzpQXZBuuDuLYLu1FGmg@mail.gmail.com>

On Saturday 21 May 2011 19:42:34 Grant Likely wrote:
> 1) drop amba-bus entirely and use platform_device everywhere, similar
> to what OMAP has done
> 2) strictly create amba_devices for nodes compatible with "arm,amba-device"
> 3) be intelligent about amba device creation; create an amba_device
> only for devices we know are driven with amba_driver.

Or maybe

4) Use amba_device for all devices on an amba bus (identified by
the compatible property of the bus), but mark the ones that do
not have primecell compatible registers so that the amba bus
does not try to look at them but instead takes the information
from the device tree.

Even though this might seem a bit silly when most devices are
not primecell ones, but it could be used as an incentive for
hardware designers (I can dream, right?) to provide them in future
designs. It would also make it easier to document the actual bus
hierarchy correctly.

	Arnd

  parent reply	other threads:[~2011-05-22 10:03 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           ` [PATCH 2/2] drivers/amba: probe via device tree Grant Likely
2011-05-21 23:47             ` Russell King - ARM Linux
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 [this message]
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=201105221203.03970.arnd@arndb.de \
    --to=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=robherring2@gmail.com \
    --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