From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: N900 sleep mode (in 4.5-rc0, if that matters)
Date: Wed, 3 Feb 2016 21:35:18 -0800 [thread overview]
Message-ID: <20160204053518.GP19432@atomide.com> (raw)
In-Reply-To: <20160201221111.GP19432@atomide.com>
* Tony Lindgren <tony@atomide.com> [160201 14:12]:
> * Pavel Machek <pavel@ucw.cz> [160201 13:18]:
> >
> > No, sorry, that was with 4.4. As you hit "PM regression with commit
> > 5de85b9d57ab PM runtime re-init in v4.5-rc1", I thought I'd avoid
> > v4.5-rc.
>
> OK
>
> > (I assume I have to insmod and rmmod, right? Because powersave is not
> > entered if I simply compile-out usb).
>
> Depending on what the bootloader does and probably also if
> USB was used during the booting.. So yeah you may need to modprobe
> and then rmmod.
>
> > Would you have commit ids for those rmmod fixes? It might be good to
> > push them into stable, and I should try again with them applied...
>
> 055555fc459 ("usb: musb: core: Fix handling of the phy notifications")
> 03e43528ab68 ("usb: musb: Fix unbalanced pm_runtime_enable")
Oh and looks like these two phy-twl4030-phy fixes never got
merged from thread "[PATCH 0/2] Two phy-twl4030-usb fixes for
unloading the module":
phy: twl4030-usb: Relase usb phy on unload
phy: twl4030-usb: Fix unbalanced pm_runtime_enable on module reload
I'll resend those. But without those again deeper idle states
are blocked.. And it could be that n900 needs similar additional
patches for it's USB PHY as I've tested things so far only with
phy-twl4030-usb PHY based systems.
Regards,
Tony
next prev parent reply other threads:[~2016-02-04 5:35 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 12:10 N900 sleep mode (in 4.5-rc0, if that matters) Pavel Machek
2016-01-25 16:33 ` Tony Lindgren
2016-01-25 22:23 ` Pavel Machek
2016-01-25 22:50 ` Tony Lindgren
2016-01-26 14:00 ` Pavel Machek
2016-01-26 17:25 ` Tony Lindgren
2016-01-26 22:51 ` Tony Lindgren
2016-01-30 20:02 ` Pavel Machek
2016-01-30 20:14 ` Pavel Machek
2016-01-30 22:15 ` Pavel Machek
2016-02-01 18:13 ` Tony Lindgren
2016-02-01 21:17 ` Pavel Machek
2016-02-01 22:11 ` Tony Lindgren
2016-02-04 5:35 ` Tony Lindgren [this message]
2016-02-07 21:37 ` Pavel Machek
2016-02-08 8:51 ` Pali Rohár
2016-02-07 21:23 ` Pavel Machek
2016-02-09 17:24 ` Tony Lindgren
2016-02-09 17:38 ` Tony Lindgren
2016-03-20 8:38 ` Pavel Machek
2016-02-11 1:08 ` Tony Lindgren
2016-03-23 14:37 ` Pavel Machek
2016-03-20 8:33 ` Pavel Machek
2016-03-23 12:38 ` Pavel Machek
2016-03-30 19:12 ` Tony Lindgren
2016-04-04 11:09 ` Pali Rohár
2016-04-04 22:31 ` Tony Lindgren
2016-04-04 21:30 ` Pavel Machek
2016-04-04 22:07 ` Tony Lindgren
2016-04-05 10:09 ` Pavel Machek
2016-04-05 13:17 ` Pavel Machek
2016-04-05 14:22 ` 4.4: camera and unlock buttons produce tons of interrupts (was Re: N900 sleep mode) Pavel Machek
2016-04-05 15:29 ` Tony Lindgren
2016-04-05 20:51 ` Pavel Machek
2016-04-07 17:40 ` Tony Lindgren
2016-04-07 19:48 ` 4.4, 4.6: " Pavel Machek
2016-04-07 21:32 ` Tony Lindgren
2016-04-07 23:01 ` Pavel Machek
2016-04-07 23:41 ` Tony Lindgren
2016-04-08 9:19 ` Pavel Machek
2016-04-11 8:27 ` 4.6-rc2: regression with omap video and lockdep (was Re: 4.4, 4.6: camera and unlock buttons produce tons of interrupts (was Re: N900 sleep mode)) Pavel Machek
2016-04-11 9:30 ` 4.4, 4.6: camera and unlock buttons produce tons of interrupts (was Re: N900 sleep mode) Pavel Machek
2016-04-11 9:41 ` Pavel Machek
2016-04-11 21:10 ` Tony Lindgren
[not found] ` <20160412121658.GA32486@amd>
2016-04-12 12:30 ` Nokia N900 retention mode in v4.6, camera buttons fun Pavel Machek
2016-04-12 16:30 ` Tony Lindgren
2016-04-13 5:52 ` Tomi Valkeinen
2016-04-13 15:15 ` Tony Lindgren
2016-04-17 17:55 ` Pavel Machek
2016-04-18 23:47 ` Tony Lindgren
2016-04-21 13:04 ` Pali Rohár
2016-04-21 21:28 ` Pavel Machek
2016-04-22 7:05 ` Pali Rohár
2016-04-29 20:06 ` Sebastian Reichel
2016-05-01 8:52 ` Pavel Machek
2016-05-01 15:48 ` Sebastian Reichel
2016-05-02 20:12 ` Sebastian Reichel
2016-05-28 11:09 ` Pavel Machek
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=20160204053518.GP19432@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).