linux/drivers/bcma
Ricardo B. Marliere 06b5b2942c bcma: make bcma_bus_type const
Now that the driver core can properly handle constant struct bus_type,
move the bcma_bus_type variable to be a constant structure as well,
placing it into read-only memory which can not be modified at runtime.

Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Suggested-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Ricardo B. Marliere <ricardo@marliere.net>
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Kalle Valo <kvalo@kernel.org>
Link: https://msgid.link/20240204-bus_cleanup-bcma-v1-1-0d881c793190@marliere.net
2024-02-06 20:07:35 +02:00
..
bcma_private.h bcma: use dev_* printing functions 2019-01-10 13:39:19 +02:00
core.c
driver_chipcommon_b.c remove ioremap_nocache and devm_ioremap_nocache 2020-01-06 09:45:59 +01:00
driver_chipcommon_nflash.c mtd: rawnand: brcmnand: Add platform data structure for BCMA 2022-01-23 16:37:18 +01:00
driver_chipcommon_pflash.c
driver_chipcommon_pmu.c bcma: cleanup comments 2022-02-21 10:58:14 +02:00
driver_chipcommon_sflash.c
driver_chipcommon.c bcma: cleanup comments 2022-02-21 10:58:14 +02:00
driver_gmac_cmn.c
driver_gpio.c wireless-next patches for v6.2 2022-10-28 18:31:40 -07:00
driver_mips.c bcma: remove unused mips_read32 function 2023-03-31 18:04:59 +03:00
driver_pci_host.c bcma: Use PCI_HEADER_TYPE_MASK instead of literal 2023-11-30 21:21:28 +02:00
driver_pci.c bcma: fix incorrect update of BCMA_CORE_PCI_MDIO_DATA 2019-09-03 16:44:02 +03:00
driver_pcie2.c
host_pci.c bcma: simplify reference to driver name 2021-10-12 17:50:12 -05:00
host_soc.c remove ioremap_nocache and devm_ioremap_nocache 2020-01-06 09:45:59 +01:00
Kconfig
main.c bcma: make bcma_bus_type const 2024-02-06 20:07:35 +02:00
Makefile
README
scan.c bcma: Drop the unused parameter of bcma_scan_read32() 2021-08-29 14:44:57 +03:00
scan.h
sprom.c bcma: support SPROM rev 11 2022-10-19 08:59:37 +03: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.