[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdZ0oneKhFmug9k+zGP2Y0dncwHTEoQ35-ccQ=3MqQzSqw@mail.gmail.com>
Date: Wed, 27 Jan 2016 15:04:56 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Stefan Agner <stefan@...er.ch>
Cc: Shawn Guo <shawnguo@...nel.org>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
Adrian Alonso <aalonso@...escale.com>,
Markus Pargmann <mpa@...gutronix.de>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] pinctrl: freescale: imx: implement gpio_disable_free for Vybrid
On Fri, Jan 8, 2016 at 7:50 PM, Stefan Agner <stefan@...er.ch> wrote:
> The Freescale Vybrid SoC has GPIO capabilities as part of the
> IOMUXC. To enable GPIO's, the gpio_request_enable callback has
> been implemented, however the corsponding gpio_disable_free
> callback is missing. So far, disabling (unexporting) a GPIO left
> the pin in its last state.
>
> Implement a proper gpio_disable_free function which clears the
> three enable bits which influence the state (IBE, OBE and PUE).
>
> Signed-off-by: Stefan Agner <stefan@...er.ch>
Patch applied.
Yours,
Linus Walleij
Powered by blists - more mailing lists