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: Tue, 9 Feb 2016 09:24:04 -0800 [thread overview]
Message-ID: <20160209172403.GK19432@atomide.com> (raw)
In-Reply-To: <20160207212316.GA6147@amd>
* Pavel Machek <pavel@ucw.cz> [160207 13:24]:
> Hi!
>
> > > (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")
>
> Ok, with that, I can insmod and rmmod. But I still get:
>
> 00001fff 48005020 (fa005020) cm_idlest_per blocking bits: 0007e000
I think the cm_idlest_per is fine.
> ffdffebd 48004a20 (fa004a20) cm_idlest1_core blocking bits: 00200042
> 0000000d 48004a28 (fa004a28) cm_idlest3_core
Bit 21 in cm_idlest1_core is for MCSPI4 so WLAN. Does that go
down if do sleep 5; cat /sys/kernel/debug/pm_debug/count ?
If not, the're PM runtime missing or broken somewhere.
FYI, below is my omap3 usb test script that I use to start and
stop USB, it also works on n900. And after stopping it n900
continues hitting deeper idle states just fine.
That is with these two phy patches applied on v4.5-rc3:
"phy: twl4030-usb: Fix unbalanced pm_runtime_enable on module reload")
"phy: twl4030-usb: Relase usb phy on unload")
Maybe I gave you wrong info on the USB patches needed.. But these
two above are needed on v4.5-rc3. And looks like Kishon has now
applied them.
Oh and I also have the MMC PM runtime regression fix here that I
have not yet posted. Will post today. But I guess you're on
v4.4 right now still.
Regards,
Tony
8< --------
#!/bin/bash
# Change for your UDC controller
phy_module=phy_twl4030_usb
udc_glue=omap2430
udc_module=musb_hdrc
udc_name=musb-hdrc.0.auto
start_usb_gadgets() {
vendor=0x1d6b
product=0x0106
file=$1
mount -t configfs none /sys/kernel/config
mkdir /sys/kernel/config/usb_gadget/g1
old_pwd=$(pwd)
cd /sys/kernel/config/usb_gadget/g1
echo $product > idProduct
echo $vendor > idVendor
mkdir strings/0x409
echo 123456789 > strings/0x409/serialnumber
echo foo > strings/0x409/manufacturer
echo "Multi Gadget" > strings/0x409/product
mkdir configs/c.1
echo 100 > configs/c.1/MaxPower
mkdir configs/c.1/strings/0x409
echo "Config 100mA" > configs/c.1/strings/0x409/configuration
mkdir configs/c.5
echo 500 > configs/c.5/MaxPower
mkdir configs/c.5/strings/0x409
echo "Config 500mA" > configs/c.5/strings/0x409/configuration
mkdir functions/mass_storage.0
echo $file > functions/mass_storage.0/lun.0/file
ln -s functions/mass_storage.0 configs/c.1
ln -s functions/mass_storage.0 configs/c.5
mkdir functions/acm.0
ln -s functions/acm.0 configs/c.1
ln -s functions/acm.0 configs/c.5
mkdir functions/ecm.0
ln -s functions/ecm.0 configs/c.1
ln -s functions/ecm.0 configs/c.5
# Adding rndis seems to cause alignment trap or some
# random oops on reboot after rmmod $udc_glue
echo $udc_name > /sys/kernel/config/usb_gadget/g1/UDC
cd $old_pwd
}
stop_usb_gadgets() {
old_pwd=$(pwd)
cd /sys/kernel/config/usb_gadget/g1
echo "" > /sys/kernel/config/usb_gadget/g1/UDC
rm configs/c.1/ecm.0
rm configs/c.5/ecm.0
rmdir functions/ecm.0
rm configs/c.1/acm.0
rm configs/c.5/acm.0
rmdir functions/acm.0
echo "" > functions/mass_storage.0/lun.0/file
rm configs/c.1/mass_storage.0
rm configs/c.5/mass_storage.0
rmdir functions/mass_storage.0
rmmod $udc_glue
rmmod $phy_module
rmmod $udc_module
cd $old_pwd
}
case $1 in
start)
modprobe libcomposite
modprobe $phy_module
modprobe $udc_glue
start_usb_gadgets ""
;;
stop)
stop_usb_gadgets
;;
*)
;;
esac
next prev parent reply other threads:[~2016-02-09 17:24 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
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 [this message]
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=20160209172403.GK19432@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).