Home
last modified time | relevance | path

Searched refs:I2C (Results 1 – 25 of 1031) sorted by relevance

12345678910>>...42

/Linux-v5.4/sound/soc/codecs/
DKconfig2 # Helper to resolve issues with configs that have SPI enabled but I2C
3 # modular, meaning we can't build the codec driver in with I2C support.
8 default m if I2C=m
9 default y if I2C=y
23 select SND_SOC_AD193X_I2C if I2C
26 select SND_SOC_ADAU1373 if I2C
27 select SND_SOC_ADAU1761_I2C if I2C
29 select SND_SOC_ADAU1781_I2C if I2C
32 select SND_SOC_ADAV803 if I2C
34 select SND_SOC_ADAU1977_I2C if I2C
[all …]
/Linux-v5.4/drivers/i2c/
DKconfig3 # I2C subsystem configuration
6 menu "I2C support"
8 config I2C config
9 tristate "I2C support"
13 I2C (pronounce: I-squared-C) is a slow serial bus protocol used in
15 or System Management Bus is a subset of the I2C protocol. More
19 Both I2C and SMBus are supported here. You will need this for
22 If you want I2C support, you should say Y here and also to the
25 This I2C support can also be built as a module. If so, the module
29 bool "ACPI I2C Operation region support"
[all …]
/Linux-v5.4/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.
30 i2c@70038000 { /* HS-I2C on i.MX51 */
Di2c-mux-gpmux.txt1 General Purpose I2C Bus Mux
3 This binding describes an I2C bus multiplexer that uses a mux controller
4 from the mux subsystem to route the I2C signals.
12 | | I2C |-|--| Mux |
22 - i2c-parent: The phandle of the I2C bus that this multiplexer's master-side
26 * Standard I2C mux properties. See i2c-mux.txt in this directory.
27 * I2C child bus nodes. See i2c-mux.txt in this directory. The sub-bus number
31 - mux-locked: If present, explicitly allow unrelated I2C transactions on the
32 parent I2C adapter at these times:
34 + between setup of the multiplexer and the child bus I2C transaction
[all …]
Dnvidia,tegra186-bpmp-i2c.txt1 NVIDIA Tegra186 BPMP I2C controller
4 devices, such as the I2C controller for the power management I2C bus. Software
6 transactions on that I2C bus. This binding describes an I2C bus that is
9 The BPMP I2C node must be located directly inside the main BPMP node. See
12 This node represents an I2C controller. See ../i2c/i2c.txt for details of the
13 core I2C binding.
20 - #address-cells: Address cells for I2C device address.
28 Indicates the I2C bus number this DT node represent, as defined by the
Di2c-sprd.txt1 I2C for Spreadtrum platforms
7 - interrupts: Should contain I2C interrupt.
9 "i2c" for I2C clock,
10 "source" for I2C source (parent) clock,
11 "enable" for I2C module enable clock.
13 - clock-frequency: Constains desired I2C bus clock frequency in Hz.
14 - #address-cells: Should be 1 to describe address cells for I2C device address.
15 - #size-cells: Should be 0 means no size cell for I2C device address.
18 - Child nodes conforming to I2C bus binding
Di2c.txt1 Generic device tree bindings for I2C busses
4 This document describes generic bindings which can be used to describe I2C
12 - compatible - name of I2C bus controller following generic names
18 The cells properties above define that an address of children of an I2C bus
36 For I2C adapters that have child nodes that are a mixture of both I2C
37 devices and non-I2C devices, the 'i2c-bus' subnode can be used for
38 populating I2C devices. If the 'i2c-bus' subnode is present, only
39 subnodes of this will be considered as I2C slaves. The properties,
44 Number of nanoseconds the SCL signal takes to fall; t(f) in the I2C
51 Number of nanoseconds the SCL signal takes to rise; t(r) in the I2C
[all …]
Di2c-demux-pinctrl.txt1 Pinctrl-based I2C Bus DeMux
3 This binding describes an I2C bus demultiplexer that uses pin multiplexing to
4 route the I2C signals, and represents the pin multiplexing configuration using
5 the pinctrl device tree bindings. This may be used to select one I2C IP core at
6 runtime which may have a better feature set for a given task than another I2C
14 | |I2C IP Core1|--\ | +-----+ +-----+
18 | |I2C IP Core2|--/ |
25 - i2c-parent: List of phandles of I2C masters available for selection. The first
27 - i2c-bus-name: The name of this bus. Also needed as pinctrl-name for the I2C
30 Furthermore, I2C mux properties and child nodes. See i2c-mux.txt in this
[all …]
Dbrcm,iproc-i2c.txt1 Broadcom iProc I2C controller
10 I2C controller registers
13 This is the I2C bus clock. Need to be either 100000 or 400000
16 Always 1 (for I2C addresses)
24 Should contain the I2C interrupt. For certain revisions of the I2C
25 controller, I2C interrupt is unwired to the interrupt controller. In such
Di2c-stm32.txt1 * I2C controller embedded in STMicroelectronics STM32 I2C platform
8 - interrupts: Must contain the interrupt id for I2C event and then the
9 interrupt id for I2C error.
11 - clocks: Must contain the input clock of the I2C instance.
13 operation for I2C transfer
18 - clock-frequency: Desired I2C bus clock frequency in Hz. If not specified,
26 - i2c-scl-rising-time-ns: I2C SCL Rising time for the board (default: 25)
28 - i2c-scl-falling-time-ns: I2C SCL Falling time for the board (default: 10)
30 I2C Timings are derived from these 2 values
/Linux-v5.4/drivers/i2c/muxes/
DKconfig3 # Multiplexer I2C chip drivers configuration
6 menu "Multiplexer I2C Chip support"
10 tristate "GPIO-based I2C arbitration"
15 I2C multimaster arbitration scheme using GPIOs and a challenge &
23 tristate "GPIO-based I2C multiplexer"
27 GPIO based I2C multiplexer. This driver provides access to
28 I2C busses connected through a MUX, which is controlled
35 tristate "General Purpose I2C multiplexer"
40 general purpose I2C multiplexer. This driver provides access to
41 I2C busses connected through a MUX, which in turn is controlled
[all …]
/Linux-v5.4/Documentation/i2c/
Dsummary.rst2 I2C and SMBus
5 I2C (pronounce: I squared C) is a protocol developed by Philips. It is a
9 I2C is widely used with embedded systems. Some systems use variants that
10 don't meet branding requirements, and so are not advertised as being I2C.
12 SMBus (System Management Bus) is based on the I2C protocol, and is mostly
13 a subset of I2C protocols and signaling. Many I2C devices will work on an
15 achieve I2C branding. Modern PC mainboards rely on SMBus. The most common
16 devices connected through SMBus are RAM modules configured using I2C EEPROMs,
19 Because the SMBus is mostly a subset of the generalized I2C bus, we can
20 use its protocols on many I2C systems. However, there are systems that don't
[all …]
Dinstantiating-devices.rst2 How to instantiate I2C devices
5 Unlike PCI or USB devices, I2C devices are not enumerated at the hardware
7 I2C bus segment, and what address these devices are using. For this
8 reason, the kernel code must instantiate I2C devices explicitly. There are
12 Method 1a: Declare the I2C devices by bus number
15 This method is appropriate when the I2C bus is a system bus as is the case
16 for many embedded systems. On such systems, each I2C bus has a number
17 which is known in advance. It is thus possible to pre-declare the I2C
46 The above code declares 3 devices on I2C bus 1, including their respective
47 addresses and custom data needed by their drivers. When the I2C bus in
[all …]
/Linux-v5.4/drivers/i2c/busses/
DKconfig6 menu "I2C Hardware Bus support"
41 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
51 756/766/768 mainboard I2C interfaces. The driver also includes
52 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
53 the nVidia nForce I2C interface.
76 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
86 MP2 PCIe I2C adapter.
92 tristate "Hix5hd2 high-speed I2C driver"
95 Say Y here to include support for the high-speed I2C controller
108 801 family of mainboard I2C interfaces. Specifically, the following
[all …]
/Linux-v5.4/drivers/media/tuners/
DKconfig5 …A_ANALOG_TV_SUPPORT || MEDIA_DIGITAL_TV_SUPPORT || MEDIA_RADIO_SUPPORT || MEDIA_SDR_SUPPORT) && I2C
28 depends on MEDIA_SUPPORT && I2C
36 depends on MEDIA_SUPPORT && I2C
43 depends on MEDIA_SUPPORT && I2C
52 depends on MEDIA_SUPPORT && I2C
59 depends on MEDIA_SUPPORT && I2C
66 depends on MEDIA_SUPPORT && I2C
74 depends on MEDIA_SUPPORT && I2C
81 depends on MEDIA_SUPPORT && I2C
95 depends on MEDIA_SUPPORT && I2C
[all …]
/Linux-v5.4/drivers/media/dvb-frontends/
DKconfig12 depends on DVB_CORE && I2C
20 depends on DVB_CORE && I2C
28 depends on DVB_CORE && I2C
36 depends on DVB_CORE && I2C
45 depends on DVB_CORE && I2C
52 depends on DVB_CORE && I2C
61 depends on DVB_CORE && I2C
70 depends on DVB_CORE && I2C && I2C_MUX
81 depends on DVB_CORE && I2C
90 depends on DVB_CORE && I2C
[all …]
/Linux-v5.4/drivers/media/i2c/
DKconfig9 tristate "I2C module for IR" if !MEDIA_SUBDRV_AUTOSELECT || EXPERT
10 depends on I2C && RC_CORE
14 some video boards have the IR connected via I2C bus.
16 If your board doesn't have an I2C IR chip, you may disable this
25 comment "I2C drivers hidden by 'Autoselect ancillary drivers'"
28 menu "I2C Encoders, decoders, sensors and other helper chips"
35 depends on VIDEO_V4L2 && I2C
47 depends on VIDEO_V4L2 && I2C
56 depends on I2C
65 depends on VIDEO_V4L2 && I2C && VIDEO_V4L2_SUBDEV_API
[all …]
/Linux-v5.4/Documentation/driver-api/
Di2c.rst4 I\ :sup:`2`\ C (or without fancy typography, "I2C") is an acronym for
8 the same bus. I2C only needs two signals (SCL for clock, SDA for data),
10 I2C devices use seven bit addresses, and bus speeds of up to 400 kHz;
12 I2C is a multi-master bus; open drain signaling is used to arbitrate
16 The Linux I2C programming interfaces support the master side of bus
18 structured around two kinds of driver, and two kinds of device. An I2C
22 I2C bus segment it manages. On each I2C bus segment will be I2C devices
26 are functions to perform various I2C protocol operations; at this writing
30 systems are also I2C conformant. The electrical constraints are tighter
32 Controllers that support I2C can also support most SMBus operations, but
[all …]
/Linux-v5.4/drivers/iio/chemical/
DKconfig10 depends on I2C
16 Say Y here to build I2C interface support for the following
27 depends on (I2C || SPI)
29 select BME680_I2C if I2C
35 This driver can also be built as a module. If so, the module for I2C
40 depends on I2C && BME680
50 depends on I2C
54 Say Y here to build I2C interface support for the AMS
59 depends on I2C
61 Say Y here to build I2C interface support for the AMS
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/i3c/
Di3c.txt27 - i2c-scl-hz: frequency of the SCL signal used for I2C transfers.
29 values of I2C devices described in the device tree to determine
30 the maximum I2C frequency.
32 I2C devices
35 Each I2C device connected to the bus should be described in a subnode. All
42 + first cell : still encoding the I2C address. 10 bit addressing is not
50 bit[7:5]: I2C device index. Possible values
51 * 0: I2C device has a 50 ns spike filter
52 * 1: I2C device does not have a 50 ns spike filter but supports high
54 * 2: I2C device does not have a 50 ns spike filter and is not tolerant
[all …]
/Linux-v5.4/sound/soc/samsung/
DKconfig46 depends on MACH_JIVE && I2C
55 depends on I2C
63 depends on I2C=y
84 depends on ARCH_S3C24XX && I2C
91 depends on ARCH_S3C24XX && I2C
98 depends on ARCH_H1940 && I2C
106 depends on MACH_RX1950 && I2C
116 depends on I2C
128 depends on I2C=y
137 depends on I2C && SPI_MASTER
[all …]
/Linux-v5.4/drivers/iio/pressure/
DKconfig11 depends on I2C
20 tristate "Bosch Sensortec BMP180/BMP280 pressure sensor I2C driver"
21 depends on (I2C || SPI_MASTER)
23 select BMP280_I2C if (I2C)
31 will be called bmp280 and you will also get bmp280-i2c for I2C
37 depends on I2C
58 depends on I2C
62 It can be accessed over I2C bus.
83 depends on I2C
97 depends on I2C
[all …]
/Linux-v5.4/drivers/i2c/algos/
DKconfig3 # I2C algorithm drivers configuration
6 menu "I2C Algorithms"
10 tristate "I2C bit-banging interfaces"
13 tristate "I2C PCF 8584 interfaces"
16 tristate "I2C PCA 9564 interfaces"
/Linux-v5.4/Documentation/i2c/busses/
Di2c-diolan-u2c.rst6 * Diolan U2C-12 I2C-USB adapter
16 This is the driver for the Diolan U2C-12 USB-I2C adapter.
18 The Diolan U2C-12 I2C-USB Adapter provides a low cost solution to connect
19 a computer to I2C slave devices using a USB interface. It also supports
22 This driver only supports the I2C interface of U2C-12. The driver does not use
29 * frequency: I2C bus frequency

12345678910>>...42