From: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org,
Linus Walleij
<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
Jeremy Kerr <jeremy.kerr-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Subject: [RFC PATCH v3 0/2] amba bus device tree probing
Date: Wed, 25 May 2011 16:31:11 -0500 [thread overview]
Message-ID: <1306359073-16274-1-git-send-email-robherring2@gmail.com> (raw)
From: Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>
This is updated amba bus DT probe support. It has changed significantly since
v2 based on the discussion and the conclusions from that discussion:
- The Linux amba_bus is really for ARM Primecell peripherals, not a type of bus.
- The amba_bus is not going to be replaced by platform_bus.
The bus scanning is done entirely by of_platform_bus_populate/probe and only
the device creation is handled by the amba bus code. This patch set can support
Grant's options 2 or 3 depending on the match table used.
Applies to devicetree/next on git://git.secretlab.ca/git/linux-2.6
Rob
Rob Herring (2):
drivers/amba: create devices from device tree
dt: add custom device creation to platform bus scan
drivers/amba/bus.c | 51 +++++++++++++++++++++++++++++++++++++++++++
drivers/of/platform.c | 27 ++++++++++++++++------
include/linux/amba/bus.h | 5 ++++
include/linux/of_platform.h | 11 ++++++--
4 files changed, 83 insertions(+), 11 deletions(-)
--
1.7.4.1
next reply other threads:[~2011-05-25 21:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 21:31 Rob Herring [this message]
[not found] ` <1306359073-16274-1-git-send-email-robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-05-25 21:31 ` [RFC PATCH v3 1/2] drivers/amba: create devices from device tree Rob Herring
2011-05-26 7:41 ` Linus Walleij
2011-05-25 21:31 ` [RFC PATCH v3 2/2] dt: add custom device creation to platform bus scan Rob Herring
[not found] ` <1306359073-16274-3-git-send-email-robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-05-26 13:11 ` Arnd Bergmann
[not found] ` <201105261511.23659.arnd-r2nGTMty4D4@public.gmane.org>
2011-05-26 18:43 ` Rob Herring
[not found] ` <4DDE9F4A.5050507-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-05-27 12:06 ` Arnd Bergmann
[not found] ` <201105271406.18841.arnd-r2nGTMty4D4@public.gmane.org>
2011-06-01 16:52 ` Rob Herring
[not found] ` <4DE66E39.2070300-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-06-01 16:58 ` Grant Likely
[not found] ` <BANLkTimTdVKspjJ8GD4M90wiKCC0SzkgpA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-01 21:29 ` Arnd Bergmann
[not found] ` <201106012329.20651.arnd-r2nGTMty4D4@public.gmane.org>
2011-06-08 3:12 ` Rob Herring
[not found] ` <4DEEE8AF.50603-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-06-08 6:16 ` Arnd Bergmann
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=1306359073-16274-1-git-send-email-robherring2@gmail.com \
--to=robherring2-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=jeremy.kerr-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@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).