From: Hui Wang <jason77.wang@gmail.com>
To: dmitry.torokhov@gmail.com, jiejing.zhang@freescale.com,
shawn.guo@linaro.org
Cc: linux-input@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org
Subject: [PATCH v4 0/3] Input: egalax_ts: parse devicetree to get gpio
Date: Thu, 16 Aug 2012 18:47:28 +0800 [thread overview]
Message-ID: <1345114051-3052-1-git-send-email-jason77.wang@gmail.com> (raw)
V4:
add of_match_table in the driver, and change egalax_ts gpio irq type value from
2 to 8 (falling edge to low level) in the dts.
V3:
Although have got Ack-by from driver author in the V2, i have to send
V3 since the driver is changed due to the change of a property name
in the dts.
As Shawn.guo suggested, i renamed property "irq-gpio" to "wakeup-gpios".
The reason is that, firstly the idiom of gpio naming in DT is *-gpios,
even though most of time, it could be just one gpio, secondly as the pin is
accessed as a gpio only in egalax_wake_up_device for waking up the device.
This time i send the patches both to linux-input and linux-arm, 0001 and
0002 belongs to linux-input, while the 0003 belongs to linux-arm.
V2:
Add return value checking for waking up the controller in the probe
function.
V1:
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 (3):
Input: egalax_ts: get gpio from devicetree node
Input: add devicetree binding note for egalax_ts
ARM: dts: imx6q-sabrelite: add eeti egalax touchscreen
.../bindings/input/touchscreen/egalax-ts.txt | 19 +++++++++++++++
arch/arm/boot/dts/imx6q-sabrelite.dts | 16 ++++++++++++
arch/arm/boot/dts/imx6q.dtsi | 7 +++++
drivers/input/touchscreen/egalax_ts.c | 25 +++++++++++++++++--
4 files changed, 64 insertions(+), 3 deletions(-)
create mode 100644 Documentation/devicetree/bindings/input/touchscreen/egalax-ts.txt
--
1.7.6
next reply other threads:[~2012-08-16 10:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 10:47 Hui Wang [this message]
2012-08-16 10:47 ` [PATCH v4 1/3] Input: egalax_ts: get gpio from devicetree node Hui Wang
2012-08-16 10:47 ` [PATCH v4 2/3] Input: add devicetree binding note for egalax_ts Hui Wang
2012-08-16 10:47 ` [PATCH v4 3/3] ARM: dts: imx6q-sabrelite: add eeti egalax Hui Wang
2012-08-17 0:33 ` Shawn Guo
2012-08-17 1:20 ` Hui Wang
2012-08-17 0:32 ` [PATCH v4 2/3] Input: add devicetree binding note for egalax_ts Shawn Guo
2012-08-17 0:31 ` [PATCH v4 1/3] Input: egalax_ts: get gpio from devicetree node Shawn Guo
2012-10-09 11:58 ` Arnd Bergmann
2012-10-10 3:26 ` Hui Wang
2012-10-10 6:18 ` Arnd Bergmann
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=1345114051-3052-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-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=shawn.guo@linaro.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).