PageRenderTime 45ms CodeModel.GetById 24ms RepoModel.GetById 0ms app.codeStats 0ms

#! | 19 lines | 15 code | 4 blank | 0 comment | 0 complexity | ea5572b01aa0385124ea5114dac6a36a MD5 | raw file
Possible License(s): GPL-2.0, LGPL-2.0, AGPL-1.0
  1. Broadcom introduced new bus as replacement for older SSB. It is based on AMBA,
  2. however from programming point of view there is nothing AMBA specific we use.
  3. Standard AMBA drivers are platform specific, have hardcoded addresses and use
  4. AMBA standard fields like CID and PID.
  5. In case of Broadcom's cards every device consists of:
  6. 1) Broadcom specific AMBA device. It is put on AMBA bus, but can not be treated
  7. as standard AMBA device. Reading it's CID or PID can cause machine lockup.
  8. 2) AMBA standard devices called ports or wrappers. They have CIDs (AMBA_CID)
  9. and PIDs (0x103BB369), but we do not use that info for anything. One of that
  10. devices is used for managing Broadcom specific core.
  11. Addresses of AMBA devices are not hardcoded in driver and have to be read from
  12. EPROM.
  13. In this situation we decided to introduce separated bus. It can contain up to
  14. 16 devices identified by Broadcom specific fields: manufacturer, id, revision
  15. and class.