[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9f02caa1-638a-cb72-c87f-69e4282ae67d@gmail.com>
Date: Wed, 1 Mar 2017 10:29:00 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: linux-kernel@...r.kernel.org,
Linus Walleij <linus.walleij@...aro.org>
Cc: swarren@...dia.com, andy.shevchenko@...il.com, alcooperx@...il.com,
"open list:PIN CONTROL SUBSYSTEM" <linux-gpio@...r.kernel.org>
Subject: Re: [PATCH fixes v2] pinctrl: Really force states during
suspend/resume
On 02/27/2017 03:06 PM, Florian Fainelli wrote:
> In case a platform only defaults a "default" set of pins, but not a
> "sleep" set of pins, and this particular platform suspends and resumes
> in a way that the pin states are not preserved by the hardware, when we
> resume, we would call pinctrl_single_resume() -> pinctrl_force_default()
> -> pinctrl_select_state() and the first thing we do is check that the
> pins state is the same as before, and do nothing.
>
> In order to fix this, decouple pinctrl_select_state and make it become
> pinctrl_commit_state(), taking an additional ignore_state_check boolean
> which allows us to bypass the state check during suspend/resume, since
> we really want to re-apply the previous pin states in these case.
>
> Fixes: 6e5e959dde0d ("pinctrl: API changes to support multiple states per device")
> Signed-off-by: Florian Fainelli <f.fainelli@...il.com>
Linus, I have a better version of this coming where the p->state ==
state check is just moved into pinctrl_select_state() instead.
--
Florian
Powered by blists - more mailing lists