From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: linux-gpio <linux-gpio@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bamvor Jian Zhang <bamv2005@gmail.com>,
Drew Fustini <drew@pdp7.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v5 4/7] gpiolib: add support for biasing output lines
Date: Mon, 4 Nov 2019 23:59:27 +0800 [thread overview]
Message-ID: <20191104155927.GA17106@sol> (raw)
In-Reply-To: <CAMpxmJUExXZ=ptMyRczvdujc7x9JP62Zy9m+WByYD4=w=1180w@mail.gmail.com>
On Mon, Nov 04, 2019 at 04:50:30PM +0100, Bartosz Golaszewski wrote:
> pon., 4 lis 2019 o 16:39 Kent Gibson <warthog618@gmail.com> napisał(a):
> >
> > Allow pull up/down bias to be set on output lines.
> > Use case is for open source or open drain applications where
> > internal pull up/down may conflict with external biasing.
> >
> > Signed-off-by: Kent Gibson <warthog618@gmail.com>
> > ---
> > drivers/gpio/gpiolib.c | 8 ++++++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
> > index 7d8ff52ada42..de08d1a4a3fb 100644
> > --- a/drivers/gpio/gpiolib.c
> > +++ b/drivers/gpio/gpiolib.c
> > @@ -555,8 +555,9 @@ static int linehandle_create(struct gpio_device *gdev, void __user *ip)
> > (lflags & GPIOHANDLE_REQUEST_OPEN_SOURCE)))
> > return -EINVAL;
> >
> > - /* Bias flags only allowed for input mode. */
> > - if (!(lflags & GPIOHANDLE_REQUEST_INPUT) &&
> > + /* Bias flags only allowed for input or output mode. */
> > + if (!((lflags & GPIOHANDLE_REQUEST_INPUT) ||
> > + (lflags & GPIOHANDLE_REQUEST_OUTPUT)) &&
> > ((lflags & GPIOHANDLE_REQUEST_BIAS_DISABLE) ||
> > (lflags & GPIOHANDLE_REQUEST_BIAS_PULL_UP) ||
> > (lflags & GPIOHANDLE_REQUEST_BIAS_PULL_DOWN)))
> > @@ -3144,6 +3145,9 @@ int gpiod_direction_output(struct gpio_desc *desc, int value)
> > }
> >
> > set_output_value:
> > + ret = gpio_set_bias(gc, desc);
> > + if (ret)
> > + return ret;
> > return gpiod_direction_output_raw_commit(desc, value);
>
> Ugh, I missed one thing here - my for-next branch doesn't contain the
> following commit e735244e2cf0 ("gpiolib: don't clear FLAG_IS_OUT when
> emulating open-drain/open-source") which happens to modify this
> function.
>
> If I provided you with a branch containing it - would it be a lot of
> effort on your part to rebase it on top of it? If so - I can do it
> myself.
>
I can do a rebase - though not until tomorrow (it is getting late here).
I would like that commit in as well - I suspect it being missing is
the reason a couple of the gpiod tests I was working on are failing.
I was in the process of tracking that down when I switched back to this.
Cheers,
Kent.
next prev parent reply other threads:[~2019-11-04 15:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 15:38 [PATCH v5 0/7] gpio: expose line bias flags to userspace Kent Gibson
2019-11-04 15:38 ` [PATCH v5 1/7] gpio: expose pull-up/pull-down line " Kent Gibson
2019-11-04 15:38 ` [PATCH v5 2/7] gpiolib: add support for pull up/down to lineevent_create Kent Gibson
2019-11-04 15:38 ` [PATCH v5 3/7] gpiolib: add support for disabling line bias Kent Gibson
2019-11-04 15:38 ` [PATCH v5 4/7] gpiolib: add support for biasing output lines Kent Gibson
2019-11-04 15:50 ` Bartosz Golaszewski
2019-11-04 15:59 ` Kent Gibson [this message]
2019-11-04 16:19 ` Bartosz Golaszewski
2019-11-05 2:03 ` Kent Gibson
2019-11-05 6:06 ` Kent Gibson
2019-11-05 9:10 ` Bartosz Golaszewski
2019-11-04 15:38 ` [PATCH v5 5/7] gpio: mockup: add set_config to support pull up/down Kent Gibson
2019-11-04 15:38 ` [PATCH v5 6/7] gpiolib: move validation of line handle flags into helper function Kent Gibson
2019-11-04 15:38 ` [PATCH v5 7/7] gpio: add new SET_CONFIG ioctl() to gpio chardev Kent Gibson
2019-11-04 19:58 ` [PATCH v5 0/7] gpio: expose line bias flags to userspace Drew Fustini
2019-11-05 0:12 ` Kent Gibson
2019-11-05 5:34 ` Kent Gibson
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=20191104155927.GA17106@sol \
--to=warthog618@gmail.com \
--cc=bamv2005@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=drew@pdp7.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.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).