From: Kishore Batta <kishore.batta@oss.qualcomm.com>
To: Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Jeff Hugo <jeff.hugo@oss.qualcomm.com>,
Carl Vanderlip <carl.vanderlip@oss.qualcomm.com>,
Oded Gabbay <ogabbay@kernel.org>,
Manivannan Sadhasivam <mani@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
mhi@lists.linux.dev,
Kishore Batta <kishore.batta@oss.qualcomm.com>
Subject: [PATCH v3 3/9] bus: mhi: Match devices exposing the protocol on the SAHARA channel
Date: Tue, 10 Mar 2026 12:52:00 +0530 [thread overview]
Message-ID: <20260310-sahara_protocol_new_v2-v3-3-994ea4b0d5ad@oss.qualcomm.com> (raw)
In-Reply-To: <20260310-sahara_protocol_new_v2-v3-0-994ea4b0d5ad@oss.qualcomm.com>
Some Qualcomm devices expose the Sahara protocol on a generic SAHARA MHI
channel rather than a QAIC specific channel name. As a result, the sahara
driver does not currently bind to such devices and never probes.
Extend the MHI device ID match table to also match the SAHARA channel
name. This allows the Sahara protocol driver to bind to devices that
expose the protocol directly on a standard sahara MHI channel.
Signed-off-by: Kishore Batta <kishore.batta@oss.qualcomm.com>
---
drivers/bus/mhi/sahara/sahara.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/bus/mhi/sahara/sahara.c b/drivers/bus/mhi/sahara/sahara.c
index 8ff7b6425ac5423ef8f32117151dca10397686a8..e3499977e7c6b53bc624a8eb00d0636f2ea63307 100644
--- a/drivers/bus/mhi/sahara/sahara.c
+++ b/drivers/bus/mhi/sahara/sahara.c
@@ -911,8 +911,10 @@ static void sahara_mhi_dl_xfer_cb(struct mhi_device *mhi_dev, struct mhi_result
static const struct mhi_device_id sahara_mhi_match_table[] = {
{ .chan = "QAIC_SAHARA", },
+ { .chan = "SAHARA"},
{},
};
+MODULE_DEVICE_TABLE(mhi, sahara_mhi_match_table);
static struct mhi_driver sahara_mhi_driver = {
.id_table = sahara_mhi_match_table,
--
2.34.1
next prev parent reply other threads:[~2026-03-10 7:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 7:21 [PATCH v3 0/9] Qualcomm Sahara protocol enhancements Kishore Batta
2026-03-10 7:21 ` [PATCH v3 1/9] Add documentation for Sahara protocol Kishore Batta
2026-03-11 3:35 ` Claude review: " Claude Code Review Bot
2026-03-10 7:21 ` [PATCH v3 2/9] bus: mhi: Move sahara protocol driver under drivers/bus/mhi Kishore Batta
2026-03-11 3:35 ` Claude review: " Claude Code Review Bot
2026-03-10 7:22 ` Kishore Batta [this message]
2026-03-11 3:35 ` Claude review: bus: mhi: Match devices exposing the protocol on the SAHARA channel Claude Code Review Bot
2026-03-10 7:22 ` [PATCH v3 4/9] bus: mhi: Centralize firmware image table selection at probe time Kishore Batta
2026-03-11 3:35 ` Claude review: " Claude Code Review Bot
2026-03-10 7:22 ` [PATCH v3 5/9] bus: mhi: Add QDU100 variant and image_id firmware fallback Kishore Batta
2026-03-11 3:35 ` Claude review: " Claude Code Review Bot
2026-03-10 7:22 ` [PATCH v3 6/9] bus: mhi: Load DDR training data using per-device serial number Kishore Batta
2026-03-11 3:35 ` Claude review: " Claude Code Review Bot
2026-03-10 7:22 ` [PATCH v3 7/9] bus: mhi: Capture DDR training data using command mode Kishore Batta
2026-03-11 3:35 ` Claude review: " Claude Code Review Bot
2026-03-10 7:22 ` [PATCH v3 8/9] bus: mhi: Expose DDR training data via controller sysfs Kishore Batta
2026-03-11 3:35 ` Claude review: " Claude Code Review Bot
2026-03-10 7:22 ` [PATCH v3 9/9] Documentation: ABI: Add sysfs ABI documentation for DDR training data Kishore Batta
2026-03-11 3:35 ` Claude review: " Claude Code Review Bot
2026-03-11 3:35 ` Claude review: Qualcomm Sahara protocol enhancements Claude Code Review Bot
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=20260310-sahara_protocol_new_v2-v3-3-994ea4b0d5ad@oss.qualcomm.com \
--to=kishore.batta@oss.qualcomm.com \
--cc=carl.vanderlip@oss.qualcomm.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mhi@lists.linux.dev \
--cc=ogabbay@kernel.org \
--cc=skhan@linuxfoundation.org \
/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