From: Laxman Dewangan <ldewangan@nvidia.com>
To: Arnd Bergmann <arnd@arndb.de>,
Alexander Stein <alexander.stein@systec-electronic.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2 1/1] Input: gpio_keys - add device tree support for interrupt only keys
Date: Thu, 13 Nov 2014 16:32:59 +0530 [thread overview]
Message-ID: <54648FE3.4080109@nvidia.com> (raw)
In-Reply-To: <1616597.6UJpl1xeSr@wuerfel>
On Thursday 13 November 2014 04:30 PM, Arnd Bergmann wrote:
> On Thursday 13 November 2014 11:52:48 Alexander Stein wrote:
>> On Thursday 13 November 2014 11:47:13, Arnd Bergmann wrote:
>>> Regarding your initial use case of testing interrupt polarity, would
>>> you have been able to do the same thing by looking at the interrupt
>>> count in /proc/interrupts?
>> This is only possible if some driver actually requests this interrupt, no?
> Yes, I think that is correct, at least with sparseirq, which is now the
> default. For interrupts that are mapped by the irqchip, you can look
> up the number of spurious interrupts in /proc/irq/<nr>/spurious.
>
>
yes, I came across multiple PMIC(TPS65910, MAXIM, Ricoh) module which
generates interrupt when their On-key pin get toggle. Key is connected
with this pin of PMIC and for on-key driver, we are using the gpio-keys
driver by passing interrupt number instead of complete new driver.
next prev parent reply other threads:[~2014-11-13 11:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 16:02 [PATCH v2 1/1] Input: gpio_keys - add device tree support for interrupt only keys Alexander Stein
2014-11-12 16:04 ` Arnd Bergmann
2014-11-12 16:38 ` Alexander Stein
2014-11-12 19:16 ` Arnd Bergmann
2014-11-13 10:35 ` Alexander Stein
2014-11-13 10:47 ` Arnd Bergmann
2014-11-13 10:52 ` Alexander Stein
2014-11-13 11:00 ` Arnd Bergmann
2014-11-13 11:02 ` Laxman Dewangan [this message]
2014-11-13 10:59 ` Laxman Dewangan
2014-11-13 11:05 ` Arnd Bergmann
2014-11-13 11:17 ` Laxman Dewangan
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=54648FE3.4080109@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=alexander.stein@systec-electronic.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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 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.