kernel-fxtec-pro1x/drivers/bcma
Piotr Haber 1fffa905ad bcma: fix unregistration of cores
When cores are unregistered, entries
need to be removed from cores list in a safe manner.

Reported-by: Stanislaw Gruszka <sgruszka@redhat.com>
Reviewed-by: Arend Van Spriel <arend@broadcom.com>
Signed-off-by: Piotr Haber <phaber@broadcom.com>
Cc: stable@vger.kernel.org
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2012-10-15 14:45:51 -04:00
..
bcma_private.h bcma: detect and register NAND flash device 2012-08-21 16:05:53 -04:00
core.c bcma: change delays to follow timers-howto guide 2012-09-28 13:54:02 -04:00
driver_chipcommon.c bcma: fix CC driver compilation on MIPS 2012-07-11 15:40:21 -04:00
driver_chipcommon_nflash.c bcma: detect and register NAND flash device 2012-08-21 16:05:53 -04:00
driver_chipcommon_pmu.c bcma: change delays to follow timers-howto guide 2012-09-28 13:54:02 -04:00
driver_chipcommon_sflash.c bcma: detect and register serial flash device 2012-08-21 16:05:52 -04:00
driver_gmac_cmn.c bcma: add trivial GBIT MAC COMMON driver 2012-07-12 15:27:18 -04:00
driver_mips.c bcma: fix regression in interrupt assignment on mips 2012-07-26 15:37:57 -04:00
driver_pci.c bcma: change delays to follow timers-howto guide 2012-09-28 13:54:02 -04:00
driver_pci_host.c bcma: change delays to follow timers-howto guide 2012-09-28 13:54:02 -04:00
host_pci.c bcma: handle BCM43227 2012-09-24 15:02:07 -04:00
host_soc.c bcma: make some functions static 2012-08-10 15:26:52 -04:00
Kconfig bcma: detect and register NAND flash device 2012-08-21 16:05:53 -04:00
main.c bcma: fix unregistration of cores 2012-10-15 14:45:51 -04:00
Makefile bcma: add place for flash memory support 2012-07-17 15:11:40 -04:00
README
scan.c bcma: add missing iounmap on error path 2012-07-26 15:37:57 -04:00
scan.h bcma: fix typo - reading number of slave wrappers 2012-07-12 15:27:17 -04:00
sprom.c bcma: handle BCM43227 2012-09-24 15:02:07 -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.