linux/drivers/bcma
Rafał Miłecki cbbc0138ef bcma: mips: fix clearing device IRQ
We were using wrong IRQ number so clearing wasn't working at all.
Depending on a platform this could result in a one device having two
interrupts assigned. On BCM4706 this resulted in all IRQs being broken.

Cc: Hauke Mehrtens <hauke@hauke-m.de>
Cc: stable@vger.kernel.org
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
Acked-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2012-12-10 15:49:53 -05:00
..
bcma_private.h bcma: unify naming schema for clock functions 2012-12-10 15:47:30 -05:00
core.c bcma: change delays to follow timers-howto guide 2012-09-28 13:54:02 -04:00
driver_chipcommon_nflash.c bcma: mark nflash if it is the boot flash 2012-10-19 15:52:37 -04:00
driver_chipcommon_pmu.c bcma: unify naming schema for clock functions 2012-12-10 15:47:30 -05:00
driver_chipcommon_sflash.c bcma: add some more flash chips for serial flash 2012-10-19 15:52:39 -04:00
driver_chipcommon.c bcma: unify naming schema for clock functions 2012-12-10 15:47:30 -05:00
driver_gmac_cmn.c bcma: add trivial GBIT MAC COMMON driver 2012-07-12 15:27:18 -04:00
driver_mips.c bcma: mips: fix clearing device IRQ 2012-12-10 15:49:53 -05:00
driver_pci_host.c bcma: handle return value of pci_assign_resource 2012-11-30 13:38:13 -05:00
driver_pci.c bcma: change delays to follow timers-howto guide 2012-09-28 13:54:02 -04:00
host_pci.c bcma: suspend/resume callbacks should be conditionally compiled on CONFIG_PM_SLEEP 2012-10-29 15:19:31 -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: register watchdog driver 2012-12-06 14:58:57 -05: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: use fallback sprom if sprom on card was not valid 2012-10-19 15:52:53 -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.