[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZQpG5eHdDUy4aRxr6vEgs0qZHRMXUkCfms_VBYwiQeXg@mail.gmail.com>
Date: Wed, 12 Jun 2019 10:55:46 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Grygorii Strashko <grygorii.strashko@...com>
Cc: Russell King <rmk@....linux.org.uk>,
Tony Lindgren <tony@...mide.com>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Linux-OMAP <linux-omap@...r.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Santosh Shilimkar <ssantosh@...nel.org>,
Russell King <rmk+kernel@...linux.org.uk>
Subject: Re: [PATCH-next 15/20] gpio: gpio-omap: remove dataout variation in
context handling
On Mon, Jun 10, 2019 at 7:13 PM Grygorii Strashko
<grygorii.strashko@...com> wrote:
> From: Russell King <rmk+kernel@...linux.org.uk>
>
> When a GPIO block has the set/clear dataout registers implemented, it
> also has the normal dataout register implemented. Reading this register
> reads the current GPIO output state, and writing it sets the GPIOs to
> the explicit state. This is the behaviour that we want when saving and
> restoring the context, so use the dataout register exclusively.
>
> Signed-off-by: Russell King <rmk+kernel@...linux.org.uk>
> Signed-off-by: Grygorii Strashko <grygorii.strashko@...com>
Patch applied.
Yours,
Linus Walleij
Powered by blists - more mailing lists