alistair23-linux/drivers/bcma
Rafał Miłecki d6a3b51ada bcma: move parallel flash support to separated file
This follows the way of handling other flashes and cleans code a bit. As
next task we will want to move flash code to ChipCommon driver as:
1) Flash controllers are accesible using ChipCommon registers
2) This code isn't MIPS specific
This change prepares bcma for that.

Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
2016-03-07 14:41:08 +02:00
..
bcma_private.h bcma: move parallel flash support to separated file 2016-03-07 14:41:08 +02:00
core.c
driver_chipcommon.c bcma: add support for BCM47094 2016-02-06 13:46:59 +02:00
driver_chipcommon_b.c
driver_chipcommon_nflash.c
driver_chipcommon_pflash.c bcma: move parallel flash support to separated file 2016-03-07 14:41:08 +02:00
driver_chipcommon_pmu.c bcma: support PMU present as separated bus core 2016-02-06 13:36:11 +02:00
driver_chipcommon_sflash.c bcma: support identifying MX25L25635F serial flash 2016-02-06 13:33:05 +02:00
driver_gmac_cmn.c
driver_gpio.c Major changes: 2016-02-16 20:38:29 -05:00
driver_mips.c bcma: move parallel flash support to separated file 2016-03-07 14:41:08 +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: claim only 14e4:4365 PCI Dell card with SoftMAC BCM43142 2016-02-06 13:49:17 +02:00
host_soc.c
Kconfig bcma: move parallel flash support to separated file 2016-03-07 14:41:08 +02:00
main.c bcma: move parallel flash support to separated file 2016-03-07 14:41:08 +02:00
Makefile bcma: move parallel flash support to separated file 2016-03-07 14:41:08 +02:00
README
scan.c bcma: support chipsets with PMU and GCI cores (devices) 2016-02-06 13:34:51 +02:00
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.