new file mode 100644
@@ -0,0 +1,78 @@
+Input: keyset
+
+A simple binding to represent a set of keys as described in
+include/uapi/linux/input.h. This is targeted at devices that want
+to react to certain key combination being pressed or need to
+perform some configuration based on a set of input keys.
+
+It can also be used in a scenario where the system has a whole
+needs to respond to a specific sequence of keys.
+
+Required properties:
+ - linux,input-keyset: An array of 1-cell entries representing the
+ values associated with the KEY_xyz #defines found in input.h.
+
+Example1:
+Applicable to a specific device:
+
+ matrix-keypad {
+ compatible = "gpio-matrix-keypad";
+ debounce-delay-ms = <5>;
+ col-scan-delay-us = <2>;
+
+ row-gpios = <&gpio2 25 0
+ &gpio2 26 0
+ &gpio2 27 0>;
+
+ col-gpios = <&gpio2 21 0
+ &gpio2 22 0
+ &gpio2 23 0>;
+
+ linux,keymap = <0x00000002
+ 0x01000005
+ 0x02000008
+ 0x00010003
+ 0x01010006
+ 0x02010009
+ 0x00020004
+ 0x01020007
+ 0x0202000a>;
+
+ linux,keyset = <0x04
+ 0x05
+ 0x0a>;
+ };
+
+Example2:
+Used as a system-wide parameter:
+
+ sysrq {
+ linux,input-keyset = <0x01
+ 0x0A
+ 0x19>;
+ timout-ms = <3000>;
+ };
+
+Would represent KEY_1, KEY_9 and KEY_P.
+
+Example3:
+Binding used when multiple declarations are needed:
+
+acme_keysets {
+ keyset0 {
+ linux,input-keyset = <0x01
+ 0x02
+ 0x03>;
+ };
+ keyset1 {
+ linux,input-keyset = <0x04
+ 0x05
+ 0x06>;
+ };
+ keyset2 {
+ linux,input-keyset = <0x07
+ 0x08
+ 0x09>;
+ };
+
+};