devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
Cc: Rob Herring <robherring2@gmail.com>,
	Alexandre Courbot <gnurou@gmail.com>,
	Frank Rowand <frowand.list@gmail.com>,
	Matt Porter <mporter@konsulko.com>,
	Koen Kooi <koen@dominion.thruhere.net>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Guenter Roeck <linux@roeck-us.net>, Marek Vasut <marex@denx.de>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH 2/2] gpio: Support cascaded GPIO chip lookup for OF
Date: Mon, 13 Jun 2016 08:48:45 +0200	[thread overview]
Message-ID: <CACRpkdb-movUA67=8WrCcYTO5WyAjUcur44R=vQ0iaBp-tMSmg@mail.gmail.com> (raw)
In-Reply-To: <8F93AE08-B340-481B-A5B3-F42227D9D729@konsulko.com>

On Wed, Jun 8, 2016 at 3:41 PM, Pantelis Antoniou
<pantelis.antoniou@konsulko.com> wrote:

> Devices that use interrupts usually convert the GPIO to an interrupt and use it.
> Since the xlat op will return the real GPIO spec the interrupt conversion will work.
>
> Bare interrupt lines are sort-of out of fashion nowadays I think. I’m eager to be
> proven wrong though with a recent portable expansion board that uses them.

No. We have established since several years back that gpiochip and interrupt
chip use cases are orthogonal, and there is absolutely *NO* requirement that
a consumer call .to_irq() on a GPIO line before using it as an interrupt, if the
driver exposes an interrupt chip.

It is true that external interrupt lines are out-of-fashion and usually replaced
with GPIOs that can trigger IRQs. However the latter have two interfaces
independent of each other.

A practical usecase is the SMSC911x ethernet drivers that have their IRQ
wired to both external interrupt lines and GPIO lines used as IRQ in different
use cases. It should not need to know whether the interrupt provider is a
"real" IRQ line or a GPIO line providing an IRQ. It just wants "some IRQ",
and this should be hidden from the driver and the hardware's DT bindings.

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2016-06-13  6:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03 20:26 [PATCH 0/2] gpio: of: Support cascaded GPIO Pantelis Antoniou
     [not found] ` <1464985616-11821-1-git-send-email-pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
2016-06-03 20:26   ` [PATCH 1/2] gpio: Remove const from gpiospec in of_xlate Pantelis Antoniou
2016-06-03 20:26 ` [PATCH 2/2] gpio: Support cascaded GPIO chip lookup for OF Pantelis Antoniou
2016-06-07 21:00   ` Rob Herring
     [not found]     ` <CAL_JsqLi4=6v-8B8eF-H1iQGa+3Zh=rzAWbCAJubnLNEitPaLQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-08 13:41       ` Pantelis Antoniou
2016-06-08 15:18         ` Rob Herring
     [not found]           ` <CAL_Jsq+Z9NrvkZa0x4ZjC_POn96h1yQxXbrHsrMQ-MtvjWKWzQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-08 15:32             ` Pantelis Antoniou
2016-06-08 18:45               ` Rob Herring
2016-06-13  6:48         ` Linus Walleij [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='CACRpkdb-movUA67=8WrCcYTO5WyAjUcur44R=vQ0iaBp-tMSmg@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=gnurou@gmail.com \
    --cc=koen@dominion.thruhere.net \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=marex@denx.de \
    --cc=mark.rutland@arm.com \
    --cc=mporter@konsulko.com \
    --cc=pantelis.antoniou@konsulko.com \
    --cc=robherring2@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).