Lines Matching refs:pinmux

453 different pins by pinmux settings.
463 The purpose of the pinmux functionality in the pin controller subsystem is to
464 abstract and provide pinmux settings to the devices you choose to instantiate
474   identify three pinmux functions, one for spi, one for i2c and one for mmc.
495   and their machine-specific particulars are kept inside the pinmux driver,
516   use device spi0 with pinmux function fspi0 group gspi0 and i2c0 on function
554 by inspecting available pinmux hardware, and a necessary assumption since we
555 expect pinmux drivers to present *all* possible function vs pin group mappings
562 The pinmux core takes care of preventing conflicts on pins and calling
565 It is the responsibility of the pinmux driver to impose further restrictions
580 #include <linux/pinctrl/pinmux.h>
730 The beauty of the pinmux subsystem is that since it keeps track of all
733 things - when it gets a selector passed in, the pinmux subsystem makes
738 All the above functions are mandatory to implement for a pinmux driver.
751 The public pinmux API contains two functions named pinctrl_request_gpio()
814      Physical pins --- pad --- pinmux -+- I2C
844      Physical pins --- pad --- pinmux -+- I2C
988 constrained and how the clock tree looks. Of course pinmux settings are also
1023 must match a function provided by the pinmux driver handling this pin range.
1028 You register this pinmux mapping to the pinmux subsystem by simply:
1174 pinmux core.
1246   kernel memory to hold the pinmux state. All mapping table parsing or similar