From: Hui Wang <jason77.wang@gmail.com>
To: dmitry.torokhov@gmail.com, jiejing.zhang@freescale.com
Cc: linux-input@vger.kernel.org, devicetree-discuss@lists.ozlabs.org
Subject: [PATCH 0/2] Input: egalax_ts: parse devicetree to get gpio
Date: Tue, 7 Aug 2012 17:39:30 +0800 [thread overview]
Message-ID: <1344332372-9287-1-git-send-email-jason77.wang@gmail.com> (raw)
eeti touch screen controller is an external chip for most platforms,
it connect to CPU via i2c bus, and it has a irq request pin need to be
connected to a gpio of the CPU, this irq request pin also act as a
wake up signal for touch screen controller, we need to get this gpio
number and operate it to wake up the controller, the old way to get
gpio is irq_to_gpio(), this API is dying and most platforms don't support
it, we change it to a more generic way to use devcietree.
Hui Wang (2):
Input: egalax_ts: get gpio from devicetree node
Input: add devicetree binding note for egalax_ts
.../bindings/input/touchscreen/egalax-ts.txt | 17 +++++++++++++++++
drivers/input/touchscreen/egalax_ts.c | 12 ++++++++++--
2 files changed, 27 insertions(+), 2 deletions(-)
create mode 100644 Documentation/devicetree/bindings/input/touchscreen/egalax-ts.txt
--
1.7.6
next reply other threads:[~2012-08-07 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 9:39 Hui Wang [this message]
2012-08-07 9:39 ` [PATCH 1/2] Input: egalax_ts: get gpio from devicetree node Hui Wang
2012-08-07 9:39 ` [PATCH 2/2] Input: add devicetree binding note for egalax_ts Hui Wang
2012-08-08 3:44 ` [PATCH 1/2] Input: egalax_ts: get gpio from devicetree node Zhang Jiejing-B33651
2012-08-08 5:35 ` Hui Wang
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=1344332372-9287-1-git-send-email-jason77.wang@gmail.com \
--to=jason77.wang@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jiejing.zhang@freescale.com \
--cc=linux-input@vger.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 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).