From: Andreas Kemnade <andreas-cLv4Z9ELZ06ZuzBka8ofvg@public.gmane.org>
To: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
Cc: b-liu-l0cyMroinI0@public.gmane.org,
gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Discussions about the Letux Kernel
<letux-kernel-S0jZdbWzriLCfDggNXIi3w@public.gmane.org>,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] usb: musb: fix enumeration after resume
Date: Tue, 6 Feb 2018 20:09:57 +0100 [thread overview]
Message-ID: <20180206200957.196ab0b3@aktux> (raw)
In-Reply-To: <20180206184725.GD21573-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
Hi,
On Tue, 6 Feb 2018 10:47:25 -0800
Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org> wrote:
> * Andreas Kemnade <andreas-cLv4Z9ELZ06ZuzBka8ofvg@public.gmane.org> [180127 08:34]:
> > On dm3730 there are enumeration problems after resume.
> > Investigation led to the cause that the MUSB_POWER_SOFTCONN
> > bit is not set. If it was set before suspend (because it
> > was enabled via musb_pullup()), it is set in
> > musb_restore_context() so the pullup is enabled. But then
> > musb_start() is called which overwrites MUSB_POWER and
> > therefore disables MUSB_POWER_SOFTCONN, so no pullup is
> > enabled and the device is not enumerated.
>
> I just gave this patch a quick try and things seem to behave
> for me from PM point of view:
>
> Tested-by: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
>
> Unrelated to this patch, I also noticed that we now somehow
> higher idle power consumption initially when musb modules are
> loaded. It used to idle after that but now to get things to
> idle I had to plug and unplug a USB device once to the musb
> port.
>
Hmm, I have seen this effect with some earlier kernels but not with
4.15. My observation is that current consumption went down again after
a modprobe g_ether and ifconfig usb0 up
I was loading modules piece by piece and waited 10s after each and then
measured.
Regards,
Andreas
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Kemnade <andreas@kemnade.info>
To: Tony Lindgren <tony@atomide.com>
Cc: b-liu@ti.com, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Discussions about the Letux Kernel <letux-kernel@openphoenux.org>,
linux-omap@vger.kernel.org
Subject: usb: musb: fix enumeration after resume
Date: Tue, 6 Feb 2018 20:09:57 +0100 [thread overview]
Message-ID: <20180206200957.196ab0b3@aktux> (raw)
Hi,
On Tue, 6 Feb 2018 10:47:25 -0800
Tony Lindgren <tony@atomide.com> wrote:
> * Andreas Kemnade <andreas@kemnade.info> [180127 08:34]:
> > On dm3730 there are enumeration problems after resume.
> > Investigation led to the cause that the MUSB_POWER_SOFTCONN
> > bit is not set. If it was set before suspend (because it
> > was enabled via musb_pullup()), it is set in
> > musb_restore_context() so the pullup is enabled. But then
> > musb_start() is called which overwrites MUSB_POWER and
> > therefore disables MUSB_POWER_SOFTCONN, so no pullup is
> > enabled and the device is not enumerated.
>
> I just gave this patch a quick try and things seem to behave
> for me from PM point of view:
>
> Tested-by: Tony Lindgren <tony@atomide.com>
>
> Unrelated to this patch, I also noticed that we now somehow
> higher idle power consumption initially when musb modules are
> loaded. It used to idle after that but now to get things to
> idle I had to plug and unplug a USB device once to the musb
> port.
>
Hmm, I have seen this effect with some earlier kernels but not with
4.15. My observation is that current consumption went down again after
a modprobe g_ether and ifconfig usb0 up
I was loading modules piece by piece and waited 10s after each and then
measured.
Regards,
Andreas
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Kemnade <andreas@kemnade.info>
To: Tony Lindgren <tony@atomide.com>
Cc: b-liu@ti.com, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Discussions about the Letux Kernel <letux-kernel@openphoenux.org>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] usb: musb: fix enumeration after resume
Date: Tue, 6 Feb 2018 20:09:57 +0100 [thread overview]
Message-ID: <20180206200957.196ab0b3@aktux> (raw)
In-Reply-To: <20180206184725.GD21573@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]
Hi,
On Tue, 6 Feb 2018 10:47:25 -0800
Tony Lindgren <tony@atomide.com> wrote:
> * Andreas Kemnade <andreas@kemnade.info> [180127 08:34]:
> > On dm3730 there are enumeration problems after resume.
> > Investigation led to the cause that the MUSB_POWER_SOFTCONN
> > bit is not set. If it was set before suspend (because it
> > was enabled via musb_pullup()), it is set in
> > musb_restore_context() so the pullup is enabled. But then
> > musb_start() is called which overwrites MUSB_POWER and
> > therefore disables MUSB_POWER_SOFTCONN, so no pullup is
> > enabled and the device is not enumerated.
>
> I just gave this patch a quick try and things seem to behave
> for me from PM point of view:
>
> Tested-by: Tony Lindgren <tony@atomide.com>
>
> Unrelated to this patch, I also noticed that we now somehow
> higher idle power consumption initially when musb modules are
> loaded. It used to idle after that but now to get things to
> idle I had to plug and unplug a USB device once to the musb
> port.
>
Hmm, I have seen this effect with some earlier kernels but not with
4.15. My observation is that current consumption went down again after
a modprobe g_ether and ifconfig usb0 up
I was loading modules piece by piece and waited 10s after each and then
measured.
Regards,
Andreas
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-06 19:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-27 8:34 usb: musb: fix enumeration after resume Andreas Kemnade
2018-01-27 8:34 ` [PATCH] " Andreas Kemnade
[not found] ` <20180127083403.928-1-andreas-cLv4Z9ELZ06ZuzBka8ofvg@public.gmane.org>
2018-02-06 18:47 ` Tony Lindgren
2018-02-06 18:47 ` Tony Lindgren
2018-02-06 18:47 ` Tony Lindgren
[not found] ` <20180206184725.GD21573-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2018-02-06 19:09 ` Andreas Kemnade [this message]
2018-02-06 19:09 ` [PATCH] " Andreas Kemnade
2018-02-06 19:09 ` Andreas Kemnade
2018-02-07 20:32 ` [PATCH] " Bin Liu
2018-02-07 20:32 ` Bin Liu
2018-02-07 20:32 ` Bin Liu
-- strict thread matches above, loose matches on Subject: below --
2018-02-06 18:46 Bin Liu
2018-02-06 18:46 ` [PATCH] " Bin Liu
2018-02-06 19:00 Andreas Kemnade
2018-02-06 19:00 ` [PATCH] " Andreas Kemnade
2018-02-07 20:37 Bin Liu
2018-02-07 20:37 ` [PATCH] " Bin Liu
2018-02-16 7:10 Andreas Kemnade
2018-02-16 7:10 ` [PATCH] " Andreas Kemnade
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=20180206200957.196ab0b3@aktux \
--to=andreas-clv4z9elz06zuzbka8ofvg@public.gmane.org \
--cc=b-liu-l0cyMroinI0@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=letux-kernel-S0jZdbWzriLCfDggNXIi3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.