On Wed, 2017-10-25 at 09:11 +0100, Charles Keepax wrote: > On Fri, Oct 20, 2017 at 07:02:27PM +1030, Andrew Jeffery wrote: > > On Fri, 2017-10-20 at 09:43 +0200, Linus Walleij wrote: > > > On Fri, Oct 20, 2017 at 9:17 AM, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote: > > > > > > On Fri, Oct 20, 2017 at 5:37 AM, Andrew Jeffery <andrew@xxxxxxxx> 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. > > Seems reasonable to me to just expand the existing stuff to cover > reset as well, I don't think that should cause any issues for the > Arizona stuff. Great. I addressed this in the non-RFC series. Thanks for the feedback. Andrew
Attachment:
signature.asc
Description: This is a digitally signed message part
