Version:  2.0.40 2.2.26 2.4.37 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7

Linux/drivers/i2c/muxes/Kconfig

  1 #
  2 # Multiplexer I2C chip drivers configuration
  3 #
  4 
  5 menu "Multiplexer I2C Chip support"
  6         depends on I2C_MUX
  7 
  8 config I2C_ARB_GPIO_CHALLENGE
  9         tristate "GPIO-based I2C arbitration"
 10         depends on GPIOLIB || COMPILE_TEST
 11         depends on OF
 12         help
 13           If you say yes to this option, support will be included for an
 14           I2C multimaster arbitration scheme using GPIOs and a challenge &
 15           response mechanism where masters have to claim the bus by asserting
 16           a GPIO.
 17 
 18           This driver can also be built as a module.  If so, the module
 19           will be called i2c-arb-gpio-challenge.
 20 
 21 config I2C_MUX_GPIO
 22         tristate "GPIO-based I2C multiplexer"
 23         depends on GPIOLIB
 24         help
 25           If you say yes to this option, support will be included for a
 26           GPIO based I2C multiplexer. This driver provides access to
 27           I2C busses connected through a MUX, which is controlled
 28           through GPIO pins.
 29 
 30           This driver can also be built as a module.  If so, the module
 31           will be called i2c-mux-gpio.
 32 
 33 config I2C_MUX_PCA9541
 34         tristate "NXP PCA9541 I2C Master Selector"
 35         help
 36           If you say yes here you get support for the NXP PCA9541
 37           I2C Master Selector.
 38 
 39           This driver can also be built as a module.  If so, the module
 40           will be called i2c-mux-pca9541.
 41 
 42 config I2C_MUX_PCA954x
 43         tristate "Philips PCA954x I2C Mux/switches"
 44         depends on GPIOLIB || COMPILE_TEST
 45         help
 46           If you say yes here you get support for the Philips PCA954x
 47           I2C mux/switch devices.
 48 
 49           This driver can also be built as a module.  If so, the module
 50           will be called i2c-mux-pca954x.
 51 
 52 config I2C_MUX_PINCTRL
 53         tristate "pinctrl-based I2C multiplexer"
 54         depends on PINCTRL
 55         help
 56           If you say yes to this option, support will be included for an I2C
 57           multiplexer that uses the pinctrl subsystem, i.e. pin multiplexing.
 58           This is useful for SoCs whose I2C module's signals can be routed to
 59           different sets of pins at run-time.
 60 
 61           This driver can also be built as a module. If so, the module will be
 62           called pinctrl-i2cmux.
 63 
 64 config I2C_MUX_REG
 65         tristate "Register-based I2C multiplexer"
 66         help
 67           If you say yes to this option, support will be included for a
 68           register based I2C multiplexer. This driver provides access to
 69           I2C busses connected through a MUX, which is controlled
 70           by a single register.
 71 
 72           This driver can also be built as a module.  If so, the module
 73           will be called i2c-mux-reg.
 74 
 75 config I2C_DEMUX_PINCTRL
 76         tristate "pinctrl-based I2C demultiplexer"
 77         depends on PINCTRL && OF
 78         select OF_DYNAMIC
 79         help
 80           If you say yes to this option, support will be included for an I2C
 81           demultiplexer that uses the pinctrl subsystem. This is useful if you
 82           want to change the I2C master at run-time depending on features.
 83 
 84 endmenu

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us