^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) Broadcom introduced new bus as replacement for older SSB. It is based on AMBA,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2) however from programming point of view there is nothing AMBA specific we use.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4) Standard AMBA drivers are platform specific, have hardcoded addresses and use
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5) AMBA standard fields like CID and PID.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7) In case of Broadcom's cards every device consists of:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8) 1) Broadcom specific AMBA device. It is put on AMBA bus, but can not be treated
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9) as standard AMBA device. Reading it's CID or PID can cause machine lockup.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) 2) AMBA standard devices called ports or wrappers. They have CIDs (AMBA_CID)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) and PIDs (0x103BB369), but we do not use that info for anything. One of that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) devices is used for managing Broadcom specific core.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) Addresses of AMBA devices are not hardcoded in driver and have to be read from
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) EPROM.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) In this situation we decided to introduce separated bus. It can contain up to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) 16 devices identified by Broadcom specific fields: manufacturer, id, revision
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) and class.