From: Jeffrey Hugo <quic_jhugo@quicinc.com>
To: Slark Xiao <slark_xiao@163.com>,
<manivannan.sadhasivam@linaro.org>, <loic.poulain@linaro.org>,
<ryazanov.s.a@gmail.com>, <johannes@sipsolutions.net>
Cc: <netdev@vger.kernel.org>, <mhi@lists.linux.dev>,
<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/3] bus: mhi: host: Add name for mhi_controller
Date: Fri, 28 Jun 2024 08:38:57 -0600 [thread overview]
Message-ID: <cde35f69-4d6e-d46d-88ca-9c5d6d5e757f@quicinc.com> (raw)
In-Reply-To: <20240628073626.1447288-1-slark_xiao@163.com>
On 6/28/2024 1:36 AM, Slark Xiao wrote:
> For SDX72 MBIM mode, it starts data mux id from 112 instead of 0.
> This would lead to device can't ping outside successfully.
> Also MBIM side would report "bad packet session (112)".
Weird indentation
> In oder to fix this issue, we decide to use the modem name
"order"
> to do a match in client driver side. Then client driver could
> set a corresponding mux_id value for this modem product.
>
> Signed-off-by: Slark Xiao <slark_xiao@163.com>
> ---
> drivers/bus/mhi/host/pci_generic.c | 1 +
> include/linux/mhi.h | 2 ++
> 2 files changed, 3 insertions(+)
>
> diff --git a/drivers/bus/mhi/host/pci_generic.c b/drivers/bus/mhi/host/pci_generic.c
> index 1fb1c2f2fe12..14a11880bcea 100644
> --- a/drivers/bus/mhi/host/pci_generic.c
> +++ b/drivers/bus/mhi/host/pci_generic.c
> @@ -1086,6 +1086,7 @@ static int mhi_pci_probe(struct pci_dev *pdev, const struct pci_device_id *id)
> mhi_cntrl->runtime_get = mhi_pci_runtime_get;
> mhi_cntrl->runtime_put = mhi_pci_runtime_put;
> mhi_cntrl->mru = info->mru_default;
> + mhi_cntrl->name = info->name;
>
> if (info->edl_trigger)
> mhi_cntrl->edl_trigger = mhi_pci_generic_edl_trigger;
> diff --git a/include/linux/mhi.h b/include/linux/mhi.h
> index b573f15762f8..86aa4f52842c 100644
> --- a/include/linux/mhi.h
> +++ b/include/linux/mhi.h
> @@ -361,6 +361,7 @@ struct mhi_controller_config {
> * @wake_set: Device wakeup set flag
> * @irq_flags: irq flags passed to request_irq (optional)
> * @mru: the default MRU for the MHI device
> + * @name: name of the modem
Why restrict this to modems? There are plenty of other MHI devices
> *
> * Fields marked as (required) need to be populated by the controller driver
> * before calling mhi_register_controller(). For the fields marked as (optional)
> @@ -445,6 +446,7 @@ struct mhi_controller {
> bool wake_set;
> unsigned long irq_flags;
> u32 mru;
> + const char *name;
Please run pahole
> };
>
> /**
next prev parent reply other threads:[~2024-06-28 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 7:36 Slark Xiao
2024-06-28 14:38 ` Jeffrey Hugo [this message]
2024-06-29 8:03 ` Slark Xiao
2024-06-29 12:03 ` Manivannan Sadhasivam
2024-06-28 8:29 [PATCH v3 1/3] bus: mhi: host: Add Foxconn SDX72 related support Slark Xiao
2024-06-28 8:29 ` [PATCH v3 2/3] bus: mhi: host: Add name for mhi_controller Slark Xiao
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=cde35f69-4d6e-d46d-88ca-9c5d6d5e757f@quicinc.com \
--to=quic_jhugo@quicinc.com \
--cc=johannes@sipsolutions.net \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mhi@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=ryazanov.s.a@gmail.com \
--cc=slark_xiao@163.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®