^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) # Sensor device 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 "I2C Hardware Bus support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7) depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9) comment "PC SMBus host controller drivers"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) config I2C_ALI1535
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) tristate "ALI 1535"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) If you say yes to this option, support will be included for the SMB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) controller is part of the 7101 device, which is an ACPI-compliant
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) Power Management Unit (PMU).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) will be called i2c-ali1535.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) config I2C_ALI1563
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) tristate "ALI 1563"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) If you say yes to this option, support will be included for the SMB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) controller is part of the 7101 device, which is an ACPI-compliant
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) Power Management Unit (PMU).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34) will be called i2c-ali1563.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36) config I2C_ALI15X3
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) tristate "ALI 15x3"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41) Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44) will be called i2c-ali15x3.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46) config I2C_AMD756
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47) tristate "AMD 756/766/768/8111 and nVidia nForce"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50) If you say yes to this option, support will be included for the AMD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51) 756/766/768 mainboard I2C interfaces. The driver also includes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52) support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53) the nVidia nForce I2C interface.
^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-amd756.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58) config I2C_AMD756_S4882
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59) tristate "SMBus multiplexing on the Tyan S4882"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60) depends on I2C_AMD756 && X86
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62) Enabling this option will add specific SMBus support for the Tyan
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63) S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64) over 8 different channels, where the various memory module EEPROMs
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 65) and temperature sensors live. Saying yes here will give you access
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 66) to these in addition to the trunk.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 67)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 68) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 69) will be called i2c-amd756-s4882.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 70)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 71) config I2C_AMD8111
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 72) tristate "AMD 8111"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 73) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 74) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 75) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 76) second (SMBus 2.0) AMD 8111 mainboard I2C interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 77)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 78) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 79) will be called i2c-amd8111.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 80)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 81) config I2C_AMD_MP2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 82) tristate "AMD MP2 PCIe"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 83) depends on PCI && ACPI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 84) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 85) If you say yes to this option, support will be included for the AMD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 86) MP2 PCIe I2C adapter.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 87)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 88) This driver can also be built as modules. If so, the modules will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 89) be called i2c-amd-mp2-pci and i2c-amd-mp2-plat.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 90)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 91) config I2C_HIX5HD2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 92) tristate "Hix5hd2 high-speed I2C driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 93) depends on ARCH_HISI || ARCH_HIX5HD2 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 94) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 95) Say Y here to include support for the high-speed I2C controller
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 96) used in HiSilicon hix5hd2 SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 97)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 98) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 99) will be called i2c-hix5hd2.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) config I2C_I801
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) tristate "Intel 82801 (ICH/PCH)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104) select CHECK_SIGNATURE if X86 && DMI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) select I2C_SMBUS
^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 the Intel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108) 801 family of mainboard I2C interfaces. Specifically, the following
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) versions of the chipset are supported:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110) 82801AA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111) 82801AB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112) 82801BA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113) 82801CA/CAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114) 82801DB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115) 82801EB/ER (ICH5/ICH5R)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116) 6300ESB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117) ICH6
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118) ICH7
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119) ESB2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120) ICH8
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121) ICH9
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122) EP80579 (Tolapai)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123) ICH10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) 5/3400 Series (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125) 6 Series (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126) Patsburg (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127) DH89xxCC (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128) Panther Point (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129) Lynx Point (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130) Avoton (SOC)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131) Wellsburg (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132) Coleto Creek (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133) Wildcat Point (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134) BayTrail (SOC)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135) Braswell (SOC)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136) Sunrise Point (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137) Kaby Lake (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138) DNV (SOC)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139) Broxton (SOC)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140) Lewisburg (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141) Gemini Lake (SOC)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142) Cannon Lake (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143) Cedar Fork (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144) Ice Lake (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145) Comet Lake (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146) Elkhart Lake (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147) Tiger Lake (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148) Jasper Lake (SOC)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149) Emmitsburg (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) Alder Lake (PCH)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) will be called i2c-i801.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155) config I2C_ISCH
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) tristate "Intel SCH SMBus 1.0"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158) select LPC_SCH
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160) Say Y here if you want to use SMBus controller on the Intel SCH
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161) based systems.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164) will be called i2c-isch.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) config I2C_ISMT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167) tristate "Intel iSMT SMBus Controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) depends on PCI && X86
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170) If you say yes to this option, support will be included for the Intel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171) iSMT SMBus host controller interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173) This driver can also be built as a module. If so, the module will be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174) called i2c-ismt.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176) config I2C_PIIX4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177) tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180) If you say yes to this option, support will be included for the Intel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181) PIIX4 family of mainboard I2C interfaces. Specifically, the following
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182) versions of the chipset are supported (note that Serverworks is part
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183) of Broadcom):
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) Intel PIIX4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185) Intel 440MX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186) ATI IXP200
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187) ATI IXP300
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188) ATI IXP400
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189) ATI SB600
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190) ATI SB700/SP5100
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191) ATI SB800
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192) AMD Hudson-2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193) AMD ML
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194) AMD CZ
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195) Hygon CZ
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196) Serverworks OSB4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197) Serverworks CSB5
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198) Serverworks CSB6
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199) Serverworks HT-1000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200) Serverworks HT-1100
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201) SMSC Victory66
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203) Some AMD chipsets contain two PIIX4-compatible SMBus
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) controllers. This driver will attempt to use both controllers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205) on the SB700/SP5100, if they have been initialized by the BIOS.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208) will be called i2c-piix4.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210) config I2C_CHT_WC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211) tristate "Intel Cherry Trail Whiskey Cove PMIC smbus controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212) depends on INTEL_SOC_PMIC_CHTWC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215) SMBus controller found in the Intel Cherry Trail Whiskey Cove PMIC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216) found on some Intel Cherry Trail systems.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218) Note this controller is hooked up to a TI bq24292i charger-IC,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219) combined with a FUSB302 Type-C port-controller as such it is advised
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220) to also select CONFIG_TYPEC_FUSB302=m.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222) config I2C_NFORCE2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 223) tristate "Nvidia nForce2, nForce3 and nForce4"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 224) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 225) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 226) If you say yes to this option, support will be included for the Nvidia
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 227) nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 228)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 229) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 230) will be called i2c-nforce2.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 231)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 232) config I2C_NFORCE2_S4985
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 233) tristate "SMBus multiplexing on the Tyan S4985"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 234) depends on I2C_NFORCE2 && X86
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 235) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 236) Enabling this option will add specific SMBus support for the Tyan
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 237) S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 238) over 4 different channels, where the various memory module EEPROMs
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 239) live. Saying yes here will give you access to these in addition
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 240) to the trunk.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 241)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 242) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 243) will be called i2c-nforce2-s4985.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 244)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 245) config I2C_NVIDIA_GPU
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 246) tristate "NVIDIA GPU I2C controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 247) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 248) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 249) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 250) NVIDIA GPU I2C controller which is used to communicate with the GPU's
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 251) Type-C controller. This driver can also be built as a module called
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 252) i2c-nvidia-gpu.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 253)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 254) config I2C_SIS5595
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 255) tristate "SiS 5595"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 256) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 257) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 258) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 259) SiS5595 SMBus (a subset of I2C) interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 260)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 261) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 262) will be called i2c-sis5595.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 263)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 264) config I2C_SIS630
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 265) tristate "SiS 630/730/964"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 266) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 267) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 268) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 269) SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 270)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 271) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 272) will be called i2c-sis630.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 273)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 274) config I2C_SIS96X
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 275) tristate "SiS 96x"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 276) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 277) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 278) If you say yes to this option, support will be included for the SiS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 279) 96x SMBus (a subset of I2C) interfaces. Specifically, the following
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 280) chipsets are supported:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 281) 645/961
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 282) 645DX/961
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 283) 645DX/962
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 284) 648/961
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 285) 650/961
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 286) 735
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 287) 745
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 288)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 289) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 290) will be called i2c-sis96x.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 291)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 292) config I2C_VIA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 293) tristate "VIA VT82C586B"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 294) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 295) select I2C_ALGOBIT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 296) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 297) If you say yes to this option, support will be included for the VIA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 298) 82C586B I2C interface
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 299)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 300) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 301) will be called i2c-via.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 302)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 303) config I2C_VIAPRO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 304) tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 305) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 306) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 307) If you say yes to this option, support will be included for the VIA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 308) VT82C596 and later SMBus interface. Specifically, the following
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 309) chipsets are supported:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 310) VT82C596A/B
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 311) VT82C686A/B
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 312) VT8231
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 313) VT8233/A
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 314) VT8235
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 315) VT8237R/A/S
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 316) VT8251
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 317) CX700
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 318) VX800/VX820
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 319) VX855/VX875
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 320) VX900
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 321)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 322) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 323) will be called i2c-viapro.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 324)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 325) if ACPI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 326)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 327) comment "ACPI drivers"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 328)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 329) config I2C_SCMI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 330) tristate "SMBus Control Method Interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 331) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 332) This driver supports the SMBus Control Method Interface. It needs the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 333) BIOS to declare ACPI control methods as described in the SMBus Control
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 334) Method Interface specification.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 335)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 336) To compile this driver as a module, choose M here:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 337) the module will be called i2c-scmi.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 338)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 339) endif # ACPI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 340)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 341) comment "Mac SMBus host controller drivers"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 342) depends on PPC_CHRP || PPC_PMAC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 343)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 344) config I2C_HYDRA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 345) tristate "CHRP Apple Hydra Mac I/O I2C interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 346) depends on PCI && PPC_CHRP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 347) select I2C_ALGOBIT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 348) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 349) This supports the use of the I2C interface in the Apple Hydra Mac
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 350) I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 351) have such a machine.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 352)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 353) This support is also available as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 354) will be called i2c-hydra.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 355)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 356) config I2C_POWERMAC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 357) tristate "Powermac I2C interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 358) depends on PPC_PMAC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 359) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 360) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 361) This exposes the various PowerMac i2c interfaces to the linux i2c
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 362) layer and to userland. It is used by various drivers on the PowerMac
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 363) platform, and should generally be enabled.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 364)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 365) This support is also available as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 366) will be called i2c-powermac.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 367)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 368) comment "I2C system bus drivers (mostly embedded / system-on-chip)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 369)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 370) config I2C_ALTERA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 371) tristate "Altera Soft IP I2C"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 372) depends on ARCH_SOCFPGA || NIOS2 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 373) depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 374) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 375) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 376) Altera Soft IP I2C interfaces on SoCFPGA and Nios2 architectures.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 377)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 378) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 379) will be called i2c-altera.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 380)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 381) config I2C_ASPEED
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 382) tristate "Aspeed I2C Controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 383) depends on ARCH_ASPEED || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 384) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 385) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 386) Aspeed I2C controller.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 387)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 388) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 389) will be called i2c-aspeed.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 390)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 391) config I2C_AT91
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 392) tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 393) depends on ARCH_AT91 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 394) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 395) This supports the use of the I2C interface on Atmel AT91
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 396) processors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 397)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 398) A serious problem is that there is no documented way to issue
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 399) repeated START conditions for more than two messages, as needed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 400) to support combined I2C messages. Use the i2c-gpio driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 401) unless your system can cope with this limitation.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 402)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 403) Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 404) don't have clock stretching in transmission mode. For that reason,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 405) you can encounter underrun issues causing premature stop sendings if
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 406) the latency to fill the transmission register is too long. If you
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 407) are facing this situation, use the i2c-gpio driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 408)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 409) config I2C_AT91_SLAVE_EXPERIMENTAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 410) tristate "Microchip AT91 I2C experimental slave mode"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 411) depends on I2C_AT91
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 412) select I2C_SLAVE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 413) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 414) If you say yes to this option, support for the slave mode will be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 415) added. Caution: do not use it for production. This feature has not
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 416) been tested in a heavy way, help wanted.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 417) There are known bugs:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 418) - It can hang, on a SAMA5D4, after several transfers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 419) - There are some mismtaches with a SAMA5D4 as slave and a SAMA5D2 as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 420) master.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 421)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 422) config I2C_AU1550
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 423) tristate "Au1550/Au1200/Au1300 SMBus interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 424) depends on MIPS_ALCHEMY
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 425) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 426) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 427) Au1550/Au1200/Au1300 SMBus interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 428)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 429) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 430) will be called i2c-au1550.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 431)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 432) config I2C_AXXIA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 433) tristate "Axxia I2C controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 434) depends on ARCH_AXXIA || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 435) default ARCH_AXXIA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 436) select I2C_SLAVE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 437) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 438) Say yes if you want to support the I2C bus on Axxia platforms.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 439)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 440) Please note that this controller is limited to transfers of maximum
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 441) 255 bytes in length. Any attempt to to a larger transfer will return
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 442) an error.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 443)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 444) config I2C_BCM2835
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 445) tristate "Broadcom BCM2835 I2C controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 446) depends on ARCH_BCM2835 || ARCH_BRCMSTB || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 447) depends on COMMON_CLK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 448) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 449) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 450) BCM2835 I2C controller.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 451)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 452) If you don't know what to do here, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 453)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 454) This support is also available as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 455) will be called i2c-bcm2835.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 456)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 457) config I2C_BCM_IPROC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 458) tristate "Broadcom iProc I2C controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 459) depends on ARCH_BCM_IPROC || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 460) default ARCH_BCM_IPROC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 461) select I2C_SLAVE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 462) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 463) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 464) Broadcom iProc I2C controller.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 465)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 466) If you don't know what to do here, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 467)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 468) config I2C_BCM_KONA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 469) tristate "BCM Kona I2C adapter"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 470) depends on ARCH_BCM_MOBILE || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 471) default y if ARCH_BCM_MOBILE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 472) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 473) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 474) I2C interface on the Broadcom Kona family of processors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 475)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 476) If you do not need KONA I2C interface, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 477)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 478) config I2C_BRCMSTB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 479) tristate "BRCM Settop/DSL I2C controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 480) depends on ARCH_BCM2835 || ARCH_BRCMSTB || BMIPS_GENERIC || \
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 481) ARCH_BCM_63XX || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 482) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 483) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 484) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 485) I2C interface on the Broadcom Settop/DSL SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 486)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 487) If you do not need I2C interface, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 488)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 489) config I2C_CADENCE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 490) tristate "Cadence I2C Controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 491) depends on ARCH_ZYNQ || ARM64 || XTENSA || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 492) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 493) Say yes here to select Cadence I2C Host Controller. This controller is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 494) e.g. used by Xilinx Zynq.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 495)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 496) config I2C_CBUS_GPIO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 497) tristate "CBUS I2C driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 498) depends on GPIOLIB || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 499) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 500) Support for CBUS access using I2C API. Mostly relevant for Nokia
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 501) Internet Tablets (770, N800 and N810).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 502)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 503) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 504) will be called i2c-cbus-gpio.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 505)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 506) config I2C_CPM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 507) tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 508) depends on CPM1 || CPM2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 509) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 510) This supports the use of the I2C interface on Freescale
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 511) processors with CPM1 or CPM2.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 512)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 513) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 514) will be called i2c-cpm.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 515)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 516) config I2C_DAVINCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 517) tristate "DaVinci I2C driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 518) depends on ARCH_DAVINCI || ARCH_KEYSTONE || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 519) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 520) Support for TI DaVinci I2C controller driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 521)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 522) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 523) will be called i2c-davinci.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 524)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 525) Please note that this driver might be needed to bring up other
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 526) devices such as DaVinci NIC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 527) For details please see http://www.ti.com/davinci
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 528)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 529) config I2C_DESIGNWARE_CORE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 530) tristate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 531) select REGMAP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 532)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 533) config I2C_DESIGNWARE_SLAVE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 534) bool "Synopsys DesignWare Slave"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 535) depends on I2C_DESIGNWARE_CORE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 536) select I2C_SLAVE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 537) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 538) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 539) Synopsys DesignWare I2C slave adapter.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 540)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 541) This is not a standalone module, this module compiles together with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 542) i2c-designware-core.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 543)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 544) config I2C_DESIGNWARE_PLATFORM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 545) tristate "Synopsys DesignWare Platform"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 546) depends on (ACPI && COMMON_CLK) || !ACPI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 547) select I2C_DESIGNWARE_CORE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 548) select MFD_SYSCON if MIPS_BAIKAL_T1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 549) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 550) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 551) Synopsys DesignWare I2C adapter.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 552)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 553) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 554) will be called i2c-designware-platform.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 555)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 556) config I2C_DESIGNWARE_BAYTRAIL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 557) bool "Intel Baytrail I2C semaphore support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 558) depends on ACPI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 559) depends on I2C_DESIGNWARE_PLATFORM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 560) depends on (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI) || \
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 561) (I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 562) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 563) This driver enables managed host access to the PMIC I2C bus on select
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 564) Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 565) the host to request uninterrupted access to the PMIC's I2C bus from
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 566) the platform firmware controlling it. You should say Y if running on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 567) a BayTrail system using the AXP288.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 568)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 569) config I2C_DESIGNWARE_PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 570) tristate "Synopsys DesignWare PCI"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 571) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 572) select I2C_DESIGNWARE_CORE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 573) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 574) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 575) Synopsys DesignWare I2C adapter. Only master mode is supported.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 576)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 577) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 578) will be called i2c-designware-pci.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 579)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 580) config I2C_DIGICOLOR
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 581) tristate "Conexant Digicolor I2C driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 582) depends on ARCH_DIGICOLOR || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 583) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 584) Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 585)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 586) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 587) will be called i2c-digicolor.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 588)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 589) config I2C_EFM32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 590) tristate "EFM32 I2C controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 591) depends on ARCH_EFM32 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 592) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 593) This driver supports the i2c block found in Energy Micro's EFM32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 594) SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 595)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 596) config I2C_EG20T
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 597) tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 598) depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 599) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 600) This driver is for PCH(Platform controller Hub) I2C of EG20T which
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 601) is an IOH(Input/Output Hub) for x86 embedded processor.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 602) This driver can access PCH I2C bus device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 603)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 604) This driver also can be used for LAPIS Semiconductor IOH(Input/
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 605) Output Hub), ML7213, ML7223 and ML7831.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 606) ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 607) for MP(Media Phone) use and ML7831 IOH is for general purpose use.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 608) ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 609) ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 610)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 611) config I2C_EMEV2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 612) tristate "EMMA Mobile series I2C adapter"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 613) depends on HAVE_CLK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 614) select I2C_SLAVE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 615) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 616) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 617) I2C interface on the Renesas Electronics EM/EV family of processors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 618)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 619) config I2C_EXYNOS5
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 620) tristate "Exynos high-speed I2C driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 621) depends on OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 622) depends on ARCH_EXYNOS || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 623) default y if ARCH_EXYNOS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 624) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 625) High-speed I2C controller on Exynos5 and newer Samsung SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 626)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 627) config I2C_GPIO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 628) tristate "GPIO-based bitbanging I2C"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 629) depends on GPIOLIB || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 630) select I2C_ALGOBIT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 631) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 632) This is a very simple bitbanging I2C driver utilizing the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 633) arch-neutral GPIO API to control the SCL and SDA lines.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 634)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 635) config I2C_GPIO_FAULT_INJECTOR
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 636) bool "GPIO-based fault injector"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 637) depends on I2C_GPIO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 638) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 639) This adds some functionality to the i2c-gpio driver which can inject
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 640) faults to an I2C bus, so another bus master can be stress-tested.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 641) This is for debugging. If unsure, say 'no'.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 642)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 643) config I2C_HIGHLANDER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 644) tristate "Highlander FPGA SMBus interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 645) depends on SH_HIGHLANDER || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 646) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 647) If you say yes to this option, support will be included for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 648) the SMBus interface located in the FPGA on various Highlander
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 649) boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 650) FPGAs. This is wholly unrelated to the SoC I2C.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 651)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 652) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 653) will be called i2c-highlander.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 654)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 655) config I2C_IBM_IIC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 656) tristate "IBM PPC 4xx on-chip I2C interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 657) depends on 4xx
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 658) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 659) Say Y here if you want to use IIC peripheral found on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 660) embedded IBM PPC 4xx based systems.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 661)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 662) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 663) will be called i2c-ibm_iic.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 664)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 665) config I2C_IMG
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 666) tristate "Imagination Technologies I2C SCB Controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 667) depends on MIPS || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 668) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 669) Say Y here if you want to use the IMG I2C SCB controller,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 670) available on the TZ1090 and other IMG SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 671)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 672) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 673) will be called i2c-img-scb.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 674)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 675) config I2C_IMX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 676) tristate "IMX I2C interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 677) depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 678) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 679) Say Y here if you want to use the IIC bus controller on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 680) the Freescale i.MX/MXC, Layerscape or ColdFire processors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 681)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 682) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 683) will be called i2c-imx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 684)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 685) config I2C_IMX_LPI2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 686) tristate "IMX Low Power I2C interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 687) depends on ARCH_MXC || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 688) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 689) Say Y here if you want to use the Low Power IIC bus controller
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 690) on the Freescale i.MX processors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 691)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 692) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 693) will be called i2c-imx-lpi2c.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 694)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 695) config I2C_IOP3XX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 696) tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 697) depends on ARCH_IOP32X || ARCH_IXP4XX || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 698) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 699) Say Y here if you want to use the IIC bus controller on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 700) the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 701)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 702) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 703) will be called i2c-iop3xx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 704)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 705) config I2C_JZ4780
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 706) tristate "JZ4780 I2C controller interface support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 707) depends on MIPS || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 708) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 709) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 710) Ingenic JZ4780 I2C controller.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 711)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 712) If you don't know what to do here, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 713)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 714) config I2C_KEMPLD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 715) tristate "Kontron COM I2C Controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 716) depends on MFD_KEMPLD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 717) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 718) This enables support for the I2C bus interface on some Kontron ETX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 719) and COMexpress (ETXexpress) modules.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 720)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 721) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 722) will be called i2c-kempld.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 723)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 724) config I2C_LPC2K
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 725) tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 726) depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 727) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 728) This driver supports the I2C interface found several NXP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 729) devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 730)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 731) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 732) will be called i2c-lpc2k.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 733)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 734) config I2C_MLXBF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 735) tristate "Mellanox BlueField I2C controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 736) depends on MELLANOX_PLATFORM && ARM64
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 737) select I2C_SLAVE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 738) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 739) Enabling this option will add I2C SMBus support for Mellanox BlueField
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 740) system.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 741)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 742) This driver can also be built as a module. If so, the module will be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 743) called i2c-mlxbf.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 744)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 745) This driver implements an I2C SMBus host controller and enables both
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 746) master and slave functions.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 747)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 748) config I2C_MESON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 749) tristate "Amlogic Meson I2C controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 750) depends on ARCH_MESON || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 751) depends on COMMON_CLK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 752) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 753) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 754) I2C interface on the Amlogic Meson family of SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 755)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 756) config I2C_MPC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 757) tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 758) depends on PPC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 759) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 760) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 761) built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 762) MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 763)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 764) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 765) will be called i2c-mpc.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 766)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 767) config I2C_MT65XX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 768) tristate "MediaTek I2C adapter"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 769) depends on ARCH_MEDIATEK || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 770) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 771) This selects the MediaTek(R) Integrated Inter Circuit bus driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 772) for MT65xx and MT81xx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 773) If you want to use MediaTek(R) I2C interface, say Y or M here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 774) If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 775)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 776) config I2C_MT7621
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 777) tristate "MT7621/MT7628 I2C Controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 778) depends on (RALINK && (SOC_MT7620 || SOC_MT7621)) || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 779) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 780) Say Y here to include support for I2C controller in the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 781) MediaTek MT7621/MT7628 SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 782)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 783) config I2C_MV64XXX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 784) tristate "Marvell mv64xxx I2C Controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 785) depends on MV64X60 || PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 786) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 787) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 788) built-in I2C interface on the Marvell 64xxx line of host bridges.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 789) This driver is also used for Allwinner SoCs I2C controllers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 790)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 791) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 792) will be called i2c-mv64xxx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 793)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 794) config I2C_MXS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 795) tristate "Freescale i.MX28 I2C interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 796) depends on SOC_IMX28 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 797) select STMP_DEVICE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 798) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 799) Say Y here if you want to use the I2C bus controller on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 800) the Freescale i.MX28 processors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 801)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 802) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 803) will be called i2c-mxs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 804)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 805) config I2C_NOMADIK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 806) tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 807) depends on ARM_AMBA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 808) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 809) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 810) I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 811) as well as the STA2X11 PCIe I/O HUB.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 812)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 813) config I2C_NPCM7XX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 814) tristate "Nuvoton I2C Controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 815) depends on ARCH_NPCM7XX || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 816) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 817) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 818) Nuvoton I2C controller, which is available on the NPCM7xx BMC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 819) controller.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 820) Driver can also support slave mode (select I2C_SLAVE).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 821)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 822) config I2C_OCORES
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 823) tristate "OpenCores I2C Controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 824) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 825) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 826) OpenCores I2C controller. For details see
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 827) http://www.opencores.org/projects.cgi/web/i2c/overview
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 828)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 829) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 830) will be called i2c-ocores.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 831)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 832) config I2C_OMAP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 833) tristate "OMAP I2C adapter"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 834) depends on ARCH_OMAP || ARCH_K3 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 835) default y if MACH_OMAP_H3 || MACH_OMAP_OSK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 836) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 837) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 838) I2C interface on the Texas Instruments OMAP1/2 family of processors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 839) Like OMAP1510/1610/1710/5912 and OMAP242x.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 840) For details see http://www.ti.com/omap.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 841)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 842) config I2C_OWL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 843) tristate "Actions Semiconductor Owl I2C Controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 844) depends on ARCH_ACTIONS || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 845) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 846) Say Y here if you want to use the I2C bus controller on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 847) the Actions Semiconductor Owl SoC's.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 848)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 849) config I2C_PASEMI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 850) tristate "PA Semi SMBus interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 851) depends on PPC_PASEMI && PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 852) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 853) Supports the PA Semi PWRficient on-chip SMBus interfaces.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 854)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 855) config I2C_PCA_PLATFORM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 856) tristate "PCA9564/PCA9665 as platform device"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 857) select I2C_ALGOPCA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 858) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 859) This driver supports a memory mapped Philips PCA9564/PCA9665
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 860) parallel bus to I2C bus controller.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 861)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 862) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 863) will be called i2c-pca-platform.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 864)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 865) config I2C_PMCMSP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 866) tristate "PMC MSP I2C TWI Controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 867) depends on PMC_MSP || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 868) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 869) This driver supports the PMC TWI controller on MSP devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 870)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 871) This driver can also be built as module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 872) will be called i2c-pmcmsp.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 873)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 874) config I2C_PNX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 875) tristate "I2C bus support for Philips PNX and NXP LPC targets"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 876) depends on ARCH_LPC32XX || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 877) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 878) This driver supports the Philips IP3204 I2C IP block master and/or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 879) slave controller
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 880)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 881) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 882) will be called i2c-pnx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 883)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 884) config I2C_PXA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 885) tristate "Intel PXA2XX I2C adapter"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 886) depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF) || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 887) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 888) If you have devices in the PXA I2C bus, say yes to this option.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 889) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 890) will be called i2c-pxa.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 891)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 892) config I2C_PXA_PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 893) def_bool I2C_PXA && X86_32 && PCI && OF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 894)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 895) config I2C_PXA_SLAVE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 896) bool "Intel PXA2XX I2C Slave comms support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 897) depends on I2C_PXA && !X86_32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 898) select I2C_SLAVE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 899) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 900) Support I2C slave mode communications on the PXA I2C bus. This
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 901) is necessary for systems where the PXA may be a target on the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 902) I2C bus.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 903)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 904) config I2C_QCOM_CCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 905) tristate "Qualcomm Camera Control Interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 906) depends on ARCH_QCOM || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 907) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 908) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 909) built-in camera control interface on the Qualcomm SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 910)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 911) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 912) will be called i2c-qcom-cci.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 913)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 914) config I2C_QCOM_GENI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 915) tristate "Qualcomm Technologies Inc.'s GENI based I2C controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 916) depends on ARCH_QCOM || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 917) depends on QCOM_GENI_SE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 918) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 919) This driver supports GENI serial engine based I2C controller in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 920) master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 921) yes to this option, support will be included for the built-in I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 922) interface on the Qualcomm Technologies Inc.'s SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 923)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 924) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 925) will be called i2c-qcom-geni.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 926)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 927) config I2C_QUP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 928) tristate "Qualcomm QUP based I2C controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 929) depends on ARCH_QCOM || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 930) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 931) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 932) built-in I2C interface on the Qualcomm SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 933)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 934) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 935) will be called i2c-qup.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 936)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 937) config I2C_RIIC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 938) tristate "Renesas RIIC adapter"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 939) depends on ARCH_RENESAS || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 940) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 941) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 942) Renesas RIIC I2C interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 943)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 944) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 945) will be called i2c-riic.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 946)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 947) config I2C_RK3X
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 948) tristate "Rockchip RK3xxx I2C adapter"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 949) depends on OF && COMMON_CLK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 950) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 951) Say Y here to include support for the I2C adapter in Rockchip RK3xxx
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 952) SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 953)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 954) This driver can also be built as a module. If so, the module will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 955) be called i2c-rk3x.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 956)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 957) config HAVE_S3C2410_I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 958) bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 959) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 960) This will include I2C support for Samsung SoCs. If you want to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 961) include I2C support for any machine, kindly select this in the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 962) respective Kconfig file.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 963)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 964) config I2C_S3C2410
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 965) tristate "S3C/Exynos I2C Driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 966) depends on HAVE_S3C2410_I2C || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 967) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 968) Say Y here to include support for I2C controller in the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 969) Samsung SoCs (S3C, S5Pv210, Exynos).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 970)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 971) config I2C_SH7760
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 972) tristate "Renesas SH7760 I2C Controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 973) depends on CPU_SUBTYPE_SH7760
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 974) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 975) This driver supports the 2 I2C interfaces on the Renesas SH7760.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 976)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 977) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 978) will be called i2c-sh7760.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 979)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 980) config I2C_SH_MOBILE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 981) tristate "SuperH Mobile I2C Controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 982) depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 983) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 984) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 985) built-in I2C interface on the Renesas SH-Mobile processor.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 986)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 987) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 988) will be called i2c-sh_mobile.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 989)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 990) config I2C_SIMTEC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 991) tristate "Simtec Generic I2C interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 992) select I2C_ALGOBIT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 993) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 994) If you say yes to this option, support will be included for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 995) the Simtec Generic I2C interface. This driver is for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 996) simple I2C bus used on newer Simtec products for general
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 997) I2C, such as DDC on the Simtec BBD2016A.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 998)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 999) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1000) will be called i2c-simtec.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1001)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1002) config I2C_SIRF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1003) tristate "CSR SiRFprimaII I2C interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1004) depends on ARCH_SIRF || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1005) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1006) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1007) CSR SiRFprimaII I2C interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1008)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1009) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1010) will be called i2c-sirf.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1011)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1012) config I2C_SPRD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1013) tristate "Spreadtrum I2C interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1014) depends on I2C=y && (ARCH_SPRD || COMPILE_TEST)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1015) depends on COMMON_CLK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1016) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1017) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1018) Spreadtrum I2C interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1019)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1020) config I2C_ST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1021) tristate "STMicroelectronics SSC I2C support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1022) depends on ARCH_STI || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1023) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1024) Enable this option to add support for STMicroelectronics SoCs
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1025) hardware SSC (Synchronous Serial Controller) as an I2C controller.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1026)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1027) This driver can also be built as module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1028) will be called i2c-st.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1029)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1030) config I2C_STM32F4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1031) tristate "STMicroelectronics STM32F4 I2C support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1032) depends on ARCH_STM32 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1033) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1034) Enable this option to add support for STM32 I2C controller embedded
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1035) in STM32F4 SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1036)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1037) This driver can also be built as module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1038) will be called i2c-stm32f4.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1039)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1040) config I2C_STM32F7
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1041) tristate "STMicroelectronics STM32F7 I2C support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1042) depends on ARCH_STM32 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1043) select I2C_SLAVE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1044) select I2C_SMBUS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1045) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1046) Enable this option to add support for STM32 I2C controller embedded
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1047) in STM32F7 SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1048)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1049) This driver can also be built as module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1050) will be called i2c-stm32f7.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1051)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1052) config I2C_STU300
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1053) tristate "ST Microelectronics DDC I2C interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1054) depends on MACH_U300 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1055) default y if MACH_U300
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1056) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1057) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1058) I2C interface from ST Microelectronics simply called "DDC I2C"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1059) supporting both I2C and DDC, used in e.g. the U300 series
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1060) mobile platforms.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1061)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1062) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1063) will be called i2c-stu300.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1064)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1065) config I2C_SUN6I_P2WI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1066) tristate "Allwinner sun6i internal P2WI controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1067) depends on RESET_CONTROLLER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1068) depends on MACH_SUN6I || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1069) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1070) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1071) P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1072) SOCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1073) The P2WI looks like an SMBus controller (which supports only byte
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1074) accesses), except that it only supports one slave device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1075) This interface is used to connect to specific PMIC devices (like the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1076) AXP221).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1077)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1078) config I2C_SYNQUACER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1079) tristate "Socionext SynQuacer I2C controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1080) depends on ARCH_SYNQUACER || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1081) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1082) Say Y here to include support for the I2C controller used in some
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1083) Fujitsu and Socionext SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1084)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1085) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1086) will be called i2c-synquacer.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1087)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1088) config I2C_TEGRA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1089) tristate "NVIDIA Tegra internal I2C controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1090) depends on ARCH_TEGRA || (COMPILE_TEST && (ARC || ARM || ARM64 || M68K || RISCV || SUPERH || SPARC))
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1091) # COMPILE_TEST needs architectures with readsX()/writesX() primitives
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1092) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1093) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1094) I2C controller embedded in NVIDIA Tegra SOCs
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1095)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1096) config I2C_TEGRA_BPMP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1097) tristate "NVIDIA Tegra BPMP I2C controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1098) depends on TEGRA_BPMP || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1099) default y if TEGRA_BPMP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1100) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1101) If you say yes to this option, support will be included for the I2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1102) controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1103)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1104) This I2C driver is a 'virtual' I2C driver. The real driver is part
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1105) of the BPMP firmware, and this driver merely communicates with that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1106) real driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1107)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1108) config I2C_UNIPHIER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1109) tristate "UniPhier FIFO-less I2C controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1110) depends on ARCH_UNIPHIER || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1111) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1112) If you say yes to this option, support will be included for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1113) the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1114) or older UniPhier SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1115)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1116) config I2C_UNIPHIER_F
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1117) tristate "UniPhier FIFO-builtin I2C controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1118) depends on ARCH_UNIPHIER || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1119) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1120) If you say yes to this option, support will be included for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1121) the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1122) PH1-Pro5, or newer UniPhier SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1123)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1124) config I2C_VERSATILE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1125) tristate "ARM Versatile/Realview I2C bus support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1126) depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1127) select I2C_ALGOBIT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1128) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1129) Say yes if you want to support the I2C serial bus on ARMs Versatile
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1130) range of platforms.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1131)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1132) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1133) will be called i2c-versatile.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1134)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1135) config I2C_WMT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1136) tristate "Wondermedia WM8xxx SoC I2C bus support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1137) depends on ARCH_VT8500 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1138) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1139) Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1140) SoCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1141)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1142) This driver can also be built as a module. If so, the module will be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1143) called i2c-wmt.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1144)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1145) config I2C_OCTEON
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1146) tristate "Cavium OCTEON I2C bus support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1147) depends on CAVIUM_OCTEON_SOC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1148) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1149) Say yes if you want to support the I2C serial bus on Cavium
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1150) OCTEON SOC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1151)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1152) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1153) will be called i2c-octeon.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1154)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1155) config I2C_THUNDERX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1156) tristate "Cavium ThunderX I2C bus support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1157) depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1158) select I2C_SMBUS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1159) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1160) Say yes if you want to support the I2C serial bus on Cavium
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1161) ThunderX SOC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1162)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1163) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1164) will be called i2c-thunderx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1165)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1166) config I2C_XILINX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1167) tristate "Xilinx I2C Controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1168) depends on HAS_IOMEM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1169) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1170) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1171) Xilinx I2C controller.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1172)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1173) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1174) will be called xilinx_i2c.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1175)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1176) config I2C_XLR
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1177) tristate "Netlogic XLR and Sigma Designs I2C support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1178) depends on CPU_XLR || ARCH_TANGO || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1179) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1180) This driver enables support for the on-chip I2C interface of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1181) the Netlogic XLR/XLS MIPS processors and Sigma Designs SOCs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1182)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1183) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1184) will be called i2c-xlr.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1185)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1186) config I2C_XLP9XX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1187) tristate "XLP9XX I2C support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1188) depends on CPU_XLP || ARCH_THUNDER2 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1189) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1190) This driver enables support for the on-chip I2C interface of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1191) the Broadcom XLP9xx/XLP5xx MIPS and Vulcan ARM64 processors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1192)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1193) This driver can also be built as a module. If so, the module will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1194) be called i2c-xlp9xx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1195)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1196) config I2C_RCAR
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1197) tristate "Renesas R-Car I2C Controller"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1198) depends on ARCH_RENESAS || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1199) select I2C_SLAVE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1200) select I2C_SMBUS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1201) select RESET_CONTROLLER if ARCH_RCAR_GEN3
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1202) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1203) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1204) R-Car I2C controller.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1205)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1206) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1207) will be called i2c-rcar.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1208)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1209) comment "External I2C/SMBus adapter drivers"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1210)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1211) config I2C_DIOLAN_U2C
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1212) tristate "Diolan U2C-12 USB adapter"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1213) depends on USB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1214) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1215) If you say yes to this option, support will be included for Diolan
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1216) U2C-12, a USB to I2C interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1217)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1218) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1219) will be called i2c-diolan-u2c.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1220)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1221) config I2C_DLN2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1222) tristate "Diolan DLN-2 USB I2C adapter"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1223) depends on MFD_DLN2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1224) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1225) If you say yes to this option, support will be included for Diolan
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1226) DLN2, a USB to I2C interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1227)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1228) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1229) will be called i2c-dln2.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1230)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1231) config I2C_PARPORT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1232) tristate "Parallel port adapter"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1233) depends on PARPORT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1234) select I2C_ALGOBIT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1235) select I2C_SMBUS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1236) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1237) This supports parallel port I2C adapters such as the ones made by
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1238) Philips or Velleman, Analog Devices evaluation boards, and more.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1239) Basically any adapter using the parallel port as an I2C bus with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1240) no extra chipset is supported by this driver, or could be. Please
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1241) read the file Documentation/i2c/busses/i2c-parport.rst for details.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1242)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1243) This support is also available as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1244) will be called i2c-parport.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1245)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1246) config I2C_ROBOTFUZZ_OSIF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1247) tristate "RobotFuzz Open Source InterFace USB adapter"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1248) depends on USB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1249) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1250) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1251) RobotFuzz Open Source InterFace USB to I2C interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1252)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1253) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1254) will be called i2c-osif.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1255)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1256) config I2C_TAOS_EVM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1257) tristate "TAOS evaluation module"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1258) depends on TTY
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1259) select SERIO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1260) select SERIO_SERPORT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1261) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1262) This supports TAOS evaluation modules on serial port. In order to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1263) use this driver, you will need the inputattach tool, which is part
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1264) of the input-utils package.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1265)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1266) If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1267)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1268) This support is also available as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1269) will be called i2c-taos-evm.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1270)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1271) config I2C_TINY_USB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1272) tristate "Tiny-USB adapter"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1273) depends on USB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1274) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1275) If you say yes to this option, support will be included for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1276) i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1277) http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1278)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1279) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1280) will be called i2c-tiny-usb.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1281)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1282) config I2C_VIPERBOARD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1283) tristate "Viperboard I2C master support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1284) depends on MFD_VIPERBOARD && USB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1285) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1286) Say yes here to access the I2C part of the Nano River
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1287) Technologies Viperboard as I2C master.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1288) See viperboard API specification and Nano
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1289) River Tech's viperboard.h for detailed meaning
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1290) of the module parameters.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1291)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1292) comment "Other I2C/SMBus bus drivers"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1293)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1294) config I2C_ACORN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1295) tristate "Acorn IOC/IOMD I2C bus support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1296) depends on ARCH_ACORN
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1297) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1298) select I2C_ALGOBIT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1299) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1300) Say yes if you want to support the I2C bus on Acorn platforms.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1301)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1302) If you don't know, say Y.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1303)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1304) config I2C_ELEKTOR
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1305) tristate "Elektor ISA card"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1306) depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1307) select I2C_ALGOPCF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1308) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1309) This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1310) such an adapter.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1311)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1312) This support is also available as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1313) will be called i2c-elektor.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1314)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1315) config I2C_ICY
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1316) tristate "ICY Zorro card"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1317) depends on ZORRO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1318) select I2C_ALGOPCF
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1319) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1320) This supports the PCF8584 Zorro bus I2C adapter, known as ICY.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1321) Say Y if you own such an adapter.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1322)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1323) This support is also available as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1324) will be called i2c-icy.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1325)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1326) If you have a 2019 edition board with an LTC2990 sensor at address
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1327) 0x4c, loading the module 'ltc2990' is sufficient to enable it.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1328)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1329) config I2C_MLXCPLD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1330) tristate "Mellanox I2C driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1331) depends on X86_64 || COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1332) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1333) This exposes the Mellanox platform I2C busses to the linux I2C layer
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1334) for X86 based systems.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1335) Controller is implemented as CPLD logic.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1336)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1337) This driver can also be built as a module. If so, the module will be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1338) called as i2c-mlxcpld.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1339)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1340) config I2C_PCA_ISA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1341) tristate "PCA9564/PCA9665 on an ISA bus"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1342) depends on ISA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1343) select I2C_ALGOPCA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1344) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1345) This driver supports ISA boards using the Philips PCA9564/PCA9665
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1346) parallel bus to I2C bus controller.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1347)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1348) This driver can also be built as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1349) will be called i2c-pca-isa.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1350)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1351) This device is almost undetectable and using this driver on a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1352) system which doesn't have this device will result in long
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1353) delays when I2C/SMBus chip drivers are loaded (e.g. at boot
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1354) time). If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1355)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1356) config I2C_SIBYTE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1357) tristate "SiByte SMBus interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1358) depends on SIBYTE_SB1xxx_SOC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1359) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1360) Supports the SiByte SOC on-chip I2C interfaces (2 channels).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1361)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1362) config I2C_CROS_EC_TUNNEL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1363) tristate "ChromeOS EC tunnel I2C bus"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1364) depends on CROS_EC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1365) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1366) If you say yes here you get an I2C bus that will tunnel i2c commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1367) through to the other side of the ChromeOS EC to the i2c bus
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1368) connected there. This will work whatever the interface used to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1369) talk to the EC (SPI, I2C or LPC).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1370)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1371) config I2C_XGENE_SLIMPRO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1372) tristate "APM X-Gene SoC I2C SLIMpro devices support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1373) depends on ARCH_XGENE && MAILBOX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1374) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1375) Enable I2C bus access using the APM X-Gene SoC SLIMpro
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1376) co-processor. The I2C device access the I2C bus via the X-Gene
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1377) to SLIMpro (On chip coprocessor) mailbox mechanism.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1378) If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1379)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1380) config SCx200_ACB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1381) tristate "Geode ACCESS.bus support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1382) depends on X86_32 && PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1383) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1384) Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1385) SC1100 processors and the CS5535 and CS5536 Geode companion devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1386)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1387) If you don't know what to do here, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1388)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1389) This support is also available as a module. If so, the module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1390) will be called scx200_acb.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1391)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1392) config I2C_OPAL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1393) tristate "IBM OPAL I2C driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1394) depends on PPC_POWERNV
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1395) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1396) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1397) This exposes the PowerNV platform i2c busses to the linux i2c layer,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1398) the driver is based on the OPAL interfaces.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1399)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1400) This driver can also be built as a module. If so, the module will be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1401) called as i2c-opal.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1402)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1403) config I2C_ZX2967
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1404) tristate "ZTE ZX2967 I2C support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1405) depends on ARCH_ZX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1406) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1407) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1408) Selecting this option will add ZX2967 I2C driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1409) This driver can also be built as a module. If so, the module will be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1410) called i2c-zx2967.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1411)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1412) config I2C_FSI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1413) tristate "FSI I2C driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1414) depends on FSI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1415) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1416) Driver for FSI bus attached I2C masters. These are I2C masters that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1417) are connected to the system over an FSI bus, instead of the more
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1418) common PCI or MMIO interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1419)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1420) This driver can also be built as a module. If so, the module will be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1421) called as i2c-fsi.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1422)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1423) endmenu
Orange Pi5 kernel
Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards
3 Commits
0 Branches
0 Tags