[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b6148647-c84c-4d21-ba68-6ed5a015aca7@tuxon.dev>
Date: Mon, 20 Nov 2023 11:08:00 +0200
From: claudiu beznea <claudiu.beznea@...on.dev>
To: thomas.perrot@...tlin.com, Russell King <linux@...linux.org.uk>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
clement.leger@...tlin.com
Subject: Re: [PATCH] ARM: at91: pm: set soc_pm.data.mode in
at91_pm_secure_init()
On 20.10.2023 16:02, thomas.perrot@...tlin.com wrote:
> From: Thomas Perrot <thomas.perrot@...tlin.com>
>
> In non secure mode, soc_pm.data.mode is set when entering pm in
> at91_pm_begin(). This value is used (not only) to determine if the system
> is going into slow clock mode (at91_suspend_entering_slow_clock()). This
> function is called from various drivers to check this and act accordingly.
> If not set, the driver might enter an incorrect suspend mode. When using
> secure suspend mode, at91_pm_begin() is not called and thus
> soc_pm.data.mode is not set. Since when using secure suspend, only one
> suspend mode is supported, set this value directly in
> at91_pm_secure_init().
>
> Signed-off-by: Clément Léger <clement.leger@...tlin.com>
> Signed-off-by: Thomas Perrot <thomas.perrot@...tlin.com>
Applied to at91-soc, thanks!
Powered by blists - more mailing lists