Lines Matching +full:led +full:- +full:order
7 Note that it only applies to the new descriptor-based interface. For a
8 description of the deprecated integer-based GPIO interface please refer to
9 gpio-legacy.txt (actually, there is no real mapping possible with the old
20 -----------
26 <function>-gpios, where <function> is the function the driver will request
32 led-gpios = <&gpio 15 GPIO_ACTIVE_HIGH>, /* red */
36 power-gpios = <&gpio 1 GPIO_ACTIVE_LOW>;
39 Properties named <function>-gpio are also considered valid and old bindings use
44 "led" function, and GPIO 1 as the "power" GPIO::
48 red = gpiod_get_index(dev, "led", 0, GPIOD_OUT_HIGH);
49 green = gpiod_get_index(dev, "led", 1, GPIOD_OUT_HIGH);
50 blue = gpiod_get_index(dev, "led", 2, GPIOD_OUT_HIGH);
54 The led GPIOs will be active high, while the power GPIO will be active low (i.e.
58 the <function>-prefix of the GPIO suffixes ("gpios" or "gpio", automatically
60 "led-gpios" example, use the prefix without the "-" as con_id parameter: "led".
64 (``snprintf(... "%s-%s", con_id, gpio_suffixes[]``).
67 ----
85 ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
88 "led-gpios",
96 "power-gpios",
104 Documentation/firmware-guide/acpi/gpio-properties.rst.
107 -------------
121 - key is either the label of the gpiod_chip instance providing the GPIO, or
123 - chip_hwnum is the hardware number of the GPIO within the chip, or U16_MAX
125 - con_id is the name of the GPIO function from the device point of view. It
127 - idx is the index of the GPIO within the function.
128 - flags is defined to specify the following properties:
129 * GPIO_ACTIVE_HIGH - GPIO line is active high
130 * GPIO_ACTIVE_LOW - GPIO line is active low
131 * GPIO_OPEN_DRAIN - GPIO line is set up as open drain
132 * GPIO_OPEN_SOURCE - GPIO line is set up as open source
133 * GPIO_PERSISTENT - GPIO line is persistent during
135 * GPIO_TRANSITORY - GPIO line is transitory and may loose its
150 .. code-block:: c
155 GPIO_LOOKUP_IDX("gpio.0", 15, "led", 0, GPIO_ACTIVE_HIGH),
156 GPIO_LOOKUP_IDX("gpio.0", 16, "led", 1, GPIO_ACTIVE_HIGH),
157 GPIO_LOOKUP_IDX("gpio.0", 17, "led", 2, GPIO_ACTIVE_HIGH),
171 red = gpiod_get_index(dev, "led", 0, GPIOD_OUT_HIGH);
172 green = gpiod_get_index(dev, "led", 1, GPIOD_OUT_HIGH);
173 blue = gpiod_get_index(dev, "led", 2, GPIOD_OUT_HIGH);
177 Since the "led" GPIOs are mapped as active-high, this example will switch their
179 as active-low, its actual signal will be 0 after this code. Contrary to the
180 legacy integer GPIO interface, the active-low property is handled during
184 the new descriptor-oriented interface.
188 .. code-block:: c
199 The line will be hogged as soon as the gpiochip is created or - in case the
200 chip was created earlier - when the hog table is registered.
203 --------------
210 In order to qualify for fast bitmap processing, the array must meet the
213 - pin hardware number of array member 0 must also be 0,
214 - pin hardware numbers of consecutive array members which belong to the same
217 Otherwise fast bitmap processing path is not used in order to avoid consecutive
218 pins which belong to the same chip but are not in hardware order being processed