From: Thomas Perrot <thomas.perrot@bootlin.com>
To: Loic Poulain <loic.poulain@linaro.org>
Cc: Aleksander Morgado <aleksander@aleksander.es>,
Manivannan Sadhasivam <manivannan.sadhasivam@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, 18 Oct 2021 16:07:06 +0200 [thread overview]
Message-ID: <1f846b0be78560c1299fa26d351b66567be403e1.camel@bootlin.com> (raw)
In-Reply-To: <CAMZdPi_J7ePh22v7J3WgqO9X3Y1KffTm__TfL9jGHj61H2x9QA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3037 bytes --]
Hi,
On Mon, 2021-10-18 at 14:46 +0200, Loic Poulain wrote:
> On Mon, 18 Oct 2021 at 13:26, Thomas Perrot <
> thomas.perrot@bootlin.com> wrote:
> >
> > Hi Loic,
> >
> > On Mon, 2021-10-18 at 11:59 +0200, Loic Poulain wrote:
> > > Hi Aleksander,
> > >
> > > On Mon, 18 Oct 2021 at 11:14, Aleksander Morgado
> > > <aleksander@aleksander.es> wrote:
> > > >
> > > > Hey all,
> > > >
> > > > > [ 7.056113] mhi-pci-generic 0000:01:00.0: MHI PCI device
> > > > > found:
> > > > > sierra-em919x
> > > > > [ 7.063298] mhi-pci-generic 0000:01:00.0: BAR 0: assigned
> > > > > [mem
> > > > > 0x600000000-0x600000fff 64bit]
> > > > > [ 7.071846] mhi-pci-generic 0000:01:00.0: enabling device
> > > > > (0000
> > > > > -> 0002)
> > > > > [ 7.078671] mhi-pci-generic 0000:01:00.0: using shared MSI
> > > >
> > > > In this specific setup we request 4 MSI vectors through
> > > > pci_alloc_irq_vectors(), but only end up allocating a single
> > > > one
> > > > (i.e.
> > > > mhi_cntrl->nr_irqs = 1). Could that be related to the problem
> > > > somehow?
> > >
> > > It shouldn't, we have the 'shared IRQ' fallback which is used
> > > when we
> > > can not setup multiple MSI, and this works with other SDX55 based
> > > modems.
> > >
> >
> > Compared to other SDX55 based modems, EM919x uses the same event
> > ring
> > for the control, the data and the diag, and we use the macro
> > MHI_EVENT_CONFIG_CTRL to configure it.
> > - Perhaps this macro is not suitable in this case?
>
> Well it should work, but it's usually better to have a dedicated
> event
> ring for non-control stuff.
> The number of event ring is normally driven by the host, is it a
> limitation with EM919X?
I asked the question to our Sierra distributor, because it isn't
indicated in the technical documentation that I have, I'm still waiting
for the answer.
> What is done in the downstream driver?
As we encountered issues with the generic event ring configuration, I
tried with a configuration equivalent to that of the vendor driver,
that uses the same ring for data, control and diag stuff.
Best regards,
Thomas
>
> > - Could this be explaining, what are we observing?
>
> Hmm, as I said device should follow what the host is configuring in
> terms of event rings, but maybe in your case a specific configuration
> is expected, so it would be nice to double check with what is done in
> the downstream driver. As well, do you have any way to access the
> serial/debug console of the EM919X?
>
> > Moreover, we have voluntarily reduced the number of shared MSI
> > vectors
> > to one, on a platform able to provide enough, then we observe the
> > same
> > kind of issues, as on i.MX6DL which end up allocating a single one.
> > However, we carried out this test only with the vendor driver.
>
> You mean the same initialization issue?
>
> Regards,
> Loic
--
Thomas Perrot, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-10-18 14:08 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 [this message]
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
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=1f846b0be78560c1299fa26d351b66567be403e1.camel@bootlin.com \
--to=thomas.perrot@bootlin.com \
--cc=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.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