summaryrefslogtreecommitdiff
path: root/drivers/mux/Kconfig
diff options
context:
space:
mode:
authorPeter Rosin <peda@axentia.se>2017-05-14 22:51:06 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-06-03 13:29:26 +0300
commita3b02a9c6591ce154cd44e2383406390a45b530c (patch)
treed6d0547b25d3117c103370ee24020cfd6cced3fe /drivers/mux/Kconfig
parent256ac0375098e50d59c415fcbb561f2927fa8780 (diff)
downloadlinux-a3b02a9c6591ce154cd44e2383406390a45b530c.tar.xz
mux: minimal mux subsystem
Add a new minimalistic subsystem that handles multiplexer controllers. When multiplexers are used in various places in the kernel, and the same multiplexer controller can be used for several independent things, there should be one place to implement support for said multiplexer controller. A single multiplexer controller can also be used to control several parallel multiplexers, that are in turn used by different subsystems in the kernel, leading to a need to coordinate multiplexer accesses. The multiplexer subsystem handles this coordination. Thanks go out to Lars-Peter Clausen, Jonathan Cameron, Rob Herring, Wolfram Sang, Paul Gortmaker, Dan Carpenter, Colin Ian King, Greg Kroah-Hartman and last but certainly not least to Philipp Zabel for helpful comments, reviews, patches and general encouragement! Reviewed-by: Jonathan Cameron <jic23@kernel.org> Signed-off-by: Peter Rosin <peda@axentia.se> Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de> Tested-by: Philipp Zabel <p.zabel@pengutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/mux/Kconfig')
-rw-r--r--drivers/mux/Kconfig16
1 files changed, 16 insertions, 0 deletions
diff --git a/drivers/mux/Kconfig b/drivers/mux/Kconfig
new file mode 100644
index 000000000000..23ab2cde83b1
--- /dev/null
+++ b/drivers/mux/Kconfig
@@ -0,0 +1,16 @@
+#
+# Multiplexer devices
+#
+
+menuconfig MULTIPLEXER
+ tristate "Multiplexer subsystem"
+ help
+ Multiplexer controller subsystem. Multiplexers are used in a
+ variety of settings, and this subsystem abstracts their use
+ so that the rest of the kernel sees a common interface. When
+ multiple parallel multiplexers are controlled by one single
+ multiplexer controller, this subsystem also coordinates the
+ multiplexer accesses.
+
+ To compile the subsystem as a module, choose M here: the module will
+ be called mux-core.