Lines Matching refs:functions

187 determine the total number of legal selectors, then it will call the other functions
367 When GPIO-specific functions in the pin control subsystem are called, these
370 pin controller handling the matching range is found, GPIO-specific functions
396 PINMUX, also known as padmux, ballmux, alternate functions or mission modes
399 functions, depending on the application. By "application" in this context
473   pin control driver knows the possible functions. In the example above you can
474   identify three pinmux functions, one for spi, one for i2c and one for mmc.
478   for the three available functions.
494   for a certain set of pins. The knowledge of the functions and pin groups
571 Pinmux drivers are required to supply a few callback functions, some are
737 All the above functions are mandatory to implement for a pinmux driver.
745 and similar functions. There are cases where you may be using something
750 The public pinmux API contains two functions named pinctrl_request_gpio()
751 and pinctrl_free_gpio(). These two functions shall *ONLY* be called from
766 setting and then the device functions.
768 For this reason there are two functions a pin control driver can implement
782 Alternatively to using these special functions, it is fully allowed to use
783 named functions for each GPIO pin, the pinctrl_request_gpio() will attempt to
862   be exposed through the pinctrl subsystem, as mux functions.
870 Depending on the exact HW register design, some functions exposed by the
1015 we need to specify which one of them contains the functions we wish to map.
1266 device drivers bookkeeping operations, like checking available functions and
1312 back-end. This is when the GPIO driver may call out to the functions
1408 can be used by different functions at different times on a running system.