summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin
diff options
context:
space:
mode:
authorBeleswar Padhi <b-padhi@ti.com>2026-10-01 01:31:57 +0530
committerJassi Brar <jassisinghbrar@gmail.com>2026-10-11 19:50:47 -0500
commitbbf7f0d6162fc68af1fc0c7ad1c5e35a3e64010a (patch)
tree8e79ad67fe2b3ce5571716df428529610cb13651 /tools/perf/scripts/python/bin
parent65dacbb315a2a842a21979b5c3f27eccd72b215a (diff)
mailbox: ti-msgmgr: Do not report rx poll timeout as a send failure
In polled rx mode, used from system suspend until resume, ti_msgmgr_send_data() writes the message to the tx queue and then waits for the response. If no response arrives in time it returns the poll error. The mailbox core treats a ->send_data() error as a send failure. So, it leaves the message queued without making it the active request, and mbox_send_message() still returns success. The message is then submitted again on the next tx_tick() or mbox_send_message(), after the client has probably timed out and moved on. So, the firmware receives the same message twice, and later requests are sent late and can have responses matched to the wrong request. The message has already been transmitted at this point, so return 0 and only log the missing response. The client detects this case with its own response timeout anyways. Signed-off-by: Beleswar Padhi <b-padhi@ti.com> Acked-by: Andrew Davis <afd@ti.com> Signed-off-by: Jassi Brar <jassisinghbrar@gmail.com>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions