From: Sumit Kumar <sumit.kumar@oss.qualcomm.com>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>,
Akhil Vinod <akhil.vinod@oss.qualcomm.com>,
Subramanian Ananthanarayanan
<subramanian.ananthanarayanan@oss.qualcomm.com>,
linux-kernel@vger.kernel.org, mhi@lists.linux.dev,
linux-arm-msm@vger.kernel.org, quic_vpernami@quicinc.com,
Sumit Kumar <sumit.kumar@oss.qualcomm.com>
Subject: [PATCH v2 0/3] bus: mhi: Add loopback driver
Date: Tue, 04 Nov 2025 11:09:04 +0530 [thread overview]
Message-ID: <20251104-loopback_mhi-v2-0-727a3fd9aa74@oss.qualcomm.com> (raw)
This series adds MHI loopback drivers to enable comprehensive testing and
validation of MHI data path functionality between host controllers and
endpoint devices. The drivers support configurable transfer sizes, TRE
chaining, and provide real-time status reporting for thorough testing.
Testing is initiated with sysfs entries from the host side and results are
reflected back in the sysfs entry.
The device side driver echoes back the data recieved.
Signed-off-by: Sumit Kumar <sumit.kumar@oss.qualcomm.com>
---
Changes in v2:
- Use __free(kfree) macro for buffers
- Removed NET layer socket buffer dependency, now using buffer and len
- Created a New Api for queuing buffers for clients which do not use skb
- Link to v1: https://lore.kernel.org/r/20250923-loopback_mhi-v1-0-8618f31f44aa@oss.qualcomm.com
---
Sumit Kumar (3):
bus: mhi: host: Add loopback driver with sysfs interface
bus: mhi: ep: Create mhi_ep_queue_buf API for raw buffer queuing
bus: mhi: ep: Add loopback driver for data path testing
drivers/bus/mhi/ep/Kconfig | 8 +
drivers/bus/mhi/ep/Makefile | 1 +
drivers/bus/mhi/ep/main.c | 23 ++-
drivers/bus/mhi/ep/mhi_ep_loopback.c | 134 ++++++++++++++
drivers/bus/mhi/host/Kconfig | 7 +
drivers/bus/mhi/host/Makefile | 1 +
drivers/bus/mhi/host/mhi_loopback.c | 347 +++++++++++++++++++++++++++++++++++
include/linux/mhi_ep.h | 10 +
8 files changed, 525 insertions(+), 6 deletions(-)
---
base-commit: e6b9dce0aeeb91dfc0974ab87f02454e24566182
change-id: 20250903-loopback_mhi-dee55ff0d462
Best regards,
--
Sumit Kumar <sumit.kumar@oss.qualcomm.com>
next reply other threads:[~2025-11-04 5:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 5:39 Sumit Kumar [this message]
2025-11-04 5:39 ` [PATCH v2 1/3] bus: mhi: host: Add loopback driver with sysfs interface Sumit Kumar
2025-11-05 22:17 ` Bjorn Andersson
2025-11-07 12:28 ` Manivannan Sadhasivam
2025-11-10 4:00 ` Bjorn Andersson
2025-11-10 6:26 ` Manivannan Sadhasivam
2025-11-10 14:28 ` Bjorn Andersson
2025-11-04 5:39 ` [PATCH v2 2/3] bus: mhi: ep: Create mhi_ep_queue_buf API for raw buffer queuing Sumit Kumar
2025-11-05 22:20 ` Bjorn Andersson
2025-11-04 5:39 ` [PATCH v2 3/3] bus: mhi: ep: Add loopback driver for data path testing Sumit Kumar
2025-11-05 22:31 ` Bjorn Andersson
2025-11-09 22:40 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251104-loopback_mhi-v2-0-727a3fd9aa74@oss.qualcomm.com \
--to=sumit.kumar@oss.qualcomm.com \
--cc=akhil.vinod@oss.qualcomm.com \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mhi@lists.linux.dev \
--cc=quic_vpernami@quicinc.com \
--cc=subramanian.ananthanarayanan@oss.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox