Home
last modified time | relevance | path

Searched +full:button +full:- +full:right +full:- +full:gpios (Results 1 – 3 of 3) sorted by relevance

/Documentation/devicetree/bindings/input/
Dgpio-mouse.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/gpio-mouse.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 to 5-7 GPIO lines.
14 - Anshul Dalal <anshulusr@gmail.com>
18 const: gpio-mouse
20 scan-interval-ms:
23 up-gpios:
26 down-gpios:
[all …]
/Documentation/devicetree/bindings/gpio/
Dgpio.txt4 1) gpios property
5 -----------------
7 GPIO properties should be named "[<name>-]gpios", with <name> being the purpose
8 of this GPIO for the device. While a non-existent <name> is considered valid
9 for compatibility reasons (resolving to the "gpios" property), it is not allowed
10 for new bindings. Also, GPIO properties named "[<name>-]gpio" are valid and old
15 cases should they contain more than one. If your device uses several GPIOs with
17 meaningful name. The only case where an array of GPIOs is accepted is when
18 several GPIOs serve the same function (e.g. a parallel data line).
20 The exact purpose of each gpios property must be documented in the device tree
[all …]
/Documentation/driver-api/gpio/
Ddriver.rst13 Internal Representation of GPIOs
26 between 0 and n-1, n being the number of GPIOs managed by the chip.
29 example if a system uses a memory-mapped set of I/O-registers where 32 GPIO
30 lines are handled by one bit per line in a 32-bit register, it makes sense to
44 So for example one platform could use global numbers 32-159 for GPIOs, with a
45 controller defining 128 GPIOs at a "base" of 32 ; while another platform uses
46 global numbers 0..63 with one set of GPIO controllers, 64-79 with another type
47 of GPIO controller, and on one particular board 80-95 with an FPGA. The legacy
49 2000-2063 to identify GPIO lines in a bank of I2C GPIO expanders.
60 - methods to establish GPIO line direction
[all …]