[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171226033125.GA4210@X250>
Date: Tue, 26 Dec 2017 11:31:26 +0800
From: Shawn Guo <shawnguo@...nel.org>
To: Peng Fan <peng.fan@....com>
Cc: Dong Aisheng <aisheng.dong@....com>, linux-kernel@...r.kernel.org,
Russell King <linux@...linux.org.uk>,
Fabio Estevam <fabio.estevam@....com>,
Sascha Hauer <kernel@...gutronix.de>, van.freenix@...il.com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] arm: imx: suspend/resume: use outer_disable/resume
On Sun, Dec 10, 2017 at 08:07:18PM +0800, Peng Fan wrote:
> Use outer_disable/resume for suspend/resume.
> With the two APIs used, code could be simplified and easy to extend
> to introduce l2c_write_sec for i.MX platforms when moving Linux Kernel
> runs in non-secure world.
>
> Signed-off-by: Peng Fan <peng.fan@....com>
> Cc: Shawn Guo <shawnguo@...nel.org>
> Cc: Sascha Hauer <kernel@...gutronix.de>
> Cc: Fabio Estevam <fabio.estevam@....com>
> Cc: Russell King <linux@...linux.org.uk>
> Cc: Dong Aisheng <aisheng.dong@....com>
> ---
> arch/arm/mach-imx/pm-imx6.c | 2 ++
> arch/arm/mach-imx/suspend-imx6.S | 24 ------------------------
I'm fine with the patch in general. But this piece of code is running
on a few i.MX6 platforms, and I'm wondering on which SoCs you have
verified the change work fine.
Shawn
Powered by blists - more mailing lists