From: Andreas Kemnade <andreas@kemnade.info>
To: Tony Lindgren <tony@atomide.com>
Cc: Bin Liu <b-liu@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
letux-kernel@openphoenux.org
Subject: Re: [PATCH] usb: musb: Check devctl status again for a spurious session request
Date: Thu, 3 Jun 2021 23:22:03 +0200 [thread overview]
Message-ID: <20210603232203.51f6293b@aktux> (raw)
In-Reply-To: <YLcaIqqjtmizjRLL@atomide.com>
Hi Tony,
On Wed, 2 Jun 2021 08:41:54 +0300
Tony Lindgren <tony@atomide.com> wrote:
> * Andreas Kemnade <andreas@kemnade.info> [210528 09:37]:
> > rmmod omap2430 seems to bring back suspend current current to low
> > currents.
>
> I wonder if the recent musb fix patch helps with this?
>
> [PATCH] usb: musb: fix MUSB_QUIRK_B_DISCONNECT_99 handling
> https://lore.kernel.org/lkml/20210528140446.278076-1-thomas.petazzoni@bootlin.com/
>
it does not help.
I did some more experiments and found out that
echo on >/sys/bus/platform/devices/480ab000.usb_otg_hs/power/control
sleep 3
before doing an rtcwake -m mem helps
2 seconds are not long enough.
All with usb disconnected.
some debug printks inserted into omap2430.c (doing it without the echo
on thing) [ 355.643768] PM: suspend entry (deep)
[ 355.643920] Filesystems sync: 0.000 seconds
[ 355.644683] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 355.646392] OOM killer disabled.
[ 355.646423] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 355.648010] printk: Suspending console(s) (use no_console_suspend to debug)
[ 355.649291] musb-hdrc musb-hdrc.1.auto: omap2430 runtime_resume
[ 355.966522] musb-omap2430 480ab000.usb_otg_hs: omap2430 suspend
[ 355.966552] musb-hdrc musb-hdrc.1.auto: omap2430 runtime_suspend
[ 355.975250] musb-hdrc musb-hdrc.1.auto: omap2430 runtime_suspend
[ 355.977294] Disabling non-boot CPUs ...
[ 355.977325] Successfully put all powerdomains to target state
[ 355.979034] musb-hdrc musb-hdrc.1.auto: omap2430 runtime_resume
[ 356.244628] musb-omap2430 480ab000.usb_otg_hs: omap2430 resume
[ 356.244659] musb-hdrc musb-hdrc.1.auto: omap2430 runtime_resume
[ 356.486145] musb-hdrc musb-hdrc.1.auto: VBUS b_idle, devctl 80
[ 356.486175] musb-hdrc musb-hdrc.1.auto: VBUS Disconnect
[ 356.486175] musb-hdrc musb-hdrc.1.auto: musb_set_peripheral: already in peripheral mode: 80
There are two suspends in a row, I tried to fix it but it seems not to
be the cause for trouble.
Regards,
Andreas
next prev parent reply other threads:[~2021-06-03 21:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 15:06 [PATCH] usb: musb: Check devctl status again for a spurious session request Tony Lindgren
2021-05-27 19:15 ` Andreas Kemnade
2021-05-28 5:57 ` Tony Lindgren
2021-05-28 9:37 ` Andreas Kemnade
2021-06-02 5:41 ` Tony Lindgren
2021-06-03 21:22 ` Andreas Kemnade [this message]
2021-06-04 8:35 ` Andreas Kemnade
2021-06-04 9:39 ` Tony Lindgren
2021-06-04 9:59 ` Andreas Kemnade
2021-06-04 10:08 ` Tony Lindgren
2021-06-04 10:20 ` Andreas Kemnade
2021-06-04 14:45 ` Andreas Kemnade
2021-06-04 16:59 ` Andreas Kemnade
2021-06-05 5:18 ` Tony Lindgren
2021-06-05 14:20 ` Andreas Kemnade
2021-06-06 6:01 ` Tony Lindgren
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=20210603232203.51f6293b@aktux \
--to=andreas@kemnade.info \
--cc=b-liu@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=letux-kernel@openphoenux.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=tony@atomide.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).