omap-mailbox.txt 4.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108
  1. OMAP2+ Mailbox Driver
  2. =====================
  3. The OMAP mailbox hardware facilitates communication between different processors
  4. using a queued mailbox interrupt mechanism. The IP block is external to the
  5. various processor subsystems and is connected on an interconnect bus. The
  6. communication is achieved through a set of registers for message storage and
  7. interrupt configuration registers.
  8. Each mailbox IP block has a certain number of h/w fifo queues and output
  9. interrupt lines. An output interrupt line is routed to an interrupt controller
  10. within a processor subsystem, and there can be more than one line going to a
  11. specific processor's interrupt controller. The interrupt line connections are
  12. fixed for an instance and are dictated by the IP integration into the SoC
  13. (excluding the SoCs that have a Interrupt Crossbar IP). Each interrupt line is
  14. programmable through a set of interrupt configuration registers, and have a rx
  15. and tx interrupt source per h/w fifo. Communication between different processors
  16. is achieved through the appropriate programming of the rx and tx interrupt
  17. sources on the appropriate interrupt lines.
  18. The number of h/w fifo queues and interrupt lines dictate the usable registers.
  19. All the current OMAP SoCs except for the newest DRA7xx SoC has a single IP
  20. instance. DRA7xx has multiple instances with different number of h/w fifo queues
  21. and interrupt lines between different instances. The interrupt lines can also be
  22. routed to different processor sub-systems on DRA7xx as they are routed through
  23. the Crossbar, a kind of interrupt router/multiplexer.
  24. Mailbox Device Node:
  25. ====================
  26. A Mailbox device node is used to represent a Mailbox IP instance within a SoC.
  27. The sub-mailboxes are represented as child nodes of this parent node.
  28. Required properties:
  29. --------------------
  30. - compatible: Should be one of the following,
  31. "ti,omap2-mailbox" for OMAP2420, OMAP2430 SoCs
  32. "ti,omap3-mailbox" for OMAP3430, OMAP3630 SoCs
  33. "ti,omap4-mailbox" for OMAP44xx, OMAP54xx, AM33xx,
  34. AM43xx and DRA7xx SoCs
  35. - reg: Contains the mailbox register address range (base
  36. address and length)
  37. - interrupts: Contains the interrupt information for the mailbox
  38. device. The format is dependent on which interrupt
  39. controller the OMAP device uses
  40. - ti,hwmods: Name of the hwmod associated with the mailbox
  41. - ti,mbox-num-users: Number of targets (processor devices) that the mailbox
  42. device can interrupt
  43. - ti,mbox-num-fifos: Number of h/w fifo queues within the mailbox IP block
  44. Child Nodes:
  45. ============
  46. A child node is used for representing the actual sub-mailbox device that is
  47. used for the communication between the host processor and a remote processor.
  48. Each child node should have a unique node name across all the different
  49. mailbox device nodes.
  50. Required properties:
  51. --------------------
  52. - ti,mbox-tx: sub-mailbox descriptor property defining a Tx fifo
  53. - ti,mbox-rx: sub-mailbox descriptor property defining a Rx fifo
  54. Sub-mailbox Descriptor Data
  55. ---------------------------
  56. Each of the above ti,mbox-tx and ti,mbox-rx properties should have 3 cells of
  57. data that represent the following:
  58. Cell #1 (fifo_id) - mailbox fifo id used either for transmitting
  59. (ti,mbox-tx) or for receiving (ti,mbox-rx)
  60. Cell #2 (irq_id) - irq identifier index number to use from the parent's
  61. interrupts data. Should be 0 for most of the cases, a
  62. positive index value is seen only on mailboxes that have
  63. multiple interrupt lines connected to the MPU processor.
  64. Cell #3 (usr_id) - mailbox user id for identifying the interrupt line
  65. associated with generating a tx/rx fifo interrupt.
  66. Example:
  67. --------
  68. /* OMAP4 */
  69. mailbox: mailbox@4a0f4000 {
  70. compatible = "ti,omap4-mailbox";
  71. reg = <0x4a0f4000 0x200>;
  72. interrupts = <GIC_SPI 26 IRQ_TYPE_LEVEL_HIGH>;
  73. ti,hwmods = "mailbox";
  74. ti,mbox-num-users = <3>;
  75. ti,mbox-num-fifos = <8>;
  76. mbox_ipu: mbox_ipu {
  77. ti,mbox-tx = <0 0 0>;
  78. ti,mbox-rx = <1 0 0>;
  79. };
  80. mbox_dsp: mbox_dsp {
  81. ti,mbox-tx = <3 0 0>;
  82. ti,mbox-rx = <2 0 0>;
  83. };
  84. };
  85. /* AM33xx */
  86. mailbox: mailbox@480C8000 {
  87. compatible = "ti,omap4-mailbox";
  88. reg = <0x480C8000 0x200>;
  89. interrupts = <77>;
  90. ti,hwmods = "mailbox";
  91. ti,mbox-num-users = <4>;
  92. ti,mbox-num-fifos = <8>;
  93. mbox_wkupm3: wkup_m3 {
  94. ti,mbox-tx = <0 0 0>;
  95. ti,mbox-rx = <0 0 3>;
  96. };
  97. };