From: Sumit Kumar <sumit.kumar@oss.qualcomm.com>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Manivannan Sadhasivam <mani@kernel.org>,
Jeff Hugo <jeff.hugo@oss.qualcomm.com>,
mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
Subject: Re: [PATCH v5 1/3] bus: mhi: host: clients: Add loopback driver with sysfs interface
Date: Wed, 19 Aug 2026 15:18:04 +0530 [thread overview]
Message-ID: <3dad5ae0-d5ff-4de5-9d02-2ccfd2a10127@oss.qualcomm.com> (raw)
In-Reply-To: <aoQbo-k7QA5YpUNm@monoceros>
On 8/18/2026 2:20 PM, Uwe Kleine-König wrote:
> Hello,
>
> On Mon, Aug 17, 2026 at 03:44:34PM +0530, Sumit Kumar wrote:
>> +#include <linux/mhi.h>
>> +#include <linux/mod_devicetable.h>
> Please rely on <linux/mhi.h> to provide mhi_device_id and drop the
> inclusion for <linux/mod_devicetable.h>. The latter header is ugly and
> should go away soon.
thanks, Will rebase and fix it
>
>> [...]
>> +static struct attribute *mhi_loopback_attrs[] = {
>> + &dev_attr_tre_size.attr,
>> + &dev_attr_max_tre_size.attr,
>> + &dev_attr_num_tre.attr,
>> + &dev_attr_start.attr,
>> + NULL,
> Please no , after sentinel entries.
Acknowledged, will remove it.
>
>> +};
>> +
>> +static const struct attribute_group mhi_loopback_group = {
>> + .attrs = mhi_loopback_attrs,
>> +};
>> +
>> +static int mhi_loopback_probe(struct mhi_device *mhi_dev,
>> + const struct mhi_device_id *id)
>> +{
>> + struct mhi_loopback *loopback;
>> + int ret;
>> +
>> + loopback = devm_kzalloc(&mhi_dev->dev, sizeof(*loopback), GFP_KERNEL);
>> + if (!loopback)
>> + return -ENOMEM;
>> +
>> + loopback->mdev = mhi_dev;
>> + loopback->tre_size = MHI_LOOPBACK_DEFAULT_TRE_SIZE;
>> + loopback->num_tre = MHI_LOOPBACK_DEFAULT_NUM_TRE;
>> +
>> + mutex_init(&loopback->lb_mutex);
>> + init_completion(&loopback->comp);
>> +
>> + dev_set_drvdata(&mhi_dev->dev, loopback);
>> +
>> + ret = mhi_prepare_for_transfer(mhi_dev);
>> + if (ret) {
>> + dev_err(&mhi_dev->dev, "Failed to prepare for transfers: %d\n", ret);
> dev_err_probe() please.
Sure.
>
>> + return ret;
>> + }
>> +
>> + ret = sysfs_create_group(&mhi_dev->dev.kobj, &mhi_loopback_group);
>> + if (ret) {
>> + dev_err(&mhi_dev->dev, "Failed to create sysfs attributes: %d\n", ret);
>> + mhi_unprepare_from_transfer(mhi_dev);
>> + return ret;
>> + }
>> +
>> + return 0;
>> +}
>> +
>> +static void mhi_loopback_remove(struct mhi_device *mhi_dev)
>> +{
>> + /* Blocks until any in-progress store() has returned */
>> + sysfs_remove_group(&mhi_dev->dev.kobj, &mhi_loopback_group);
>> + mhi_unprepare_from_transfer(mhi_dev);
>> +}
>> +
>> +static const struct mhi_device_id mhi_loopback_id_table[] = {
>> + { .chan = "LOOPBACK"},
>> + {}
> { } (i.e. a space between the curly braces) is the more common way to
> write that. Please also add a space before the closing } in the line
> above.
Will fix this too.
>
>> +};
>> +MODULE_DEVICE_TABLE(mhi, mhi_loopback_id_table);
> Best regards
> Uwe
next prev parent reply other threads:[~2026-08-19 9:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 10:14 [PATCH v5 0/3] bus: mhi: Add loopback driver Sumit Kumar
2026-08-17 10:14 ` [PATCH v5 1/3] bus: mhi: host: clients: Add loopback driver with sysfs interface Sumit Kumar
2026-08-17 20:14 ` Jeff Hugo
2026-08-19 9:46 ` Sumit Kumar
2026-08-18 8:50 ` Uwe Kleine-König
2026-08-19 9:48 ` Sumit Kumar [this message]
2026-08-17 10:14 ` [PATCH v5 2/3] bus: mhi: ep: Add mhi_ep_queue_buf() API for raw buffer queuing Sumit Kumar
2026-08-17 10:14 ` [PATCH v5 3/3] bus: mhi: ep: clients: Add loopback driver for data path testing Sumit Kumar
2026-08-18 8:53 ` Uwe Kleine-König
2026-08-19 9:48 ` Sumit Kumar
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=3dad5ae0-d5ff-4de5-9d02-2ccfd2a10127@oss.qualcomm.com \
--to=sumit.kumar@oss.qualcomm.com \
--cc=jeff.hugo@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=u.kleine-koenig@baylibre.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
all inboxes | Powered by JetHome®