linux/drivers/bcma
Nathan Hintz 4acabf454a bcma: Account for variable PCI memory base/size
PCI Memory Resource start address and size are variable, dependent on
the H/W configuration.  Modify the computation of io_map_base to use the
computed values.

Signed-off-by: Nathan Hintz <nlhintz@hotmail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2012-05-16 12:46:04 -04:00
..
bcma_private.h bcma: add PCIe host controller 2012-02-06 14:53:04 -05:00
core.c bcma: implement setting core clock mode to dynamic 2012-05-16 12:45:22 -04:00
driver_chipcommon_pmu.c bcma: silence PMU warning for BCM4331 2012-03-07 13:56:37 -05:00
driver_chipcommon.c bcma: fix implicit use of export.h contents 2011-10-31 19:32:02 -04:00
driver_mips.c bcma: get CPU clock 2011-08-08 14:29:29 -04:00
driver_pci_host.c bcma: Account for variable PCI memory base/size 2012-05-16 12:46:04 -04:00
driver_pci.c bcma: add bcma_core_pci_config_fixup() 2012-05-16 12:45:22 -04:00
host_pci.c bcma: add boardinfo struct 2012-05-16 12:45:21 -04:00
host_soc.c bcma: add SOC bus 2011-08-08 14:29:25 -04:00
Kconfig bcma: fix build error on MIPS; implicit pcibios_enable_device 2012-04-10 14:13:30 -04:00
main.c bcma: export bcma_find_core 2012-03-05 15:20:50 -05:00
Makefile bcma: add mips driver 2011-08-08 14:29:26 -04:00
README
scan.c bcma: Find names of non BCM cores 2012-05-16 12:45:26 -04:00
scan.h
sprom.c bcma/ssb: parse new attributes from sprom 2012-05-16 12:45:22 -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.