[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdbju9yFxuNtn+GsjNc=PSH=dF6AOEZygujm+sJVdv-eWQ@mail.gmail.com>
Date: Fri, 20 Jan 2017 10:49:25 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Neil Armstrong <narmstrong@...libre.com>
Cc: Mika Westerberg <mika.westerberg@...ux.intel.com>,
Alexandre Courbot <gnurou@...il.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/3] pinctrl / gpio: Introduce .set_config() callback for
GPIO chips
On Fri, Jan 20, 2017 at 10:24 AM, Neil Armstrong
<narmstrong@...libre.com> wrote:
>>> - return ret;
>>> + return pinctrl_gpio_set_config(chip->base + offset, config);
>>> }
>>
>> This is the beauty of it all..
>
> It would be even cooler it this becomes a generic helper !
It does, with this series we can push debounce and open source/drain
back to the pinctrl back-end.
Then the road is open to push any config this way, which I think will
also be needed for userspace GPIO to set up not just this but also
pull-ups etc. But we will add that step by step.
This provides a piece of much-needed infrastructure for this.
Yours,
Linus Walleij
Powered by blists - more mailing lists