linux/drivers/bcma
Rafał Miłecki 26f2622edf bcma: use boardflags define from ssb code
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2011-08-09 15:42:36 -04:00
..
bcma_private.h bcma: get CPU clock 2011-08-08 14:29:29 -04:00
core.c bcma: add SOC bus 2011-08-08 14:29:25 -04:00
driver_chipcommon.c bcma: add serial console support 2011-08-08 14:29:28 -04:00
driver_chipcommon_pmu.c bcma: get CPU clock 2011-08-08 14:29:29 -04:00
driver_mips.c bcma: get CPU clock 2011-08-08 14:29:29 -04:00
driver_pci.c bcma: use boardflags define from ssb code 2011-08-09 15:42:36 -04:00
driver_pci_host.c bcma: detect PCI core working in hostmode 2011-07-07 13:13:34 -04: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
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: add mips driver 2011-08-08 14:29:26 -04:00
Makefile bcma: add mips driver 2011-08-08 14:29:26 -04:00
README bcma: add Broadcom specific AMBA bus driver 2011-05-10 15:54:54 -04:00
scan.c bcma: add SOC bus 2011-08-08 14:29:25 -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.