From: Loic Poulain <loic.poulain@linaro.org>
To: Aleksander Morgado <aleksander@aleksander.es>
Cc: Thomas Perrot <thomas.perrot@bootlin.com>,
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 11:59:21 +0200 [thread overview]
Message-ID: <CAMZdPi9cbDVWVxvimg-uc_TRvskrxbjEQ4AxdLjA57Ewm2tSPA@mail.gmail.com> (raw)
In-Reply-To: <CAAP7uc+5=GMGgz3MKfSWaAtes1WwCCx+6iYhb058ZUr0=A52cg@mail.gmail.com>
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.
Regards,
Loic
next prev parent reply other threads:[~2021-10-18 9:48 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 [this message]
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
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=CAMZdPi9cbDVWVxvimg-uc_TRvskrxbjEQ4AxdLjA57Ewm2tSPA@mail.gmail.com \
--to=loic.poulain@linaro.org \
--cc=aleksander@aleksander.es \
--cc=hemantk@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.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).