linux_dsm_epyc7002

mirror of https://github.com/AuxXxilium/linux_dsm_epyc7002.git synced 2024-12-28 11:18:45 +07:00

History

Florian Fainelli 459c35148e bcma: gpio: Correct number of GPIOs for BCM53573 Broadcom BCM53573 SoCs actually have 32 GPIOs, and not 16. Fixes: `3f37ec79dd` ("bcma: support BCM53573 series of wireless SoCs") Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>		2017-07-27 13:59:07 +03:00
..
bcma_private.h
core.c
driver_chipcommon_b.c
driver_chipcommon_nflash.c
driver_chipcommon_pflash.c
driver_chipcommon_pmu.c
driver_chipcommon_sflash.c
driver_chipcommon.c
driver_gmac_cmn.c
driver_gpio.c	bcma: gpio: Correct number of GPIOs for BCM53573	2017-07-27 13:59:07 +03:00
driver_mips.c
driver_pci_host.c
driver_pci.c
driver_pcie2.c
host_pci.c
host_soc.c
Kconfig
main.c	bcma: fill core OF info independently of bus type	2017-03-20 19:12:01 +02:00
Makefile
README
scan.c
scan.h
sprom.c
TODO

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.