From: Shawn Guo <shawnguo2@yeah.net>
To: Xu Yang <xu.yang_2@nxp.com>
Cc: Peter Chen <peter.chen@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
imx@lists.linux.dev, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: i.MX kernel hangup caused by chipidea USB gadget driver
Date: Wed, 11 Jun 2025 10:59:51 +0800 [thread overview]
Message-ID: <aEjxJ3atSw/8JwNo@dragon> (raw)
In-Reply-To: <emdju6mml2o65hmtiyf5jwlzhudmbpyx433wz5a73lkpinzbyp@2oexfo2ra7xs>
On Tue, Jun 10, 2025 at 07:54:41PM +0800, Xu Yang wrote:
> > However, your change seems working fine on i.MX8MM EVK. It's probably
> > due to the fact that host disconnects gadget for some reason when EVK
> > suspends. This is a different behavior from the custom board above.
> > We do not really expect this disconnecting, do we?
>
> It's an expected behavior on i.MX8MM EVK. The host will see device disconnected
> after imx8mm do system suspend. It's because the usb phy power will be off after
> system suspend. If you enable wakeup capabiklity for usb phy, the usb phy power
> will keep on and you will not see disconnect event anymore.
>
> # echo enabled > /sys/devices/platform/usbphynop1/power/wakeup
Ah, indeed! Thanks for the information!
Shawn
prev parent reply other threads:[~2025-06-11 3:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 5:31 i.MX kernel hangup caused by chipidea USB gadget driver Shawn Guo
2025-06-09 11:53 ` Xu Yang
2025-06-09 13:54 ` Alan Stern
2025-06-10 10:08 ` Shawn Guo
2025-06-10 11:27 ` Xu Yang
2025-06-09 14:17 ` John Ernberg
2025-06-10 2:12 ` Peter Chen (CIX)
2025-06-10 10:17 ` Shawn Guo
2025-06-10 11:33 ` Xu Yang
2025-06-10 3:04 ` Shawn Guo
2025-06-10 15:03 ` John Ernberg
2025-06-10 11:30 ` Xu Yang
2025-06-10 15:05 ` John Ernberg
2025-06-12 13:23 ` John Ernberg
2025-06-13 3:13 ` Xu Yang
2025-06-10 9:50 ` Shawn Guo
2025-06-10 11:54 ` Xu Yang
2025-06-11 2:59 ` Shawn Guo [this message]
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=aEjxJ3atSw/8JwNo@dragon \
--to=shawnguo2@yeah.net \
--cc=imx@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@kernel.org \
--cc=shawnguo@kernel.org \
--cc=xu.yang_2@nxp.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