From: Dinh Nguyen <dinguyen@opensource.altera.com>
To: Alan Tull <atull@opensource.altera.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Pavel Machek <pavel@denx.de>, Arnd Bergmann <arnd@arndb.de>,
Steffen Trumtrar <s.trumtrar@pengutronix.de>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org,
Delicious Quinoq <delicious.quinoa@gmail.com>
Subject: Re: [PATCHv6 0/2] socfpga: support suspend to ram*
Date: Thu, 4 Jun 2015 17:35:06 -0500 [thread overview]
Message-ID: <5570D29A.2030007@opensource.altera.com> (raw)
In-Reply-To: <556E028E.2080800@opensource.altera.com>
Hi Alan,
On 06/02/2015 02:22 PM, Dinh Nguyen wrote:
> On 06/02/2015 01:35 PM, Alan Tull wrote:
>> Support suspend to ram on socfpga.
>> * allocate space in ocram using sram driver.
>> * Add a function in ocram to place DDR in self-refresh
>> and suspend.
>> * Prevent suspend if EDAC is enabled.
>> * Add a device tree binding document for the Altera
>> SOCFPGA SDRAM controller that is used to put DDR in
>> self-refresh mode.
>>
>> Alan Tull (2):
>> ARM: socfpga: support suspend to ram
>> ARM: socfpga: dts: add sdram controller dt binding doc
>>
>> .../arm/altera/socfpga-sdram-controller.txt | 12 ++
>> arch/arm/mach-socfpga/Kconfig | 10 +-
>> arch/arm/mach-socfpga/Makefile | 1 +
>> arch/arm/mach-socfpga/core.h | 6 +-
>> arch/arm/mach-socfpga/pm.c | 149 ++++++++++++++++++++
>> arch/arm/mach-socfpga/self-refresh.S | 136 ++++++++++++++++++
>> arch/arm/mach-socfpga/socfpga.c | 6 +-
>> drivers/edac/altera_edac.c | 20 +++
>> 8 files changed, 337 insertions(+), 3 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/arm/altera/socfpga-sdram-controller.txt
>> create mode 100644 arch/arm/mach-socfpga/pm.c
>> create mode 100644 arch/arm/mach-socfpga/self-refresh.S
>>
>
>
> Applied.
>
I had to un-apply this patch because I noticed that it's touching
drivers/edac/altera_edac.c. This part should be a separate patch and
need to go through linux-edac.
Dinh
next prev parent reply other threads:[~2015-06-04 22:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 18:35 [PATCHv6 0/2] socfpga: support suspend to ram* Alan Tull
2015-06-02 18:35 ` [PATCHv6 1/2] ARM: socfpga: support suspend to ram Alan Tull
[not found] ` <1433270139-7042-2-git-send-email-atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
2015-06-09 9:46 ` Pavel Machek
2015-06-02 18:35 ` [PATCHv6 2/2] ARM: socfpga: dts: add sdram controller dt binding doc Alan Tull
2015-06-02 19:22 ` [PATCHv6 0/2] socfpga: support suspend to ram* Dinh Nguyen
2015-06-04 22:35 ` Dinh Nguyen [this message]
[not found] ` <5570D29A.2030007-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
2015-06-05 13:14 ` Dinh Nguyen
2015-06-05 14:11 ` atull
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=5570D29A.2030007@opensource.altera.com \
--to=dinguyen@opensource.altera.com \
--cc=arnd@arndb.de \
--cc=atull@opensource.altera.com \
--cc=delicious.quinoa@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pavel@denx.de \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.trumtrar@pengutronix.de \
/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).