[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201104181619.35115.arnd@arndb.de>
Date: Mon, 18 Apr 2011 16:19:34 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Rafał Miłecki <zajec5@...il.com>
Cc: George Kashperko <george@...u.edu.ua>,
Hauke Mehrtens <hauke@...ke-m.de>,
Russell King <rmk@....linux.org.uk>,
linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Arend van Spriel <arend@...adcom.com>,
Jonas Gorski <jonas.gorski@...il.com>,
b43-dev@...ts.infradead.org, Greg KH <greg@...ah.com>,
Andy Botting <andy@...ybotting.com>,
Larry Finger <Larry.Finger@...inger.net>
Subject: Re: Could I (ab)use bus (struct bus_type) for virtual Broadcom bus?
On Monday 18 April 2011, Rafał Miłecki wrote:
> W dniu 17 kwietnia 2011 19:38 użytkownik Arnd Bergmann <arnd@...db.de> napisał:
>
> > In general, the bus_type directly relates to how a device gets probed.
> > If broadcom uses the same basic register layout as regular AMBA devices,
> > it should use the amba bus type.
>
> From Broadcom side we *could* use some registers that are AMBA
> specific, they are present... but there is totally no point in doing
> that. Everything we use is Broadcom specific.
>
>
> > I think it would be fine to extend the AMBA bus slightly if there are
> > just minor differences.
>
> As I said, Broadcom specific driver use nothing from AMBA common
> things. Plus we implement routines that are Broadcom specific and no
> other platform will use them.
You mean the hardware has two sets of registers containing the same
information, one of them the standard registers, and one with broadcom
specific ones?
Why don't you just use the standard ones then?
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