From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Aleksander Morgado <aleksander@aleksander.es>
Cc: Loic Poulain <loic.poulain@linaro.org>,
Thomas Perrot <thomas.perrot@bootlin.com>,
hemantk@codeaurora.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
bbhatt@codeaurora.org
Subject: Re: Sierra Wireless EM9191 integration issues in mhi+wwan
Date: Sat, 9 Oct 2021 16:21:32 +0530 [thread overview]
Message-ID: <20211009105132.GA204538@thinkpad> (raw)
In-Reply-To: <CAAP7ucLJYfftfCuKxnW8Q7-duyEuGgHA5gk+h2JyyAzNq75QSA@mail.gmail.com>
+ Bhaumik
On Thu, Oct 07, 2021 at 03:04:44PM +0200, Aleksander Morgado wrote:
> Hey all,
>
> I'm working on a setup using a RPi CM4 based board and a Sierra
> Wireless EM9191 module, running OpenWRT 21.02 and backported mhi+wwan
> drivers (from latest 5.15 rc). The kernel also has the
> mhi_pci_dev_info entry written by Thomas, as per
> https://forum.sierrawireless.com/t/sierra-wireless-airprime-em919x-pcie-support/24927
>
> The EM9191 is now running 02.08.01.00 (latest firmware from Sierra),
> upgraded in several steps back from the original 01.04.01.02 the
> module came with. The firmware upgrades were done with
> qmi-firmware-update and the module in USB mode in a desktop PC.
>
> Most of the system boots end up with the mhi driver reporting that the
> module firmware crashed in different ways:
>
> [ 7.060730] mhi-pci-generic 0000:01:00.0: MHI PCI device found: sierra-em919x
> [ 7.067906] mhi-pci-generic 0000:01:00.0: BAR 0: assigned [mem
> 0x600000000-0x600000fff 64bit]
> [ 7.076455] mhi-pci-generic 0000:01:00.0: enabling device (0000 -> 0002)
> [ 7.083277] mhi-pci-generic 0000:01:00.0: using shared MSI
> [ 7.089508] mhi mhi0: Requested to power ON
> [ 7.094080] mhi mhi0: Attempting power on with EE: PASS THROUGH,
> state: SYS ERROR
> [ 7.180371] mhi mhi0: local ee: INVALID_EE state: RESET device ee:
> PASS THROUGH state: SYS ERROR
> [ 7.187146] mhi mhi0: Power on setup success
> [ 7.187219] mhi mhi0: Handling state transition: PBL
> [ 7.189165] mhi mhi0: System error detected
> [ 7.189178] mhi mhi0: Device MHI is not in valid state
> [ 7.189189] mhi-pci-generic 0000:01:00.0: firmware crashed (7)
> [ 7.213682] mhi mhi0: Handling state transition: SYS ERROR
> [ 7.219183] mhi mhi0: Transitioning from PM state: Linkdown or
> Error Fatal Detect to: SYS ERROR Process
> [ 7.228590] mhi-pci-generic 0000:01:00.0: firmware crashed (6)
> [ 7.234429] mhi mhi0: Failed to transition from PM state: Linkdown
> or Error Fatal Detect to: SYS ERROR Process
> [ 7.244433] mhi mhi0: Exiting with PM state: Linkdown or Error
> Fatal Detect, MHI state: RESET
> [ 7.252963] mhi mhi0: Handling state transition: DISABLE
> [ 7.258278] mhi mhi0: Processing disable transition with PM state:
> Linkdown or Error Fatal Detect
> [ 7.267155] mhi mhi0: Waiting for all pending event ring processing
> to complete
> [ 7.274480] mhi mhi0: Waiting for all pending threads to complete
> [ 7.280576] mhi mhi0: Reset all active channels and remove MHI devices
> [ 7.287110] mhi mhi0: Resetting EV CTXT and CMD CTXT
> [ 7.292077] mhi mhi0: Exiting with PM state: DISABLE, MHI state: RESET
> [ 7.298683] mhi-pci-generic 0000:01:00.0: failed to power up MHI controller
> [ 7.306184] mhi-pci-generic: probe of 0000:01:00.0 failed with error -110
>
> Some of the boots successfully finish and I can talk to both the QMI
> and MBIM ports exposed by the WWAN subsystem, but the success rate is
> extremely low.
>
Can you share the success log also?
Thanks,
Mani
> Thomas, are you seeing similar issues in your setup?
>
> --
> Aleksander
> https://aleksander.es
next prev parent reply other threads:[~2021-10-09 10:51 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 [this message]
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
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=20211009105132.GA204538@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=aleksander@aleksander.es \
--cc=bbhatt@codeaurora.org \
--cc=hemantk@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=loic.poulain@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