kernel_optimize_test/drivers/bcma
Hauke Mehrtens e7027075d0 bcma: fix null pointer in bcma_core_pci_irq_ctl
pc could be null if hosttype != BCMA_HOSTTYPE_PCI.
If we are on a device without a pci core this function is called with
pc = null by b43 and brcmsmac. If the host type is PCI we have a pci
core as well and pc can not be null.

Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2012-06-08 13:47:07 -04:00
..
bcma_private.h
core.c bcma: Add flush for BCMA_RESET_CTL write 2012-05-16 12:46:04 -04:00
driver_chipcommon_pmu.c bcma: add ext PA workaround for BCM4331 and BCM43431 2012-06-04 15:26:40 -04:00
driver_chipcommon.c
driver_mips.c
driver_pci_host.c bcma: reads/writes are always 4 bytes, so always map 4 bytes 2012-05-16 12:46:04 -04:00
driver_pci.c bcma: fix null pointer in bcma_core_pci_irq_ctl 2012-06-08 13:47:07 -04:00
host_pci.c bcma: Add __devexit to bcma_host_pci_remove 2012-05-16 12:46:04 -04:00
host_soc.c
Kconfig bcma: fix build error on MIPS; implicit pcibios_enable_device 2012-04-10 14:13:30 -04:00
main.c
Makefile
README
scan.c Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net 2012-05-24 11:54:29 -07:00
scan.h
sprom.c bcma: add ext PA workaround for BCM4331 and BCM43431 2012-06-04 15:26:40 -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.