brintos

brintos / linux-shallow public Read only

0
0
Text · 5.1 KiB · 97678cc Raw
118 lines · plain
1What:		/sys/kernel/debug/scmi/<n>/raw/message2Date:		March 20233KernelVersion:	6.34Contact:	cristian.marussi@arm.com5Description:	SCMI Raw synchronous message injection/snooping facility; write6		a complete SCMI synchronous command message (header included)7		in little-endian binary format to have it sent to the configured8		backend SCMI server for instance <n>.9		Any subsequently received response can be read from this same10		entry if it arrived within the configured timeout.11		Each write to the entry causes one command request to be built12		and sent while the replies are read back one message at time13		(receiving an EOF at each message boundary).14Users:		Debugging, any userspace test suite15 16What:		/sys/kernel/debug/scmi/<n>/raw/message_async17Date:		March 202318KernelVersion:	6.319Contact:	cristian.marussi@arm.com20Description:	SCMI Raw asynchronous message injection/snooping facility; write21		a complete SCMI asynchronous command message (header included)22		in little-endian binary format to have it sent to the configured23		backend SCMI server for instance <n>.24		Any subsequently received response can be read from this same25		entry if it arrived within the configured timeout.26		Any additional delayed response received afterwards can be read27		from this same entry too if it arrived within the configured28		timeout.29		Each write to the entry causes one command request to be built30		and sent while the replies are read back one message at time31		(receiving an EOF at each message boundary).32Users:		Debugging, any userspace test suite33 34What:		/sys/kernel/debug/scmi/<n>/raw/errors35Date:		March 202336KernelVersion:	6.337Contact:	cristian.marussi@arm.com38Description:	SCMI Raw message errors facility; any kind of timed-out or39		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 at42		each message boundary).43Users:		Debugging, any userspace test suite44 45What:		/sys/kernel/debug/scmi/<n>/raw/notification46Date:		March 202347KernelVersion:	6.348Contact:	cristian.marussi@arm.com49Description:	SCMI Raw notification snooping facility; any notification50		emitted by the backend SCMI server, for instance <n>, can be51		read from this entry.52		Each read gives back one message at time (receiving an EOF at53		each message boundary).54Users:		Debugging, any userspace test suite55 56What:		/sys/kernel/debug/scmi/<n>/raw/reset57Date:		March 202358KernelVersion:	6.359Contact:	cristian.marussi@arm.com60Description:	SCMI Raw stack reset facility; writing a value to this entry61		causes the internal queues of any kind of received message,62		still pending to be read out for instance <n>, to be immediately63		flushed.64		Can be used to reset and clean the SCMI Raw stack between to65		different test-run.66Users:		Debugging, any userspace test suite67 68What:		/sys/kernel/debug/scmi/<n>/raw/channels/<m>/message69Date:		March 202370KernelVersion:	6.371Contact:	cristian.marussi@arm.com72Description:	SCMI Raw synchronous message injection/snooping facility; write73		a complete SCMI synchronous command message (header included)74		in little-endian binary format to have it sent to the configured75		backend SCMI server for instance <n> through the <m> transport76		channel.77		Any subsequently received response can be read from this same78		entry if it arrived on channel <m> within the configured79		timeout.80		Each write to the entry causes one command request to be built81		and sent while the replies are read back one message at time82		(receiving an EOF at each message boundary).83		Channel identifier <m> matches the SCMI protocol number which84		has been associated with this transport channel in the DT85		description, with base protocol number 0x10 being the default86		channel for this instance.87		Note that these per-channel entries rooted at <..>/channels88		exist only if the transport is configured to have more than89		one default channel.90Users:		Debugging, any userspace test suite91 92What:		/sys/kernel/debug/scmi/<n>/raw/channels/<m>/message_async93Date:		March 202394KernelVersion:	6.395Contact:	cristian.marussi@arm.com96Description:	SCMI Raw asynchronous message injection/snooping facility; write97		a complete SCMI asynchronous command message (header included)98		in little-endian binary format to have it sent to the configured99		backend SCMI server for instance <n> through the <m> transport100		channel.101		Any subsequently received response can be read from this same102		entry if it arrived on channel <m> within the configured103		timeout.104		Any additional delayed response received afterwards can be read105		from this same entry too if it arrived within the configured106		timeout.107		Each write to the entry causes one command request to be built108		and sent while the replies are read back one message at time109		(receiving an EOF at each message boundary).110		Channel identifier <m> matches the SCMI protocol number which111		has been associated with this transport channel in the DT112		description, with base protocol number 0x10 being the default113		channel for this instance.114		Note that these per-channel entries rooted at <..>/channels115		exist only if the transport is configured to have more than116		one default channel.117Users:		Debugging, any userspace test suite118