linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Kent Gibson <warthog618@gmail.com>
Cc: Russell King - ARM Linux admin <linux@armlinux.org.uk>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-gpio <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] gpiolib: fix up emulated open drain outputs
Date: Wed, 11 Dec 2019 10:39:30 +0100	[thread overview]
Message-ID: <CAMpxmJVm-CDNMuY=Y85BWgn2ZNOB5CveavfiCTxYphKDDDw4TA@mail.gmail.com> (raw)
In-Reply-To: <20191208133436.GA20748@sol>

niedz., 8 gru 2019 o 14:34 Kent Gibson <warthog618@gmail.com> napisał(a):
>
> > > > >
> > > > > 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.
> >
> > That would be nice, but it would also be nice to be sure that the fix
> > works there _and_ it doesn't break anything by fixing it.
> >
> > I regard this as a risky change: with open drain/open source "outputs"
> > it is quite obvious when the pin is being driven, it is in output mode.
> > When the driver is off though, it is debatable whether it should be
> > regarded as in input or output mode.
> >
>
> Higher powers can make the call on that.
>
> I just wanted to point out that the fix only deals with one of the two
> cases that need to be fixed - in case that slipped by.
>

I'll apply this patch as is and if someone reports problems with the
opposite condition, then we'll fix that too.

Bartosz

      reply	other threads:[~2019-12-11  9:39 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
2019-12-08 13:02       ` Russell King - ARM Linux admin
2019-12-08 13:34         ` Kent Gibson
2019-12-11  9:39           ` Bartosz Golaszewski [this message]

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='CAMpxmJVm-CDNMuY=Y85BWgn2ZNOB5CveavfiCTxYphKDDDw4TA@mail.gmail.com' \
    --to=bgolaszewski@baylibre.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=warthog618@gmail.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).