From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: Droid 4: suspend to RAM? Date: Wed, 8 Aug 2018 23:32:04 +0200 Message-ID: <20180808213204.GD15831@amd> References: <20180725200205.GA29594@amd> <20180725212853.GA1965@amd> <20180727113214.GA32069@amd> <20180808090512.GQ99251@atomide.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qrgsu6vtpU/OV/zm" Return-path: Content-Disposition: inline In-Reply-To: <20180808090512.GQ99251@atomide.com> Sender: linux-kernel-owner@vger.kernel.org To: Tony Lindgren Cc: Michael Nazzareno Trimarchi , kernel list , linux-arm-kernel , Linux OMAP Mailing List , Sebastian Reichel , nekit1000@gmail.com, mpartap@gmx.net, Merlijn Wajer List-Id: linux-omap@vger.kernel.org --Qrgsu6vtpU/OV/zm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed 2018-08-08 02:05:12, Tony Lindgren wrote: > * Pavel Machek [180727 11:35]: > > Hi! > > > > > high even before modem (and thus USB) is enabled. > > > > > > > > > > Interestingly, CyanogenMod and Jolla seem to have higher power > > > > > consumption than stock operating system. > > > > > > > > > > (My Linux can survive for 10 hours, stock system could survive fo= r 4 > > > > > days if I'm not mistaken). > > > > > > > > > > I thought I would experiment with suspend to RAM.. and it indeed > > > > > seemed to suspend ok, but I could not wake it up. Do I need to se= t up > > > > > wakeup with button somehow? Is suspend to RAM required for good p= ower > > > > > consumption? > > > >=20 > > > > Sorry but pm subsystem has debug mode that you can test in a easy w= ay. > > > > You can even wakeup by any rtc alarm easily. > > >=20 > > > Yes, that is how it works on PC (but there power button works, > > > too). Is it expected to work on Droid in v4.18? > >=20 > > I tried setting up wakeup using RTC, but no, it does not seem to work: > >=20 > > root@devuan:/my/tui/d4# rtcwake -m no -s 5 > > rtcwake: wakeup using /dev/rtc0 at Fri Jul 27 11:28:44 2018 > > root@devuan:/my/tui/d4# echo mem > /sys/power/state >=20 > Works for me here as tested on next-20180808, maybe you don't have > CONFIG_RTC_DRV_CPCAP? Maybe you are trying to use >CONFIG_RTC_DRV_OMAP? I tried with mainline... there will be no graphics in next, right? And yes, I had CONFIG_RTC_DRV_CPCAP and not CONFIG_RTC_DRV_OMAP. > Then for deeper idle modes, you need to also idle UARTs, and unbind or > unload USB related modules. You should get to something like 160mW > power consumption with mdm6600 enabled and SoC suspended that way. That's slightly interesting. echo mem > /sys/power/state should do all the work, right? Disable UARTs etc. Plus, is 160mW still a bit high? > Then again system running idle is about the same with timers and > interrupts working so I'd just idle UARTs and unload USB modules :) >=20 > My UART idle script below for reference. Thanks, let me try... Pavel =09 --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --Qrgsu6vtpU/OV/zm Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAltrYVQACgkQMOfwapXb+vLYEwCeM0ld60aka5Cynv+F+DJV3Czj EFMAn2CUGI1kG6iO+DwhP3kwi3nZvq9e =QizL -----END PGP SIGNATURE----- --Qrgsu6vtpU/OV/zm--