From: Sanchayan Maity <maitysanchayan@gmail.com>
To: linux-input@vger.kernel.org, devicetree@vger.kernel.org
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
shawn.guo@linaro.org, kernel@pengutronix.de, stefan@agner.ch,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Sanchayan Maity <maitysanchayan@gmail.com>
Subject: [PATCH v2 0/4] Add support for touchscreen on Colibri VF50
Date: Thu, 16 Jul 2015 20:43:18 +0530 [thread overview]
Message-ID: <cover.1437058481.git.maitysanchayan@gmail.com> (raw)
Hello,
The patchset adds support for 4 wire touchscreen on Toradex Colibri
VF50 modules. Patches are based on top of shawn's branch.
Changes since v1:
1. Fix/drop comments
2. Use an inline function for multiple gpiod_get calls in probe
3. Remove the pull up in the pinmux specified in DT for touchctrl_gpios
4. Add the io-channel-cells property before status property.
5. Add GPIOLIB as dependency in the Kconfig file
Version 1 of the patchset can be found here
https://lkml.org/lkml/2015/6/30/103
Thank you for the feedback Stefan.
Thanks & Regards,
Sanchayan.
Sanchayan Maity (4):
ARM: dts: vfxxx: Add io-channel-cells property for ADC node
ARM: dts: vf500-colibri: Add device tree node for touchscreen support
touchscreen: colibri-vf50-ts: Add touchscreen support for Colibri VF50
input: Add DT binding documentation for Colibri VF50 touchscreen
.../bindings/input/touchscreen/colibri-vf50-ts.txt | 34 ++
arch/arm/boot/dts/vf500-colibri-eval-v3.dts | 4 +
arch/arm/boot/dts/vf500-colibri.dtsi | 46 +++
arch/arm/boot/dts/vfxxx.dtsi | 2 +
drivers/input/touchscreen/Kconfig | 12 +
drivers/input/touchscreen/Makefile | 1 +
drivers/input/touchscreen/colibri-vf50-ts.c | 451 +++++++++++++++++++++
7 files changed, 550 insertions(+)
create mode 100644 Documentation/devicetree/bindings/input/touchscreen/colibri-vf50-ts.txt
create mode 100644 drivers/input/touchscreen/colibri-vf50-ts.c
--
2.4.6
next reply other threads:[~2015-07-16 15:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 15:13 Sanchayan Maity [this message]
2015-07-16 15:13 ` [PATCH v2 1/4] ARM: dts: vfxxx: Add io-channel-cells property for ADC node Sanchayan Maity
2015-07-28 3:14 ` Shawn Guo
2015-07-16 15:13 ` [PATCH v2 2/4] ARM: dts: vf500-colibri: Add device tree node for touchscreen support Sanchayan Maity
2015-07-28 3:19 ` Shawn Guo
2015-07-16 15:13 ` [PATCH v2 3/4] touchscreen: colibri-vf50-ts: Add touchscreen support for Colibri VF50 Sanchayan Maity
2015-07-17 23:42 ` Dmitry Torokhov
2015-07-18 12:37 ` maitysanchayan
2015-07-21 14:43 ` Stefan Agner
2015-07-21 17:20 ` Dmitry Torokhov
2015-07-22 5:50 ` maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w
2015-08-03 15:25 ` maitysanchayan
2015-08-03 21:04 ` Dmitry Torokhov
2015-08-05 7:27 ` maitysanchayan
2015-07-18 11:03 ` Nicolae Rosia
2015-07-18 12:28 ` maitysanchayan
2015-07-16 15:13 ` [PATCH v2 4/4] input: Add DT binding documentation for Colibri VF50 touchscreen Sanchayan Maity
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=cover.1437058481.git.maitysanchayan@gmail.com \
--to=maitysanchayan@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawn.guo@linaro.org \
--cc=stefan@agner.ch \
/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).