linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aleksander Morgado <aleksander@aleksander.es>
To: Thomas Perrot <thomas.perrot@bootlin.com>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	Loic Poulain <loic.poulain@linaro.org>,
	Hemant Kumar <hemantk@codeaurora.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: Sierra Wireless EM9191 integration issues in mhi+wwan
Date: Mon, 8 Nov 2021 21:16:48 +0100	[thread overview]
Message-ID: <CAAP7ucKsFcU9UpGZFPVMYK1g7-JDgfNDvTbVQQkDFWiODmObwQ@mail.gmail.com> (raw)
In-Reply-To: <d787fb8d6588ba5e05232fc5809d4cbd80117ebf.camel@bootlin.com>

Hey!

> > > On our setup, using i.MX6DL based board and a PCIe Sierra Wireless
> > > EM9190 module, running Yocto and Linux 5.13, we don't have much
> > > success
> > > for the moment, qmi and mbim commands very often end in timeout.
> > >
> > > Otherwise, when responses are received, we also can observe strange
> > > things: unexpected messages, response to previous commands or queue
> > > buffer issue.
> > >
> >
> > Once all my boot reliability issues seem solved, I've also started to
> > notice what you mean here. If I run a normal ModemManager build with
> > both QMI and MBIM enabled, MM will try to probe both the QMI and MBIM
> > ports. When that happens, I have no idea why, the modem gets in some
> > weird state with commands timing out and what not. Maybe it's because
> > we're using both ports at the same time, maybe it's because we run
> > QMI
> > on both the QMI and MBIM ports, no idea, the only thing I know is
> > that
> > if you choose to use either one or the other, the whole setup is
> > fully
> > stable.
> >
> > E.g. I'm right now testing my build after compiling ModemManager
> > using
> > --without-mbim (so QMI only), and I have absolutely no error.
>
> That's very good news!
>
> > Another
> > option if you don't want to rebuild MM is to flag the MBIM or the QMI
> > port as ID_MM_PORT_IGNORE with udev rules, which is very likely what
> > I'll end up doing in upstream ModemManager to have a proper default.
> >
> > I was thinking in preparing and sending for review the EM91xx entry
> > for drivers/bus/mhi/pci_generic.c, but it's mostly based on what you
> > suggested in the Sierra Wireless forum, so not sure if you'd like to
> > send it yourself here?
>
> I can send it myself here, and I add you as developer if you'd like ?
>

Then please send it yourself, I just suggested a couple minor changes
on the work you did :)
Thanks!

-- 
Aleksander
https://aleksander.es

      reply	other threads:[~2021-11-08 20:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-07 13:04 Sierra Wireless EM9191 integration issues in mhi+wwan Aleksander Morgado
2021-10-09 10:51 ` Manivannan Sadhasivam
2021-10-12 19:38   ` Aleksander Morgado
2021-10-22  4:42     ` Manivannan Sadhasivam
2021-10-22  9:20       ` Aleksander Morgado
2021-10-22 14:40         ` Manivannan Sadhasivam
2021-10-25  8:10           ` Aleksander Morgado
2021-11-02 10:50             ` Manivannan Sadhasivam
2021-11-02 16:13               ` Aleksander Morgado
2021-11-02 16:22                 ` Manivannan Sadhasivam
2021-11-02 16:55                   ` Aleksander Morgado
2021-11-02 18:09                     ` Manivannan Sadhasivam
     [not found]                       ` <CAMZdPi9+zrsDy9WTipamRWBXMOxUX1tfsk2W52b9wG-4q21fWA@mail.gmail.com>
2021-11-04 22:50                         ` Bhaumik Bhatt
2021-11-08  7:40                       ` Manivannan Sadhasivam
2021-11-08 13:38                         ` Aleksander Morgado
2021-10-11 14:44 ` Thomas Perrot
2021-10-12 19:44   ` Aleksander Morgado
2021-10-14  9:51     ` Thomas Perrot
2021-10-14 10:04       ` Aleksander Morgado
2021-10-14 17:28         ` Loic Poulain
2021-10-14 20:25           ` Aleksander Morgado
2021-10-18  9:14             ` Aleksander Morgado
2021-10-18  9:59               ` Loic Poulain
2021-10-18 11:26                 ` Thomas Perrot
2021-10-18 12:46                   ` Loic Poulain
2021-10-18 14:07                     ` Thomas Perrot
2021-10-18 14:16                       ` Thomas Perrot
2021-10-19  8:38                       ` Aleksander Morgado
2021-10-20  8:43                         ` Aleksander Morgado
2021-10-22 14:33                     ` Aleksander Morgado
2021-11-08 15:11   ` Aleksander Morgado
2021-11-08 16:31     ` Thomas Perrot
2021-11-08 20:16       ` Aleksander Morgado [this message]

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=CAAP7ucKsFcU9UpGZFPVMYK1g7-JDgfNDvTbVQQkDFWiODmObwQ@mail.gmail.com \
    --to=aleksander@aleksander.es \
    --cc=hemantk@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=loic.poulain@linaro.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=thomas.perrot@bootlin.com \
    --cc=thomas.petazzoni@bootlin.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;
as well as URLs for NNTP newsgroup(s).