1What:		/sys/kernel/debug/scmi/<n>/raw/message
2Date:		March 2023
3KernelVersion:	6.3
4Contact:	cristian.marussi@arm.com
5Description:	SCMI Raw synchronous message injection/snooping facility; write
6		a complete SCMI synchronous command message (header included)
7		in little-endian binary format to have it sent to the configured
8		backend SCMI server for instance <n>.
9		Any subsequently received response can be read from this same
10		entry if it arrived within the configured timeout.
11		Each write to the entry causes one command request to be built
12		and sent while the replies are read back one message at time
13		(receiving an EOF at each message boundary).
14Users:		Debugging, any userspace test suite
15
16What:		/sys/kernel/debug/scmi/<n>/raw/message_async
17Date:		March 2023
18KernelVersion:	6.3
19Contact:	cristian.marussi@arm.com
20Description:	SCMI Raw asynchronous message injection/snooping facility; write
21		a complete SCMI asynchronous command message (header included)
22		in little-endian binary format to have it sent to the configured
23		backend SCMI server for instance <n>.
24		Any subsequently received response can be read from this same
25		entry if it arrived within the configured timeout.
26		Any additional delayed response received afterwards can be read
27		from this same entry too if it arrived within the configured
28		timeout.
29		Each write to the entry causes one command request to be built
30		and sent while the replies are read back one message at time
31		(receiving an EOF at each message boundary).
32Users:		Debugging, any userspace test suite
33
34What:		/sys/kernel/debug/scmi/<n>/raw/errors
35Date:		March 2023
36KernelVersion:	6.3
37Contact:	cristian.marussi@arm.com
38Description:	SCMI Raw message errors facility; any kind of timed-out or
39		generally unexpectedly received SCMI message, for instance <n>,
40		can be read from this entry.
41		Each read gives back one message at time (receiving an EOF at
42		each message boundary).
43Users:		Debugging, any userspace test suite
44
45What:		/sys/kernel/debug/scmi/<n>/raw/notification
46Date:		March 2023
47KernelVersion:	6.3
48Contact:	cristian.marussi@arm.com
49Description:	SCMI Raw notification snooping facility; any notification
50		emitted by the backend SCMI server, for instance <n>, can be
51		read from this entry.
52		Each read gives back one message at time (receiving an EOF at
53		each message boundary).
54Users:		Debugging, any userspace test suite
55
56What:		/sys/kernel/debug/scmi/<n>/raw/reset
57Date:		March 2023
58KernelVersion:	6.3
59Contact:	cristian.marussi@arm.com
60Description:	SCMI Raw stack reset facility; writing a value to this entry
61		causes the internal queues of any kind of received message,
62		still pending to be read out for instance <n>, to be immediately
63		flushed.
64		Can be used to reset and clean the SCMI Raw stack between to
65		different test-run.
66Users:		Debugging, any userspace test suite
67
68What:		/sys/kernel/debug/scmi/<n>/raw/channels/<m>/message
69Date:		March 2023
70KernelVersion:	6.3
71Contact:	cristian.marussi@arm.com
72Description:	SCMI Raw synchronous message injection/snooping facility; write
73		a complete SCMI synchronous command message (header included)
74		in little-endian binary format to have it sent to the configured
75		backend SCMI server for instance <n> through the <m> transport
76		channel.
77		Any subsequently received response can be read from this same
78		entry if it arrived on channel <m> within the configured
79		timeout.
80		Each write to the entry causes one command request to be built
81		and sent while the replies are read back one message at time
82		(receiving an EOF at each message boundary).
83		Note that these per-channel entries rooted at <..>/channels
84		exist only if the transport is configured to have more than
85		one channel.
86Users:		Debugging, any userspace test suite
87
88What:		/sys/kernel/debug/scmi/<n>/raw/channels/<m>/message_async
89Date:		March 2023
90KernelVersion:	6.3
91Contact:	cristian.marussi@arm.com
92Description:	SCMI Raw asynchronous message injection/snooping facility; write
93		a complete SCMI asynchronous command message (header included)
94		in little-endian binary format to have it sent to the configured
95		backend SCMI server for instance <n> through the <m> transport
96		channel.
97		Any subsequently received response can be read from this same
98		entry if it arrived on channel <m> within the configured
99		timeout.
100		Any additional delayed response received afterwards can be read
101		from this same entry too if it arrived within the configured
102		timeout.
103		Each write to the entry causes one command request to be built
104		and sent while the replies are read back one message at time
105		(receiving an EOF at each message boundary).
106		Note that these per-channel entries rooted at <..>/channels
107		exist only if the transport is configured to have more than
108		one channel.
109Users:		Debugging, any userspace test suite
110