linux/drivers/bcma
Rafał Miłecki ab54bc8460 bcma: fill core details for every device
We were setting things like dma_dev, IRQ, etc. during core registration
only. We need such info for cores handled internally (e.g. ChipCommon)
as well.

Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
Acked-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2014-10-27 14:16:13 -04:00
..
bcma_private.h bcma: fill core details for every device 2014-10-27 14:16:13 -04:00
core.c
driver_chipcommon_b.c bcma: add support for chipcommon B core 2014-09-09 15:33:05 -04:00
driver_chipcommon_nflash.c
driver_chipcommon_pmu.c bcma: add support for BCM43131 that was found in Tenda W311E 2014-07-29 10:32:57 -04:00
driver_chipcommon_sflash.c bcma: fix sparse warnings in driver_chipcommon_sflash.c 2014-01-03 15:37:01 -05:00
driver_chipcommon.c bcma: add support for BCM43142 2013-06-27 13:42:16 -04:00
driver_gmac_cmn.c
driver_gpio.c This is the bulk of GPIO changes for the v3.18 development 2014-10-09 14:58:15 -04:00
driver_mips.c bcma: get info about flash type SoC booted from 2014-09-04 13:50:11 -04:00
driver_pci_host.c bcma: change max PCI read request size to 128 2013-08-26 14:09:02 -04:00
driver_pci.c bcma: make bcma_core_pci_{up,down}() callable from atomic context 2013-09-26 14:02:33 -04:00
driver_pcie2.c bcma: add driver for PCIe Gen 2 core 2014-07-07 16:32:16 -04:00
host_pci.c bcma: move bus struct setup into early part of host specific code 2014-09-09 15:27:18 -04:00
host_soc.c bcma: register bcma as device tree driver 2014-09-30 13:17:14 -04:00
Kconfig bcma: gpio: add own IRQ domain 2014-01-23 13:02:37 +01:00
main.c bcma: fill core details for every device 2014-10-27 14:16:13 -04:00
Makefile bcma: add support for chipcommon B core 2014-09-09 15:33:05 -04:00
README
scan.c bcma: fill core details for every device 2014-10-27 14:16:13 -04:00
scan.h
sprom.c bcma: add support for BCM43131 that was found in Tenda W311E 2014-07-29 10:32:57 -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.