Greg Kroah-Hartman
598cf27219
Link: https://lore.kernel.org/r/20260217200002.683975158@linuxfoundation.org Tested-by: Florian Fainelli <florian.fainelli@broadcom.com> Tested-by: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com> Tested-by: Peter Schneider <pschneider1968@googlemail.com> Tested-by: Jon Hunter <jonathanh@nvidia.com> Tested-by: Salvatore Bonaccorso <carnil@debian.org> Tested-by: Brett A C Sheffield <bacs@librecast.net> Tested-by: Mark Brown <broonie@kernel.org> Tested-by: Luna Jernberg <droidbittin@gmail.com> Tested-by: Ronald Warsow <rwarsow@gmx.de> Tested-by: Justin M. Forbes <jforbes@fedoraproject.org> Tested-by: Ron Economos <re@w6rz.net> Tested-by: Miguel Ojeda <ojeda@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
20 lines
956 B
Plaintext
20 lines
956 B
Plaintext
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.
|