a58d0b4d51
This allows us to increase compile-test coverage without having to build a kernel for MIPS. That's particularly interesting for subsystem maintainers that want to test as many drivers as possible in a single build. We also add a dependency on HAS_IOMEM in BCMA_HOST_SOC to make sure the driver is not selected when the arch does not implement IO accessors. Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com> Acked-by: Kalle Valo <kvalo@codeaurora.org> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com> |
||
---|---|---|
.. | ||
bcma_private.h | ||
core.c | ||
driver_chipcommon.c | ||
driver_chipcommon_b.c | ||
driver_chipcommon_nflash.c | ||
driver_chipcommon_pflash.c | ||
driver_chipcommon_pmu.c | ||
driver_chipcommon_sflash.c | ||
driver_gmac_cmn.c | ||
driver_gpio.c | ||
driver_mips.c | ||
driver_pci.c | ||
driver_pci_host.c | ||
driver_pcie2.c | ||
host_pci.c | ||
host_soc.c | ||
Kconfig | ||
main.c | ||
Makefile | ||
README | ||
scan.c | ||
scan.h | ||
sprom.c | ||
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.