linux-hardened/drivers/bcma
Rafał Miłecki 49280625eb bcma: lower dependency of BCMA_DRIVER_PCI_HOSTMODE
This extension of BCMA_DRIVER_PCI has no reason to depend on
BCMA_HOST_PCI. User may just want to have PCI device attached to SoC
registered without enabling any extra client mode code.
This can be useful when having non-bcma PCI device attached or when
using other PCI driver.

Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
2015-06-08 14:33:26 +03:00
..
bcma_private.h bcma: allow disabling (not building) PCI driver 2015-03-13 16:25:50 +02:00
core.c
driver_chipcommon.c bcma: fix watchdog on some ARM chipsets 2015-01-29 10:44:44 +02:00
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
driver_gmac_cmn.c
driver_gpio.c bcma: enable 32 GPIO pins for BCM4707 2015-05-09 16:28:07 +03:00
driver_mips.c MIPS: BCM47xx: Move NVRAM header to the include/linux/. 2015-04-01 17:22:00 +02:00
driver_pci.c bcma: move PCI IRQ control function to host specific code 2015-03-13 16:25:50 +02:00
driver_pci_host.c bcma: add missing includes 2015-03-03 15:26:38 +02:00
driver_pcie2.c bcma: add missing includes 2015-03-03 15:26:38 +02:00
host_pci.c bcma: move PCI IRQ control function to host specific code 2015-03-13 16:25:50 +02:00
host_soc.c bcma: use standard bus scanning during early register 2015-01-23 21:47:55 +02:00
Kconfig bcma: lower dependency of BCMA_DRIVER_PCI_HOSTMODE 2015-06-08 14:33:26 +03:00
main.c bcma: enable support for PCIe Gen 2 host devices 2015-03-02 16:59:45 +02:00
Makefile bcma: prepare Kconfig symbol for PCI driver 2015-03-05 14:11:45 +02:00
README
scan.c bcma: use standard bus scanning during early register 2015-01-23 21:47:55 +02:00
scan.h
sprom.c bcma: detect SPROM revision 11 2015-01-29 10:49:28 +02: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.