Home
last modified time | relevance | path

Searched refs:I2C (Results 1 – 200 of 641) sorted by relevance

1234

/linux-4.1.27/sound/soc/codecs/
DKconfig1 # Helper to resolve issues with configs that have SPI enabled but I2C
2 # modular, meaning we can't build the codec driver in with I2C support.
7 default m if I2C=m
8 default y if I2C=y
22 select SND_SOC_AD193X_I2C if I2C
25 select SND_SOC_ADAU1373 if I2C
26 select SND_SOC_ADAU1761_I2C if I2C
28 select SND_SOC_ADAU1781_I2C if I2C
31 select SND_SOC_ADAV803 if I2C
33 select SND_SOC_ADAU1977_I2C if I2C
[all …]
/linux-4.1.27/drivers/i2c/
DKconfig2 # I2C subsystem configuration
5 menu "I2C support"
7 config I2C config
8 tristate "I2C support"
11 I2C (pronounce: I-squared-C) is a slow serial bus protocol used in
13 or System Management Bus is a subset of the I2C protocol. More
17 Both I2C and SMBus are supported here. You will need this for
20 If you want I2C support, you should say Y here and also to the
23 This I2C support can also be built as a module. If so, the module
27 bool "ACPI I2C Operation region support"
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Dnvidia,tegra20-i2c.txt1 NVIDIA Tegra20/Tegra30/Tegra114 I2C controller driver.
10 nvidia,tegra20-i2c-dvc: Tegra20 has specific I2C controller called as DVC I2C
11 controller. This only support master mode of I2C communication. Register
12 interface/offset and interrupts handling are different than generic I2C
13 controller. Driver of DVC I2C controller is only compatible with
15 nvidia,tegra20-i2c: Tegra20 has 4 generic I2C controller. This can support
16 master and slave mode of I2C communication. The i2c-tegra driver only
17 support master mode of I2C communication. Driver of I2C controller is
19 nvidia,tegra30-i2c: Tegra30 has 5 generic I2C controller. This controller is
20 very much similar to Tegra20 I2C controller with additional feature:
[all …]
Di2c-imx.txt1 * Freescale Inter IC (I2C) and High Speed Inter IC (HS-I2C) for i.MX
5 - "fsl,imx1-i2c" for I2C compatible with the one integrated on i.MX1 SoC
6 - "fsl,imx21-i2c" for I2C compatible with the one integrated on i.MX21 SoC
7 - "fsl,vf610-i2c" for I2C compatible with the one integrated on Vybrid vf610 SoC
8 - reg : Should contain I2C/HS-I2C registers location and length
9 - interrupts : Should contain I2C/HS-I2C interrupt
10 - clocks : Should contain the I2C/HS-I2C clock specifier
13 - clock-frequency : Constains desired I2C/HS-I2C bus clock frequency in Hz.
26 i2c@70038000 { /* HS-I2C on i.MX51 */
Dtrivial-devices.txt12 abracon,abb5zes3 AB-RTCMC-32.768kHz-B5ZE-S3: Real Time Clock/Calendar Module with I2C Interface
13 ad,ad7414 SMBus/I2C Digital Temperature Sensor in 6-Pin SOT with SMBus Alert and Over Temperature …
41 dallas,ds1307 64 x 8, Serial, I2C Real-Time Clock
42 dallas,ds1338 I2C RTC with 56-Byte NV RAM
43 dallas,ds1340 I2C RTC with Trickle Charger
44 dallas,ds1374 I2C, 32-Bit Binary Counter Watchdog RTC with Trickle Charger and Reset Input/Output
53 epson,rx8025 High-Stability. I2C-Bus INTERFACE REAL TIME CLOCK MODULE
54 epson,rx8581 I2C-BUS INTERFACE REAL TIME CLOCK MODULE
62 infineon,slb9635tt Infineon SLB9635 (Soft-) I2C TPM (old protocol, max 100khz)
63 infineon,slb9645tt Infineon SLB9645 I2C TPM (new protocol, max 400khz)
[all …]
Dbrcm,iproc-i2c.txt1 Broadcom iProc I2C controller
10 I2C controller registers
13 Should contain the I2C interrupt
16 This is the I2C bus clock. Need to be either 100000 or 400000
19 Always 1 (for I2C addresses)
Di2c-mux-pinctrl.txt1 Pinctrl-based I2C Bus Mux
3 This binding describes an I2C bus multiplexer that uses pin multiplexing to
4 route the I2C signals, and represents the pin multiplexing configuration
13 | |I2C|---|Pinmux| |
23 - i2c-parent: The phandle of the I2C bus that this multiplexer's master-side
31 * Standard I2C mux properties. See mux.txt in this directory.
33 * I2C child bus nodes. See mux.txt in this directory.
35 For each named state defined in the pinctrl-names property, an I2C child bus
36 will be created. I2C child bus numbers are assigned based on the index into
Di2c-mux-gpio.txt1 GPIO-based I2C Bus Mux
3 This binding describes an I2C bus multiplexer that uses GPIOs to
4 route the I2C signals.
12 | | I2C |-|--| Mux |
22 - i2c-parent: The phandle of the I2C bus that this multiplexer's master-side
25 * Standard I2C mux properties. See mux.txt in this directory.
26 * I2C child bus nodes. See mux.txt in this directory.
32 For each i2c child node, an I2C child bus will be created. They will
Di2c-jz4780.txt1 * Ingenic JZ4780 I2C Bus controller
5 - reg: Should contain the address & size of the I2C controller registers.
7 - clocks: Should contain a single clock specifier for the JZ4780 I2C clock.
8 - clock-frequency: desired I2C bus clock frequency in Hz.
16 delivers interrupts to the I2C block.
Di2c-mux-pca954x.txt1 * NXP PCA954x I2C bus switch
9 - reg: The I2C address of the device.
13 - Standard I2C mux properties. See i2c-mux.txt in this directory.
14 - I2C child bus nodes. See i2c-mux.txt in this directory.
21 multiplexers on the bus and the devices behind them use same I2C addresses.
Di2c-octeon.txt1 * Two Wire Serial Interface (TWSI) / I2C
7 - reg: The base address of the TWSI/I2C bus controller register bank.
11 - #size-cells: Must be <0>. I2C addresses have no size component.
15 - clock-frequency: The I2C bus clock rate in Hz.
Di2c-rk3x.txt1 * Rockchip RK3xxx I2C controller
3 This driver interfaces with the native I2C controller present in Rockchip
18 - on those SoCs an alias with the correct I2C bus ID (bit offset in the GRF)
25 (t(r) in I2C specification). If not specified this is assumed to be
29 (t(f) in the I2C specification). If not specified this is assumed to
33 (t(f) in the I2C specification). If not specified we'll use the SCL
Di2c-pxa-pci-ce4100.txt1 CE4100 I2C
4 CE4100 has one PCI device which is described as the I2C-Controller. This
5 PCI device has three PCI-bars, each bar contains a complete I2C
6 controller. So we have a total of three independent I2C-Controllers
12 of the specific I2C controller. This were his exact words:
62 /* This I2C controller has no devices */
71 /* This I2C controller has one gpio controller */
Dbrcm,bcm2835-i2c.txt1 Broadcom BCM2835 I2C controller
7 - clocks : The clock feeding the I2C controller.
10 - clock-frequency : desired I2C bus clock frequency in Hz.
Di2c-sirf.txt1 I2C for SiRFprimaII platforms
10 - clock-frequency : Constains desired I2C/HS-I2C bus clock frequency in Hz.
Di2c-arb-gpio-challenge.txt1 GPIO-based I2C Arbitration Using a Challenge & Response Mechanism
4 the master of an I2C bus in a multimaster situation.
7 the standard I2C multi-master rules. Using GPIOs is generally useful in
12 * It is nonstandard (not using standard I2C multimaster)
47 - Standard I2C mux properties. See mux.txt in this directory.
48 - Single I2C child bus node at reg 0. See mux.txt in this directory.
83 // Normal I2C device
Di2c-vt8500.txt1 * Wondermedia I2C Controller
8 - clocks : phandle to the I2C clock source
12 - clock-frequency : desired I2C bus clock frequency in Hz.
Di2c-mxs.txt1 * Freescale MXS Inter IC (I2C) Controller
7 - clock-frequency: Desired I2C bus clock frequency in Hz.
10 and I2C DMA channel ID.
Dbrcm,kona-i2c.txt1 Broadcom Kona Family I2C
4 This I2C controller is used in the following Broadcom SoCs:
18 - clock-frequency: The I2C bus frequency in Hz
Di2c-davinci.txt1 * Texas Instruments Davinci I2C
12 - clock-frequency : desired I2C bus clock frequency in Hz.
14 registers. PFUNC registers allow to switch I2C pins to function as
Di2c-st.txt1 ST SSC binding, for I2C mode operation
11 operation for I2C transfer.
14 - clock-frequency : Desired I2C bus clock frequency in Hz. If not specified,
22 when I2C instance is not performing a transfer.
Di2c-cros-ec-tunnel.txt1 I2C bus that tunnels through the ChromeOS EC (cros-ec)
17 - One node per I2C device connected to the tunnelled I2C bus.
Di2c-exynos5.txt1 * Samsung's High Speed I2C controller
3 The Samsung's High Speed I2C controller is used to interface with I2C devices
Dti,bq32k.txt1 * TI BQ32000 I2C Serial Real-Time Clock
5 - reg: I2C address for chip
Di2c-meson.txt1 Amlogic Meson I2C controller
12 - clock-frequency: the desired I2C bus clock frequency in Hz; in
Di2c-digicolor.txt1 Conexant Digicolor I2C controller
12 - clock-frequency: the desired I2C bus clock frequency in Hz; in
Di2c-hix5hd2.txt1 I2C for Hisilicon hix5hd2 chipset platform
13 - clock-frequency: Desired I2C bus frequency in Hz, otherwise defaults to 100000
Di2c-mpc.txt1 * I2C
22 - clock-frequency : desired I2C bus clock frequency in Hz.
23 - fsl,timeout : I2C bus timeout in microseconds.
Di2c-at91.txt1 I2C for Atmel platforms
15 - clock-frequency: Desired I2C bus frequency in Hz, otherwise defaults to 100000
Di2c-img-scb.txt1 IMG Serial Control Bus (SCB) I2C Controller
11 - clock-frequency: The I2C bus frequency in Hz
Di2c-rcar.txt1 I2C for R-Car platforms
18 - clock-frequency: desired I2C bus clock frequency in Hz. The absence of this
Di2c-pnx.txt1 * NXP PNX I2C Controller
15 - clock-frequency: desired I2C bus clock frequency in Hz, Default: 100000 Hz
Di2c-axxia.txt1 LSI Axxia I2C
14 - clock-frequency : Desired I2C bus clock frequency in Hz. If not specified,
Di2c-omap.txt1 I2C for OMAP platforms
11 - clock-frequency : Desired I2C bus clock frequency in Hz. Otherwise
Di2c-sunxi-p2wi.txt22 - reg : the I2C slave address used during the initialization
23 process to switch from I2C to P2WI mode
Di2c-mv64xxx.txt2 * Marvell MV64XXX I2C controller
21 - clock-frequency : Desired I2C bus clock frequency in Hz. If not set the
Di2c-s3c2410.txt1 * Samsung's I2C controller
3 The Samsung's I2C controller is used to interface with I2C devices.
Dqcom,i2c-qup.txt1 Qualcomm Universal Peripheral (QUP) I2C controller
9 - interrupts: Should contain I2C interrupt.
/linux-4.1.27/Documentation/i2c/
Dsummary1 I2C and SMBus
4 I2C (pronounce: I squared C) is a protocol developed by Philips. It is a
8 I2C is widely used with embedded systems. Some systems use variants that
9 don't meet branding requirements, and so are not advertised as being I2C.
11 SMBus (System Management Bus) is based on the I2C protocol, and is mostly
12 a subset of I2C protocols and signaling. Many I2C devices will work on an
14 achieve I2C branding. Modern PC mainboards rely on SMBus. The most common
15 devices connected through SMBus are RAM modules configured using I2C EEPROMs,
18 Because the SMBus is mostly a subset of the generalized I2C bus, we can
19 use its protocols on many I2C systems. However, there are systems that don't
[all …]
Dinstantiating-devices1 How to instantiate I2C devices
4 Unlike PCI or USB devices, I2C devices are not enumerated at the hardware
6 I2C bus segment, and what address these devices are using. For this
7 reason, the kernel code must instantiate I2C devices explicitly. There are
11 Method 1a: Declare the I2C devices by bus number
14 This method is appropriate when the I2C bus is a system bus as is the case
15 for many embedded systems. On such systems, each I2C bus has a number
16 which is known in advance. It is thus possible to pre-declare the I2C
45 The above code declares 3 devices on I2C bus 1, including their respective
46 addresses and custom data needed by their drivers. When the I2C bus in
[all …]
Dslave-interface1 Linux I2C slave interface description
6 Linux can also be an I2C slave in case I2C controllers have slave support.
9 acts as a dual memory driver. While another I2C master on the bus can access it
10 like a regular EEPROM, the Linux I2C slave can access the content via sysfs and
11 retrieve/provide information as needed. The software backend driver and the I2C
18 e.g. sysfs I2C slave events I/O registers
23 ----------------------------------------------------------------+-- I2C
26 Note: Technically, there is also the I2C core between the backend and the
33 I2C slave backends behave like standard I2C clients. So, you can instantiate
46 I2C slave events
[all …]
Dfault-codes2 codes in the I2C/SMBus stack.
17 In short, your I2C driver code may need to know these codes in order
22 I2C and SMBus fault codes
39 Returned by I2C adapters when they lose arbitration in master
43 Also returned when trying to invoke an I2C operation in an
44 atomic context, when some task is already using that I2C bus
85 Returned by I2C adapters to indicate that the address phase
87 an I2C device was temporarily not responding, usually it
103 Similarly, if an I2C adapter can't execute all legal I2C
107 that if an adapter supports I2C it supports all of I2C.)
[all …]
Dwriting-clients1 This is a small guide for those who want to write kernel drivers for I2C
26 driver model device node, and its I2C address.
119 The Linux I2C stack was originally written to support access to hardware
121 that were more appropriate to SMBus (and PCs) than to I2C. One of these
126 As Linux and its I2C stack became more widely used in embedded systems
128 problematic. Drivers for I2C devices that issue interrupts need more (and
138 boot firmware, reports what I2C devices exist. For example, there may be
139 a table, in the kernel or from the boot loader, identifying I2C devices
142 create i2c_client objects for each I2C device.
144 I2C device drivers using this binding model work just like any other
[all …]
Dsmbus-protocol10 which is a subset from the I2C protocol. Fortunately, many devices use
13 If you write a driver for some I2C device, please try to use the SMBus
15 I2C protocol). This makes it possible to use the device driver on both
16 SMBus adapters and I2C adapters (the SMBus command set is automatically
17 translated to I2C on I2C adapters, but plain I2C commands can not be
28 the corresponding functionality flag to ensure that the underlying I2C
40 Addr (7 bits): I2C 7 bit address. Note that this can be expanded as usual to
41 get a 10 bit I2C address.
48 [..]: Data sent by I2C device, as opposed to data sent by the host adapter.
234 * I2C bus drivers which support SMBus alert should call
[all …]
Dfunctionality4 Because not every I2C or SMBus adapter implements everything in the
5 I2C specifications, a client can not trust that everything it needs
22 flags (which modify the I2C protocol!)
50 emulated by a real I2C adapter (using
74 A typical full-I2C adapter would use the following (from the i2c-pxa
83 addition of I2C block transactions) which i2c-core can emulate using
88 of an I2C adapter.
121 i2c-core will transparently implement SMBus transactions on top of I2C
Di2c-protocol10 Addr (7 bits): I2C 7 bit address. Note that this can be expanded as usual to
11 get a 10 bit I2C address.
18 [..]: Data sent by I2C device, as opposed to data sent by the host adapter.
52 The following modifications to the I2C protocol can also be generated by
76 I2C device but may also be used between direction changes by some
86 Force a stop condition (P) after the message. Some I2C related protocols
Ddev-interface11 I2C device files are character device files with major device number 89
49 int addr = 0x40; /* The I2C address */
57 I2C to communicate with your device. SMBus commands are preferred if
72 /* Using I2C Write, equivalent of
81 /* Using I2C Read, equivalent of i2c_smbus_read_byte(file) */
88 Note that only a subset of the I2C and SMBus protocols can be achieved by
176 when you use the /dev interface to I2C:
183 respectively. You can think of i2c-dev as a generic I2C chip driver
192 i2c-dev. Examples include I2C_FUNCS, which queries the I2C adapter
199 and calls that would have been performed by kernel I2C chip drivers
[all …]
Dten-bit-addresses1 The I2C protocol knows about two kinds of device addresses: normal 7 bit
6 I2C messages to and from 10-bit address devices have a different format.
7 See the I2C specification for the details.
Dslave-eeprom-backend1 Linux I2C slave eeprom backend
7 I2C bus. The memory contents can be modified from userspace via this file
Dold-module-parameters1 I2C device driver binding control from user-space
19 Attaching a driver to an I2C device
30 Preventing a driver from attaching to an I2C device
/linux-4.1.27/drivers/media/tuners/
DKconfig4 …A_ANALOG_TV_SUPPORT || MEDIA_DIGITAL_TV_SUPPORT || MEDIA_RADIO_SUPPORT || MEDIA_SDR_SUPPORT) && I2C
23 depends on MEDIA_SUPPORT && I2C
31 depends on MEDIA_SUPPORT && I2C
40 depends on MEDIA_SUPPORT && I2C
47 depends on MEDIA_SUPPORT && I2C
54 depends on MEDIA_SUPPORT && I2C
62 depends on MEDIA_SUPPORT && I2C
69 depends on MEDIA_SUPPORT && I2C
83 depends on MEDIA_SUPPORT && I2C
90 depends on MEDIA_SUPPORT && I2C
[all …]
/linux-4.1.27/drivers/media/dvb-frontends/
DKconfig9 depends on DVB_CORE && I2C
17 depends on DVB_CORE && I2C
25 depends on DVB_CORE && I2C
33 depends on DVB_CORE && I2C
40 depends on DVB_CORE && I2C && I2C_MUX
50 depends on DVB_CORE && I2C
59 depends on DVB_CORE && I2C
68 depends on DVB_CORE && I2C
80 depends on DVB_CORE && I2C
87 depends on DVB_CORE && I2C
[all …]
/linux-4.1.27/drivers/media/i2c/soc_camera/
DKconfig5 depends on SOC_CAMERA && I2C
11 depends on SOC_CAMERA && I2C
18 depends on SOC_CAMERA && I2C
25 depends on SOC_CAMERA && I2C
31 depends on SOC_CAMERA && I2C
37 depends on SOC_CAMERA && I2C
43 depends on SOC_CAMERA && I2C
49 depends on SOC_CAMERA && I2C
55 depends on SOC_CAMERA && I2C
61 depends on SOC_CAMERA && I2C
[all …]
/linux-4.1.27/drivers/i2c/busses/
DKconfig5 menu "I2C Hardware Bus support"
40 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
50 756/766/768 mainboard I2C interfaces. The driver also includes
51 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
52 the nVidia nForce I2C interface.
75 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
81 tristate "Hix5hd2 high-speed I2C driver"
84 Say Y here to include support for high-speed I2C controller in the
96 801 family of mainboard I2C interfaces. Specifically, the following
157 PIIX4 family of mainboard I2C interfaces. Specifically, the following
[all …]
/linux-4.1.27/drivers/i2c/muxes/
DKconfig2 # Multiplexer I2C chip drivers configuration
5 menu "Multiplexer I2C Chip support"
9 tristate "GPIO-based I2C arbitration"
13 I2C multimaster arbitration scheme using GPIOs and a challenge &
21 tristate "GPIO-based I2C multiplexer"
25 GPIO based I2C multiplexer. This driver provides access to
26 I2C busses connected through a MUX, which is controlled
33 tristate "NXP PCA9541 I2C Master Selector"
36 I2C Master Selector.
42 tristate "Philips PCA954x I2C Mux/switches"
[all …]
/linux-4.1.27/drivers/media/i2c/
DKconfig8 tristate "I2C module for IR" if !MEDIA_SUBDRV_AUTOSELECT
9 depends on I2C && RC_CORE
13 some video boards have the IR connected via I2C bus.
15 If your board doesn't have an I2C IR chip, you may disable this
31 depends on VIDEO_V4L2 && I2C
43 depends on VIDEO_V4L2 && I2C
52 depends on I2C
61 depends on I2C
70 depends on I2C
79 depends on VIDEO_V4L2 && I2C
[all …]
/linux-4.1.27/drivers/i2c/algos/
DKconfig2 # I2C algorithm drivers configuration
5 menu "I2C Algorithms"
9 tristate "I2C bit-banging interfaces"
12 tristate "I2C PCF 8584 interfaces"
15 tristate "I2C PCA 9564 interfaces"
/linux-4.1.27/Documentation/i2c/busses/
Di2c-diolan-u2c4 * Diolan U2C-12 I2C-USB adapter
13 This is the driver for the Diolan U2C-12 USB-I2C adapter.
15 The Diolan U2C-12 I2C-USB Adapter provides a low cost solution to connect
16 a computer to I2C slave devices using a USB interface. It also supports
19 This driver only supports the I2C interface of U2C-12. The driver does not use
26 * frequency: I2C bus frequency
Di2c-pca-isa5 Parallel bus to I2C bus controller
23 Parallel bus to I2C bus controller
/linux-4.1.27/drivers/iio/pressure/
DKconfig10 depends on I2C
35 depends on I2C
38 pressure sensor connected via I2C.
45 depends on I2C
65 tristate "support I2C bus connection"
66 depends on I2C && MS5611
68 Say Y here to build I2C bus support for MS5611.
84 depends on (I2C || SPI_MASTER) && SYSFS
86 select IIO_ST_PRESS_I2C if (I2C)
96 - st_pressure_i2c (necessary for the I2C devices [optional*]);
[all …]
/linux-4.1.27/drivers/hid/i2c-hid/
DKconfig1 menu "I2C HID support"
2 depends on I2C
5 tristate "HID over I2C transport layer"
7 depends on I2C && INPUT
11 other HID based devices which is connected to your computer via I2C.
/linux-4.1.27/sound/soc/samsung/
DKconfig48 depends on SND_SOC_SAMSUNG && MACH_JIVE && I2C
57 depends on I2C
66 depends on I2C=y
107 depends on SND_SOC_SAMSUNG && ARCH_S3C24XX && I2C
114 depends on SND_SOC_SAMSUNG && ARCH_S3C24XX && I2C
121 depends on SND_SOC_SAMSUNG && ARCH_H1940 && I2C
129 depends on SND_SOC_SAMSUNG && MACH_RX1950 && I2C
145 depends on SND_SOC_SAMSUNG && MACH_SMARTQ && I2C
159 depends on I2C
168 depends on I2C=y
[all …]
/linux-4.1.27/Documentation/hwmon/
Dina2xx7 Addresses: I2C 0x40 - 0x4f
13 Addresses: I2C 0x40 - 0x4f
19 Addresses: I2C 0x40 - 0x4f
25 Addresses: I2C 0x40 - 0x4f
31 Addresses: I2C 0x40 - 0x4f
40 The INA219 is a high-side current shunt and power monitor with an I2C
44 The INA220 is a high or low side current shunt and power monitor with an I2C
47 The INA226 is a current shunt and power monitor with an I2C interface.
51 with an I2C interface. The chips monitor both a shunt voltage drop and
Dlm907 Addresses scanned: I2C 0x4c
12 Addresses scanned: I2C 0x4c and 0x4d
17 Addresses scanned: I2C 0x4c and 0x4d
22 Addresses scanned: I2C 0x4c
27 Addresses scanned: I2C 0x4c and 0x4d
32 Addresses scanned: I2C 0x4c and 0x4d
37 Addresses scanned: I2C 0x4c and 0x4d
42 Addresses scanned: I2C 0x4c and 0x4d
47 Addresses scanned: I2C 0x4d
52 Addresses scanned: I2C 0x4e
[all …]
Dtmp4217 Addresses scanned: I2C 0x2a, 0x4c, 0x4d, 0x4e and 0x4f
11 Addresses scanned: I2C 0x4c, 0x4d, 0x4e and 0x4f
15 Addresses scanned: I2C 0x4c and 0x4d
19 Addresses scanned: I2C 0x2a, 0x4c, 0x4d, 0x4e and 0x4f
23 Addresses scanned: I2C 0x4c and 0x4d
36 in degrees Celsius. The chips are wired over I2C/SMBus and specified
Dadm10217 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
11 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
15 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
19 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
23 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
27 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
31 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
35 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
39 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
43 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
Dtmp4017 Addresses scanned: I2C 0x4c
11 Addresses scanned: I2C 0x4c, 0x4d, 0x4e
15 Addresses scanned: I2C 0x4c, 0x4d
19 Addresses scanned: I2C 0x4c, 0x4d
23 Addresses scanned: I2C 0x48 - 0x4f
Dshtc126 The device communicates with the I2C protocol. All sensors are set to I2C
31 1. blocking (pull the I2C clock line down while performing the measurement) or
33 the I2C bus will be busy during that time. By default, non-blocking mode
Dhih613021 The devices communicate with the I2C protocol. All sensors are set to the same
22 I2C address 0x27 by default, so an entry with I2C_BOARD_INFO("hih6130", 0x27)
26 instantiate I2C devices.
Dmcp302126 Communication to the MCP3021/MCP3221 is performed using a 2-wire I2C
27 compatible interface. Standard (100 kHz) and Fast (400 kHz) I2C modes are
28 available. The default I2C device address is 0x4d (contact the Microchip
Demc14036 Addresses scanned: I2C 0x18, 0x1c, 0x29, 0x4c, 0x4d, 0x5c
12 Addresses scanned: I2C 0x18, 0x29, 0x4c, 0x4d
18 Addresses scanned: I2C 0x4c
23 Addresses scanned: I2C 0x4c
Dlineage-pem34 on I2C bus #1:
38 All Lineage CPL power entry modules have a built-in I2C bus master selector
40 driver to the pca9541 I2C master selector driver.
Dadm10317 Addresses scanned: I2C 0x2c to 0x2e
13 Addresses scanned: I2C 0x2c to 0x2e
Dltc415117 The LTC4151 is a High Voltage I2C Current and Voltage Monitor.
28 on I2C bus #0:
/linux-4.1.27/drivers/mfd/
DKconfig26 depends on I2C=y
35 depends on I2C=y && OF
44 depends on I2C=y
48 the I2C driver and the core APIs _only_, you have to select
55 depends on I2C=y && GPIOLIB
77 depends on I2C
86 depends on I2C=y
104 tristate "ChromeOS Embedded Controller (I2C)"
105 depends on MFD_CROS_EC && I2C
109 EC through an I2C bus. This uses a simple byte-level protocol with
[all …]
/linux-4.1.27/drivers/iio/light/
DKconfig12 depends on I2C
22 depends on I2C
32 depends on I2C
41 depends on I2C
52 depends on I2C
63 depends on I2C
73 depends on I2C
85 depends on I2C
92 hooked to an I2C bus.
99 depends on I2C
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/sound/
Dadi,ssm2602.txt3 SSM2602 support both I2C and SPI as the configuration interface,
5 SSM2603 and SSM2604 only support I2C as the configuration interface.
11 - reg : the I2C address of the device for I2C, the chip select
Dda9055.txt3 DA9055 provides Audio CODEC support (I2C only).
5 The Audio CODEC device in DA9055 has it's own I2C address which is configurable,
8 For details on accompanying PMIC I2C device, see the following:
14 - reg: Specifies the I2C slave address
Dcs4265.txt3 This device supports I2C only.
9 - reg : the I2C address of the device for I2C. The I2C address depends on
Dak4642.txt1 AK4642 I2C transmitter
3 This device supports I2C mode only.
8 - reg : The chip select number on the I2C bus
Dwm8728.txt3 This device supports both I2C and SPI (configured with pin strapping
10 - reg : the I2C address of the device for I2C, the chip select
Dwm8741.txt3 This device supports both I2C and SPI (configured with pin strapping
10 - reg : the I2C address of the device for I2C, the chip select
Dwm8737.txt3 This device supports both I2C and SPI (configured with pin strapping
10 - reg : the I2C address of the device for I2C, the chip select
Dwm8711.txt3 This device supports both I2C and SPI (configured with pin strapping
10 - reg : the I2C address of the device for I2C, the chip select
Dwm8776.txt3 This device supports both I2C and SPI (configured with pin strapping
10 - reg : the I2C address of the device for I2C, the chip select
Dwm8510.txt3 This device supports both I2C and SPI (configured with pin strapping
10 - reg : the I2C address of the device for I2C, the chip select
Dwm8750.txt3 These devices support both I2C and SPI (configured with pin strapping
10 - reg : the I2C address of the device for I2C, the chip select
Dmax98925.txt3 This device supports I2C.
13 - reg : the I2C address of the device for I2C
Dcs4270.txt3 The driver for this device currently only supports I2C.
9 - reg : the I2C address of the device for I2C
Dwm8753.txt3 This device supports both I2C and SPI (configured with pin strapping
10 - reg : the I2C address of the device for I2C, the chip select
Dwm8804.txt3 This device supports both I2C and SPI (configured with pin strapping
10 - reg : the I2C address of the device for I2C, the chip select
Dwm8731.txt3 This device supports both I2C and SPI (configured with pin strapping
10 - reg : the I2C address of the device for I2C, the chip select
Des8328.txt3 This device supports both I2C and SPI.
13 - reg : the I2C address of the device for I2C, the chip select number for SPI
Dwm8580.txt3 This device supports I2C only.
9 - reg : the I2C address of the device.
Dwm8523.txt3 This device supports I2C only.
9 - reg : the I2C address of the device.
Dmax98095.txt3 This device supports I2C only.
9 - reg : The I2C address of the device.
Dcs42l73.txt7 - reg : the I2C address of the device for I2C
Dssm4567.txt3 This device supports I2C only.
7 - reg : the I2C address of the device. This will either be 0x34 (LR_SEL/ADDR connected to AGND),
Dtpa6130a2.txt3 The tpa6130a2 serial control bus communicates through I2C protocols
12 - reg - <int> - I2C slave address
Dpcm512x.txt3 These devices support both I2C and SPI (configured with pin strapping
11 - reg : the I2C address of the device for I2C, the chip select
Dwm8904.txt3 This device supports I2C only.
7 - reg: the I2C address of the device.
Drt5631.txt3 This device supports I2C only.
9 - reg : the I2C address of the device.
Dssm2518.txt3 This device supports I2C only.
7 - reg : the I2C address of the device. This will either be 0x34 (ADDR pin low)
Dtas2552.txt3 The tas2552 serial control bus communicates through I2C protocols
8 - reg - I2C slave address
Dcs42xx8.txt7 - reg : the I2C address of the device for I2C
Dalc5632.txt3 This device supports I2C only.
9 - reg : the I2C address of the device.
Dmax98090.txt3 This device supports I2C only.
9 - reg : The I2C address of the device.
Drt5640.txt3 This device supports I2C only.
9 - reg : The I2C address of the device.
Dtlv320aic32x4.txt3 The tlv320aic32x4 serial control bus communicates through I2C protocols
7 - reg: I2C slave address
Dwm8962.txt3 This device supports I2C only.
9 - reg : the I2C address of the device.
Dwm8960.txt3 This device supports I2C only.
9 - reg : the I2C address of the device.
/linux-4.1.27/drivers/media/radio/si4713/
DKconfig3 depends on USB && I2C && RADIO_SI4713
17 tristate "Silicon Labs Si4713 FM Radio Transmitter support with I2C"
18 depends on I2C && RADIO_SI4713
21 This is a driver for I2C devices with the Silicon Labs SI4713
25 computer's I2C port.
32 depends on I2C && RADIO_SI4713
/linux-4.1.27/drivers/regulator/
DKconfig63 the voltage is programmed via I2C interface.
75 depends on I2C
79 regulator via I2C bus.
83 depends on I2C
193 depends on I2C
198 converter 12A DC-DC Buck controlled through an I2C
203 depends on I2C
209 step down converter 12A or 16A DC-DC Buck controlled through an I2C
225 depends on I2C
232 programmed through an I2C interface.
[all …]
/linux-4.1.27/drivers/iio/magnetometer/
DKconfig10 depends on I2C
21 depends on I2C
29 depends on I2C
52 depends on (I2C || SPI_MASTER) && SYSFS
54 select IIO_ST_MAGN_I2C_3AXIS if (I2C)
64 - st_magn_i2c (necessary for the I2C devices [optional*]);
/linux-4.1.27/drivers/iio/accel/
DKconfig10 depends on I2C
22 depends on I2C
51 depends on (I2C || SPI_MASTER) && SYSFS
53 select IIO_ST_ACCEL_I2C_3AXIS if (I2C)
64 - st_accel_i2c (necessary for the I2C devices [optional*]);
91 depends on I2C
103 depends on I2C
119 depends on I2C
131 depends on I2C
/linux-4.1.27/drivers/nfc/nxp-nci/
DKconfig16 tristate "NXP-NCI I2C support"
17 depends on NFC_NXP_NCI && I2C
19 This module adds support for an I2C interface to the NXP NCI
21 Select this if your platform is using the I2C bus.
/linux-4.1.27/drivers/hwmon/
DKconfig35 Say Y here if you want the I2C chip drivers to produce a bunch of
37 a problem with I2C support and want to see more of what is going
96 depends on I2C
106 depends on I2C
116 depends on I2C
127 depends on I2C
138 depends on I2C
149 depends on I2C
160 depends on I2C
170 depends on I2C
[all …]
/linux-4.1.27/Documentation/video4linux/bttv/
DICs17 I2C 0xa0-0xa1, (24LC02B also responds to 0xa2-0xaf)
18 Philips SAA5246AGP/E: Videotext decoder chip, I2C 0x22-0x23
25 TSA5522: 1.4 GHz I2C-bus controlled synthesizer, I2C 0xc2-0xc3
/linux-4.1.27/drivers/iio/dac/
DKconfig10 depends on (SPI_MASTER && I2C!=m) || I2C
32 depends on (SPI_MASTER && I2C!=m) || I2C
33 select REGMAP_I2C if I2C
55 depends on (SPI_MASTER && I2C!=m) || I2C
147 depends on I2C
150 (I2C 8-Bit DACs with rail-to-rail outputs):
162 depends on I2C
170 depends on I2C
173 MCP 4725 12-bit digital-to-analog converter (DAC) with I2C
/linux-4.1.27/drivers/misc/lis3lv02d/
DKconfig23 tristate "STMicroeletronics LIS3LV02Dx three-axis digital accelerometer (I2C)"
24 depends on I2C && INPUT
29 via I2C. The accelerometer data is readable via
36 will be called lis3lv02d and a specific module for the I2C transport
/linux-4.1.27/drivers/misc/eeprom/
DKconfig4 tristate "I2C EEPROMs / RAMs / ROMs from most vendors"
5 depends on I2C && SYSFS
7 Enable this driver to get read/write support to most I2C EEPROMs
23 If you use this with an SMBus adapter instead of an I2C adapter,
42 tristate "Old I2C EEPROM reader"
43 depends on I2C && SYSFS
46 available on modern memory DIMMs and Sony Vaio laptops via I2C. Such
54 depends on I2C
/linux-4.1.27/Documentation/devicetree/bindings/gpio/
Dgpio-mcp23s08.txt2 8-/16-bit I/O expander with serial interface (I2C/SPI)
8 - "mcp,mcp23008" (DEPRECATED) for 8 GPIO I2C version or
9 - "mcp,mcp23017" (DEPRECATED) for 16 GPIO I2C version of the chip
13 - "microchip,mcp23008" for 8 GPIO I2C version or
14 - "microchip,mcp23017" for 16 GPIO I2C version of the chip
21 - reg : For an address on its bus. I2C uses this a the I2C address of the chip.
63 Example I2C (with interrupt):
/linux-4.1.27/drivers/input/touchscreen/
DKconfig74 tristate "support I2C bus connection"
75 depends on TOUCHSCREEN_AD7879 && I2C
77 Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus.
95 depends on I2C && OF
106 tristate "Atmel mXT I2C Touchscreen"
107 depends on I2C
110 Say Y here if you have Atmel mXT series I2C touchscreen,
120 depends on I2C
133 depends on I2C
146 depends on I2C
[all …]
/linux-4.1.27/drivers/staging/iio/light/
DKconfig8 depends on I2C
20 depends on I2C
30 depends on I2C
37 depends on I2C
/linux-4.1.27/Documentation/spi/
Dspi-sc18is60215 This driver provides connects a NXP SC18IS602/603 I2C-bus to SPI bridge to the
26 This driver requires the I2C adapter driver to support raw I2C messages. I2C
/linux-4.1.27/drivers/char/tpm/
DKconfig38 tristate "TPM Interface Specification 1.2 Interface (I2C - Atmel)"
39 depends on I2C
41 If you have an Atmel I2C TPM security chip say Yes and it will be
47 tristate "TPM Interface Specification 1.2 Interface (I2C - Infineon)"
48 depends on I2C
51 TCG TIS 1.2 TPM specification and Infineon's I2C Protocol Stack
58 tristate "TPM Interface Specification 1.2 Interface (I2C - Nuvoton)"
59 depends on I2C
61 If you have a TPM security chip with an I2C interface from
/linux-4.1.27/drivers/leds/
DKconfig48 depends on I2C
70 depends on LEDS_CLASS && I2C
166 depends on I2C && INPUT
194 tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
196 depends on I2C
215 depends on LEDS_CLASS && I2C
225 depends on LEDS_CLASS && I2C
236 depends on LEDS_CLASS && I2C
246 depends on LEDS_CLASS && I2C
265 depends on LEDS_CLASS && I2C
[all …]
/linux-4.1.27/drivers/iio/temperature/
DKconfig8 depends on I2C
11 MLX90614 contact-less infrared sensor connected with I2C.
18 depends on I2C
/linux-4.1.27/sound/soc/fsl/
DKconfig99 # I2C is necessary for the CS4270 driver
100 depends on MPC8610_HPCD && I2C
112 # I2C is necessary for the WM8776 driver
113 depends on P1022_DS && I2C
126 # I2C is necessary for the WM8960 driver
127 depends on P1022_RDK && I2C
199 depends on MACH_IMX27_VISSTRIM_M10 && I2C
222 depends on ARCH_MXC && I2C
234 depends on OF && I2C && INPUT
245 depends on OF && (I2C || SPI)
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/
Dbrcm,bcm11351-pinctrl.txt49 Standard, I2C, and HDMI. Each type accepts a different set of pin config
83 Optional Properties (for I2C pins):
89 in parallel for I2C pins, so the valid values
137 // group node defining 2 I2C pins
196 "bsc1_scl", I2C
197 "bsc1_sda", I2C
198 "bsc2_scl", I2C
199 "bsc2_sda", I2C
331 "pmu_scl", I2C
332 "pmu_sda", I2C
[all …]
/linux-4.1.27/drivers/iio/gyro/
DKconfig55 depends on I2C
78 depends on (I2C || SPI_MASTER) && SYSFS
80 select IIO_ST_GYRO_I2C_3AXIS if (I2C)
90 - st_gyro_i2c (necessary for the I2C devices [optional*]);
106 tristate "InvenSense ITG3200 Digital 3-Axis Gyroscope I2C driver"
107 depends on I2C
/linux-4.1.27/drivers/media/radio/si470x/
DKconfig27 tristate "Silicon Labs Si470x FM Radio Receiver support with I2C"
28 depends on I2C && RADIO_SI470X && !USB_SI470X
30 This is a driver for I2C devices with the Silicon Labs SI470x
34 computer's I2C port.
/linux-4.1.27/Documentation/dvb/
Dtechnisat.txt42 b.) => "Generic I2C PLL based tuners"
46 b.) => "Generic I2C PLL based tuners"
60 b.) => "Generic I2C PLL based tuners"
64 b.) => "Generic I2C PLL based tuners"
71 b.) => "Generic I2C PLL based tuners"
/linux-4.1.27/Documentation/devicetree/bindings/hid/
Dhid-over-i2c.txt1 * HID over I2C Device-Tree bindings
3 HID over I2C provides support for various Human Interface Devices over the
4 I2C bus. These devices can be for example touchpads, keyboards, touch screens
/linux-4.1.27/drivers/macintosh/
DKconfig194 depends on I2C && I2C_POWERMAC && PPC_PMAC && !PPC_PMAC64
201 depends on I2C && I2C_POWERMAC && PPC_PMAC && !PPC_PMAC64
213 depends on WINDFARM && I2C && CPU_FREQ_PMAC64 && PMAC_SMU
220 depends on WINDFARM && I2C && CPU_FREQ_PMAC64 && ADB_PMU
228 depends on WINDFARM && I2C && CPU_FREQ_PMAC64 && ADB_PMU
236 depends on WINDFARM && I2C && CPU_FREQ_PMAC64 && PMAC_SMU
244 depends on WINDFARM && I2C && PMAC_SMU
253 depends on WINDFARM && I2C && PMAC_SMU
272 depends on PPC_PMAC && !PPC64 && INPUT && ((ADB_PMU && I2C = y) || (ADB_PMU && !I2C) || I2C)
276 implementations for PMU and I2C.
[all …]
/linux-4.1.27/sound/soc/pxa/
DKconfig42 depends on SND_PXA2XX_SOC && PXA_SHARP_C7xx && I2C
51 depends on SND_PXA2XX_SOC && PXA_SHARP_Cxx00 && I2C
60 depends on SND_PXA2XX_SOC && MACH_ZIPIT2 && I2C
68 depends on SND_PXA2XX_SOC && MACH_POODLE && I2C
142 depends on SND_PXA910_SOC && MACH_TTC_DKB && I2C=y
165 depends on I2C && SPI_MASTER
174 depends on SND_PXA2XX_SOC && MACH_H4700 && I2C
183 depends on SND_PXA2XX_SOC && MACH_MAGICIAN && I2C
202 depends on SND_PXA2XX_SOC && MACH_INTELMOTE2 && I2C
/linux-4.1.27/drivers/staging/nvec/
DREADME4 embedded controller (EC) via I2C bus. The EC is an I2C master while the host
5 processor is the I2C slave. Requests from the host processor to the EC are
/linux-4.1.27/drivers/media/v4l2-core/
DKconfig8 depends on (I2C || I2C=n) && VIDEO_DEV
9 default (I2C || I2C=n) && VIDEO_DEV
/linux-4.1.27/Documentation/devicetree/bindings/mfd/
Dda9055.txt3 DA9055 consists of a large and varied group of sub-devices (I2C Only):
14 The CODEC device in DA9055 has a separate, configurable I2C address and so
17 For details on accompanying CODEC I2C device, see the following:
24 - reg: Specifies the I2C slave address (defaults to 0x5a but can be modified)
Dcros-ec.txt6 The EC can be connect through various means (I2C, SPI, LPC) and the
12 Required properties (I2C):
14 - reg: I2C slave address
34 Example for I2C:
D88pm860x.txt5 - reg : the I2C slave address for the 88pm860x chip
13 - marvell,88pm860x-slave-addr: 88pm860x are two chips solution. <reg> stores the I2C address
14 of one chip, and this property stores the I2C address of
Drn5t618.txt6 through a I2C interface.
10 - reg: the I2C slave address of the device
Ds2mpa01.txt6 and an RTC. It is interfaced to the host controller using an I2C interface.
7 Each sub-block is addressed by the host system using different I2C slave
12 - reg: Specifies the I2C slave address of the PMIC block. It should be 0x66.
/linux-4.1.27/drivers/staging/iio/addac/
DKconfig28 tristate "support I2C bus connection"
29 depends on I2C && ADT7316
31 Say yes here to build I2C bus support for Analog Devices ADT7316/7/8
/linux-4.1.27/drivers/media/platform/s5p-tv/
DKconfig23 depends on I2C
42 depends on VIDEO_DEV && VIDEO_V4L2 && I2C
47 as module. It is an I2C driver, that exposes a V4L2
52 depends on VIDEO_DEV && VIDEO_V4L2 && I2C
57 as module. It is an I2C driver, that exposes a V4L2
/linux-4.1.27/sound/soc/davinci/
DKconfig40 depends on SND_EDMA_SOC && SOC_AM33XX && I2C
50 depends on SND_EDMA_SOC && I2C
78 depends on SND_EDMA_SOC && MACH_DAVINCI_DM6467_EVM && I2C
87 depends on SND_EDMA_SOC && MACH_DAVINCI_DA830_EVM && I2C
96 depends on SND_EDMA_SOC && MACH_DAVINCI_DA850_EVM && I2C
/linux-4.1.27/Documentation/zh_CN/
Dgpio.txt47 匮乏的 SOC。同时还有通过 I2C 或 SPI 串行总线连接的“GPIO扩展器”
114 使用编号2000-2063来标识一个 I2C 接口的 GPIO 扩展器中的 GPIO。
186 函数可以使得模拟接口(译者注:例如 GPIO 模拟 I2C、1-wire 或 SPI)的
192 某些 GPIO 控制器必须通过基于总线(如 I2C 或 SPI)的消息访问。读或写这些
408 这不一定是错误的。一个常见的例子就是 I2C 时钟的延长：一个需要较慢时钟的
409 从设备延迟 SCK 的上升沿，而 I2C 主设备相应地调整其信号传输速率。
512 对于外部 GPIO 控制器(例如 I2C 或 SPI 扩展器、专用芯片、多功能器件、FPGA
521 初始化顺序很重要。例如，如果一个设备依赖基于 I2C 的(扩展)GPIO，那么它的
/linux-4.1.27/drivers/staging/iio/cdc/
DKconfig8 depends on I2C
18 depends on I2C
28 depends on I2C
/linux-4.1.27/drivers/power/
DKconfig108 depends on I2C
155 depends on I2C
162 depends on I2C || I2C=n
164 Say Y here to enable support for batteries with BQ27x00 (I2C/HDQ) chips.
169 depends on I2C
172 Say Y here to enable support for batteries with BQ27x00 (I2C) chips.
218 depends on I2C
226 depends on I2C
238 depends on I2C && MACH_ZIPIT2
315 depends on I2C
[all …]
/linux-4.1.27/drivers/media/pci/saa7146/
DKconfig3 depends on PCI && VIDEO_V4L2 && I2C
15 depends on PCI && VIDEO_V4L2 && I2C
26 depends on PCI && VIDEO_V4L2 && I2C
/linux-4.1.27/drivers/media/pci/mantis/
DKconfig3 depends on PCI && I2C && INPUT && RC_CORE
12 depends on MANTIS_CORE && DVB_CORE && PCI && I2C
31 depends on MANTIS_CORE && DVB_CORE && PCI && I2C
/linux-4.1.27/sound/soc/tegra/
DKconfig66 depends on SND_SOC_TEGRA && I2C && GPIOLIB
76 depends on SND_SOC_TEGRA && I2C && GPIOLIB
86 depends on SND_SOC_TEGRA && I2C && GPIOLIB
106 depends on SND_SOC_TEGRA && I2C
115 depends on SND_SOC_TEGRA && I2C && GPIOLIB
124 depends on SND_SOC_TEGRA && I2C && GPIOLIB
134 depends on SND_SOC_TEGRA && I2C && GPIOLIB
/linux-4.1.27/Documentation/video4linux/
DREADME.pvrusb231 1b. I2C adaptor implementation and corresponding I2C client drivers
82 driver and the msp3400.ko I2C client driver (which is found
136 tie together and configure various I2C modules as they attach to
137 the I2C bus. There are two versions of this file. The "v4l2"
146 compatible commands to the I2C modules. It is here where state
148 commands that are in turn send to the various I2C modules.
151 compatible commands to the I2C modules. It is here where state
153 commands that are in turn send to the various I2C modules.
156 kernel-friendly I2C adaptor driver, through which other external
157 I2C client drivers (e.g. msp3400, tuner, lirc) may connect and
[all …]
Dsi4713.txt1 Driver for I2C radios for the Silicon Labs Si4713 FM Radio Transmitters
9 This chip is a Silicon Labs product. It is a I2C device, currently on 0x63 address.
23 There are two modules to handle this device. One is a I2C device driver
26 The I2C device driver exports a v4l2-subdev interface to the kernel.
31 So, it uses the I2C device driver as a sub device in order to send the user
32 commands to the actual device. Basically it is a wrapper to the I2C device driver.
/linux-4.1.27/drivers/input/misc/
DKconfig56 tristate "support I2C bus connection"
57 depends on INPUT_AD714X && I2C
60 Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
87 depends on I2C
91 acceleration sensor hooked to an I2C bus.
226 depends on I2C
230 through I2C interface.
237 depends on I2C
240 connected via an I2C bus.
247 depends on X86 && I2C && LEDS_CLASS
[all …]
/linux-4.1.27/Documentation/i2c/muxes/
Di2c-mux-gpio8 i2c-gpio-mux is an i2c mux driver providing access to I2C bus segments
9 from a master I2C bus and a hardware MUX controlled through GPIO pins.
23 SCL/SDA of the master I2C bus is multiplexed to bus segment 1..M
31 gpio_i2cmux_platform_data with the I2C adapter number of the master
/linux-4.1.27/sound/soc/intel/
DKconfig49 depends on SND_SOC_INTEL_SST && X86_INTEL_LPSS && I2C && \
61 depends on SND_SOC_INTEL_SST && X86_INTEL_LPSS && I2C
70 depends on SND_SOC_INTEL_SST && X86_INTEL_LPSS && I2C
92 depends on X86 && I2C
104 depends on X86_INTEL_LPSS && I2C
/linux-4.1.27/Documentation/misc-devices/
Disl2900317 ADC, I2C user programmable lux range select for optimized counts/lux, and
18 I2C multi-function control and monitoring capabilities. The internal ADC
31 it, so the detection routine will just try to read from the configured I2C
/linux-4.1.27/Documentation/devicetree/bindings/input/
Dcap11xx.txt3 The node for this device must be a child of a I2C controller node, as the
4 device communication via I2C only.
13 reg: The I2C slave address of the device.
Delants_i2c.txt1 Elantech I2C Touchscreen
5 - reg: I2C address of the chip.
Delan_i2c.txt1 Elantech I2C Touchpad
5 - reg: I2C address of the chip.
/linux-4.1.27/Documentation/devicetree/bindings/iio/light/
Dcm36651.txt1 * Capella CM36651 I2C Proximity and Color Light sensor
5 - reg: the I2C address of the device
Dgp2ap020a00f.txt1 * Sharp GP2AP020A00F I2C Proximity/ALS sensor
9 - reg : the I2C slave address of the light sensor
/linux-4.1.27/Documentation/devicetree/bindings/rtc/
Ddallas,ds1339.txt1 * Dallas DS1339 I2C Serial Real-Time Clock
5 - reg: I2C address for chip
Dabracon,abx80x.txt1 Abracon ABX80X I2C ultra low power RTC/Alarm chip
20 - "reg": I2C bus address of the device
Disil,isl12057.txt1 Intersil ISL12057 I2C RTC/Alarm chip
3 ISL12057 is a trivial I2C device (it has simple device tree bindings,
21 - "reg": I2C bus address of the device
/linux-4.1.27/drivers/staging/iio/meter/
DKconfig50 depends on SPI || I2C
59 tristate "support I2C bus connection"
60 depends on ADE7854 && I2C
63 Say Y here if you have ADE7854/58/68/78 hooked to an I2C bus.
/linux-4.1.27/Documentation/devicetree/bindings/input/touchscreen/
Dpixcir_i2c_ts.txt1 * Pixcir I2C touchscreen controllers
5 - reg: I2C address of the chip
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/cpm/
Di2c.txt1 * I2C
3 The I2C controller is expressed as a bus under the CPM node.
7 - reg : On CPM2 devices, the second resource doesn't specify the I2C
/linux-4.1.27/drivers/input/mouse/
DKconfig222 tristate "Cypress APA I2C Trackpad support"
223 depends on I2C
227 I2C Trackpads, including the ones used in 2012 Samsung Chromebooks.
229 Say Y here if you have a Cypress APA I2C Trackpad.
235 tristate "ELAN I2C Touchpad support"
236 depends on I2C
238 This driver adds support for Elan I2C/SMbus Trackpads.
240 Say Y here if you have a ELAN I2C/SMbus Touchpad.
246 bool "Enable I2C support"
251 a standard I2C controller.
[all …]
/linux-4.1.27/drivers/misc/
DKconfig15 depends on (I2C || SPI) && SYSFS
35 tristate "support I2C bus connection"
36 depends on AD525X_DPOT && I2C
38 Say Y here if you have a digital potentiometers hooked to an I2C bus.
184 depends on I2C
299 depends on I2C
309 depends on I2C && SYSFS
319 depends on I2C
329 depends on I2C && SYSFS
339 depends on I2C && SYSFS
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/dma/
Dste-dma40.txt66 4: I2C port 1
67 5: I2C port 3
68 6: I2C port 2
69 7: I2C port 4
77 15: I2C port 0
/linux-4.1.27/Documentation/devicetree/bindings/leds/
Dleds-lp8860.txt6 signal, a SPI/I2C master, or both.
11 - reg - I2C slave address
/linux-4.1.27/drivers/media/platform/marvell-ccic/
DKconfig3 depends on PCI && I2C && VIDEO_V4L2
16 depends on ARCH_MMP && I2C && VIDEO_V4L2
/linux-4.1.27/sound/aoa/codecs/
DKconfig3 select I2C
12 select I2C
/linux-4.1.27/arch/arm/mach-davinci/
DKconfig71 select I2C
80 select I2C
112 select I2C
126 select I2C
137 select I2C
146 detected automatically based on successful probe of the I2C
175 EVM is detected automatically based on successful probe of the I2C
207 select I2C
/linux-4.1.27/sound/soc/blackfin/
DKconfig18 select SND_SOC_SSM2602_I2C if I2C
25 depends on SND_BF5XX_I2S && I2C
35 depends on SND_BF5XX_I2S && I2C
48 depends on SND_BF5XX_I2S && I2C
61 depends on SND_BF5XX_I2S && I2C
77 select SND_SOC_ADAV803 if I2C
98 select SND_SOC_AD193X_I2C if I2C
/linux-4.1.27/Documentation/devicetree/bindings/
Deeprom.txt1 EEPROMs (I2C)
11 - reg : the I2C address of the EEPROM
Dunittest.txt33 ** I2C unittest device
48 ** I2C unittest mux
/linux-4.1.27/Documentation/devicetree/bindings/extcon/
Dextcon-sm5502.txt7 the host controller using an I2C interface.
11 - reg: Specifies the I2C slave address of the MUIC block. It should be 0x25
Dextcon-rt8973a.txt4 The Richtek RT8973A is Micro USB Switch with OVP and I2C interface. The RT8973A
13 - reg: Specifies the I2C slave address of the MUIC block. It should be 0x14
/linux-4.1.27/Documentation/zh_CN/video4linux/
Dv4l2-framework.txt35 并同时创建非 V4L2 设备（如 DVB、ALSA、FB、I2C 和红外输入设备）。
39 复杂性。通常这些 IC 通过一个或多个 I2C 总线连接到主桥驱动器，但也可
215 这些一般为 I2C 接口设备，但并不一定都是。为了给驱动提供调用子设备的
236 对于其他总线也需要做类似的操作。针对 I2C 总线上的子设备辅助函数帮你
378 信息。所有驱动可以包含多个 I2C 总线的子设备，但也有子设备是通过 GPIO
432 I2C 子设备驱动
438 添加 v4l2_subdev 支持的推荐方法是让 I2C 驱动将 v4l2_subdev 结构体
439 嵌入到为每个 I2C 设备实例创建的状态结构体中。而最简单的设备没有状态
495 I2C 地址数组，让函数自动探测。这些探测地址只有在前一个参数为 0 的
/linux-4.1.27/Documentation/leds/
Dleds-blinkm.txt4 communicate through I2C. The default address of these modules is
6 dasy-chain up to 127 BlinkMs on an I2C bus.
52 in the sysfs folder of the I2C device.
/linux-4.1.27/drivers/media/pci/ttpci/
DKconfig6 depends on DVB_CORE && PCI && I2C
54 depends on DVB_CORE && PCI && I2C
64 depends on DVB_BUDGET_CORE && I2C
90 depends on DVB_BUDGET_CORE && I2C
117 depends on DVB_BUDGET_CORE && I2C
140 depends on DVB_BUDGET_CORE && I2C
/linux-4.1.27/drivers/gpu/drm/i2c/
DKconfig1 menu "I2C encoder or helper chips"
2 depends on DRM && DRM_KMS_HELPER && I2C
/linux-4.1.27/Documentation/devicetree/bindings/media/
Dsi4713.txt6 DSP-mode format. It is programmable through an I2C interface.
10 - reg: the I2C address of the device
Dexynos4-fimc-is.txt5 processor, ISP, DRC and FD IP blocks and peripheral devices such as UART, I2C
32 i2c-isp (ISP I2C bus controller) nodes
47 firmware must be child nodes of their corresponding ISP I2C bus controller node.
/linux-4.1.27/drivers/staging/sm750fb/
Dddk750_power.c146 gate = FIELD_SET(gate, CURRENT_GATE, I2C, ON); in enableZVPort()
232 gate = FIELD_SET(gate, CURRENT_GATE, I2C, ON); in enableI2C()
234 gate = FIELD_SET(gate, CURRENT_GATE, I2C, OFF); in enableI2C()
/linux-4.1.27/drivers/w1/masters/
DKconfig28 tristate "Maxim DS2482 I2C to 1-Wire bridge"
29 depends on I2C
32 I2C to 1-Wire bridge.
/linux-4.1.27/drivers/staging/iio/magnetometer/
DKconfig12 tristate "Honeywell HMC5843/5883/5883L 3-Axis Magnetometer (I2C)"
13 depends on I2C
/linux-4.1.27/drivers/iio/humidity/
DKconfig17 depends on I2C
27 depends on I2C
/linux-4.1.27/drivers/char/tpm/st33zp24/
DKconfig13 tristate "TPM 1.2 ST33ZP24 I2C support"
15 depends on I2C
/linux-4.1.27/arch/arm/plat-samsung/
DKconfig108 Compile in platform device definitions for I2C channel 1
113 Compile in platform device definitions for I2C channel 2
118 Compile in platform device definition for I2C controller 3
123 Compile in platform device definition for I2C controller 4
128 Compile in platform device definition for I2C controller 5
133 Compile in platform device definition for I2C controller 6
138 Compile in platform device definition for I2C controller 7
/linux-4.1.27/drivers/gpio/
DKconfig93 # This symbol is selected by both I2C and SPI expanders
515 menu "I2C GPIO expanders"
516 depends on I2C
519 tristate "ADP5588 I2C GPIO expander"
520 depends on I2C
534 depends on I2C && OF_GPIO
538 I2C GPIO expanders. The register space will be extended by powers
546 depends on I2C
549 GPIO driver for Maxim MAX7300 I2C-based GPIO expander.
552 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
[all …]
/linux-4.1.27/drivers/staging/media/mn88473/
DTODO10 * I2C errors
16 missing for the reason it is much easier to compare I2C data sniffs when
/linux-4.1.27/drivers/staging/media/mn88472/
DTODO10 * I2C errors
16 missing for the reason it is much easier to compare I2C data sniffs when
/linux-4.1.27/arch/cris/arch-v10/drivers/
DKconfig432 bool "I2C support"
435 Enables an I2C driver on ETRAX100.
442 # this is true for most products since PB-I2C seems to be somewhat
445 bool "I2C uses PB not PB-I2C"
448 Select whether to use the special I2C mode in the PB I/O register or
450 that access the I2C I/O pins directly instead of going through the
451 I2C driver, like the DS1302 realtime-clock driver. If you are
455 int "I2C SDA bit number"
462 int "I2C SCL bit number"
469 bool "I2C EEPROM (non-volatile RAM) support"
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/power/
Dltc2941.txt10 type of I2C chip attached.
11 - reg: The 7-bit I2C address.
/linux-4.1.27/drivers/sbus/char/
DKconfig42 The BBC devices on the UltraSPARC III have two I2C controllers. The
43 first I2C controller connects mainly to configuration PROMs (NVRAM,
44 CPU configuration, DIMM types, etc.). The second I2C controller
/linux-4.1.27/drivers/media/pci/cx88/
DKconfig3 depends on VIDEO_DEV && PCI && I2C && RC_CORE
75 bool "VP-3054 Secondary I2C Bus Support"
82 Secondary I2C bus, such at DNTV Live! DVB-T Pro.

1234