Lines Matching refs:subsystem

1 PINCTRL (PIN CONTROL) subsystem
2 This document outlines the pin control subsystem in Linux
4 This subsystem deals with:
87 To enable the pinctrl subsystem and the subgroups for PINMUX and PINCONF and
119 subsystem has a mechanism for enumerating groups of pins and retrieving the
126 These two groups are presented to the pin control subsystem by implementing
186 The pin control subsystem will call the .get_groups_count() function to
278 Interaction with the GPIO subsystem
287 situations a cross-subsystem mapping between pins and GPIOs is needed.
289 Since the pin controller subsystem have its pinspace local to the pin
290 controller we need a mapping so that the pin control subsystem can figure out
367 When GPIO-specific functions in the pin control subsystem are called, these
374 controller subsystem will look up the corresponding pin number from the passed
376 that, the subsystem passes it on to the pin control driver, so the driver
463 The purpose of the pinmux functionality in the pin controller subsystem is to
472   control subsystem in the drivers/pinctrl/* directory of the kernel. The
556 to the subsystem.
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
741 Pin control interaction with the GPIO subsystem
869   exposed through the pinctrl subsystem, as "pin configuration" settings.
873   be exposed through the pinctrl subsystem, as mux functions.
877   setting GPIO pin direction should be exposed through the GPIO subsystem,
882 GPIO subsystem may call into the pinctrl subsystem in order to
896 If you make a 1-to-1 map to the GPIO subsystem for this pin, you may start
964 GPIO subsystem. It is just an electrical configuration used by that device
1028 You register this pinmux mapping to the pinmux subsystem by simply:
1319 probing, nevertheless orthogonal to the GPIO subsystem.
1321 But there are also situations where it makes sense for the GPIO subsystem
1322 to communicate directly with the pinctrl subsystem, using the latter as a
1324 described in the section "Pin control interaction with the GPIO subsystem"
1327 need not interact with the pin control subsystem at all.