We got multiple patches to add mux support to device tree, so people are using it happily already and build up on it. I also used it in a project without encountering problems. 20 months of EXPERIMENTAL should do for this.
Signed-off-by: Wolfram Sang <[email protected]> Cc: Lars-Peter Clausen <[email protected]> Cc: Stephen Warren <[email protected]> Cc: David Daney <[email protected]> Cc: Peter Korsgaard <[email protected]> Cc: Guenter Roeck <[email protected]> Cc: Michael Lawnick <[email protected]> Cc: Jean Delvare <[email protected]> --- drivers/i2c/Kconfig | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/i2c/Kconfig b/drivers/i2c/Kconfig index 5f13c62..5a3bb3d 100644 --- a/drivers/i2c/Kconfig +++ b/drivers/i2c/Kconfig @@ -49,7 +49,6 @@ config I2C_CHARDEV config I2C_MUX tristate "I2C bus multiplexing support" - depends on EXPERIMENTAL help Say Y here if you want the I2C core to support the ability to handle multiplexed I2C bus topologies, by presenting each -- 1.7.10 -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
