From: Linus Walleij <linus.walleij@linaro.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
Neil Armstrong <narmstrong@baylibre.com>
Cc: Alexandre Courbot <gnurou@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] pinctrl / gpio: Introduce .set_config() callback for GPIO chips
Date: Fri, 20 Jan 2017 10:13:05 +0100 [thread overview]
Message-ID: <CACRpkdbsOvJkpNtjvCXRNWV6dA6onzomn-E+9n=xJabmcRGbEQ@mail.gmail.com> (raw)
In-Reply-To: <20170119094820.83595-4-mika.westerberg@linux.intel.com>
On Thu, Jan 19, 2017 at 10:48 AM, Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:
> Currently we already have two pin configuration related callbacks
> available for GPIO chips .set_single_ended() and .set_debounce(). In
> future we expect to have even more, which does not scale well if we need
> to add yet another callback to the GPIO chip structure for each possible
> configuration parameter.
>
> Better solution is to reuse what we already have available in the
> generic pinconf.
>
> To support this, we introduce a new .set_config() callback for GPIO
> chips. The callback takes a single packed pin configuration value as
> parameter. This can then be extended easily beyond what is currently
> supported by just adding new types to the generic pinconf enum.
>
> We then convert the existing drivers over .set_config() and finally
> remove the .set_single_ended() and .set_debounce() callbacks.
>
> Suggested-by: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Yes!!! This is exactly how this should be done.
Can't wait to apply the final version of this.
> +static int gpio_set_drive_mode(struct gpio_chip *gc, unsigned offset,
> + enum pin_config_param mode)
> +{
> + unsigned long config = { PIN_CONF_PACKED(mode, 0) };
> +
> + return gc->set_config ? gc->set_config(gc, offset, config) : -ENOTSUPP;
> +}
I would name it gpio_set_drive_single_ended() as the open source/open
drain is all we support here.
> if (test_bit(FLAG_OPEN_DRAIN, &desc->flags)) {
> /* First see if we can enable open drain in hardware */
> - if (gc->set_single_ended) {
> - ret = gc->set_single_ended(gc, gpio_chip_hwgpio(desc),
> - LINE_MODE_OPEN_DRAIN);
> - if (!ret)
> - goto set_output_value;
> - }
> + ret = gpio_set_drive_mode(gc, gpio_chip_hwgpio(desc),
> + PIN_CONFIG_DRIVE_OPEN_DRAIN);
> + if (!ret)
> + goto set_output_value;
Aha I see, so if we fail to set single ended we get to the next step.
Nice.
> /* Emulate open drain by not actively driving the line high */
> if (val)
> return gpiod_direction_input(desc);
> }
(...)
> - if (gc->set_single_ended) {
> - ret = gc->set_single_ended(gc, gpio_chip_hwgpio(desc),
> - LINE_MODE_OPEN_SOURCE);
> - if (!ret)
> - goto set_output_value;
> - }
> + ret = gpio_set_drive_mode(gc, gpio_chip_hwgpio(desc),
> + PIN_CONFIG_DRIVE_OPEN_SOURCE);
> /* Emulate open source by not actively driving the line low */
> if (!val)
> return gpiod_direction_input(desc);
But here the handling seems to be wrong? You still need
the if (!ret) goto set_output_value?
> } else {
> - /* Make sure to disable open drain/source hardware, if any */
> - if (gc->set_single_ended)
> - gc->set_single_ended(gc,
> - gpio_chip_hwgpio(desc),
> - LINE_MODE_PUSH_PULL);
> + gpio_set_drive_mode(gc, gpio_chip_hwgpio(desc),
> + PIN_CONFIG_DRIVE_PUSH_PULL);
Nice.
> -static int sx150x_gpio_set_single_ended(struct gpio_chip *chip,
> - unsigned int offset,
> - enum single_ended_mode mode)
> +static int sx150x_gpio_set_config(struct gpio_chip *chip, unsigned int offset,
> + unsigned long config)
> {
> - struct sx150x_pinctrl *pctl = gpiochip_get_data(chip);
> - int ret;
> -
> - switch (mode) {
> - case LINE_MODE_PUSH_PULL:
> - if (pctl->data->model != SX150X_789 ||
> - sx150x_pin_is_oscio(pctl, offset))
> - return 0;
> -
> - ret = regmap_write_bits(pctl->regmap,
> - pctl->data->pri.x789.reg_drain,
> - BIT(offset), 0);
> - break;
> -
> - case LINE_MODE_OPEN_DRAIN:
> - if (pctl->data->model != SX150X_789 ||
> - sx150x_pin_is_oscio(pctl, offset))
> - return -ENOTSUPP;
> -
> - ret = regmap_write_bits(pctl->regmap,
> - pctl->data->pri.x789.reg_drain,
> - BIT(offset), BIT(offset));
> - break;
> - default:
> - ret = -ENOTSUPP;
> - break;
> - }
> -
> - return ret;
> + return pinctrl_gpio_set_config(chip->base + offset, config);
> }
This is the beauty of it all..
> @@ -811,16 +782,26 @@ static int sx150x_pinconf_set(struct pinctrl_dev *pctldev, unsigned int pin,
> break;
>
> case PIN_CONFIG_DRIVE_OPEN_DRAIN:
> - ret = sx150x_gpio_set_single_ended(&pctl->gpio,
> - pin, LINE_MODE_OPEN_DRAIN);
> + if (pctl->data->model != SX150X_789 ||
> + sx150x_pin_is_oscio(pctl, pin))
> + return -ENOTSUPP;
> +
> + ret = regmap_write_bits(pctl->regmap,
> + pctl->data->pri.x789.reg_drain,
> + BIT(pin), BIT(pin));
> if (ret < 0)
> return ret;
>
> break;
>
> case PIN_CONFIG_DRIVE_PUSH_PULL:
> - ret = sx150x_gpio_set_single_ended(&pctl->gpio,
> - pin, LINE_MODE_PUSH_PULL);
> + if (pctl->data->model != SX150X_789 ||
> + sx150x_pin_is_oscio(pctl, pin))
> + return 0;
> +
> + ret = regmap_write_bits(pctl->regmap,
> + pctl->data->pri.x789.reg_drain,
> + BIT(pin), 0);
> if (ret < 0)
> return ret;
>
> @@ -1178,7 +1159,7 @@ static int sx150x_probe(struct i2c_client *client,
> pctl->gpio.direction_output = sx150x_gpio_direction_output;
> pctl->gpio.get = sx150x_gpio_get;
> pctl->gpio.set = sx150x_gpio_set;
> - pctl->gpio.set_single_ended = sx150x_gpio_set_single_ended;
> + pctl->gpio.set_config = sx150x_gpio_set_config;
Would be nice if some SX150x person could look at this but it seems just
right to me.
> diff --git a/include/linux/gpio/driver.h b/include/linux/gpio/driver.h
> index c2748accea71..2939c1d84add 100644
> --- a/include/linux/gpio/driver.h
> +++ b/include/linux/gpio/driver.h
> @@ -8,6 +8,7 @@
> #include <linux/irqdomain.h>
> #include <linux/lockdep.h>
> #include <linux/pinctrl/pinctrl.h>
> +#include <linux/pinctrl/pinconf-generic.h>
Yups there is lands...
Thanks, I'm impressed.
Hope I'll be able to apply v2.
Yours,
Linus Walleij
next prev parent reply other threads:[~2017-01-20 9:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 9:48 [PATCH 0/3] pinctrl / gpio: Allow GPIO chips to use generic pinconfig Mika Westerberg
2017-01-19 9:48 ` [PATCH 1/3] pinctrl: Widen the generic pinconf argument from 16 to 24 bits Mika Westerberg
2017-01-19 12:04 ` Andy Shevchenko
2017-01-20 8:43 ` Linus Walleij
2017-01-19 9:48 ` [PATCH 2/3] pinctrl: Allow configuration of pins from gpiolib based drivers Mika Westerberg
2017-01-19 12:11 ` Andy Shevchenko
2017-01-20 8:48 ` Linus Walleij
2017-01-19 9:48 ` [PATCH 3/3] pinctrl / gpio: Introduce .set_config() callback for GPIO chips Mika Westerberg
2017-01-19 12:17 ` Andy Shevchenko
2017-01-20 9:13 ` Linus Walleij [this message]
2017-01-20 9:24 ` Neil Armstrong
2017-01-20 9:49 ` Linus Walleij
2017-01-20 13:36 ` Mika Westerberg
2017-01-19 12:17 ` [PATCH 0/3] pinctrl / gpio: Allow GPIO chips to use generic pinconfig Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACRpkdbsOvJkpNtjvCXRNWV6dA6onzomn-E+9n=xJabmcRGbEQ@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gnurou@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=narmstrong@baylibre.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).