From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] ARM: PXA: Zipit Z2: Add USB host and device support
Date: Mon, 29 Oct 2012 12:14:34 +0100 [thread overview]
Message-ID: <508E651A.5070009@gmail.com> (raw)
In-Reply-To: <CA+E=qVcJ=WLJwS49zgb_=6or7Me3LLGQtBbfzBtS-p+U6Tw-pQ@mail.gmail.com>
On 29.10.2012 12:12, Vasily Khoruzhick wrote:
> On Mon, Oct 29, 2012 at 2:00 PM, Daniel Mack <zonque@gmail.com> wrote:
>
>>> Well, there's an issue - Z2 does not preserve memory contents in deep sleep
>>> (but it does in sleep), so userspace can't be fixed here unfortunatelly.
>>> There's no another possibility to turn Z2 off, and plain sleep is too
>>> power hungry.
>>> So the only way to keep Z2 in low-power mode is fake power off, which just puts
>>> Z2 in deep sleep.
>>
>> Why can't the userspace trigger a deep sleep then instead of powering
>> off? Which details do I lack?
>
> How? echo mem >/sys/power/state puts system into non-deep sleep. Anyway, kernel
> is not ready for fake power off instead of suspend (we can't resume
> from deep sleep,
> memory content is not preserved), so there can be some data loss.
> Adding some sysfs file to control sleep type does not look like a good
> idea to me.
>
> Btw, how other DT-capable boards handle power off?
No idea. I never actually used that kind of power state.
next prev parent reply other threads:[~2012-10-29 11:14 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 15:35 [PATCH 1/5] ARM: PXA: Add z2-usb-switch driver Vasily Khoruzhick
2012-10-28 15:35 ` [PATCH 2/5] ARM: PXA: Zipit Z2: Add USB host and device support Vasily Khoruzhick
2012-10-28 21:59 ` Marek Vasut
2012-10-28 22:38 ` Vasily Khoruzhick
2012-10-28 22:43 ` Marek Vasut
2012-10-28 22:58 ` Daniel Mack
2012-10-29 9:33 ` Vasily Khoruzhick
2012-10-29 9:42 ` Daniel Mack
2012-10-29 10:07 ` Vasily Khoruzhick
2012-10-29 10:22 ` Marek Vasut
2012-10-29 10:26 ` Vasily Khoruzhick
2012-10-29 10:44 ` Daniel Mack
2012-10-29 10:52 ` Vasily Khoruzhick
2012-10-29 11:00 ` Daniel Mack
2012-10-29 11:12 ` Vasily Khoruzhick
2012-10-29 11:14 ` Daniel Mack [this message]
2012-10-30 20:01 ` Vasily Khoruzhick
2012-10-30 20:05 ` Daniel Mack
2012-10-30 21:20 ` Vasily Khoruzhick
2012-10-31 14:00 ` Haojian Zhuang
2012-10-31 15:31 ` Haojian Zhuang
2012-11-02 20:52 ` Vasily Khoruzhick
2012-11-02 21:29 ` Vasily Khoruzhick
2012-11-05 17:31 ` Vasily Khoruzhick
2012-12-04 8:30 ` Haojian Zhuang
2012-10-29 10:48 ` Daniel Mack
2012-10-28 15:35 ` [PATCH 3/5] ARM: PXA: Zipit Z2: Fix oops in z2_power_off Vasily Khoruzhick
2012-10-28 15:35 ` [PATCH 4/5] ARM: PXA: Zipit Z2: Change active_state of power button Vasily Khoruzhick
2012-10-28 22:01 ` Marek Vasut
2012-10-28 22:31 ` mark at engine12.com
2012-10-28 15:35 ` [PATCH 5/5] ARM: PXA: Zipit Z2: Fix backlight PWM device number Vasily Khoruzhick
2012-10-28 22:01 ` Marek Vasut
2012-10-28 22:23 ` Vasily Khoruzhick
2012-10-28 22:39 ` Marek Vasut
2012-10-28 15:39 ` [PATCH 1/5] ARM: PXA: Add z2-usb-switch driver Vasily Khoruzhick
2012-10-28 15:42 ` [PATCH v2 " Vasily Khoruzhick
2012-10-28 17:03 ` Marko Katić
2012-10-28 18:12 ` Vasily Khoruzhick
2012-10-28 21:57 ` Marek Vasut
2012-10-28 22:27 ` Vasily Khoruzhick
2012-10-28 22:38 ` Marek Vasut
2012-10-28 22:45 ` Vasily Khoruzhick
2012-10-28 22:48 ` Marek Vasut
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=508E651A.5070009@gmail.com \
--to=zonque@gmail.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).