Lines Matching refs:be

4 This document explains how GPIOs can be assigned to given devices and functions.
12 is mandatory) or ARCH_WANT_OPTIONAL_GPIOLIB (if GPIO support can be omitted) in
14 describe its hardware layout. Currently, mappings can be defined through device
19 GPIOs can easily be mapped to devices and functions in the device tree. The
38 it but are only supported for compatibility reasons and should not be used for
52 The led GPIOs will be active-high, while the power GPIO will be active-low (i.e.
53 gpiod_is_active_low(power) will be true).
55 The second parameter of the gpiod_get() functions, the con_id string, has to be
67 The above DT example can be converted to an equivalent ACPI description
106 Finally, GPIOs can be bound to devices and functions using platform data. Board
122 	can be NULL, in which case it will be matched for calls to gpiod_get()
125 	can be NULL, in which case it will match any function.
132 In the future, these flags might be extended to support more properties.
136 A lookup table can then be defined as follows, with an empty entry defining its
150 And the table can be added by the board code as follows:
154 The driver controlling "foo.0" will then be able to obtain its GPIOs as follows:
166 as active-low, its actual signal will be 0 after this code. Contrary to the legacy