linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/9] ARM: tegra: add platform suspend support
Date: Tue, 12 Mar 2013 13:32:59 -0600	[thread overview]
Message-ID: <513F82EB.1030407@wwwdotorg.org> (raw)
In-Reply-To: <1363060916-8897-1-git-send-email-josephl@nvidia.com>

On 03/11/2013 10:01 PM, Joseph Lo wrote:
> This series introduces a basic functionality for Tegra to support the
> platform suspend and resume.
> 
> Note: This series only adds the support for Tegra20 and Tegra30. The
> Tegra114 will be supported later.

Aside from the few issues that have already been pointed out, this looks
OK now. I have a couple questions:

1) Please remind me if this series depends on anything. If not, I hope
to apply it mostly directly on top of 3.9-rc1 or so.

2) You mentioned that Tegra114 isn't supported. What is the failure mode
on Tegra114? Is suspend simply not available and hence can't be
requested, or will suspend attempts gracefully return an error, or will
there we crashes, boot failures, etc.?

3) Sorry for asking this again, but since only LP2 is actually
implemented in patch 4, what happens if the user selects LP0 or LP1?
Does the system (a) just use LP2, (b) fail to suspend, and hence
immediately resume, (c) suspend, but can't be resumed, ...?

Thanks.

  reply	other threads:[~2013-03-12 19:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12  4:01 [PATCH V2 0/9] ARM: tegra: add platform suspend support Joseph Lo
2013-03-12 19:32 ` Stephen Warren [this message]
2013-03-13  6:04   ` Joseph Lo
2013-03-13 17:34     ` Stephen Warren
2013-03-14  1:26       ` Joseph Lo
2013-03-14  4:43         ` Stephen Warren
2013-03-14 10:05           ` Joseph Lo

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=513F82EB.1030407@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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).