dt-bindings: input: Convert matrix-keymap to json-schema
Subsystems (4)
PATCH v2 1/2 dt-bindings: input: Convert matrix-keymap to json-schema
Convert the matrix-keymap binding to DT schema format using json-schema
---
New patch.
--- .../devicetree/bindings/input/matrix-keymap.txt | 28 +------------ .../devicetree/bindings/input/matrix-keymap.yaml | 46 ++++++++++++++++++++++ 2 files changed, 47 insertions(+), 27 deletions(-) create mode 100644 Documentation/devicetree/bindings/input/matrix-keymap.yaml
Documentation/devicetree/bindings/input/matrix-keymap.txt +1 -27
@@ -1,27 +1 @@ -A simple common binding for matrix-connected key boards. Currently targeted at -defining the keys in the scope of linux key codes since that is a stable and -standardized interface at this time. - -Required properties: -- linux,keymap: an array of packed 1-cell entries containing the equivalent - of row, column and linux key-code. The 32-bit big endian cell is packed - as: - row << 24 | column << 16 | key-code - -Optional properties: -Properties for the number of rows and columns are optional because some -drivers will use fixed values for these. -- keypad,num-rows: Number of row lines connected to the keypad controller. -- keypad,num-columns: Number of column lines connected to the keypad - controller. - -Some users of this binding might choose to specify secondary keymaps for -cases where there is a modifier key such as a Fn key. Proposed names -for said properties are "linux,fn-keymap" or with another descriptive -word for the modifier other from "Fn". - -Example: - linux,keymap = < 0x00030012 - 0x0102003a >; - keypad,num-rows = <2>; - keypad,num-columns = <8>; +This file has been moved to matrix-keymap.yaml
Documentation/devicetree/bindings/input/matrix-keymap.yaml new file +46 -0
46 lines not on this page · raw message
Signature · 1 line
2.7.4
PATCH v2 2/2 dt-bindings: input: Convert imx keypad to json-schema
Convert the i.MX KEYPAD binding to DT schema format using json-schema
---
Changes since V1:
- include matrix-keymap.yaml and "linux,keymap" is unnecessary now, remove it.
--- .../devicetree/bindings/input/imx-keypad.txt | 53 -------------- .../devicetree/bindings/input/imx-keypad.yaml | 85 ++++++++++++++++++++++ 2 files changed, 85 insertions(+), 53 deletions(-) delete mode 100644 Documentation/devicetree/bindings/input/imx-keypad.txt create mode 100644 Documentation/devicetree/bindings/input/imx-keypad.yaml
Documentation/devicetree/bindings/input/imx-keypad.txt deleted +0 -53
@@ -1,53 +0,0 @@ -* Freescale i.MX Keypad Port(KPP) device tree bindings - -The KPP is designed to interface with a keypad matrix with 2-point contact -or 3-point contact keys. The KPP is designed to simplify the software task -of scanning a keypad matrix. The KPP is capable of detecting, debouncing, -and decoding one or multiple keys pressed simultaneously on a keypad. - -Required SoC Specific Properties: -- compatible: Should be "fsl,<soc>-kpp". - -- reg: Physical base address of the KPP and length of memory mapped - region. - -- interrupts: The KPP interrupt number to the CPU(s). - -- clocks: The clock provided by the SoC to the KPP. Some SoCs use dummy -clock(The clock for the KPP is provided by the SoCs automatically). - -Required Board Specific Properties: -- pinctrl-names: The definition can be found at -pinctrl/pinctrl-bindings.txt. - -- pinctrl-0: The definition can be found at -pinctrl/pinctrl-bindings.txt. - -- linux,keymap: The definition can be found at -bindings/input/matrix-keymap.txt. - -Example: -kpp: kpp@73f94000 { - compatible = "fsl,imx51-kpp", "fsl,imx21-kpp"; - reg = <0x73f94000 0x4000>; - interrupts = <60>; - clocks = <&clks 0>; - pinctrl-names = "default"; - pinctrl-0 = <&pinctrl_kpp_1>; - linux,keymap = <0x00000067 /* KEY_UP */ - 0x0001006c /* KEY_DOWN */ - 0x00020072 /* KEY_VOLUMEDOWN */ - 0x00030066 /* KEY_HOME */ - 0x0100006a /* KEY_RIGHT */ - 0x01010069 /* KEY_LEFT */ - 0x0102001c /* KEY_ENTER */ - 0x01030073 /* KEY_VOLUMEUP */ - 0x02000040 /* KEY_F6 */ - 0x02010042 /* KEY_F8 */ - 0x02020043 /* KEY_F9 */ - 0x02030044 /* KEY_F10 */ - 0x0300003b /* KEY_F1 */ - 0x0301003c /* KEY_F2 */ - 0x0302003d /* KEY_F3 */ - 0x03030074>; /* KEY_POWER */ -};
Documentation/devicetree/bindings/input/imx-keypad.yaml new file +85 -0
85 lines not on this page · raw message
Signature · 1 line
2.7.4
Re: [PATCH V2 2/2] dt-bindings: input: Convert imx keypad to json-schema
Quoted 6 lines · Anson Huang
Convert the i.MX KEYPAD binding to DT schema format using json-schema
Signed-off-by Anson Huang <[email protected]>---
Changes since V1:
- includematrix-keymap.yamland "linux,keymap" is unnecessary now, remove it.
Quoted 7 lines
--- .../devicetree/bindings/input/imx-keypad.txt | 53 -------------- .../devicetree/bindings/input/imx-keypad.yaml | 85 ++++++++++++++++++++++ 2 files changed, 85 insertions(+), 53 deletions(-) delete mode 100644 Documentation/devicetree/bindings/input/imx-keypad.txt create mode 100644 Documentation/devicetree/bindings/input/imx-keypad.yaml
Applied, thanks!
Quoted 11 lines · Anson Huang
Convert the matrix-keymap binding to DT schema format using json-schema
Signed-off-by Anson Huang <[email protected]>---
New patch.--- .../devicetree/bindings/input/matrix-keymap.txt | 28 +------------ .../devicetree/bindings/input/matrix-keymap.yaml | 46 ++++++++++++++++++++++ 2 files changed, 47 insertions(+), 27 deletions(-) create mode 100644 Documentation/devicetree/bindings/input/matrix-keymap.yaml
Applied, thanks!