[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201103301509.04899.arnd@arndb.de>
Date: Wed, 30 Mar 2011 15:09:04 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Russell King <rmk@....linux.org.uk>
Cc: Arend van Spriel <arend@...adcom.com>,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
gregkh@...e.de, linux-wireless@...r.kernel.org,
devel@...uxdriverproject.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/1] new module for amba axi on-chip interconnect
On Tuesday 29 March 2011, Russell King wrote:
> On Tue, Mar 29, 2011 at 11:40:18AM +0200, Arend van Spriel wrote:
> > GUIDANCE NEEDED:
> > This patch puts the module at proposed location. Please provide your
> > guidance if there is a better location within the linux tree for this
> > module.
> >
> > This module has been isolated from the brcm80211 driver currently
> > located in staging and provided to other drivers for chipsets using
> > the AMBA AXI on-chip interconnect with ARM Device Management Plugin
> > (DMP) silicon IP, which provides system discovery (chip being the
> > system) and basic core function (disable, reset, etc.).
>
> What does this do which the 'amba' bus support doesn't?
I believe the one thing we really want from this driver is the bus
scan code, which is not present in the amba bus implementation,
as far as I can tell. Today, the amba bus does very little beyond
what the platform bus does, in particular you still need to
register every single device from board specific code.
When the proposed axi_scan() function gets turned into an
amba_bus_register() function, a board file can call that to
add all devices on the bus without listing them individually
and calling amba_device_register() for each one.
Basically everything else is already there in the amba bus,
no need to do it again.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists