* [PATCH 2/2] Input: mcs_touchkey: add device tree binding document
@ 2014-05-21 5:51 Beomho Seo
2014-05-21 13:53 ` Mark Rutland
0 siblings, 1 reply; 2+ messages in thread
From: Beomho Seo @ 2014-05-21 5:51 UTC (permalink / raw)
To: linux-input, devicetree, dmitry.torokhov, Joonyoung Shim,
mark.rutland
Cc: Myungjoo Ham, Jaehoon Chung, Chanwoo Choi
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
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH 2/2] Input: mcs_touchkey: add device tree binding document
2014-05-21 5:51 [PATCH 2/2] Input: mcs_touchkey: add device tree binding document Beomho Seo
@ 2014-05-21 13:53 ` Mark Rutland
0 siblings, 0 replies; 2+ messages in thread
From: Mark Rutland @ 2014-05-21 13:53 UTC (permalink / raw)
To: Beomho Seo
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
dmitry.torokhov@gmail.com, Joonyoung Shim, Myungjoo Ham,
Jaehoon Chung, Chanwoo Choi
On Wed, May 21, 2014 at 06:51:57AM +0100, Beomho Seo wrote:
> 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"
NAK. These should be in "$VENDOR,$DEVICE" format (e.g. "melfas,mcs5000").
It looks like "melfas" is already used, but is undocumented. Please add
it to vendor-prefixes.txt.
> +- reg : I2C address of the chip
> +- interrupts: interrupt to which the chip is connected
> +- key_maxval: size of keycode table
Surely this is already implicit in the size of the linux,code property
data?
This is superfluous and broken. Please get rid of it.
> +- code: key code for this device
This doesn't match the example or driver. If this is a standard
property, please refer to a definition of the format.
> +
> +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>;
Random spacing?
Please bracket individual list elements.
Cheers,
Mark.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-05-21 13:53 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-05-21 5:51 [PATCH 2/2] Input: mcs_touchkey: add device tree binding document Beomho Seo
2014-05-21 13:53 ` Mark Rutland
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).