linux

History

Hauke Mehrtens 49dc957715 bcma: add PCIe host controller Some SoCs have a PCIe host controller to make it possible to attach some other devices to it, like an other Wifi card. This code was tested with an Netgear WNDR3400 (bcm4716 based), but should work with all bcma based SoCs. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by: John W. Linville <linville@tuxdriver.com>		2012-02-06 14:53:04 -05:00
..
bcma_private.h	bcma: add PCIe host controller	2012-02-06 14:53:04 -05:00
core.c
driver_chipcommon_pmu.c
driver_chipcommon.c
driver_mips.c
driver_pci_host.c	bcma: add PCIe host controller	2012-02-06 14:53:04 -05:00
driver_pci.c	bcma: add PCIe host controller	2012-02-06 14:53:04 -05:00
host_pci.c	bcma: make some functions __devinit	2012-02-06 14:53:03 -05:00
host_soc.c
Kconfig
main.c	bcma: make some functions __devinit	2012-02-06 14:53:03 -05:00
Makefile
README
scan.c	bcma: add the core unit number	2012-02-06 14:50:39 -05:00
scan.h
sprom.c	bcma: Enable logging of SPROM offset	2012-01-24 14:21:12 -05:00
TODO

README

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.