From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: device-tree: at91: irq and gpios: problem while requesting a gpio used as an interrupt source.
Date: Wed, 15 Jan 2014 14:48:13 +0100 [thread overview]
Message-ID: <8007592.fj8kc2EY8M@wuerfel> (raw)
In-Reply-To: <CACh+v5Mccz47VMxDcrAC1NY30cY53gxEmp5MG4+n0PNn5RrsSw@mail.gmail.com>
On Wednesday 15 January 2014 14:44:24 Jean-Jacques Hiblot wrote:
> 2014/1/15 Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>:
> > On 14:04 Wed 15 Jan , Jean-Jacques Hiblot wrote:
> >> 2014/1/15 Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>:
> >> > because this the only to start to do it right
> >> > I had a very long discussion woth LinusW and Grant the Gpio need to stop to
> >> > use gpio_to_irq & co for irq.
> >> How can you get the value of the gpio that is also an interrupt source then ?
> >> Can you give a short example?
> >
> > you just have to check the irq source
> >
> > failing or raising
> >
> > but on 9261 impossible the gpio does not have such detail
> >
> > but anyway this is the invert you need to get the information from the IRQ no the way
> > arround
>
> Should I modify the touchscreen driver to use irq_to_gpio() in this
> case then ? or is this also not proper ?
irq_to_gpio no longer exists.
Arnd
next prev parent reply other threads:[~2014-01-15 13:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 10:29 device-tree: at91: irq and gpios: problem while requesting a gpio used as an interrupt source Jean-Jacques Hiblot
2014-01-13 10:35 ` boris brezillon
2014-01-13 11:05 ` Jean-Jacques Hiblot
2014-01-15 12:33 ` Jean-Christophe PLAGNIOL-VILLARD
2014-01-15 13:04 ` Jean-Jacques Hiblot
2014-01-15 13:20 ` Jean-Christophe PLAGNIOL-VILLARD
2014-01-15 13:44 ` Jean-Jacques Hiblot
2014-01-15 13:48 ` Arnd Bergmann [this message]
2014-01-15 13:56 ` Jean-Christophe PLAGNIOL-VILLARD
2014-01-15 14:41 ` Jean-Jacques Hiblot
2014-01-15 15:25 ` Jean-Christophe PLAGNIOL-VILLARD
2014-01-15 15:30 ` Jean-Jacques Hiblot
2014-01-15 18:00 ` Jean-Christophe PLAGNIOL-VILLARD
2014-01-15 17:28 ` Nicolas Ferre
2014-01-22 10:11 ` Linus Walleij
2014-01-22 12:23 ` Jean-Jacques Hiblot
2014-01-15 18:06 ` Jean-Christophe PLAGNIOL-VILLARD
2014-01-16 8:54 ` boris brezillon
2014-01-16 11:04 ` Nicolas Ferre
2014-01-16 12:02 ` Jean-Jacques Hiblot
2014-01-22 10:15 ` Linus Walleij
2014-01-23 13:16 ` Jean-Jacques Hiblot
2014-01-31 8:03 ` Linus Walleij
2014-01-15 12:02 ` Jean-Christophe PLAGNIOL-VILLARD
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=8007592.fj8kc2EY8M@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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).