diff options
| author | Sumit Kumar <sumit.kumar@oss.qualcomm.com> | 2026-10-05 16:09:29 +0530 |
|---|---|---|
| committer | Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com> | 2026-10-11 21:52:20 +0530 |
| commit | dd93cef28dcb604375236a9cfa8c683e25b66e33 (patch) | |
| tree | 9e0fb92fa55491ae844b535ebf688ca487b54613 /tools/perf/scripts/python | |
| parent | f6985f512f82757f4aad13bad87039c9190b1466 (diff) | |
| download | linux-next-dd93cef28dcb604375236a9cfa8c683e25b66e33.tar.gz linux-next-dd93cef28dcb604375236a9cfa8c683e25b66e33.zip | |
bus: mhi: host: clients: Add loopback driver with sysfs interface
The MHI specification defines a LOOPBACK channel. The endpoint firmware
echoes back whatever the host sends on this channel. Without a host-side
driver, there is no way to exercise this channel to validate MHI data path
integrity between host and endpoint.
Add a host-side loopback driver that binds to the LOOPBACK channel and
expose a sysfs interface for data path testing. The sysfs interface allows
users to configure TRE buffer size and count, trigger a loopback test, and
read the result.
The new sysfs ABI is documented under Documentation/ABI/testing/, not
stable/, since this is a new interface without established API
guarantees yet. It is unrelated to the existing stable MHI sysfs ABI
documented in Documentation/ABI/stable/sysfs-bus-mhi, despite both
being covered by the same MAINTAINERS entry.
Co-developed-by: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
Signed-off-by: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
Signed-off-by: Sumit Kumar <sumit.kumar@oss.qualcomm.com>
Link: https://patch.msgid.link/20261005-lb-v7-1-36a268b6386f@oss.qualcomm.com
Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions