linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paweł Chmiel" <pawel.mikolaj.chmiel@gmail.com>
To: dmitry.torokhov@gmail.com
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
	devicetree@vger.kernel.org, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org, pawel.mikolaj.chmiel@gmail.com,
	xc-racer2@live.ca, simon@lineageos.org
Subject: [PATCH v3 5/7] Input: dt-bindings: tm2-touchkey: Document new keycodes property
Date: Mon,  7 Jan 2019 19:53:44 +0100	[thread overview]
Message-ID: <20190107185346.30184-6-pawel.mikolaj.chmiel@gmail.com> (raw)
In-Reply-To: <20190107185346.30184-1-pawel.mikolaj.chmiel@gmail.com>

From: Jonathan Bakker <xc-racer2@live.ca>

Document new optional property for setting custom keycodes.

Signed-off-by: Jonathan Bakker <xc-racer2@live.ca>
Signed-off-by: Paweł Chmiel <pawel.mikolaj.chmiel@gmail.com>
---
Changes from v2:
  - Change property name from keycodes to linux,keycodes

Changes from v1:
  - Because key codes could be bigger than 255, use ints for keycodes
---
 .../devicetree/bindings/input/cypress,tm2-touchkey.txt        | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Documentation/devicetree/bindings/input/cypress,tm2-touchkey.txt b/Documentation/devicetree/bindings/input/cypress,tm2-touchkey.txt
index dfb3b9f0ee40..8ef1517c0220 100644
--- a/Documentation/devicetree/bindings/input/cypress,tm2-touchkey.txt
+++ b/Documentation/devicetree/bindings/input/cypress,tm2-touchkey.txt
@@ -10,6 +10,9 @@ Required properties:
 - vcc-supply : internal regulator output. 1.8V
 - vdd-supply : power supply for IC 3.3V
 
+Optional properties:
+- linux,keycodes: array of keycodes (max 4), default KEY_PHONE and KEY_BACK
+
 [0]: Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
 
 Example:
@@ -23,5 +26,6 @@ Example:
 			interrupts = <2 IRQ_TYPE_EDGE_FALLING>;
 			vcc-supply=<&ldo32_reg>;
 			vdd-supply=<&ldo33_reg>;
+			linux,keycodes = <KEY_PHONE KEY_BACK>;
 		};
 	};
-- 
2.17.1


  parent reply	other threads:[~2019-01-07 18:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 18:53 [PATCH v3 0/7] Input: tm2-touchkey: Add support for Aries and Midas Paweł Chmiel
2019-01-07 18:53 ` [PATCH v3 1/7] Input: tm2-touchkey: Add support for midas touchkey Paweł Chmiel
2019-01-07 18:53 ` [PATCH v3 2/7] Input: dt-bindings: " Paweł Chmiel
2019-01-07 18:53 ` [PATCH v3 3/7] Input: tm2-touchkey: Correct initial brightness Paweł Chmiel
2019-01-07 18:53 ` [PATCH v3 4/7] Input: tm2-touchkey: Allow specifying custom keycodes Paweł Chmiel
2019-01-07 18:53 ` Paweł Chmiel [this message]
2019-01-11 14:30   ` [PATCH v3 5/7] Input: dt-bindings: tm2-touchkey: Document new keycodes property Rob Herring
2019-01-07 18:53 ` [PATCH v3 6/7] Input: tm2-touchkey: Add support for aries touchkey variant Paweł Chmiel
2019-01-07 18:53 ` [PATCH v3 7/7] Input: dt-bindings: tm2-touchkey: Add support for aries touchkey Paweł Chmiel
2019-01-07 19:53 ` [PATCH v3 0/7] Input: tm2-touchkey: Add support for Aries and Midas 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:
  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=20190107185346.30184-6-pawel.mikolaj.chmiel@gmail.com \
    --to=pawel.mikolaj.chmiel@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=simon@lineageos.org \
    --cc=xc-racer2@live.ca \
    /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).