From: <atull@opensource.altera.com>
To: <dinguyen@opensource.altera.com>, <linux@arm.linux.org.uk>
Cc: <pavel@denx.de>, <arnd@arndb.de>, <s.trumtrar@pengutronix.de>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <delicious.quinoa@gmail.com>,
<yvanderv@opensource.altera.com>,
Alan Tull <atull@opensource.altera.com>
Subject: [PATCH v3 0/2] socfpga: fix hotplug/add suspend to ram
Date: Tue, 14 Oct 2014 14:33:37 -0500 [thread overview]
Message-ID: <1413315219-28885-1-git-send-email-atull@opensource.altera.com> (raw)
From: Alan Tull <atull@opensource.altera.com>
Patch 1: socfpga: hotplug: put cpu1 in wfi
Use WFI when putting CPU1 to sleep. Don't hold CPU1 in reset
since that results in increased power consumption. Only
briefly reset CPU1.
Patch 2: socfpga: support suspend to ram
* allocate space in ocram using sram driver
* Add a function in ocram to do suspend to ram and
place DDR in self-refresh
Alan Tull (2):
socfpga: hotplug: put cpu1 in wfi
socfpga: support suspend to ram
arch/arm/mach-socfpga/Kconfig | 1 +
arch/arm/mach-socfpga/Makefile | 1 +
arch/arm/mach-socfpga/core.h | 7 ++
arch/arm/mach-socfpga/platsmp.c | 19 ++--
arch/arm/mach-socfpga/pm.c | 150 ++++++++++++++++++++++++++++++++
arch/arm/mach-socfpga/self-refresh.S | 157 ++++++++++++++++++++++++++++++++++
arch/arm/mach-socfpga/socfpga.c | 10 +++
7 files changed, 337 insertions(+), 8 deletions(-)
create mode 100644 arch/arm/mach-socfpga/pm.c
create mode 100644 arch/arm/mach-socfpga/self-refresh.S
--
1.7.9.5
next reply other threads:[~2014-10-14 19:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 19:33 atull [this message]
2014-10-14 19:33 ` [PATCH v3 1/2] socfpga: hotplug: put cpu1 in wfi atull
2014-10-15 7:48 ` Pavel Machek
2014-10-14 19:33 ` [PATCH v3 2/2] socfpga: support suspend to ram atull
2014-10-15 7:50 ` Pavel Machek
2014-10-15 20:17 ` atull
2014-10-23 14:59 ` Dinh Nguyen
2014-10-15 19:50 ` [PATCH v3 0/2] socfpga: fix hotplug/add " Dinh Nguyen
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=1413315219-28885-1-git-send-email-atull@opensource.altera.com \
--to=atull@opensource.altera.com \
--cc=arnd@arndb.de \
--cc=delicious.quinoa@gmail.com \
--cc=dinguyen@opensource.altera.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pavel@denx.de \
--cc=s.trumtrar@pengutronix.de \
--cc=yvanderv@opensource.altera.com \
/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