olerem / icc

inter chip communication

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

icc

inter chip communication

Possible client drivers:

  • char (generic, do what you want)
  • gpio extender
  • rtc
  • watchdog
  • CAN
  • rfkill

Notes:

  • determenistic (to avoid real-time word).
  • async. Sync communication on linux is expensive. (async need timeout to responde. Async need timout to responde as well, why should we wait any way?)
  • agregation. most communications use tiny packets. tiny packets are very expensive.
  • queue. aggregation is possible only with a queue.

Information collection for different Interchip and Intra Chip communication

TODO: 3946R, RK512, Modbus, IEC870, MEWTOCOL, AK, MPI, LSV2, Interbus, DeviceNet, MSV2:

Examples of Interchip Chip Communication:

Intra Chip Communication

  • Different variants of Virtualisation

  • Name, HIF/PHY, Transport
  • ath9k-htc, USB, OSI2(HTC) + OSI3(WMI)
  • ath10k, PCIe, HTC
  • ath6kl, SDIO, HTC
  • n900, OMAP HSI, ???
  • n_gsm.c TTY gsmmux
  • n_3964 TTY OSI2 (3964r) + OSI3(RK512)

What is the difference between plain master slave communication and ICC? Abstraction level? Plaint Master-Slave: Slave_HW->Master_Bus->Bus_Driver->Slave_Driver ICC: Diff_functionalities->Slave_HW->Master_Bus->Bus_Driver->Multiple_Func_drivers

About

inter chip communication