[RFC PATCH 1/5] gpio: gpiolib: Add core support for maintaining GPIO values on reset
linus.walleij at linaro.org
Fri Oct 20 18:43:29 AEDT 2017
On Fri, Oct 20, 2017 at 9:17 AM, Linus Walleij <linus.walleij at linaro.org> wrote:
> On Fri, Oct 20, 2017 at 5:37 AM, Andrew Jeffery <andrew at aj.id.au> wrote:
>> GPIO state reset tolerance is implemented in gpiolib through the
>> addition of a new pinconf parameter. With that, some renaming of helpers
>> is done to clarify the scope of the already existing
>> gpiochip_line_is_persistent(), as it's now ambiguous as to whether that
>> means on suspend, reset or both.
> Isn't it most reasonable to say persistance covers both cases, reset
> and/or sleep? This seems a bit like overdefined.
I should also add: right now persistance is defined in negative terms,
you can supply the flag "may lose value", which means the subsystem
by default, and driver by default, will try to keep values persistent across
Then it is possible to opt in for not doing so. (Usually to save power I
I think that especially for userspace use cases, saving power should
not really be the concern, but correct me if I'm wrong. I am thinking
of a box with a DC plug wired up to a factory line here.
What we have in the Arizona driver is an opt-in where the DT can
say "don't preserve the value this line during system sleep" i.e. "lay lose
value" and we can extend that flag to mean "don't preserve this line
during reset either" but by default assume that we should.
More information about the Linux-aspeed