All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Gibson <warthog618@gmail.com>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	linux-gpio@vger.kernel.org
Subject: Re: [PATCH] gpiolib: fix up emulated open drain outputs
Date: Sun, 8 Dec 2019 15:51:43 +0800	[thread overview]
Message-ID: <20191208075143.GA13664@sol> (raw)
In-Reply-To: <20191208071823.GZ25745@shell.armlinux.org.uk>

On Sun, Dec 08, 2019 at 07:18:23AM +0000, Russell King - ARM Linux admin wrote:
> On Sun, Dec 08, 2019 at 11:43:40AM +0800, Kent Gibson wrote:
> > On Sat, Dec 07, 2019 at 04:20:18PM +0000, Russell King wrote:
> > > gpiolib has a corner case with open drain outputs that are emulated.
> > > When such outputs are outputting a logic 1, emulation will set the
> > > hardware to input mode, which will cause gpiod_get_direction() to
> > > report that it is in input mode. This is different from the behaviour
> > > with a true open-drain output.
> > > 
> > > Unify the semantics here.
> > > 
> > > Suggested-by: Linus Walleij <linus.walleij@linaro.org>
> > > Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
> > > ---
> > >  drivers/gpio/gpiolib.c | 8 ++++++++
> > >  1 file changed, 8 insertions(+)
> > > 
> > > diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
> > > index 32c2048deb8c..70c60aac41cc 100644
> > > --- a/drivers/gpio/gpiolib.c
> > > +++ b/drivers/gpio/gpiolib.c
> > > @@ -220,6 +220,14 @@ int gpiod_get_direction(struct gpio_desc *desc)
> > >  	chip = gpiod_to_chip(desc);
> > >  	offset = gpio_chip_hwgpio(desc);
> > >  
> > > +	/*
> > > +	 * Open drain emulation using input mode may incorrectly report
> > > +	 * input here, fix that up.
> > > +	 */
> > > +	if (test_bit(FLAG_OPEN_DRAIN, &desc->flags) &&
> > > +	    test_bit(FLAG_IS_OUT, &desc->flags))
> > > +		return 0;
> > > +
> > 
> > What about the FLAG_OPEN_SOURCE case?
> 
> do you have a scenario you can test?
> 

No I don't - if I had a scenario that had tripped over this problem
then I would've submitted a patch already ;-).

I'm simply pointing out that the logic that applies to
emulating OPEN_DRAIN also applies to emulating OPEN_SOURCE.
IMHO if you are fixing this for one then it should be fixed for both.

I'd love to see some test cases for the gpiolib driver-api, including
this function.
But I'm relatively new here, and am generally coming from the userspace
side, so will have to admit ignorance to anything related to testing
APIs within the kernel.

Kent.

> -- 
> RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
> FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
> According to speedtest.net: 11.9Mbps down 500kbps up

  reply	other threads:[~2019-12-08  7:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-07 16:20 [PATCH] gpiolib: fix up emulated open drain outputs Russell King
2019-12-08  3:43 ` Kent Gibson
2019-12-08  7:18   ` Russell King - ARM Linux admin
2019-12-08  7:51     ` Kent Gibson [this message]
2019-12-08 13:02       ` Russell King - ARM Linux admin
2019-12-08 13:34         ` Kent Gibson
2019-12-11  9:39           ` Bartosz Golaszewski

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=20191208075143.GA13664@sol \
    --to=warthog618@gmail.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.