original_kernel/drivers/bcma
Linus Walleij 74a473007c bcma: Fail probe if GPIO subdriver fails
We currently register the BCMA core even if the GPIO portions
fail. There is no reason for this: the GPIO should register
just fine, if it fails the BCMA driver should fail.

We already gracefully handle the case where the GPIO driver is
not compiled in.

Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Kalle Valo <kvalo@kernel.org>
Link: https://lore.kernel.org/r/20221028093000.239020-1-linus.walleij@linaro.org
2022-11-04 12:59:51 +02:00
..
Kconfig
Makefile
README
TODO
bcma_private.h
core.c
driver_chipcommon.c
driver_chipcommon_b.c
driver_chipcommon_nflash.c
driver_chipcommon_pflash.c
driver_chipcommon_pmu.c
driver_chipcommon_sflash.c
driver_gmac_cmn.c
driver_gpio.c wireless-next patches for v6.2 2022-10-28 18:31:40 -07:00
driver_mips.c
driver_pci.c
driver_pci_host.c
driver_pcie2.c
host_pci.c
host_soc.c
main.c bcma: Fail probe if GPIO subdriver fails 2022-11-04 12:59:51 +02:00
scan.c
scan.h
sprom.c bcma: support SPROM rev 11 2022-10-19 08:59:37 +03: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.