linux-kernel-test/drivers/bcma
Hauke Mehrtens 534e7a4566 bcma: add check if sprom is available before accessing it.
The SoCs like the bcm4716 do not have a sprom on the bcma bus like a
pcie device. It stores the values in some partition on flash memory.
For ssb this informations are read out in the bcm47xx arch code,
something like that should also be implemented for bcma. Without this
patch bcma panics on SoCs.

Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2011-07-11 15:02:17 -04:00
..
bcma_private.h bcma: detect PCI core working in hostmode 2011-07-07 13:13:34 -04:00
core.c drivers: bcma: export bcma_core_disable() function 2011-06-10 14:57:53 -04:00
driver_chipcommon_pmu.c bcma: fix BCM43224 rev 0 workaround 2011-06-20 15:34:19 -04:00
driver_chipcommon.c
driver_pci_host.c bcma: detect PCI core working in hostmode 2011-07-07 13:13:34 -04:00
driver_pci.c bcma: detect PCI core working in hostmode 2011-07-07 13:13:34 -04:00
host_pci.c bcma: enable support for 14e4:4357 (BCM43225) 2011-06-20 15:34:18 -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
scan.c
scan.h
sprom.c bcma: add check if sprom is available before accessing it. 2011-07-11 15:02:17 -04: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.