linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kristoffer@gaisler.com (Kristoffer Glembo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] drivers/amba: probe via device tree
Date: Mon, 23 May 2011 11:37:04 +0200	[thread overview]
Message-ID: <4DDA2AC0.1060406@gaisler.com> (raw)
In-Reply-To: <BANLkTi=8vX1Cs_fzpQXZBuuDuLYLu1FGmg@mail.gmail.com>

Hi,

Grant Likely wrote:
> In the case we're talking about the bus really is an AMBA bus, and all
> the devices on it are in some sense real amba devices.  The problem is
> that not all of the devices on the bus implement peripheral ID
> registers or other mechanisms that good upstanding AMBA devices are
> expected to have.  


Before we go hardware bashing of non primecell AMBA devices I would just
want to point out that the primecell stuff is not part of the AMBA specification.

So the "amba bus" should really have a way of marking which devices are primecell
devices instead of assuming this.

We (Aeroflex Gaisler) use an AMBA bus on our LEON SPARC chips but don't have any primecells 
devices. We went the of_platform_driver route after concluding that the AMBA bus in Linux is 
really not an AMBA bus at all. Our bus is fully probable though as all information about the 
present devices are memory mapped in a "plug and play" area.

On the other hand, there is not much point of an AMBA bus driver which does nothing more than
the platform driver. But AMBA is really a misnomer in this case.

/Kristoffer

  parent reply	other threads:[~2011-05-23  9:37 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
2011-05-23  9:37                   ` Kristoffer Glembo [this message]
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=4DDA2AC0.1060406@gaisler.com \
    --to=kristoffer@gaisler.com \
    --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).