original_kernel/drivers/bcma
Hauke Mehrtens 517f43e5a9 bcma: add functions to scan cores needed on SoCs
The chip common and mips core have to be setup early in the boot
process to get the cpu clock.
bcma_bus_early_register() gets pointers to some space to store the core
data and searches for the chip common and mips core and initializes
chip common. After that was done and the kernel is out of early boot we
just have to run bcma_bus_register() and it will search for the other
cores, initialize and register them.
The cores are getting the same numbers as before.

Acked-by: Rafał Miłecki <zajec5@gmail.com>
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2011-08-08 14:29:24 -04:00
..
Kconfig bcma: detect PCI core working in hostmode 2011-07-07 13:13:34 -04:00
Makefile bcma: detect PCI core working in hostmode 2011-07-07 13:13:34 -04:00
README
TODO
bcma_private.h bcma: add functions to scan cores needed on SoCs 2011-08-08 14:29:24 -04:00
core.c bcma: inform drivers about translation bits needed for the core 2011-07-22 09:51:12 -04:00
driver_chipcommon.c bcma: add functions to scan cores needed on SoCs 2011-08-08 14:29:24 -04:00
driver_chipcommon_pmu.c Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial 2011-07-25 13:56:39 -07:00
driver_pci.c bcma: add functions to scan cores needed on SoCs 2011-08-08 14:29:24 -04:00
driver_pci_host.c bcma: detect PCI core working in hostmode 2011-07-07 13:13:34 -04:00
host_pci.c Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next-2.6 into for-davem 2011-06-24 15:25:51 -04:00
main.c bcma: add functions to scan cores needed on SoCs 2011-08-08 14:29:24 -04:00
scan.c bcma: add functions to scan cores needed on SoCs 2011-08-08 14:29:24 -04:00
scan.h
sprom.c bcma: handle alternative SPROM location 2011-07-19 16:49:53 -04:00

README

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.