On 8/20/25 1:10 PM, Jonathan Cormier wrote:
Add trace events to help debug and measure the speed of the
communication channel.
Add parsing of the messages types but I am not sure how to parse the
flags, since the REQ and RESP flags conflict. Left as seperate commit to
The REQ and RESP flags should be handled by different TRACE_EVENTs. Right
now you only dump the content of the response messages (the ones in
rx_callback), also tracing what is sent is just as important, so you
might want to add slightly different ti_sci_msg_dump EVENT for the
sending side which uses the different REQ flag parser.
Andrew
make it easier to drop or make changes depending on comments. The two
commits should squash easily.
Nishanth Menon and Vignesh Raghavendra requested I send this patch
upstream.
Signed-off-by: Jonathan Cormier <[email protected]>
---
Jonathan Cormier (2):
firmware: ti_sci: Add trace events
firmware: ti_sci: trace: Decode message types
MAINTAINERS | 1 +
drivers/firmware/Makefile | 3 +
drivers/firmware/ti_sci.c | 11 +++
drivers/firmware/ti_sci_trace.h | 146 ++++++++++++++++++++++++++++++++++++++++
4 files changed, 161 insertions(+)
---
base-commit: d7b8f8e20813f0179d8ef519541a3527e7661d3a
change-id: 20250709-linux_master_ti_sci_trace-91fd2af65dca
Best regards,
