From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 2/2] ARM hibernation / suspend-to-disk
Date: Sun, 16 Mar 2014 04:09:17 -0300 [thread overview]
Message-ID: <20140316070917.GA3094@arch.cereza> (raw)
In-Reply-To: <1394016605-24120-3-git-send-email-sebastian.capella@linaro.org>
On Mar 05, Sebastian Capella wrote:
[..]
> diff --git a/arch/arm/mm/Kconfig b/arch/arm/mm/Kconfig
> index 1f8fed9..83707702 100644
> --- a/arch/arm/mm/Kconfig
> +++ b/arch/arm/mm/Kconfig
> @@ -611,6 +611,11 @@ config CPU_USE_DOMAINS
> config IO_36
> bool
>
> +config ARCH_HIBERNATION_POSSIBLE
> + bool
> + depends on MMU
> + default y if CPU_ARM920T || CPU_ARM926T || CPU_SA1100 || CPU_XSCALE || CPU_XSC3 || CPU_V6 || CPU_V6K || CPU_V7
> +
> comment "Processor Features"
>
Is there any reason why CPU_FEROCEON is not listed here? FWIW, I've just built
(but not really tested) a Kirkwood kernel with CONFIG_HIBERNATION=y.
And is there any reason to put this config in arch/arm/mm/Kconfig, instead of
in arch/arm/Kconfig, below ARCH_SUSPEND_POSSIBLE?
I'm also puzzled about having two separate options for suspend and hibernate,
maybe someone can explain me why a given CPU would support the former but not
the latter?
Thanks!
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-16 7:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 10:50 [PATCH v7 0/2] hibernation support on ARM Sebastian Capella
2014-03-05 10:50 ` [PATCH v7 1/2] ARM: avoid tracers in soft_restart Sebastian Capella
2014-03-06 23:45 ` Sebastian Capella
2014-03-19 23:26 ` Sebastian Capella
2014-03-05 10:50 ` [PATCH v7 2/2] ARM hibernation / suspend-to-disk Sebastian Capella
2014-03-07 4:21 ` Sebastian Capella
2014-03-07 4:42 ` Stephen Boyd
2014-03-10 18:32 ` Sebastian Capella
2014-03-16 9:46 ` Russell King - ARM Linux
2014-03-17 22:07 ` Sebastian Capella
2014-03-16 7:09 ` Ezequiel Garcia [this message]
2014-03-17 19:10 ` Sebastian Capella
2014-03-17 20:44 ` Ezequiel Garcia
2014-03-17 22:39 ` Sebastian Capella
2014-03-19 15:44 ` Ezequiel Garcia
2014-03-19 20:47 ` Sebastian Capella
2014-03-19 21:06 ` Sebastian Capella
2014-03-24 18:06 ` Sebastian Capella
2014-03-25 18:38 ` Alexander Holler
2014-03-25 18:48 ` Sebastian Capella
2014-03-25 23:36 ` Alexander Holler
2014-03-26 0:00 ` Alexander Holler
2014-03-20 3:02 ` TonyHo
2014-03-20 17:26 ` Sebastian Capella
2014-04-16 10:12 ` Russell King - ARM Linux
2014-04-16 16:42 ` Sebastian Capella
2014-04-17 20:38 ` Sebastian Capella
2014-04-23 0:38 ` Sebastian Capella
2014-04-23 16:39 ` Sebastian Capella
2014-05-07 15:37 ` Pavel Machek
2014-05-07 22:20 ` Sebastian Capella
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=20140316070917.GA3094@arch.cereza \
--to=ezequiel.garcia@free-electrons.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