From: Alexandre Courbot <acourbot@nvidia.com>
To: Tomasz Figa <t.figa@samsung.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kukjin Kim <kgene.kim@samsung.com>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Stephen Warren <swarren@nvidia.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Tomasz Figa <tomasz.figa@gmail.com>
Subject: Re: [PATCH 1/2] ARM: firmware: Introduce suspend and resume operations
Date: Thu, 26 Jun 2014 11:33:30 +0900 [thread overview]
Message-ID: <53AB867A.901@nvidia.com> (raw)
In-Reply-To: <1403713114-18923-2-git-send-email-t.figa@samsung.com>
On 06/26/2014 01:18 AM, Tomasz Figa wrote:
> This patch extends the firmware_ops structure with two new callbacks:
> .suspend() and .resume(). The former is intended to ask the firmware to
> save all its volatile state and suspend the system, without returning
> back to the kernel in between. The latter is to be called early by
> very low level platform suspend code after waking up to restore low
> level hardware state, which can't be restored in non-secure mode.
>
> While at it, outdated version of the structure is removed from the
> documentation and replaced with a reference to the header file.
Acked-by: Alexandre Courbot <acourbot@nvidia.com>
WARNING: multiple messages have this Message-ID (diff)
From: acourbot@nvidia.com (Alexandre Courbot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: firmware: Introduce suspend and resume operations
Date: Thu, 26 Jun 2014 11:33:30 +0900 [thread overview]
Message-ID: <53AB867A.901@nvidia.com> (raw)
In-Reply-To: <1403713114-18923-2-git-send-email-t.figa@samsung.com>
On 06/26/2014 01:18 AM, Tomasz Figa wrote:
> This patch extends the firmware_ops structure with two new callbacks:
> .suspend() and .resume(). The former is intended to ask the firmware to
> save all its volatile state and suspend the system, without returning
> back to the kernel in between. The latter is to be called early by
> very low level platform suspend code after waking up to restore low
> level hardware state, which can't be restored in non-secure mode.
>
> While at it, outdated version of the structure is removed from the
> documentation and replaced with a reference to the header file.
Acked-by: Alexandre Courbot <acourbot@nvidia.com>
next prev parent reply other threads:[~2014-06-26 2:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 16:18 [PATCH 0/2] Firmware-assisted suspend/resume of Exynos SoCs Tomasz Figa
2014-06-25 16:18 ` Tomasz Figa
2014-06-25 16:18 ` [PATCH 1/2] ARM: firmware: Introduce suspend and resume operations Tomasz Figa
2014-06-25 16:18 ` Tomasz Figa
2014-06-26 2:33 ` Alexandre Courbot [this message]
2014-06-26 2:33 ` Alexandre Courbot
2014-06-25 16:18 ` [PATCH 2/2] ARM: EXYNOS: Add support for firmware-assisted suspend/resume Tomasz Figa
2014-06-25 16:18 ` Tomasz Figa
2014-06-25 22:54 ` Russell King - ARM Linux
2014-06-25 22:54 ` Russell King - ARM Linux
2014-06-26 11:33 ` Daniel Drake
2014-06-26 11:33 ` Daniel Drake
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=53AB867A.901@nvidia.com \
--to=acourbot@nvidia.com \
--cc=arnd@arndb.de \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=olof@lixom.net \
--cc=swarren@nvidia.com \
--cc=t.figa@samsung.com \
--cc=tomasz.figa@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.