[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VerNfUG1=VANDgFLchCmSG=DzoKN9DxHCoi2XxvcVBJcg@mail.gmail.com>
Date: Tue, 18 May 2021 00:06:54 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Sander Vanheule <sander@...nheule.net>
Cc: Pavel Machek <pavel@....cz>, Rob Herring <robh+dt@...nel.org>,
Lee Jones <lee.jones@...aro.org>,
Mark Brown <broonie@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J . Wysocki" <rafael@...nel.org>,
Michael Walle <michael@...le.cc>,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
linux-leds@...r.kernel.org, devicetree@...r.kernel.org,
linux-gpio@...r.kernel.org, Andrew Lunn <andrew@...n.ch>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/7] gpio: regmap: Add configurable dir/value order
On Mon, May 17, 2021 at 10:28 PM Sander Vanheule <sander@...nheule.net> wrote:
>
> GPIO chips may not support setting the output value when a pin is
> configured as an input, although the current implementation assumes this
> is always possible.
But it's broken hardware.
Can it be rather marked as a quirk?
> Add support for setting pin direction before value. The order defaults
> to setting the value first, but this can be reversed by setting the
> regmap_config.no_set_on_input flag, similar to the corresponding flag in
> the gpio-mmio driver.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists