From: Tomasz Figa <tomasz.figa@gmail.com>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Kukjin Kim <kgene.kim@samsung.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Tomasz Figa <t.figa@samsung.com>,
Sachin Kamat <sachin.kamat@linaro.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Kyungmin Park <kyungmin.park@samsung.com>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org
Subject: Re: [PATCH v2 5/7] ARM: EXYNOS: PM: use c15resume firmware method if secure firmware is enabled
Date: Mon, 02 Jun 2014 15:07:46 +0200 [thread overview]
Message-ID: <538C7722.8020706@gmail.com> (raw)
In-Reply-To: <1401712543-14281-6-git-send-email-b.zolnierkie@samsung.com>
Hi,
On 02.06.2014 14:35, Bartlomiej Zolnierkiewicz wrote:
> Use c15resume firmware method instead of accessing the registers
> directly in exynos_cpu_restore_register() if secure firmware is
> enabled. This affects both PM resume method and cpuidle AFTR mode.
>
> This patch shouldn't cause any functionality changes on boards that
> don't use secure firmware.
>
> Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> Acked-by: Kyungmin Park <kyungmin.park@samsung.com>
> ---
> arch/arm/mach-exynos/pm.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm/mach-exynos/pm.c b/arch/arm/mach-exynos/pm.c
> index cf09383..aeff99e 100644
> --- a/arch/arm/mach-exynos/pm.c
> +++ b/arch/arm/mach-exynos/pm.c
> @@ -26,6 +26,7 @@
> #include <asm/hardware/cache-l2x0.h>
> #include <asm/smp_scu.h>
> #include <asm/suspend.h>
> +#include <asm/firmware.h>
>
> #include <plat/pm-common.h>
> #include <plat/pll.h>
> @@ -232,6 +233,9 @@ static void exynos_cpu_restore_register(void)
> {
> unsigned long tmp;
>
> + if (call_firmware_op(c15resume, save_arm_register) == 0)
> + return;
> +
As I mentioned in my comments to patch 2/7, instead of introducing
heavily SoC-specific operations, I'd rather add more general suspend and
resume firmware operations which would take care of both saving and
restoring those registers.
Best regards,
Tomasz
next prev parent reply other threads:[~2014-06-02 13:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 12:35 [PATCH v2 0/7] ARM: EXYNOS: cpuidle: fix AFTR mode on boards with secure firmware enabled Bartlomiej Zolnierkiewicz
2014-06-02 12:35 ` [PATCH v2 1/7] arm: firmware: Check firmware is running or not Bartlomiej Zolnierkiewicz
2014-06-02 12:51 ` Tomasz Figa
2014-06-02 13:05 ` Bartlomiej Zolnierkiewicz
2014-06-02 12:35 ` [PATCH v2 2/7] ARM: EXYNOS: add support for firmware-assisted c15resume Bartlomiej Zolnierkiewicz
2014-06-02 12:56 ` Tomasz Figa
2014-06-02 12:35 ` [PATCH v2 3/7] ARM: EXYNOS: add AFTR mode support to firmware do_idle method Bartlomiej Zolnierkiewicz
2014-06-02 13:01 ` Tomasz Figa
2014-06-02 12:35 ` [PATCH v2 4/7] ARM: EXYNOS: PM: replace EXYNOS_BOOT_VECTOR_* macros by static inlines Bartlomiej Zolnierkiewicz
2014-06-02 13:05 ` Tomasz Figa
2014-06-02 13:16 ` Bartlomiej Zolnierkiewicz
2014-06-02 16:13 ` Daniel Lezcano
2014-06-02 12:35 ` [PATCH v2 5/7] ARM: EXYNOS: PM: use c15resume firmware method if secure firmware is enabled Bartlomiej Zolnierkiewicz
2014-06-02 13:07 ` Tomasz Figa [this message]
2014-06-02 12:35 ` [PATCH v2 6/7] ARM: EXYNOS: PM: fix register setup on EXYNOS4x12 for AFTR mode code Bartlomiej Zolnierkiewicz
2014-06-02 13:10 ` Tomasz Figa
2014-06-02 12:35 ` [PATCH v2 7/7] ARM: EXYNOS: cpuidle: add secure firmware support to " Bartlomiej Zolnierkiewicz
2014-06-02 13:15 ` Tomasz Figa
2014-06-02 13:40 ` Bartlomiej Zolnierkiewicz
2014-06-02 16:28 ` Daniel Lezcano
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=538C7722.8020706@gmail.com \
--to=tomasz.figa@gmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.lezcano@linaro.org \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sachin.kamat@linaro.org \
--cc=t.figa@samsung.com \
--cc=viresh.kumar@linaro.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).