| Peter Rosin | a3b02a9 | 2017-05-14 21:51:06 +0200 | [diff] [blame] | 1 | # |
| 2 | # Multiplexer devices |
| 3 | # |
| 4 | |
| 5 | menuconfig MULTIPLEXER |
| 6 | tristate "Multiplexer subsystem" |
| 7 | help |
| 8 | Multiplexer controller subsystem. Multiplexers are used in a |
| 9 | variety of settings, and this subsystem abstracts their use |
| 10 | so that the rest of the kernel sees a common interface. When |
| 11 | multiple parallel multiplexers are controlled by one single |
| 12 | multiplexer controller, this subsystem also coordinates the |
| 13 | multiplexer accesses. |
| 14 | |
| 15 | To compile the subsystem as a module, choose M here: the module will |
| 16 | be called mux-core. |
| Peter Rosin | 2c089f0 | 2017-05-14 21:51:07 +0200 | [diff] [blame^] | 17 | |
| 18 | if MULTIPLEXER |
| 19 | |
| 20 | config MUX_GPIO |
| 21 | tristate "GPIO-controlled Multiplexer" |
| 22 | depends on GPIOLIB || COMPILE_TEST |
| 23 | help |
| 24 | GPIO-controlled Multiplexer controller. |
| 25 | |
| 26 | The driver builds a single multiplexer controller using a number |
| 27 | of gpio pins. For N pins, there will be 2^N possible multiplexer |
| 28 | states. The GPIO pins can be connected (by the hardware) to several |
| 29 | multiplexers, which in that case will be operated in parallel. |
| 30 | |
| 31 | To compile the driver as a module, choose M here: the module will |
| 32 | be called mux-gpio. |
| 33 | |
| 34 | endif |