From: Beomho Seo <beomho.seo@samsung.com>
To: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
dmitry.torokhov@gmail.com,
Joonyoung Shim <jy0922.shim@samsung.com>,
mark.rutland@arm.com
Cc: Myungjoo Ham <myungjoo.ham@samsung.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>
Subject: [PATCH 2/2] Input: mcs_touchkey: add device tree binding document
Date: Wed, 21 May 2014 14:51:57 +0900 [thread overview]
Message-ID: <537C3EFD.8040601@samsung.com> (raw)
This patch add simple device tree bindings to
MELFAS MCS5000/5080 controller.
Signed-off-by: Beomho Seo <beomho.seo@samsung.com>
---
.../devicetree/bindings/input/mcs-touchkey.txt | 25 ++++++++++++++++++++
1 file changed, 25 insertions(+)
create mode 100644 Documentation/devicetree/bindings/input/mcs-touchkey.txt
diff --git a/Documentation/devicetree/bindings/input/mcs-touchkey.txt b/Documentation/devicetree/bindings/input/mcs-touchkey.txt
new file mode 100644
index 0000000..8364799
--- /dev/null
+++ b/Documentation/devicetree/bindings/input/mcs-touchkey.txt
@@ -0,0 +1,25 @@
+* mcs_touchkey MELFAS MCS5000/5080 controller
+
+Required properties:
+- compatible: must be "mcs5000_touchkey" or "mcs5080_touchkey"
+- reg : I2C address of the chip
+- interrupts: interrupt to which the chip is connected
+- key_maxval: size of keycode table
+- code: key code for this device
+
+Example:
+
+ i2c_touch_key: i2c-gpio-0 {
+ /* ... */
+
+ touch_key@20 {
+ compatible = "mcs5080_touchkey";
+ reg = <0x20>;
+ interrupt-patrent = <gpj0>;
+ key_maxval = <2>;
+ linux, code = <0x0000009e
+ 0x000000a9>;
+ };
+
+ /* ... */
+ };
--
1.7.9.5
next reply other threads:[~2014-05-21 5:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 5:51 Beomho Seo [this message]
2014-05-21 13:53 ` [PATCH 2/2] Input: mcs_touchkey: add device tree binding document Mark Rutland
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=537C3EFD.8040601@samsung.com \
--to=beomho.seo@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jh80.chung@samsung.com \
--cc=jy0922.shim@samsung.com \
--cc=linux-input@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=myungjoo.ham@samsung.com \
/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).