All of
 help / color / mirror / Atom feed
From: Linus Walleij <>
To: Dmitry Torokhov <>,
Cc: Linus Walleij <>,
Subject: [PATCH 1/2 v3] input: keyboard: DT bindings for the D-Link DIR-685 touchkeys
Date: Tue, 30 May 2017 14:09:17 +0200	[thread overview]
Message-ID: <> (raw)

This adds device tree bindings for the D-Link DIR-685 touchkeys.
It's a simple homebrewn touchkey controller (by D-Link referred
to as "touchpad") on I2C.

Acked-by: Rob Herring <>
Signed-off-by: Linus Walleij <>
ChangeLog v2->v3:
- No changes, just resending.
ChangeLog v1->v2:
- Rename from "touchpad" to touchkeys" consistently.
- Add Rob's ACK.
 .../bindings/input/dlink,dir685-touchkeys.txt       | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/input/dlink,dir685-touchkeys.txt

diff --git a/Documentation/devicetree/bindings/input/dlink,dir685-touchkeys.txt b/Documentation/devicetree/bindings/input/dlink,dir685-touchkeys.txt
new file mode 100644
index 000000000000..10dec1c57abf
--- /dev/null
+++ b/Documentation/devicetree/bindings/input/dlink,dir685-touchkeys.txt
@@ -0,0 +1,21 @@
+* D-Link DIR-685 Touchkeys
+This is a I2C one-off touchkey controller based on the Cypress Semiconductor
+CY8C214 MCU with some firmware in its internal 8KB flash. The circuit
+board inside the router is named E119921.
+The touchkey device node should be placed inside an I2C bus node.
+Required properties:
+- compatible: must be "dlink,dir685-touchkeys"
+- reg: the I2C address of the touchkeys
+- interrupts: reference to the interrupt number
+touchkeys@26 {
+	compatible = "dlink,dir685-touchkeys";
+	reg = <0x26>;
+	interrupt-parent = <&gpio0>;
+	interrupts = <17 IRQ_TYPE_EDGE_FALLING>;

             reply	other threads:[~2017-05-30 12:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 12:09 Linus Walleij [this message]
2017-05-30 12:09 ` [PATCH 2/2 v3] input: keyboard: Add D-Link DIR-685 touchkeys driver Linus Walleij
2017-05-30 16:40   ` Dmitry Torokhov
2017-05-30 23:50     ` Linus Walleij
2017-06-05 22:12   ` Dmitry Torokhov

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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.