From: Manivannan Sadhasivam <mani@kernel.org>
To: Slark Xiao <slark_xiao@163.com>
Cc: mhi@lists.linux.dev
Subject: Re: failed to power up MHI controller issue
Date: Tue, 2 Apr 2024 10:26:47 +0530 [thread overview]
Message-ID: <20240402045647.GG2933@thinkpad> (raw)
In-Reply-To: <38c7997c.10212.18e84f08a4f.Coremail.slark_xiao@163.com>
+ MHI list
On Thu, Mar 28, 2024 at 08:02:20PM +0800, Slark Xiao wrote:
> Hi Mani,
> Hope you are doing well! I got a problem with our sdx65 device in some
>
> specific platform. MHI driver would report "failed to power up MHI controller"
> when device bootup. Actually, I can reproduce this error when host doing a
> reboot. It's Rockpro64 with SDX65, and kernel 6.6.3 or 6.7.10.
>
> So I add some logs and change dbg level log to info for more print. You can
> see my attachments for reference.
> It seems the host didn't receive the event of "MISSION MODE" and then
> power down the device.
> BTW, there are some extra log prints were added in function
> mhi_sync_power_up(). You can find it with mask "##shawn##".
> Do you have any idea to debug it?
>
Looks like something gone wrong with the device firmware. Is it possible to get
the logs from the device?
This could be due to the way the PCIe controller driver on the host handling
reboot.
But let's get the device logs first to debug further.
- Mani
--
மணிவண்ணன் சதாசிவம்
next parent reply other threads:[~2024-04-02 4:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <38c7997c.10212.18e84f08a4f.Coremail.slark_xiao@163.com>
2024-04-02 4:56 ` Manivannan Sadhasivam [this message]
2024-04-08 9:59 ` Re:Re: failed to power up MHI controller issue Slark Xiao
2024-04-09 4:35 ` Qiang Yu
[not found] ` <40210cbb.3949.18ed6b904d6.Coremail.slark_xiao@163.com>
2024-04-15 6:09 ` Qiang Yu
2024-04-15 10:33 ` Manivannan Sadhasivam
2024-04-16 3:56 ` Slark Xiao
2024-04-17 2:30 ` Qiang Yu
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=20240402045647.GG2933@thinkpad \
--to=mani@kernel.org \
--cc=mhi@lists.linux.dev \
--cc=slark_xiao@163.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 read-only IMAP folder(s) and NNTP newsgroup(s).