Based on kernel version 6.16. Page generated on 2025-08-06 08:56 EST.
| 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 | What: /sys/kernel/debug/scmi/<n>/raw/message Date: March 2023 KernelVersion: 6.3 Contact: cristian.marussi@arm.com Description: SCMI Raw synchronous message injection/snooping facility; write a complete SCMI synchronous command message (header included) in little-endian binary format to have it sent to the configured backend SCMI server for instance <n>. Any subsequently received response can be read from this same entry if it arrived within the configured timeout. Each write to the entry causes one command request to be built and sent while the replies are read back one message at time (receiving an EOF at each message boundary). Users: Debugging, any userspace test suite What: /sys/kernel/debug/scmi/<n>/raw/message_async Date: March 2023 KernelVersion: 6.3 Contact: cristian.marussi@arm.com Description: SCMI Raw asynchronous message injection/snooping facility; write a complete SCMI asynchronous command message (header included) in little-endian binary format to have it sent to the configured backend SCMI server for instance <n>. Any subsequently received response can be read from this same entry if it arrived within the configured timeout. Any additional delayed response received afterwards can be read from this same entry too if it arrived within the configured timeout. Each write to the entry causes one command request to be built and sent while the replies are read back one message at time (receiving an EOF at each message boundary). Users: Debugging, any userspace test suite What: /sys/kernel/debug/scmi/<n>/raw/message_poll Date: June 2025 KernelVersion: 6.16 Contact: cristian.marussi@arm.com Description: SCMI Raw message injection/snooping facility using polling mode; write a complete SCMI command message (header included) in little-endian binary format to have it sent to the configured backend SCMI server for instance <n>, using polling mode on the reception path. (if transport is polling capable) Any subsequently received response can be read from this same entry if it arrived within the configured timeout. Each write to the entry causes one command request to be built and sent while the replies are read back one message at time (receiving an EOF at each message boundary). Users: Debugging, any userspace test suite What: /sys/kernel/debug/scmi/<n>/raw/message_poll_async Date: June 2025 KernelVersion: 6.16 Contact: cristian.marussi@arm.com Description: SCMI Raw asynchronous message injection/snooping facility using polling-mode; write a complete SCMI asynchronous command message (header included) in little-endian binary format to have it sent to the configured backend SCMI server for instance <n>, using polling-mode on the reception path of the immediate part of the asynchronous command. (if transport is polling capable) Any subsequently received response can be read from this same entry if it arrived within the configured timeout. Any additional delayed response received afterwards can be read from this same entry too if it arrived within the configured timeout. Each write to the entry causes one command request to be built and sent while the replies are read back one message at time (receiving an EOF at each message boundary). Users: Debugging, any userspace test suite What: /sys/kernel/debug/scmi/<n>/raw/errors Date: March 2023 KernelVersion: 6.3 Contact: cristian.marussi@arm.com Description: SCMI Raw message errors facility; any kind of timed-out or generally unexpectedly received SCMI message, for instance <n>, can be read from this entry. Each read gives back one message at time (receiving an EOF at each message boundary). Users: Debugging, any userspace test suite What: /sys/kernel/debug/scmi/<n>/raw/notification Date: March 2023 KernelVersion: 6.3 Contact: cristian.marussi@arm.com Description: SCMI Raw notification snooping facility; any notification emitted by the backend SCMI server, for instance <n>, can be read from this entry. Each read gives back one message at time (receiving an EOF at each message boundary). Users: Debugging, any userspace test suite What: /sys/kernel/debug/scmi/<n>/raw/reset Date: March 2023 KernelVersion: 6.3 Contact: cristian.marussi@arm.com Description: SCMI Raw stack reset facility; writing a value to this entry causes the internal queues of any kind of received message, still pending to be read out for instance <n>, to be immediately flushed. Can be used to reset and clean the SCMI Raw stack between to different test-run. Users: Debugging, any userspace test suite What: /sys/kernel/debug/scmi/<n>/raw/channels/<m>/message Date: March 2023 KernelVersion: 6.3 Contact: cristian.marussi@arm.com Description: SCMI Raw synchronous message injection/snooping facility; write a complete SCMI synchronous command message (header included) in little-endian binary format to have it sent to the configured backend SCMI server for instance <n> through the <m> transport channel. Any subsequently received response can be read from this same entry if it arrived on channel <m> within the configured timeout. Each write to the entry causes one command request to be built and sent while the replies are read back one message at time (receiving an EOF at each message boundary). Channel identifier <m> matches the SCMI protocol number which has been associated with this transport channel in the DT description, with base protocol number 0x10 being the default channel for this instance. Note that these per-channel entries rooted at <..>/channels exist only if the transport is configured to have more than one default channel. Users: Debugging, any userspace test suite What: /sys/kernel/debug/scmi/<n>/raw/channels/<m>/message_async Date: March 2023 KernelVersion: 6.3 Contact: cristian.marussi@arm.com Description: SCMI Raw asynchronous message injection/snooping facility; write a complete SCMI asynchronous command message (header included) in little-endian binary format to have it sent to the configured backend SCMI server for instance <n> through the <m> transport channel. Any subsequently received response can be read from this same entry if it arrived on channel <m> within the configured timeout. Any additional delayed response received afterwards can be read from this same entry too if it arrived within the configured timeout. Each write to the entry causes one command request to be built and sent while the replies are read back one message at time (receiving an EOF at each message boundary). Channel identifier <m> matches the SCMI protocol number which has been associated with this transport channel in the DT description, with base protocol number 0x10 being the default channel for this instance. Note that these per-channel entries rooted at <..>/channels exist only if the transport is configured to have more than one default channel. Users: Debugging, any userspace test suite What: /sys/kernel/debug/scmi/<n>/raw/channels/<m>/message_poll Date: June 2025 KernelVersion: 6.16 Contact: cristian.marussi@arm.com Description: SCMI Raw message injection/snooping facility using polling mode; write a complete SCMI command message (header included) in little-endian binary format to have it sent to the configured backend SCMI server for instance <n> through the <m> transport channel, using polling mode on the reception path. (if transport is polling capable) Any subsequently received response can be read from this same entry if it arrived on channel <m> within the configured timeout. Each write to the entry causes one command request to be built and sent while the replies are read back one message at time (receiving an EOF at each message boundary). Channel identifier <m> matches the SCMI protocol number which has been associated with this transport channel in the DT description, with base protocol number 0x10 being the default channel for this instance. Note that these per-channel entries rooted at <..>/channels exist only if the transport is configured to have more than one default channel. Users: Debugging, any userspace test suite What: /sys/kernel/debug/scmi/<n>/raw/channels/<m>/message_poll_async Date: June 2025 KernelVersion: 6.16 Contact: cristian.marussi@arm.com Description: SCMI Raw asynchronous message injection/snooping facility using polling-mode; write a complete SCMI asynchronous command message (header included) in little-endian binary format to have it sent to the configured backend SCMI server for instance <n> through the <m> transport channel, using polling mode on the reception path of the immediate part of the asynchronous command. (if transport is polling capable) Any subsequently received response can be read from this same entry if it arrived on channel <m> within the configured timeout. Any additional delayed response received afterwards can be read from this same entry too if it arrived within the configured timeout. Each write to the entry causes one command request to be built and sent while the replies are read back one message at time (receiving an EOF at each message boundary). Channel identifier <m> matches the SCMI protocol number which has been associated with this transport channel in the DT description, with base protocol number 0x10 being the default channel for this instance. Note that these per-channel entries rooted at <..>/channels exist only if the transport is configured to have more than one default channel. Users: Debugging, any userspace test suite |