linux/drivers/bcma
Hauke Mehrtens 4b259a5cc5 bcma: export bcma_pcie_read()
This will be needed by the host controller.

Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2012-02-06 14:53:02 -05:00
..
bcma_private.h bcma: export bcma_pcie_read() 2012-02-06 14:53:02 -05:00
core.c bcma: fix implicit use of export.h contents 2011-10-31 19:32:02 -04:00
driver_chipcommon_pmu.c bcma: fix implicit use of export.h contents 2011-10-31 19:32:02 -04:00
driver_chipcommon.c bcma: fix implicit use of export.h contents 2011-10-31 19:32:02 -04:00
driver_mips.c bcma: get CPU clock 2011-08-08 14:29:29 -04:00
driver_pci_host.c bcma: detect PCI core working in hostmode 2011-07-07 13:13:34 -04:00
driver_pci.c bcma: export bcma_pcie_read() 2012-02-06 14:53:02 -05:00
host_pci.c bcma: add stub for bcma_bus_suspend() 2012-01-17 09:54:05 -05:00
host_soc.c bcma: add SOC bus 2011-08-08 14:29:25 -04:00
Kconfig bcma: add mips driver 2011-08-08 14:29:26 -04:00
main.c bcma: connect the bcma bus suspend/resume to the bcma driver suspend/resume 2012-01-17 09:54:08 -05:00
Makefile bcma: add mips driver 2011-08-08 14:29:26 -04:00
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

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.