linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Perrot <thomas.perrot@bootlin.com>
To: linux-arm-msm@vger.kernel.org
Cc: manivannan.sadhasivam@linaro.org,
	manivannan.sadhasivam@linaro.org, bbhatt@codeaurora.org
Subject: MHI driver issue with Sierra Wireless AirPrime EM919X
Date: Fri, 30 Jul 2021 19:52:18 +0200	[thread overview]
Message-ID: <1e288e5bee3f2a18e0ddb8b7a50158ecb793822d.camel@bootlin.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1959 bytes --]

Hello,

I’m trying to use the MHI driver with a Sierra Wireless AirPrime EM919X
connected to an NXP i.MX6DL through a PCIe gen2 bus, on 5.13.6, but the
device initialisation fails, as follows:

[    3.029401] mhi-pci-generic 0000:01:00.0: BAR 0: assigned [mem
0x01100000-0x01100fff 64bit]
[    3.041095] mhi-pci-generic 0000:01:00.0: enabling device (0140 ->
0142)
[    3.118299] mhi mhi0: Requested to power ON
[   11.370361] mhi mhi0: Power on setup success
[   11.372503] mhi mhi0: Wait for device to enter SBL or Mission mode
[   15.664068] mhi-pci-generic 0000:01:00.0: failed to suspend device:
-16
[   22.619948] mhi-pci-generic 0000:01:00.0: refused to change power
state from D3hot to D0
[   57.289998] mhi-pci-generic 0000:01:00.0: can't change power state
from D3hot to D0 (config space inaccessible)
[   73.769675] mhi-pci-generic 0000:01:00.0: can't change power state
from D3cold to D0 (config space inaccessible)
[   73.780188] mhi-pci-generic 0000:01:00.0: can't change power state
from D3hot to D0 (config space inaccessible)
[   73.836150] PC is at mhi_pci_read_reg+0xc/0x14
[   73.840642] LR is at mhi_get_mhi_state+0x2c/0x5c
[   74.121120] [<c05dcaf4>] (mhi_pci_read_reg) from [<c05d754c>]
(mhi_get_mhi_state+0x2c/0x5c)
[   74.129529] [<c05d754c>] (mhi_get_mhi_state) from [<c05da440>]
(mhi_pm_resume+0x38/0x298)
[   74.137754] [<c05da440>] (mhi_pm_resume) from [<c05dcbd0>]
(mhi_pci_runtime_resume+0x70/0xe0)
[   74.146326] [<c05dcbd0>] (mhi_pci_runtime_resume) from [<c0604da0>]
(pci_pm_runtime_resume+0x84/0xa0)

Do you have any idea where the issue might come from?

MHI seems to enter in READY state and waiting to enter in SBL or
Mission mode when the issue occurs, the host can start MHI
initialization by programming MMIO registers and sets the device into
MHI_M0 state.

Best regards,
Thomas

-- 
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 --]

             reply	other threads:[~2021-07-30 17:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30 17:52 Thomas Perrot [this message]
2021-08-01 21:56 ` MHI driver issue with Sierra Wireless AirPrime EM919X Hemant Kumar
2021-08-02 15:32   ` Thomas Perrot
2021-08-02 15:22 ` Loic Poulain
2021-08-02 15:37   ` Thomas Perrot
2021-08-02 16:33     ` Loic Poulain
2021-08-02 18:14       ` Bhaumik Bhatt
2021-08-03 13:44         ` Thomas Perrot
2021-08-03 15:02           ` Loic Poulain
2021-08-05  7:18             ` Thomas Perrot
2021-08-05  7:33               ` Thomas Perrot

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=1e288e5bee3f2a18e0ddb8b7a50158ecb793822d.camel@bootlin.com \
    --to=thomas.perrot@bootlin.com \
    --cc=bbhatt@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    /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).