Commit 4c19c0ec authored by Peter Rosin's avatar Peter Rosin Committed by Greg Kroah-Hartman

mux: remove the Kconfig question for the subsystem

The MULTIPLEXER question in the Kconfig might be confusing and is
of dubious value. Remove it. This makes consumers responsible for
selecting MULTIPLEXER, which they already do.
Signed-off-by: default avatarPeter Rosin <peda@axentia.se>
Reported-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent d6e4bd1b
...@@ -2,20 +2,11 @@ ...@@ -2,20 +2,11 @@
# Multiplexer devices # Multiplexer devices
# #
menuconfig MULTIPLEXER config MULTIPLEXER
tristate "Multiplexer subsystem" tristate
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.
if MULTIPLEXER menu "Multiplexer drivers"
depends on MULTIPLEXER
config MUX_ADG792A config MUX_ADG792A
tristate "Analog Devices ADG792A/ADG792G Multiplexers" tristate "Analog Devices ADG792A/ADG792G Multiplexers"
...@@ -56,4 +47,4 @@ config MUX_MMIO ...@@ -56,4 +47,4 @@ config MUX_MMIO
To compile the driver as a module, choose M here: the module will To compile the driver as a module, choose M here: the module will
be called mux-mmio. be called mux-mmio.
endif endmenu
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment