[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 4 Apr 2016 16:17:33 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Cristina Ciocan <cristina.ciocan@...el.com>
Cc: Mathias Nyman <mathias.nyman@...ux.intel.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Irina Tirdea <irina.tirdea@...el.com>,
Octavian Purdila <octavian.purdila@...el.com>
Subject: Re: [PATCH v4 6/6] pinctrl: baytrail: Add debounce configuration
On Fri, Apr 1, 2016 at 1:00 PM, Cristina Ciocan
<cristina.ciocan@...el.com> wrote:
> Make debounce setting and getting functionality available when
> configurating a certain pin.
>
> Signed-off-by: Cristina Ciocan <cristina.ciocan@...el.com>
Patch applied.
And as this is another case where GPIO has a debounce
setting call: gpiod_set_debounce() this is another case for
my suggested pinctrl_gpio_set_config() as that call is
currently not implemented in your corresponding .set_debounce()
callback for the GPIO chip, but could easily be handled
by calling back into the pinctrl back-end, right?
Yours,
Linus Walleij
Powered by blists - more mailing lists