^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) # SPDX-License-Identifier: GPL-2.0-only
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3) # Multiplexer I2C chip drivers configuration
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6) menu "Multiplexer I2C Chip support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7) depends on I2C_MUX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9) config I2C_ARB_GPIO_CHALLENGE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) tristate "GPIO-based I2C arbitration"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) depends on GPIOLIB || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) depends on OF || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) If you say yes to this option, support will be included for an
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) I2C multimaster arbitration scheme using GPIOs and a challenge &
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) response mechanism where masters have to claim the bus by asserting
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) a GPIO.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) will be called i2c-arb-gpio-challenge.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) config I2C_MUX_GPIO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) tristate "GPIO-based I2C multiplexer"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) depends on GPIOLIB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) If you say yes to this option, support will be included for a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) GPIO based I2C multiplexer. This driver provides access to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) I2C busses connected through a MUX, which is controlled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) through GPIO pins.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32) will be called i2c-mux-gpio.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34) config I2C_MUX_GPMUX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) tristate "General Purpose I2C multiplexer"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36) select MULTIPLEXER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) depends on OF || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39) If you say yes to this option, support will be included for a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40) general purpose I2C multiplexer. This driver provides access to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41) I2C busses connected through a MUX, which in turn is controlled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42) by a MUX-controller from the MUX subsystem.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45) will be called i2c-mux-gpmux.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47) config I2C_MUX_LTC4306
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48) tristate "LTC LTC4306/5 I2C multiplexer"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49) select GPIOLIB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50) select REGMAP_I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52) If you say yes here you get support for the Analog Devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53) LTC4306 or LTC4305 I2C mux/switch devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 54)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 55) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 56) will be called i2c-mux-ltc4306.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58) config I2C_MUX_PCA9541
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59) tristate "NXP PCA9541 I2C Master Selector"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61) If you say yes here you get support for the NXP PCA9541
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62) I2C Master Selector.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 65) will be called i2c-mux-pca9541.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 66)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 67) config I2C_MUX_PCA954x
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 68) tristate "NXP PCA954x and PCA984x I2C Mux/switches"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 69) depends on GPIOLIB || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 70) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 71) If you say yes here you get support for the NXP PCA954x
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 72) and PCA984x I2C mux/switch devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 73)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 74) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 75) will be called i2c-mux-pca954x.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 76)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 77) config I2C_MUX_PINCTRL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 78) tristate "pinctrl-based I2C multiplexer"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 79) depends on PINCTRL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 80) depends on OF || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 81) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 82) If you say yes to this option, support will be included for an I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 83) multiplexer that uses the pinctrl subsystem, i.e. pin multiplexing.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 84) This is useful for SoCs whose I2C module's signals can be routed to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 85) different sets of pins at run-time.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 86)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 87) This driver can also be built as a module. If so, the module will be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 88) called i2c-mux-pinctrl.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 89)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 90) config I2C_MUX_REG
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 91) tristate "Register-based I2C multiplexer"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 92) depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 93) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 94) If you say yes to this option, support will be included for a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 95) register based I2C multiplexer. This driver provides access to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 96) I2C busses connected through a MUX, which is controlled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 97) by a single register.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 98)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 99) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100) will be called i2c-mux-reg.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) config I2C_DEMUX_PINCTRL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103) tristate "pinctrl-based I2C demultiplexer"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104) depends on PINCTRL && OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) select OF_DYNAMIC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107) If you say yes to this option, support will be included for an I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108) demultiplexer that uses the pinctrl subsystem. This is useful if you
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) want to change the I2C master at run-time depending on features.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111) config I2C_MUX_MLXCPLD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112) tristate "Mellanox CPLD based I2C multiplexer"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114) If you say yes to this option, support will be included for a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115) CPLD based I2C multiplexer. This driver provides access to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116) I2C busses connected through a MUX, which is controlled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117) by a CPLD register.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120) will be called i2c-mux-mlxcpld.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122) endmenu
Orange Pi5 kernel
Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards
3 Commits
0 Branches
0 Tags