mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Slark Xiao" <slark_xiao@163.com>
To: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>
Cc: "Loic Poulain" <loic.poulain@oss.qualcomm.com>,
	mani@kernel.org, ryazanov.s.a@gmail.com,
	johannes@sipsolutions.net, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, mhi@lists.linux.dev,
	linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re:Re: [PATCH v3 2/2] net: wwan: mhi: Add network support for Foxconn T99W760
Date: Thu, 20 Nov 2025 11:04:09 +0800 (CST)	[thread overview]
Message-ID: <5d61df3a.2f2f.19a9f382a58.Coremail.slark_xiao@163.com> (raw)
In-Reply-To: <rchyzpkfozxd55x4mvpsz2toz7j26yeww7yjiios3uky734lnq@rtuiloh6aokm>

At 2025-11-19 21:47:33, "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com> wrote:
>On Wed, Nov 19, 2025 at 02:08:33PM +0100, Loic Poulain wrote:
>> On Wed, Nov 19, 2025 at 12:27 PM Dmitry Baryshkov
>> <dmitry.baryshkov@oss.qualcomm.com> wrote:
>> >
>> > On Wed, Nov 19, 2025 at 06:56:15PM +0800, Slark Xiao wrote:
>> > > T99W760 is designed based on Qualcomm SDX35 chip. It use similar
>> > > architechture with SDX72/SDX75 chip. So we need to assign initial
>> > > link id for this device to make sure network available.
>> > >
>> > > Signed-off-by: Slark Xiao <slark_xiao@163.com>
>> > > ---
>> > >  drivers/net/wwan/mhi_wwan_mbim.c | 3 ++-
>> > >  1 file changed, 2 insertions(+), 1 deletion(-)
>> > >
>> > > diff --git a/drivers/net/wwan/mhi_wwan_mbim.c b/drivers/net/wwan/mhi_wwan_mbim.c
>> > > index c814fbd756a1..a142af59a91f 100644
>> > > --- a/drivers/net/wwan/mhi_wwan_mbim.c
>> > > +++ b/drivers/net/wwan/mhi_wwan_mbim.c
>> > > @@ -98,7 +98,8 @@ static struct mhi_mbim_link *mhi_mbim_get_link_rcu(struct mhi_mbim_context *mbim
>> > >  static int mhi_mbim_get_link_mux_id(struct mhi_controller *cntrl)
>> > >  {
>> > >       if (strcmp(cntrl->name, "foxconn-dw5934e") == 0 ||
>> > > -         strcmp(cntrl->name, "foxconn-t99w515") == 0)
>> > > +         strcmp(cntrl->name, "foxconn-t99w515") == 0 ||
>> > > +         strcmp(cntrl->name, "foxconn-t99w760") == 0)
>> >
>> > Can we replace this list of strinc comparisons with some kind of device
>> > data, being set in the mhi-pci-generic driver?
>> 
>> If we move this MBIM-specific information into mhi-pci-generic, we
>> should consider using a software node (e.g. via
>> device_add_software_node) so that these properties can be accessed
>> through the generic device-property API.
>
Hi Loic,
The original solution is we defined this mux_id in mhi-pci-generic side and 
transfer it to MBIM side. But it is rejected in last year.
Why we move it back again?

>Works for me too.
>
>-- 
>With best wishes
>Dmitry

  reply	other threads:[~2025-11-20  3:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19 10:56 [PATCH v3 0/2] *** Add support for Foxconn T99W760 *** Slark Xiao
2025-11-19 10:56 ` [PATCH v3 1/2] bus: mhi: host: pci_generic: Add Foxconn T99W760 modem Slark Xiao
2025-11-19 10:56 ` [PATCH v3 2/2] net: wwan: mhi: Add network support for Foxconn T99W760 Slark Xiao
2025-11-19 11:27   ` Dmitry Baryshkov
2025-11-19 13:08     ` Loic Poulain
2025-11-19 13:47       ` Dmitry Baryshkov
2025-11-20  3:04         ` Slark Xiao [this message]
2025-11-20  5:40       ` Manivannan Sadhasivam
2025-11-20  7:44         ` Loic Poulain
2025-11-20  8:22           ` Slark Xiao
2025-11-21 12:46   ` Loic Poulain
2025-12-18  8:00     ` Slark Xiao
2025-12-30  9:50       ` Loic Poulain
2025-12-30 10:08         ` Slark Xiao
2025-12-30 11:19           ` Paolo Abeni
2025-11-20  2:07 ` [PATCH v3 0/2] *** Add support for Foxconn T99W760 *** Jakub Kicinski
2025-11-20  2:47   ` Slark Xiao
2025-11-20  5:45 ` (subset) " Manivannan Sadhasivam

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=5d61df3a.2f2f.19a9f382a58.Coremail.slark_xiao@163.com \
    --to=slark_xiao@163.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=edumazet@google.com \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loic.poulain@oss.qualcomm.com \
    --cc=mani@kernel.org \
    --cc=mhi@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=ryazanov.s.a@gmail.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®