Home
last modified time | relevance | path

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

12345678910>>...47

/OK3568_Linux_fs/u-boot/drivers/i2c/
H A DKconfig2 # I2C subsystem configuration
5 menu "I2C support"
8 bool "Enable Driver Model for I2C drivers"
11 Enable driver model for I2C. The I2C uclass interface: probe, read,
20 bool "Enable I2C compatibility layer"
23 Enable old-style I2C functions for compatibility with existing code.
29 tristate "Chrome OS EC tunnel I2C bus"
32 This provides an I2C bus that will tunnel i2c commands through to
33 the other side of the Chrome OS EC to the I2C bus connected there.
35 I2C or LPC). Some Chromebooks use this when the hardware design
[all …]
/OK3568_Linux_fs/kernel/drivers/i2c/
H A 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 …]
/OK3568_Linux_fs/kernel/sound/soc/codecs/
H A 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
366 depends on I2C
382 depends on I2C
387 depends on I2C
400 tristate "Analog Devices AU1761 CODEC - I2C"
401 depends on I2C
417 depends on I2C
[all …]
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/i2c/
H A 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 …]
H A 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 …]
H A 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
H A 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
H A 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 …]
/OK3568_Linux_fs/u-boot/drivers/i2c/muxes/
H A DKconfig2 bool "Support I2C multiplexers"
5 This enables I2C buses to be multiplexed, so that you can select
8 using a suitable I2C MUX driver.
11 bool "Support I2C multiplexers on SPL"
14 This enables I2C buses to be multiplexed, so that you can select
17 using a suitable I2C MUX driver.
20 bool "GPIO-based I2C arbitration"
24 I2C multimaster arbitration scheme using GPIOs and a challenge &
29 tristate "TI PCA954x I2C Mux/switches"
33 I2C mux/switch devices. It is x width I2C multiplexer which enables to
[all …]
/OK3568_Linux_fs/kernel/drivers/i2c/muxes/
H A 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 …]
/OK3568_Linux_fs/kernel/drivers/i2c/busses/
H A 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 …]
/OK3568_Linux_fs/kernel/Documentation/i2c/
H A 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 1: Declare the I2C devices statically
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 which
17 is known in advance. It is thus possible to pre-declare the I2C devices
23 When the I2C bus in question is registered, the I2C devices will be
25 unbound and destroyed when the I2C bus they sit on goes away (if ever).
[all …]
H A Dsummary.rst2 Introduction to I2C and SMBus
5 I²C (pronounce: I squared C and written I2C in the kernel documentation) is
9 low bandwidth communications needs. I2C is widely used with embedded
11 and so are not advertised as being I2C but come under different names,
14 The official I2C specification is the `"I2C-bus specification and user
18 SMBus (System Management Bus) is based on the I2C protocol, and is mostly
19 a subset of I2C protocols and signaling. Many I2C devices will work on an
21 achieve I2C branding. Modern PC mainboards rely on SMBus. The most common
22 devices connected through SMBus are RAM modules configured using I2C EEPROMs,
25 Because the SMBus is mostly a subset of the generalized I2C bus, we can
[all …]
H A Di2c-topology.rst2 I2C muxes and complex topologies
5 There are a couple of reasons for building more complex I2C topologies
6 than a straight-forward I2C bus with one adapter and one or more devices.
14 from the I2C bus, at least most of the time, and sits behind a gate
20 These constructs are represented as I2C adapter trees by Linux, where
23 I2C transfers, and all adapters with a parent are part of an "i2c-mux"
27 an I2C transfer on one of its child adapters. The mux driver can
37 There are two variants of locking available to I2C muxes, they can be
48 same I2C root adapter that they mux.
57 by the same I2C root adapter that they mux.
[all …]
/OK3568_Linux_fs/kernel/drivers/media/dvb-frontends/
H A DKconfig16 depends on DVB_CORE && I2C
24 depends on DVB_CORE && I2C
32 depends on DVB_CORE && I2C
40 depends on DVB_CORE && I2C
49 depends on DVB_CORE && I2C
56 depends on DVB_CORE && I2C
65 depends on DVB_CORE && I2C
74 depends on DVB_CORE && I2C && I2C_MUX
85 depends on DVB_CORE && I2C
94 depends on DVB_CORE && I2C
[all …]
/OK3568_Linux_fs/kernel/drivers/media/tuners/
H A 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 …]
/OK3568_Linux_fs/kernel/drivers/media/i2c/
H A DKconfig8 comment "IR I2C driver auto-selected by 'Autoselect ancillary drivers'"
9 depends on MEDIA_SUBDRV_AUTOSELECT && I2C && RC_CORE
12 tristate "I2C module for IR" if !MEDIA_SUBDRV_AUTOSELECT || EXPERT
13 depends on I2C && RC_CORE
17 some video boards have the IR connected via I2C bus.
19 If your board doesn't have an I2C IR chip, you may disable this
25 # V4L2 I2C drivers that aren't related with Camera support
28 comment "audio, video and radio I2C drivers auto-selected by 'Autoselect ancillary drivers'"
39 depends on VIDEO_V4L2 && I2C
51 depends on VIDEO_V4L2 && I2C
[all …]
/OK3568_Linux_fs/kernel/drivers/iio/chemical/
H A DKconfig10 depends on I2C
16 Say Y here to build I2C interface support for the following
27 depends on I2C
29 Say Y here to build I2C interface support for the following
38 depends on (I2C || SPI)
40 select BME680_I2C if I2C
46 This driver can also be built as a module. If so, the module for I2C
51 depends on I2C && BME680
61 depends on I2C
65 Say Y here to build I2C interface support for the AMS
[all …]
/OK3568_Linux_fs/kernel/Documentation/driver-api/
H A 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 …]
/OK3568_Linux_fs/u-boot/doc/
H A DI2C_Edge_Conditions1 I2C Edge Conditions:
4 I2C devices may be left in a write state if a read was occuring
9 2) I2C controller issues a start command.
10 3) The I2C writes the device address.
14 1) The I2C controller issues a start command.
15 2) The I2C controller writes the device address.
16 3) The I2C controller writes the offset.
31 !!!THIS IS AN UNDOCUMENTED I2C BUS BUG, NOT A AMCC 4xx BUG!!!
33 This reset edge condition could possibly be present in every I2C
34 controller and device available. For boards where a I2C bus reset
[all …]
/OK3568_Linux_fs/u-boot/doc/device-tree-bindings/i2c/
H A 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
/OK3568_Linux_fs/kernel/drivers/iio/pressure/
H A 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
70 depends on I2C
74 It can be accessed over I2C bus.
94 depends on I2C
[all …]
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/i3c/
H A 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 …]
/OK3568_Linux_fs/kernel/drivers/iio/light/
H A DKconfig27 depends on I2C
38 depends on I2C
48 depends on I2C
58 depends on I2C
68 depends on I2C
81 depends on I2C
83 Say Y here to build I2C interface support for the Avago
91 depends on I2C
106 depends on I2C
116 depends on I2C
[all …]
/OK3568_Linux_fs/kernel/drivers/iio/magnetometer/
H A DKconfig11 depends on I2C
18 AMI306 I2C-based 3-axis magnetometer chips.
25 depends on I2C
38 depends on I2C
50 tristate "Bosch BMC150 I2C Magnetometer Driver"
51 depends on I2C
56 I2C interface.
62 This driver also supports I2C Bosch BMC156 and BMM150 chips.
85 depends on I2C
108 depends on I2C
[all …]

12345678910>>...47