qcom,smp2p.txt 3.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105
  1. Qualcomm Shared Memory Point 2 Point binding
  2. The Shared Memory Point to Point (SMP2P) protocol facilitates communication of
  3. a single 32-bit value between two processors. Each value has a single writer
  4. (the local side) and a single reader (the remote side). Values are uniquely
  5. identified in the system by the directed edge (local processor ID to remote
  6. processor ID) and a string identifier.
  7. - compatible:
  8. Usage: required
  9. Value type: <string>
  10. Definition: must be one of:
  11. "qcom,smp2p"
  12. - interrupts:
  13. Usage: required
  14. Value type: <prop-encoded-array>
  15. Definition: one entry specifying the smp2p notification interrupt
  16. - qcom,ipc:
  17. Usage: required
  18. Value type: <prop-encoded-array>
  19. Definition: three entries specifying the outgoing ipc bit used for
  20. signaling the remote end of the smp2p edge:
  21. - phandle to a syscon node representing the apcs registers
  22. - u32 representing offset to the register within the syscon
  23. - u32 representing the ipc bit within the register
  24. - qcom,smem:
  25. Usage: required
  26. Value type: <u32 array>
  27. Definition: two identifiers of the inbound and outbound smem items used
  28. for this edge
  29. - qcom,local-pid:
  30. Usage: required
  31. Value type: <u32>
  32. Definition: specifies the identfier of the local endpoint of this edge
  33. - qcom,remote-pid:
  34. Usage: required
  35. Value type: <u32>
  36. Definition: specifies the identfier of the remote endpoint of this edge
  37. = SUBNODES
  38. Each SMP2P pair contain a set of inbound and outbound entries, these are
  39. described in subnodes of the smp2p device node. The node names are not
  40. important.
  41. - qcom,entry-name:
  42. Usage: required
  43. Value type: <string>
  44. Definition: specifies the name of this entry, for inbound entries this
  45. will be used to match against the remotely allocated entry
  46. and for outbound entries this name is used for allocating
  47. entries
  48. - interrupt-controller:
  49. Usage: required for incoming entries
  50. Value type: <empty>
  51. Definition: marks the entry as inbound; the node should be specified
  52. as a two cell interrupt-controller as defined in
  53. "../interrupt-controller/interrupts.txt"
  54. If not specified this node will denote the outgoing entry
  55. - #interrupt-cells:
  56. Usage: required for incoming entries
  57. Value type: <u32>
  58. Definition: must be 2 - denoting the bit in the entry and IRQ flags
  59. - #qcom,smem-state-cells:
  60. Usage: required for outgoing entries
  61. Value type: <u32>
  62. Definition: must be 1 - denoting the bit in the entry
  63. = EXAMPLE
  64. The following example shows the SMP2P setup with the wireless processor,
  65. defined from the 8974 apps processor's point-of-view. It encompasses one
  66. inbound and one outbound entry:
  67. wcnss-smp2p {
  68. compatible = "qcom,smp2p";
  69. qcom,smem = <431>, <451>;
  70. interrupts = <0 143 1>;
  71. qcom,ipc = <&apcs 8 18>;
  72. qcom,local-pid = <0>;
  73. qcom,remote-pid = <4>;
  74. wcnss_smp2p_out: master-kernel {
  75. qcom,entry-name = "master-kernel";
  76. #qcom,smem-state-cells = <1>;
  77. };
  78. wcnss_smp2p_in: slave-kernel {
  79. qcom,entry-name = "slave-kernel";
  80. interrupt-controller;
  81. #interrupt-cells = <2>;
  82. };
  83. };