linux/drivers/bcma
Hauke Mehrtens 67a5c29e16 bcma: move initializing of struct bcma_bus to own function.
This makes it possible to use this code in some other method.

Acked-by: Rafał Miłecki <zajec5@gmail.com>
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2011-08-08 14:29:23 -04:00
..
bcma_private.h bcma: detect PCI core working in hostmode 2011-07-07 13:13:34 -04:00
core.c bcma: inform drivers about translation bits needed for the core 2011-07-22 09:51:12 -04:00
driver_chipcommon_pmu.c Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial 2011-07-25 13:56:39 -07:00
driver_chipcommon.c Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial 2011-07-25 13:56:39 -07:00
driver_pci_host.c bcma: detect PCI core working in hostmode 2011-07-07 13:13:34 -04:00
driver_pci.c Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial 2011-07-25 13:56:39 -07:00
host_pci.c Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next-2.6 into for-davem 2011-06-24 15:25:51 -04:00
Kconfig bcma: detect PCI core working in hostmode 2011-07-07 13:13:34 -04:00
main.c bcma: add check if sprom is available before accessing it. 2011-07-11 15:02:17 -04:00
Makefile bcma: detect PCI core working in hostmode 2011-07-07 13:13:34 -04:00
README bcma: add Broadcom specific AMBA bus driver 2011-05-10 15:54:54 -04:00
scan.c bcma: move initializing of struct bcma_bus to own function. 2011-08-08 14:29:23 -04:00
scan.h bcma: add Broadcom specific AMBA bus driver 2011-05-10 15:54:54 -04:00
sprom.c bcma: handle alternative SPROM location 2011-07-19 16:49:53 -04:00
TODO bcma: add Broadcom specific AMBA bus driver 2011-05-10 15:54:54 -04:00

Broadcom introduced new bus as replacement for older SSB. It is based on AMBA,
however from programming point of view there is nothing AMBA specific we use.

Standard AMBA drivers are platform specific, have hardcoded addresses and use
AMBA standard fields like CID and PID.

In case of Broadcom's cards every device consists of:
1) Broadcom specific AMBA device. It is put on AMBA bus, but can not be treated
   as standard AMBA device. Reading it's CID or PID can cause machine lockup.
2) AMBA standard devices called ports or wrappers. They have CIDs (AMBA_CID)
   and PIDs (0x103BB369), but we do not use that info for anything. One of that
   devices is used for managing Broadcom specific core.

Addresses of AMBA devices are not hardcoded in driver and have to be read from
EPROM.

In this situation we decided to introduce separated bus. It can contain up to
16 devices identified by Broadcom specific fields: manufacturer, id, revision
and class.