linux-kernel - Re: Droid 4: suspend to RAM?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 8 Aug 2018 02:05:12 -0700
From:   Tony Lindgren <tony@...mide.com>
To:     Pavel Machek <pavel@....cz>
Cc:     Michael Nazzareno Trimarchi <michael@...rulasolutions.com>,
        kernel list <linux-kernel@...r.kernel.org>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        Linux OMAP Mailing List <linux-omap@...r.kernel.org>,
        Sebastian Reichel <sre@...nel.org>, nekit1000@...il.com,
        mpartap@....net, Merlijn Wajer <merlijn@...zup.org>
Subject: Re: Droid 4: suspend to RAM?

* Pavel Machek <pavel@....cz> [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 for 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 set up
> > > > wakeup with button somehow? Is suspend to RAM required for good power
> > > > consumption?
> > > 
> > > Sorry but pm subsystem has debug mode that you can test in a easy way.
> > > You can even wakeup by any rtc alarm easily.
> > 
> > Yes, that is how it works on PC (but there power button works,
> > too). Is it expected to work on Droid in v4.18?
> 
> I tried setting up wakeup using RTC, but no, it does not seem to work:
> 
> root@...uan:/my/tui/d4# rtcwake -m no -s 5
> rtcwake: wakeup using /dev/rtc0 at Fri Jul 27 11:28:44 2018
> root@...uan:/my/tui/d4# echo mem > /sys/power/state

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?

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.

Then again system running idle is about the same with timers and
interrupts working so I'd just idle UARTs and unload USB modules :)

My UART idle script below for reference.

Regards,

Tony

8< ----------------
#!/bin/bash

# Configure PM runtime autosuspend
uarts=$(find /sys/bus/platform/devices/4*.serial/power/ -type d)
for uart in $uarts; do
        echo -n 3000 > $uart/autosuspend_delay_ms
        echo -n enabled > $uart/wakeup
        echo -n auto > $uart/control
done

# Configure wake-up from suspend
uarts=$(find /sys/class/tty/tty[SO]*/power/ -type d 2>/dev/null)
for uart in $uarts; do
        echo -n enabled > $uart/wakeup
done

echo -n 1 > /sys/kernel/debug/pm_debug/enable_off_mode