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
738 All the above functions are mandatory to implement for a pinmux driver.
746 and similar functions. There are cases where you may be using something
751 The public pinmux API contains two functions named pinctrl_request_gpio()
752 and pinctrl_free_gpio(). These two functions shall *ONLY* be called from
767 setting and then the device functions.
769 For this reason there are two functions a pin control driver can implement
783 Alternatively to using these special functions, it is fully allowed to use
784 named functions for each GPIO pin, the pinctrl_request_gpio() will attempt to
861 peripheral functions. So again the "strict" flag should be set, denying
873   be exposed through the pinctrl subsystem, as mux functions.
881 Depending on the exact HW register design, some functions exposed by the
1026 we need to specify which one of them contains the functions we wish to map.
1277 device drivers bookkeeping operations, like checking available functions and
1323 back-end. This is when the GPIO driver may call out to the functions
1419 can be used by different functions at different times on a running system.