linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] drivers/amba: probe via device tree
Date: Wed, 25 May 2011 11:03:28 +0200	[thread overview]
Message-ID: <BANLkTinrBgA8Zw03AzGFxAiY-84Hgxfcxg@mail.gmail.com> (raw)
In-Reply-To: <201105221203.03970.arnd@arndb.de>

2011/5/22 Arnd Bergmann <arnd@arndb.de>:
> 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.

Currently the amba/primecell bus driver in drivers/amba/bus.c
will have the hardware registers override any data provided
from the board.

There are pending patches to instead have the board potentially
override the hardware, see:
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=6829/1

The reason is that some of our hardware has newer revisions
of the PrimeCells and still the hardware registers have not
been updated properly. (Yes, the people involved have been
informed.)

So you also have a case where you may want to provide an ID
and have it override the ID present in the hardware.

Yours,
Linus Walleij

  reply	other threads:[~2011-05-25  9:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19 18:28 [PATCH v2 0/2] amba bus device tree probing Rob Herring
2011-05-19 18:28 ` [PATCH 1/2] dt: check for devices already created fron DT scan Rob Herring
2011-05-19 19:54   ` Grant Likely
2011-05-19 18:28 ` [PATCH 2/2] drivers/amba: probe via device tree Rob Herring
2011-05-19 20:01   ` Grant Likely
2011-05-19 23:30     ` Rob Herring
2011-05-19 23:39       ` Grant Likely
2011-05-20 13:24         ` Rob Herring
2011-05-20 14:21           ` Arnd Bergmann
2011-05-20 15:17             ` Rob Herring
2011-05-20 16:08               ` Stephen Neuendorffer
2011-05-21 17:42                 ` 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
2011-05-25  9:03                     ` Linus Walleij [this message]
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
2011-05-21 23:35                 ` Russell King - ARM Linux
2011-05-23 15:00                   ` Stephen Neuendorffer
2011-05-23 15:47                     ` Russell King - ARM Linux
2011-05-21  4:00               ` Segher Boessenkool
2011-05-21 14:55                 ` Rob Herring
2011-05-21 15:18                   ` Segher Boessenkool
2011-05-21 17:43                     ` Grant Likely

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=BANLkTinrBgA8Zw03AzGFxAiY-84Hgxfcxg@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).