Home
last modified time | relevance | path

Searched +full:num +full:- +full:columns (Results 1 – 20 of 20) sorted by relevance

/Documentation/devicetree/bindings/input/
Dadi,adp5588.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Nuno Sá <nuno.sa@analog.com>
14 https://www.analog.com/media/en/technical-documentation/data-sheets/ADP5588.pdf
17 - $ref: matrix-keymap.yaml#
18 - $ref: input.yaml#
23 - adi,adp5587
24 - adi,adp5588
29 vcc-supply:
[all …]
Domap-keypad.txt3 TI's Keypad controller is used to interface a SoC with a matrix-type
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.
24 compatible = "ti,omap4-keypad";
25 keypad,num-rows = <2>;
26 keypad,num-columns = <8>;
[all …]
Dtwl4030-keypad.txt3 TWL4030's Keypad controller is used to interface a SoC with a matrix-type
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.
23 compatible = "ti,twl4030-keypad";
25 keypad,num-rows = <8>;
[all …]
Dlpc32xx-key.txt3 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 …]
Dsamsung,s3c6410-keypad.yaml1 # 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#
10 Samsung SoC Keypad controller is used to interface a SoC with a matrix-type
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
23 - samsung,s5pv210-keypad
31 clock-names:
[all …]
Dmatrix-keymap.yaml1 # 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 …]
Dst-keyscan.txt4 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 …]
Dbrcm,bcm-keypad.txt3 Broadcom Keypad controller is used to interface a SoC with a matrix-type
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
26 - keypad,num-columns: Number of column lines connected to the
29 - col-debounce-filter-period: The debounce period for the Column filter.
[all …]
Dtca8418_keypad.txt1 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.
Dgoogle,cros-ec-keyb.yaml1 # 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>
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
27 const: google,cros-ec-keyb
[all …]
Dqcom,pm8921-keypad.yaml1 # 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#
10 - Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
13 - $ref: input.yaml#
14 - $ref: matrix-keymap.yaml#
19 - qcom,pm8058-keypad
20 - qcom,pm8921-keypad
27 - description: key sense
[all …]
Dpxa27x-keypad.txt4 - 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
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
20 - marvell,direct-key-low-active : Direct key status register
24 - marvell,direct-key-map : It is a u16 array. Each item indicates
25 the linux key-code for the direct key.
[all …]
Dazoteq,iqs7222.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jeff LaBundy <jeff@labundy.com>
21 - azoteq,iqs7222a
22 - azoteq,iqs7222b
23 - azoteq,iqs7222c
24 - azoteq,iqs7222d
29 irq-gpios:
32 Specifies the GPIO connected to the device's active-low RDY output.
[all …]
/Documentation/devicetree/bindings/mfd/
Dtc3589x.txt1 * 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 …]
Dst,stmpe.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
15 - Linus Walleij <linus.walleij@linaro.org>
18 - $ref: /schemas/spi/spi-peripheral-props.yaml#
23 - st,stmpe601
24 - st,stmpe801
25 - st,stmpe811
26 - st,stmpe1600
27 - st,stmpe1601
[all …]
/Documentation/userspace-api/media/dvb/
Ddmx-get-stc.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
11 ----
16 --------
23 ---------
32 -----------
37 setting the :c:type:`num <dmx_stc>` field of stc before the ioctl (range 0...n).
40 ``stc->stc / stc->base``.
43 ------------
47 On error -1 is returned, and the ``errno`` variable is set
52 .. flat-table::
[all …]
Dlegacy_dvb_osd.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later OR GPL-2.0
14 The DVB OSD device controls the OnScreen-Display of the AV7110 based
15 DVB-cards with hardware MPEG2 decoder. It can be accessed through
20 The OSD is not a frame-buffer like on many other cards.
22 The color-depth is limited depending on the memory size installed.
31 -----------
36 .. code-block:: c
39 /* All functions return -2 on "not open" */
67 .. note:: All functions return -2 on "not open"
69 .. flat-table::
[all …]
/Documentation/userspace-api/media/v4l/
Dvidioc-reqbufs.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_REQBUFS - Initiate Memory Mapping, User Pointer I/O or DMA buffer I/O
78 .. flat-table:: struct v4l2_requestbuffers
79 :header-rows: 0
80 :stub-columns: 0
83 * - __u32
84 - ``count``
85 - The number of buffers requested or granted.
86 * - __u32
87 - ``type``
[all …]
Dext-ctrls-codec.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _codec-controls:
24 .. _mpeg-control-id:
27 -----------------
35 .. _v4l2-mpeg-stream-type:
40 enum v4l2_mpeg_stream_type -
41 The MPEG-1, -2 or -4 output stream type. One cannot assume anything
48 .. flat-table::
49 :header-rows: 0
50 :stub-columns: 0
[all …]
/Documentation/trace/
Dkprobes.rst29 collect debugging and performance information non-disruptively. You
41 In the typical case, Kprobes-based instrumentation is packaged as
56 Kprobes -- e.g., the difference between a pre_handler and
62 -----------------------
74 Next, Kprobes single-steps its copy of the probed instruction.
75 (It would be simpler to single-step the actual instruction in place,
80 After the instruction is single-stepped, Kprobes executes the
85 -----------------------
105 -------------
114 is an arbitrary piece of code -- typically just a nop instruction.
[all …]