Lines Matching refs:may

20   can control PINs. It may be able to multiplex, bias, set load capacitance,
28   there may be several such number spaces in a system. This pin space may
29   be sparse - i.e. there may be gaps in the space with numbers where no
98 and such things in your driver, or the code may become complicated. You must
99 also consider matching of offsets to the GPIO ranges that may be handled by
190 may need more entries in your group structure, for example specific register
199 may be able to make an output pin high impedance, or "tristate" meaning it is
200 effectively disconnected. You may be able to connect an input pin to VDD or GND
281 The GPIO drivers may want to perform operations of various types on the same
292 pin controller may be muxing several GPIO ranges (typically SoCs that have
491   controller may have the same name.
532   a certain pin controller may use different sets of pins in different
543 silicon inside the package, and may or may not match the actual number of
746 and similar functions. There are cases where you may be using something
794 may be confused by a datasheet talking about a pin being possible to set
882 GPIO subsystem may call into the pinctrl subsystem in order to
883 co-ordinate register settings across HW modules. In particular, this may
889 may be placed at some pin-specific register in all cases or as part
896 If you make a 1-to-1 map to the GPIO subsystem for this pin, you may start
915 driver may look like this:
931 And your machine configuration may look like this:
1025 As you can see we may have several pin controllers on the system and thus
1040 The mapping table may also contain pin configuration entries. It's common for
1184 and not using the "default" state, you may have to do some device driver
1203 A driver may request a certain control state to be activated, usually just the
1255   specific state for a client device. This operation may be slow, too.
1260   into hardware. However, note that some pin controllers may have their
1266 - devm_pinctrl_put() is a variant of pinctrl_put() that may be used to
1272   pinctrl_get() may not be paired with devm_pinctrl_put().
1274   devm_pinctrl_get() may not be paired with plain pinctrl_put().
1317 The above can be hidden: using the device core, the pinctrl core may be
1323 back-end. This is when the GPIO driver may call out to the functions
1356 Since it may be common to request the core to hog a few always-applicable