Home
last modified time | relevance | path

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

12345678910>>...36

/Zephyr-Core-3.7.0/drivers/i2c/
DKconfig.it8xxx25 bool "ITE IT8XXX2 I2C driver"
9 Enable I2C support on it8xxx2_evb.
16 bool "IT8XXX2 I2C FIFO mode"
20 the time between each byte to improve the I2C bus clock
21 stretching during I2C transaction.
22 The I2C controller supports two 32-bytes FIFOs,
24 I2C FIFO mode of it8xxx2 can support I2C APIs including:
30 bool "ITE IT8XXX2 I2C enhance driver"
34 This option can enable the enhance I2C
40 bool "IT8XXX2 I2C command queue mode"
[all …]
DKconfig1 # I2C configuration options
7 # I2C options
9 menuconfig I2C config
10 bool "Inter-Integrated Circuit (I2C) bus drivers"
12 Enable I2C Driver Configuration
14 if I2C
17 bool "I2C Shell"
20 Enable I2C Shell.
22 The I2C shell supports scanning, bus recovery, I2C read and write
26 bool "I2C device Stats"
[all …]
DKconfig.sc18im7045 bool "NXP SC18IM704 I2C controller driver"
10 Enables NXP SC18IM704 I2C controller driver
15 int "SC18IM704 I2C init priority"
18 SC18IM704 I2C controller initialization priority.
23 bool "Verify SC18IM704 I2C transfers"
26 Verify the I2C state register after I2C transfers to detect errors.
DKconfig.ifx_cat11 # Infineon CAT1 I2C configuration options
9 bool "Infineon CAT1 I2C driver"
14 This option enables the I2C driver for Infineon CAT1 family.
17 int "I2C Target data buffer length"
22 Buffer to receive data as an I2C Target.
25 bool "Support Asynchronous I2C driver"
29 Configure the I2C driver to be non-blocking/Asynchronous mode.
DKconfig.xec1 # Microchip XEC I2C configuration options
7 bool "XEC Microchip I2C driver"
11 Enable the Microchip XEC I2C driver.
14 bool "XEC Microchip I2C driver"
18 Enable the Microchip XEC I2C V2 driver.
DKconfig.npcx1 # NPCX I2C driver configuration options
7 bool "Nuvoton NPCX embedded controller (EC) I2C driver"
11 This option enables the I2C driver for NPCX family of
13 Say y if you wish to use I2C modules on NPCX MCU.
16 int "NPCX I2C port init priority"
20 Initialization priority for the I2C port on an NPCX device, must be
DKconfig.ambiq1 # Ambiq SDK I2C
9 bool "AMBIQ I2C driver"
15 Enable driver for Ambiq I2C.
20 bool "AMBIQ APOLLO I2C DMA Support"
22 Enable DMA for Ambiq I2C.
DKconfig.ifx_xmc41 # Infineon XMC4 I2C configuration options
9 bool "Infineon XMC4 I2C driver"
13 This option enables the I2C driver for Infineon XMC4 family.
16 int "I2C Target data buffer length"
21 Buffer to receive data as an I2C Target.
DKconfig.numaker1 # NUMAKER I2C driver configuration options
7 bool "Nuvoton NuMaker I2C driver"
12 This option enables I2C driver for Nuvoton NuMaker family of
14 Say y if you wish to enable NuMaker I2C.
DKconfig.dw5 bool "Design Ware I2C support"
9 Enable the Design Ware I2C driver
12 int "Set the clock speed for I2C"
17 bool "Use I2C integrated DMA for asynchronous transfer"
22 This option enables I2C DMA feature to be used for asynchronous
DKconfig.i2c_emul5 bool "I2C emulator"
10 Enable the I2C emulator driver. This is a fake driver in that it
12 drivers that pretend to be devices on the emulated I2C bus. It is
13 used for testing drivers for I2C devices.
DKconfig.sam05 bool "SAM0 series I2C SERCOM driver"
9 Enable the SAM0 series SERCOM I2C driver.
12 bool "DMA support for SAM0 I2C devices"
16 This enables DMA driven transactions for the I2C peripheral.
DKconfig.rcar1 # Renesas R-Car Gen3 I2C configuration options
7 bool "Renesas R-Car I2C Driver"
11 Enable Renesas R-Car I2C Driver.
DKconfig.sam_twihs1 # sam twihs I2C support
7 bool "Atmel SAM (TWIHS) I2C driver"
12 Enable Atmel SAM MCU Family (TWIHS) I2C bus driver.
Di2c_nrfx_twi.c135 NRF_DT_CHECK_NODE_HAS_PINCTRL_SLEEP(I2C(idx)); \
141 IRQ_CONNECT(DT_IRQN(I2C(idx)), DT_IRQ(I2C(idx), priority), \
157 PINCTRL_DT_DEFINE(I2C(idx)); \
166 .pcfg = PINCTRL_DT_DEV_CONFIG_GET(I2C(idx)), \
168 PM_DEVICE_DT_DEFINE(I2C(idx), twi_nrfx_pm_action); \
169 I2C_DEVICE_DT_DEFINE(I2C(idx), \
171 PM_DEVICE_DT_GET(I2C(idx)), \
DKconfig.esp321 # ESP32 I2C configuration options
8 bool "ESP32 I2C driver"
13 Enables the ESP32 I2C driver
/Zephyr-Core-3.7.0/doc/hardware/peripherals/
Di2c.rst3 Inter-Integrated Circuit (I2C) Bus
11 The terminology used in Zephyr I2C APIs follows that of the
12 `NXP I2C Bus Specification Rev 7.0 <i2c-specification_>`_. These changed
15 `I2C`_ (Inter-Integrated Circuit, pronounced "eye
18 on an I2C bus. Devices on the bus can operate in two roles: as a
20 "target" that responds to transaction commands. A I2C controller on a
26 I2C Controller API
29 Zephyr's I2C controller API is used when an I2C peripheral controls the bus,
31 the most common mode, used to interact with I2C devices like sensors and
34 This API is supported in all in-tree I2C peripheral drivers and is
[all …]
/Zephyr-Core-3.7.0/drivers/i2c/target/
DKconfig1 # I2C Target configuration options
7 # I2C options
10 bool "I2C Target Drivers"
12 Enable I2C Target Driver Configuration
20 I2C Target device driver initialization priority.
23 bool "I2C target driver for buffer mode [EXPERIMENTAL]"
DKconfig.eeprom1 # I2C EEPROM Target configuration options
7 bool "I2C Target EEPROM driver"
9 Enable virtual I2C Target EEPROM driver
12 bool "Set I2C Target EEPROM Address at Runtime"
15 Enable changing virtual I2C Target EEPROM device address at runtime
/Zephyr-Core-3.7.0/tests/drivers/i2c/i2c_target_api/common/
DKconfig1 # I2C target tests common configuration options
7 bool "Virtual I2C Driver for Target development"
8 depends on I2C
10 This driver exposes a virtual I2C driver used to debug virtual
11 I2C target drivers.
/Zephyr-Core-3.7.0/samples/drivers/i2c/custom_target/
DREADME.rst2 :name: I2C Custom Target
5 Setup a custom I2C target on the I2C interface.
10 This sample demonstrates how to setup an I2C custom target on the I2C interface
16 This sample requires an I2C peripheral which is capable of acting as a target.
/Zephyr-Core-3.7.0/samples/boards/stm32/i2c_timing/
DREADME.rst2 :name: STM32 I2C V2 timings
7 This sample simply demonstrate the **get_config** API of the stm32 I2C driver.
8 The I2C peripheral configuration is checked regarding the I2C bitrate which can be:
15 In case of the I2C V2, the I2C peripheral of the STM32 microcontrollers have
16 a TIMING register to write in order to generate the correct I2C clock signal.
17 This value depends on the peripheral clock input and the I2C speed.
21 Because the code sequence to calculate the I2C V2 TIMING value is heavy,
73 I2C timing value, report to the DTS :
76 I2C config : I2C_BITRATE_FAST
/Zephyr-Core-3.7.0/tests/drivers/i2c/i2c_bme688/
DREADME.txt1 I2C bus controller to BME688 sensor test
4 This test verifies I2C target driver API methods
6 I2C speed is set to standard.
/Zephyr-Core-3.7.0/drivers/sensor/adi/adltc2990/
DKconfig1 # ADLTC2990 Quad I2C Voltage, Current and Temperature sensor configuration options
7 bool "ADLTC2990 Quad I2C Voltage, Current and Temperature Monitor"
10 select I2C
13 Quad I2C Voltage, Current and Temperature Monitor.
/Zephyr-Core-3.7.0/tests/drivers/i2c/i2c_target_api/
DREADME.txt1 I2C Target API test
8 This test verifies I2C target driver implementations using two I2C
10 driver that simulates an EEPROM with an I2C bus target interface. Data
11 is pre-loaded into the simulated devices outside the I2C API, and the
15 This test was originally designed for I2C controllers that support both
17 I2C controllers, so this behavior is now opt-in using
25 * Register a simulated EEPROM as a I2C target device on a bus. If
40 or the controller driver has bugs, the test will fail one or more I2C

12345678910>>...36