| /freebsd/sys/contrib/device-tree/Bindings/input/ |
| H A D | gpio-matrix-keypad.txt | 1 * GPIO driven matrix keypad device tree bindings
3 GPIO driven matrix keypad is used to interface a SoC with a matrix keypad.
4 The matrix keypad supports multiple row and column lines, a key can be
5 placed at each intersection of a unique row and a unique column. The matrix
6 keypad can sense a key-press and key-release by means of GPIO lines and
10 - compatible: Should be "gpio-matrix-keypad"
11 - row-gpios: List of gpios used as row lines. The gpio specifier
14 - col-gpios: List of gpios used as column lines. The gpio specifier
17 - linux,keymap: The definition can be found at
18 bindings/input/matrix-keymap.txt
[all …]
|
| H A D | gpio-matrix-keypad.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $id: http://devicetree.org/schemas/input/gpio-matrix-keypad.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: GPIO matrix keypad
11 - Marek Vasut <marek.vasut@gmail.com>
14 GPIO driven matrix keypad is used to interface a SoC with a matrix keypad.
15 The matrix keypad supports multiple row and column lines, a key can be
16 placed at each intersection of a unique row and a unique column. The matrix
17 keypad can sense a key-press and key-release by means of GPIO lines and
[all …]
|
| H A D | qcom,pm8xxx-keypad.txt | 1 Qualcomm PM8xxx PMIC Keypad
5 - compatible:
9 "qcom,pm8058-keypad"
10 "qcom,pm8921-keypad"
12 - reg:
14 Value type: <prop-encoded-array>
15 Definition: address of keypad control register
17 - interrupts:
19 Value type: <prop-encoded-array>
25 - linux,keymap:
[all …]
|
| H A D | cirrus,ep9307-keypad.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/cirrus,ep9307-keypad.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Cirrus ep93xx keypad
10 - Alexander Sverdlin <alexander.sverdlin@gmail.com>
13 - $ref: /schemas/input/matrix-keymap.yaml#
16 The KPP is designed to interface with a keypad matrix with 2-point contact
17 or 3-point contact keys. The KPP is designed to simplify the software task
18 of scanning a keypad matrix. The KPP is capable of detecting, debouncing,
[all …]
|
| H A D | qcom,pm8921-keypad.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/qcom,pm8921-keypad.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm PM8921 PMIC KeyPad
10 - Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
13 - $ref: input.yaml#
14 - $ref: matrix-keymap.yaml#
19 - qcom,pm8058-keypad
20 - qcom,pm8921-keypad
[all …]
|
| H A D | omap-keypad.txt | 1 * TI's Keypad Controller device tree bindings
3 TI's Keypad controller is used to interface a SoC with a matrix-type
4 keypad device. The keypad controller supports multiple row and column lines.
6 The keypad controller can sense a key-press and key-release and report the
9 This binding is based on the matrix-keymap binding with the following
12 keypad,num-rows and keypad,num-columns are required.
15 - compatible: should be one of the following
16 - "ti,omap4-keypad": For controllers compatible with omap4 keypad
20 - linux,keypad-no-autorepeat: do no enable autorepeat feature.
23 keypad@4ae1c000{
[all …]
|
| H A D | brcm,bcm-keypad.txt | 1 * Broadcom Keypad Controller device tree bindings
3 Broadcom Keypad controller is used to interface a SoC with a matrix-type
4 keypad device. The keypad controller supports multiple row and column lines.
6 The keypad controller can sense a key-press and key-release and report the
9 This binding is based on the matrix-keymap binding with the following
12 keypad,num-rows and keypad,num-columns are required.
15 - compatible: should be "brcm,bcm-keypad"
17 - reg: physical base address of the controller and length of memory mapped
20 - interrupts: The interrupt number to the cpu.
23 - keypad,num-rows: Number of row lines connected to the keypad
[all …]
|
| H A D | matrix-keymap.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/matrix-keymap.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Common Key Matrices on Matrix-connected Key Boards
10 - Olof Johansson <olof@lixom.net>
13 A simple common binding for matrix-connected key boards. Currently targeted at
19 for said properties are "linux,fn-keymap" or with another descriptive
24 $ref: /schemas/types.yaml#/definitions/uint32-array
26 An array of packed 1-cell entries containing the equivalent of row,
[all …]
|
| H A D | stmpe-keypad.txt | 1 * STMPE Keypad
4 - compatible : "st,stmpe-keypad"
5 - linux,keymap : See ./matrix-keymap.txt
8 - debounce-interval : Debouncing interval time in milliseconds
9 - st,scan-count : Scanning cycles elapsed before key data is updated
10 - st,no-autorepeat : If specified device will not autorepeat
11 - keypad,num-rows : See ./matrix-keymap.txt
12 - keypad,num-columns : See ./matrix-keymap.txt
17 compatible = "st,stmpe-keypad";
19 debounce-interval = <64>;
[all …]
|
| H A D | twl4030-keypad.txt | 1 * TWL4030's Keypad Controller device tree bindings
3 TWL4030's Keypad controller is used to interface a SoC with a matrix-type
4 keypad device. The keypad controller supports multiple row and column lines.
6 The keypad controller can sense a key-press and key-release and report the
9 This binding is based on the matrix-keymap binding with the following
12 * keypad,num-rows and keypad,num-columns are required.
15 - compatible: should be one of the following
16 - "ti,twl4030-keypad": For controllers compatible with twl4030 keypad
18 - interrupt: should be one of the following
19 - <1>: For controllers compatible with twl4030 keypad controller.
[all …]
|
| H A D | pxa27x-keypad.txt | 1 * Marvell PXA Keypad controller
4 - compatible : should be "marvell,pxa27x-keypad"
5 - reg : Address and length of the register set for the device
6 - interrupts : The interrupt for the keypad controller
7 - marvell,debounce-interval : How long time the key will be
10 interval for matrix key. The value is in binary number of 2ms
12 Optional Properties For Matrix Keyes
13 Please refer to matrix-keymap.txt
16 - marvell,direct-key-count : How many direct keyes are used.
17 - marvell,direct-key-mask : The mask indicates which keyes
[all …]
|
| H A D | imx-keypad.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/imx-keypad.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Freescale i.MX Keypad Port(KPP)
10 - Liu Ying <gnuiyl@gmail.com>
13 - $ref: /schemas/input/matrix-keymap.yaml#
16 The KPP is designed to interface with a keypad matrix with 2-point contact
17 or 3-point contact keys. The KPP is designed to simplify the software task
18 of scanning a keypad matrix. The KPP is capable of detecting, debouncing,
[all …]
|
| H A D | mediatek,mt6779-keypad.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/mediatek,mt6779-keypad.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Mediatek's Keypad Controller
10 - Mattijs Korpershoek <mkorpershoek@kernel.org>
13 - $ref: /schemas/input/matrix-keymap.yaml#
16 Mediatek's Keypad controller is used to interface a SoC with a matrix-type
17 keypad device. The keypad controller supports multiple row and column lines.
19 The keypad controller can sense a key-press and key-release and report the
[all …]
|
| H A D | clps711x-keypad.txt | 1 * Cirrus Logic CLPS711X matrix keypad device tree bindings
4 - compatible: Shall contain "cirrus,ep7209-keypad".
5 - row-gpios: List of GPIOs used as row lines.
6 - poll-interval: Poll interval time in milliseconds.
7 - linux,keymap: The definition can be found at
8 bindings/input/matrix-keymap.txt.
11 - autorepeat: Enable autorepeat feature.
14 keypad {
15 compatible = "cirrus,ep7312-keypad", "cirrus,ep7209-keypad";
17 poll-interval = <120>;
[all …]
|
| H A D | imx-keypad.txt | 1 * Freescale i.MX Keypad Port(KPP) device tree bindings
3 The KPP is designed to interface with a keypad matrix with 2-point contact
4 or 3-point contact keys. The KPP is designed to simplify the software task
5 of scanning a keypad matrix. The KPP is capable of detecting, debouncing,
6 and decoding one or multiple keys pressed simultaneously on a keypad.
9 - compatible: Should be "fsl,<soc>-kpp".
11 - reg: Physical base address of the KPP and length of memory mapped
14 - interrupts: The KPP interrupt number to the CPU(s).
16 - clocks: The clock provided by the SoC to the KPP. Some SoCs use dummy
20 - pinctrl-names: The definition can be found at
[all …]
|
| H A D | st-keyscan.txt | 4 matrix-keymap.
7 - compatible: "st,sti-keyscan"
9 - reg: Register base address and size of st-keyscan controller.
11 - interrupts: Interrupt number for the st-keyscan controller.
13 - clocks: Must contain one entry, for the module clock.
14 See ../clocks/clock-bindings.txt for details.
16 - pinctrl: Should specify pin control groups used for this controller.
17 See ../pinctrl/pinctrl-bindings.txt for details.
19 - linux,keymap: The keymap for keys as described in the binding document
20 devicetree/bindings/input/matrix-keymap.txt.
[all …]
|
| H A D | tca8418_keypad.txt | 1 This binding is based on the matrix-keymap binding with the following
4 keypad,num-rows and keypad,num-columns are required.
7 - compatible: "ti,tca8418"
8 - reg: the I2C address
9 - interrupts: IRQ line number, should trigger on falling edge
10 - linux,keymap: Keys definitions, see keypad-matrix.
|
| H A D | lpc32xx-key.txt | 3 This binding is based on the matrix-keymap binding with the following
7 - compatible: Should be "nxp,lpc3220-key"
8 - reg: Physical base address of the controller and length of memory mapped
10 - interrupts: The interrupt number to the cpu.
11 - clocks: phandle to clock controller plus clock-specifier pair
12 - nxp,debounce-delay-ms: Debounce delay in ms
13 - nxp,scan-delay-ms: Repeated scan period in ms
14 - linux,keymap: the key-code to be reported when the key is pressed
16 Documentation/devicetree/bindings/input/matrix-keymap.txt
18 Note: keypad,num-rows and keypad,num-columns are required, and must be equal
[all …]
|
| H A D | google,cros-ec-keyb.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $id: http://devicetree.org/schemas/input/google,cros-ec-keyb.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Simon Glass <sjg@chromium.org>
12 - Benson Leung <bleung@chromium.org>
15 Google's ChromeOS EC Keyboard is a simple matrix keyboard
24 - description: ChromeOS EC with only buttons/switches
25 const: google,cros-ec-keyb-switches
26 - description: ChromeOS EC with keyboard and possibly buttons/switches
[all …]
|
| H A D | samsung-keypad.txt | 1 * Samsung's Keypad Controller device tree bindings
3 Samsung's Keypad controller is used to interface a SoC with a matrix-type
4 keypad device. The keypad controller supports multiple row and column lines.
6 The keypad controller can sense a key-press and key-release and report the
10 - compatible: should be one of the following
11 - "samsung,s3c6410-keypad": For controllers compatible with s3c6410 keypad
13 - "samsung,s5pv210-keypad": For controllers compatible with s5pv210 keypad
16 - reg: physical base address of the controller and length of memory mapped
19 - interrupts: The interrupt number to the cpu.
22 - samsung,keypad-num-rows: Number of row lines connected to the keypad
[all …]
|
| H A D | samsung,s3c6410-keypad.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/input/samsung,s3c6410-keypad.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Samsung SoC series Keypad Controller
10 Samsung SoC Keypad controller is used to interface a SoC with a matrix-type
11 keypad device. The keypad controller supports multiple row and column lines.
13 The keypad controller can sense a key-press and key-release and report the
17 - Krzysztof Kozlowski <krzk@kernel.org>
22 - samsung,s3c6410-keypad
[all …]
|
| H A D | cros-ec-keyb.txt | 3 Google's ChromeOS EC Keyboard is a simple matrix keyboard implemented on
8 This binding is based on matrix-keymap.txt and extends/modifies it as follows:
11 - compatible: "google,cros-ec-keyb"
14 - google,needs-ghost-filter: True to enable a ghost filter for the matrix
21 cros-ec-keyb {
22 compatible = "google,cros-ec-keyb";
23 keypad,num-rows = <8>;
24 keypad,num-columns = <13>;
25 google,needs-ghost-filter;
48 /* F5 6 - \ */
|
| H A D | ti,nspire-keypad.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/ti,nspire-keypad.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TI-NSPIRE Keypad
10 - Andrew Davis <afd@ti.com>
13 - $ref: input.yaml#
14 - $ref: matrix-keymap.yaml#
19 - ti,nspire-keypad
30 scan-interval:
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/mfd/ |
| H A D | tc3589x.txt | 1 * Toshiba TC3589x multi-purpose expander
3 The Toshiba TC3589x series are I2C-based MFD devices which may expose the
4 following built-in devices: gpio, keypad, rotator (vibrator), PWM (for
7 - TC35890
8 - TC35892
9 - TC35893
10 - TC35894
11 - TC35895
12 - TC35896
15 - compatible : must be "toshiba,tc35890", "toshiba,tc35892", "toshiba,tc35893",
[all …]
|
| H A D | adi,adp5585.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Analog Devices ADP5585 Keypad Decoder and I/O Expansion
10 - Laurent Pinchart <laurent.pinchart@ideasonboard.com>
13 The ADP5585 is a 10/11 input/output port expander with a built in keypad
14 matrix decoder, programmable logic, reset generator, and PWM generator.
19 - items:
20 - enum:
21 - adi,adp5585-00 # Default
[all …]
|