Lines Matching refs:named

285 see the section named "pin control requests from drivers" and
576 into some register named MUX to select a certain function with a certain
747 configuration for a certain device. See the section below named
750 The public pinmux API contains two functions named pinctrl_request_gpio()
783 named functions for each GPIO pin, the pinctrl_request_gpio() will attempt to
949 named "gpio-mode" that can be mapped onto the same pins to move them into
1052 named states. When running on hardware that doesn't need any pin controller
1053 configuration, the mapping table must still contain those named states, in
1056 a named state without causing any pin controller to be programmed:
1091 Further it is possible for one named state to affect the muxing of several
1205 	/* Allocate a state holder named "foo" etc */
1360 function, but with different named in the mapping as described under
1361 "Advanced mapping" above. So that for an SPI device, we have two states named