devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	"linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Giuseppe Barba <giuseppe.barba-qxv4g6HH51o@public.gmane.org>,
	Denis Ciocca <denis.ciocca-qxv4g6HH51o@public.gmane.org>
Subject: Re: [PATCH 4/4 v4] iio: st_sensors: support open drain mode
Date: Thu, 14 Apr 2016 08:30:34 -0500	[thread overview]
Message-ID: <20160414133034.GA10104@rob-hp-laptop> (raw)
In-Reply-To: <CACRpkdZs6g+UEOo+pEd1bS1tV7JpUhA1uJ9s6i=Jr39R=2RGfQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Thu, Apr 14, 2016 at 10:36:53AM +0200, Linus Walleij wrote:
> On Wed, Apr 13, 2016 at 10:52 PM, Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
> > On Tue, Apr 12, 2016 at 8:01 AM, Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> wrote:
> >> Some types of ST Sensors can be connected to the same IRQ line
> >> as other peripherals using open drain. Add a device tree binding
> >> and a sensor data property to flip the right bit in the interrupt
> >> control register to enable open drain mode on the INT line.
> >>
> >> If the line is set to be open drain, also tag on IRQF_SHARED
> >> to the IRQ flags when requesting the interrupt, as the whole
> >> point of using open drain interrupt lines is to share them with
> >> more than one peripheral (wire-or).
> >>
> >> Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> >> Cc: Giuseppe Barba <giuseppe.barba-qxv4g6HH51o@public.gmane.org>
> >> Cc: Denis Ciocca <denis.ciocca-qxv4g6HH51o@public.gmane.org>
> >> Cc: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
> >> Signed-off-by: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> >> ---
> >> ChangeLog v3->v4:
> >> - Rename DT bool property st,int-pin-open-drain to int-pin-open-drain
> >> - Rob Herring ACKed st,int-pin-open-drain but not including his ACK
> >>   on this even though it's close
> >
> > We already have st,irq-open-drain, gpio-open-drain, linux,open-drain
> > and drive-open-drain (from pinctrl).
> >
> > If we want something common, then it should probably be part of
> > interrupt bindings, not something common to IIO.
> 
> I could agree to use the pin control drive-open-drain;
> 
> It has very little to do with the interrupt bindings, there are
> so many interrupt lines in the world, the fact that some of them
> go over open drain rails doesn't matter to the interrupt-controller
> devices, it needs to be below them.

Yes, but it is open drain because the interrupt is shared. That fact is 
enough to determine how to configure the pin. Unfortunately, it is a bit 
hard to determine an interrupt is shared based on how the interrupt 
bindings work. Adding a flag doesn't work because the cell contents are 
specific to the interrupt controller (though we have standardized them 
to some extent).

> I will resubmit using the pin control binding.

Given I don't have a better suggestion, that sounds fine.

Rob

      parent reply	other threads:[~2016-04-14 13:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 13:01 [PATCH 4/4 v4] iio: st_sensors: support open drain mode Linus Walleij
     [not found] ` <1460466079-15392-1-git-send-email-linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-04-13 20:52   ` Rob Herring
     [not found]     ` <CAL_JsqKudTxbK9goinYCQhGLK=Gd_+PHgQ+mnpkU=cz4pB0k2w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-14  8:36       ` Linus Walleij
     [not found]         ` <CACRpkdZs6g+UEOo+pEd1bS1tV7JpUhA1uJ9s6i=Jr39R=2RGfQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-14 13:30           ` Rob Herring [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=20160414133034.GA10104@rob-hp-laptop \
    --to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=denis.ciocca-qxv4g6HH51o@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=giuseppe.barba-qxv4g6HH51o@public.gmane.org \
    --cc=jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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).