Lines Matching refs:possible

401 system, even though the framework makes it possible to also change the function
466 subsystems, so devices will request their mux setting, but it's also possible
473   pin control driver knows the possible functions. In the example above you can
511   the set of pins to be used by a certain device. (If only one possible group
530   It is possible to map several groups to the same combination of device,
549 We assume that the number of possible function maps to pin groups is limited by
555 expect pinmux drivers to present *all* possible function vs pin group mappings
568 is possible to perform the requested mux setting, poke the hardware so that
793 may be confused by a datasheet talking about a pin being possible to set
847 pulsed out. It is likely possible to disrupt the traffic on the pin by doing
849 possible that the GPIO, pin config and pin multiplex registers are placed into
902 So it is perfectly possible to push a pin into "GPIO mode" and drive the
1066 As it is possible to map a function to different groups of pins an optional
1091 Further it is possible for one named state to affect the muxing of several
1182 control. So if possible, handle the pin control in platform code or some other
1185 at runtime this is not possible.
1357 It is possible to mux a certain function in and out at runtime, say to move