2019-11-01 13:45:29 +01:00
|
|
|
# I2C configuration options
|
2015-08-26 14:56:43 -07:00
|
|
|
|
|
|
|
|
# Copyright (c) 2015 Intel Corporation
|
2017-01-18 17:01:01 -08:00
|
|
|
# SPDX-License-Identifier: Apache-2.0
|
2015-08-26 14:56:43 -07:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# I2C options
|
|
|
|
|
#
|
2015-09-19 23:20:52 -04:00
|
|
|
menuconfig I2C
|
2023-03-27 14:55:23 +02:00
|
|
|
bool "Inter-Integrated Circuit (I2C) bus drivers"
|
2015-09-19 23:20:52 -04:00
|
|
|
help
|
2017-04-24 11:06:58 +02:00
|
|
|
Enable I2C Driver Configuration
|
2015-08-26 14:56:43 -07:00
|
|
|
|
2017-04-08 00:53:37 +02:00
|
|
|
if I2C
|
|
|
|
|
|
2020-01-08 17:36:01 -05:00
|
|
|
config I2C_SHELL
|
2022-03-09 12:05:12 +01:00
|
|
|
bool "I2C Shell"
|
2020-01-08 17:36:01 -05:00
|
|
|
depends on SHELL
|
|
|
|
|
help
|
|
|
|
|
Enable I2C Shell.
|
|
|
|
|
|
2022-09-07 17:32:34 +03:00
|
|
|
The I2C shell supports scanning, bus recovery, I2C read and write
|
|
|
|
|
operations.
|
2020-01-08 17:36:01 -05:00
|
|
|
|
2021-10-27 15:07:10 -05:00
|
|
|
config I2C_STATS
|
2022-03-09 12:05:12 +01:00
|
|
|
bool "I2C device Stats"
|
2021-10-27 15:07:10 -05:00
|
|
|
depends on STATS
|
|
|
|
|
help
|
|
|
|
|
Enable I2C Stats.
|
|
|
|
|
|
2022-12-21 06:14:45 -08:00
|
|
|
config I2C_DUMP_MESSAGES
|
2023-03-31 18:57:46 +02:00
|
|
|
bool "Log I2C transactions"
|
2022-12-21 06:14:45 -08:00
|
|
|
depends on LOG
|
2023-03-31 18:41:54 +02:00
|
|
|
depends on I2C_LOG_LEVEL_DBG
|
2022-12-21 06:14:45 -08:00
|
|
|
help
|
|
|
|
|
Dump every I2C transaction to the system log as debug level log messages.
|
|
|
|
|
|
2023-03-31 18:57:46 +02:00
|
|
|
config I2C_DUMP_MESSAGES_ALLOWLIST
|
|
|
|
|
bool "Use allowlist for logging of I2C transactions"
|
|
|
|
|
depends on I2C_DUMP_MESSAGES
|
|
|
|
|
depends on DT_HAS_ZEPHYR_I2C_DUMP_ALLOWLIST_ENABLED
|
|
|
|
|
help
|
|
|
|
|
Use allowlist to specify which devices transactions should be logged.
|
|
|
|
|
The allowlist is defined in the devicetree using the compatible string of
|
|
|
|
|
"zephyr,i2c-dump-allowlist" and phandles to the devices that need to be traced.
|
|
|
|
|
Example of devicetree node:
|
|
|
|
|
i2c-dump-allowlist {
|
|
|
|
|
compatible = "zephyr,i2c-dump-allowlist";
|
|
|
|
|
devices = < &display0 >, < &sensor3 >;
|
|
|
|
|
};
|
|
|
|
|
|
2022-05-02 09:41:38 -05:00
|
|
|
config I2C_CALLBACK
|
|
|
|
|
bool "I2C asynchronous callback API"
|
|
|
|
|
help
|
|
|
|
|
API and implementations of i2c_transfer_cb.
|
|
|
|
|
|
2024-08-02 21:21:04 +01:00
|
|
|
config I2C_ALLOW_NO_STOP_TRANSACTIONS
|
|
|
|
|
bool "Allows I2C transfers with no STOP on the last transaction [DEPRECATED]"
|
|
|
|
|
depends on !I2C_NRFX_TWI
|
|
|
|
|
depends on !I2C_NRFX_TWIM
|
|
|
|
|
depends on !I2C_STM32
|
|
|
|
|
depends on !I2C_GD32
|
|
|
|
|
depends on !I2C_ESP32
|
2025-04-24 11:58:21 +08:00
|
|
|
depends on (!I2C_DW || I2C_RTS5912)
|
2024-08-02 21:21:04 +01:00
|
|
|
select DEPRECATED
|
|
|
|
|
help
|
|
|
|
|
Allow I2C transactions with no STOP on the last message. This is
|
|
|
|
|
unsupported and can leave the bus in an unexpected state. The option
|
|
|
|
|
will be removed in Zephyr 4.1.
|
|
|
|
|
|
2023-03-28 16:06:55 -05:00
|
|
|
config I2C_RTIO
|
|
|
|
|
bool "I2C RTIO API"
|
2024-07-01 01:43:41 -06:00
|
|
|
select EXPERIMENTAL
|
2024-02-12 13:11:14 -06:00
|
|
|
select RTIO
|
2024-07-01 01:43:41 -06:00
|
|
|
select RTIO_WORKQ
|
2023-03-28 16:06:55 -05:00
|
|
|
help
|
|
|
|
|
API and implementations of I2C for RTIO
|
|
|
|
|
|
2024-02-06 20:42:40 -06:00
|
|
|
if I2C_RTIO
|
|
|
|
|
config I2C_RTIO_SQ_SIZE
|
|
|
|
|
int "Submission queue size for blocking calls"
|
|
|
|
|
default 4
|
|
|
|
|
help
|
|
|
|
|
Blocking i2c calls when I2C_RTIO is enabled are copied into a per driver
|
|
|
|
|
submission queue. The queue depth determines the number of possible i2c_msg
|
|
|
|
|
structs that may be in the array given to i2c_transfer. A sensible default
|
|
|
|
|
is going to be 4 given the device address, register address, and a value
|
|
|
|
|
to be read or written.
|
|
|
|
|
|
|
|
|
|
config I2C_RTIO_CQ_SIZE
|
|
|
|
|
int "Completion queue size for blocking calls"
|
|
|
|
|
default 4
|
|
|
|
|
help
|
|
|
|
|
Blocking i2c calls when I2C_RTIO is enabled are copied into a per driver
|
|
|
|
|
submission queue. The queue depth determines the number of possible i2c_msg
|
|
|
|
|
structs that may be in the array given to i2c_transfer. A sensible default
|
|
|
|
|
is going to be 4 given the device address, register address, and a value
|
|
|
|
|
to be read or written.
|
|
|
|
|
|
2024-10-18 09:55:25 -05:00
|
|
|
config I2C_RTIO_FALLBACK_MSGS
|
|
|
|
|
int "Number of available i2c_msg structs for the default handler to use"
|
|
|
|
|
default 4
|
|
|
|
|
help
|
|
|
|
|
When RTIO is used with a driver that does not yet implement the submit API
|
|
|
|
|
natively the submissions are converted back to struct i2c_msg values that
|
|
|
|
|
are given to i2c_transfer. This requires some number of msgs be available to convert
|
|
|
|
|
the submissions into on the stack. MISRA rules dictate we must know this in
|
|
|
|
|
advance.
|
|
|
|
|
|
|
|
|
|
In all likelihood 4 is going to work for everyone, but in case you do end up with
|
|
|
|
|
an issue where you are using RTIO, your driver does not implement submit natively,
|
|
|
|
|
and get an error relating to not enough i2c msgs this is the Kconfig to manipulate.
|
|
|
|
|
|
2024-02-06 20:42:40 -06:00
|
|
|
endif # I2C_RTIO
|
|
|
|
|
|
|
|
|
|
|
Kconfig: Use the first default with a satisfied condition
Up until now, Zephyr has patched Kconfig to use the last 'default' with
a satisfied condition, instead of the first one. I'm not sure why the
patch was added (it predates Kconfiglib), but I suspect it's related to
Kconfig.defconfig files.
There are at least three problems with the patch:
1. It's inconsistent with how Kconfig works in other projects, which
might confuse newcomers.
2. Due to oversights, earlier 'range' properties are still preferred,
as well as earlier 'default' properties on choices.
In addition to being inconsistent, this makes it impossible to
override 'range' properties and choice 'default' properties if the
base definition of the symbol/choice already has 'range'/'default'
properties.
I've seen errors caused by the inconsistency, and I suspect there
are more.
3. A fork of Kconfiglib that adds the patch needs to be maintained.
Get rid of the patch and go back to standard Kconfig behavior, as
follows:
1. Include the Kconfig.defconfig files first instead of last in
Kconfig.zephyr.
2. Include boards/Kconfig and arch/<arch>/Kconfig first instead of
last in arch/Kconfig.
3. Include arch/<arch>/soc/*/Kconfig first instead of last in
arch/<arch>/Kconfig.
4. Swap a few other 'source's to preserve behavior for some scattered
symbols with multiple definitions.
Swap 'source's in some no-op cases too, where it might match the
intent.
5. Reverse the defaults on symbol definitions that have more than one
default.
Skip defaults that are mutually exclusive, e.g. where each default
has an 'if <some board>' condition. They are already safe.
6. Remove the prefer-later-defaults patch from Kconfiglib.
Testing was done with a Python script that lists all Kconfig
symbols/choices with multiple defaults, along with a whitelist of fixed
symbols. The script also verifies that there are no "unreachable"
defaults hidden by defaults without conditions
As an additional test, zephyr/.config was generated before and after the
change for several samples and checked to be identical (after sorting).
This commit includes some default-related cleanups as well:
- Simplify some symbol definitions, e.g. where a default has 'if FOO'
when the symbol already has 'depends on FOO'.
- Remove some redundant 'default ""' for string symbols. This is the
implicit default.
Piggyback fixes for swapped ranges on BT_L2CAP_RX_MTU and
BT_L2CAP_TX_MTU (caused by confusing inconsistency).
Piggyback some fixes for style nits too, e.g. unindented help texts.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-30 10:57:47 +02:00
|
|
|
# Include these first so that any properties (e.g. defaults) below can be
|
2019-06-18 14:45:40 -04:00
|
|
|
# overridden (by defining symbols in multiple locations)
|
2024-10-25 09:30:58 -07:00
|
|
|
source "drivers/i2c/target/Kconfig"
|
2025-01-05 13:46:45 +01:00
|
|
|
# zephyr-keep-sorted-start
|
2024-10-25 09:30:58 -07:00
|
|
|
source "drivers/i2c/Kconfig.ambiq"
|
|
|
|
|
source "drivers/i2c/Kconfig.andes_atciic100"
|
2021-07-30 16:50:39 +03:00
|
|
|
source "drivers/i2c/Kconfig.b91"
|
2024-05-10 18:08:51 +08:00
|
|
|
source "drivers/i2c/Kconfig.bcm_iproc"
|
2019-04-23 15:33:18 -05:00
|
|
|
source "drivers/i2c/Kconfig.cc13xx_cc26xx"
|
2025-02-27 10:45:07 +05:30
|
|
|
source "drivers/i2c/Kconfig.cdns"
|
Kconfig: Use the first default with a satisfied condition
Up until now, Zephyr has patched Kconfig to use the last 'default' with
a satisfied condition, instead of the first one. I'm not sure why the
patch was added (it predates Kconfiglib), but I suspect it's related to
Kconfig.defconfig files.
There are at least three problems with the patch:
1. It's inconsistent with how Kconfig works in other projects, which
might confuse newcomers.
2. Due to oversights, earlier 'range' properties are still preferred,
as well as earlier 'default' properties on choices.
In addition to being inconsistent, this makes it impossible to
override 'range' properties and choice 'default' properties if the
base definition of the symbol/choice already has 'range'/'default'
properties.
I've seen errors caused by the inconsistency, and I suspect there
are more.
3. A fork of Kconfiglib that adds the patch needs to be maintained.
Get rid of the patch and go back to standard Kconfig behavior, as
follows:
1. Include the Kconfig.defconfig files first instead of last in
Kconfig.zephyr.
2. Include boards/Kconfig and arch/<arch>/Kconfig first instead of
last in arch/Kconfig.
3. Include arch/<arch>/soc/*/Kconfig first instead of last in
arch/<arch>/Kconfig.
4. Swap a few other 'source's to preserve behavior for some scattered
symbols with multiple definitions.
Swap 'source's in some no-op cases too, where it might match the
intent.
5. Reverse the defaults on symbol definitions that have more than one
default.
Skip defaults that are mutually exclusive, e.g. where each default
has an 'if <some board>' condition. They are already safe.
6. Remove the prefer-later-defaults patch from Kconfiglib.
Testing was done with a Python script that lists all Kconfig
symbols/choices with multiple defaults, along with a whitelist of fixed
symbols. The script also verifies that there are no "unreachable"
defaults hidden by defaults without conditions
As an additional test, zephyr/.config was generated before and after the
change for several samples and checked to be identical (after sorting).
This commit includes some default-related cleanups as well:
- Simplify some symbol definitions, e.g. where a default has 'if FOO'
when the symbol already has 'depends on FOO'.
- Remove some redundant 'default ""' for string symbols. This is the
implicit default.
Piggyback fixes for swapped ranges on BT_L2CAP_RX_MTU and
BT_L2CAP_TX_MTU (caused by confusing inconsistency).
Piggyback some fixes for style nits too, e.g. unindented help texts.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-30 10:57:47 +02:00
|
|
|
source "drivers/i2c/Kconfig.dw"
|
2024-10-25 09:30:58 -07:00
|
|
|
source "drivers/i2c/Kconfig.ene"
|
Kconfig: Use the first default with a satisfied condition
Up until now, Zephyr has patched Kconfig to use the last 'default' with
a satisfied condition, instead of the first one. I'm not sure why the
patch was added (it predates Kconfiglib), but I suspect it's related to
Kconfig.defconfig files.
There are at least three problems with the patch:
1. It's inconsistent with how Kconfig works in other projects, which
might confuse newcomers.
2. Due to oversights, earlier 'range' properties are still preferred,
as well as earlier 'default' properties on choices.
In addition to being inconsistent, this makes it impossible to
override 'range' properties and choice 'default' properties if the
base definition of the symbol/choice already has 'range'/'default'
properties.
I've seen errors caused by the inconsistency, and I suspect there
are more.
3. A fork of Kconfiglib that adds the patch needs to be maintained.
Get rid of the patch and go back to standard Kconfig behavior, as
follows:
1. Include the Kconfig.defconfig files first instead of last in
Kconfig.zephyr.
2. Include boards/Kconfig and arch/<arch>/Kconfig first instead of
last in arch/Kconfig.
3. Include arch/<arch>/soc/*/Kconfig first instead of last in
arch/<arch>/Kconfig.
4. Swap a few other 'source's to preserve behavior for some scattered
symbols with multiple definitions.
Swap 'source's in some no-op cases too, where it might match the
intent.
5. Reverse the defaults on symbol definitions that have more than one
default.
Skip defaults that are mutually exclusive, e.g. where each default
has an 'if <some board>' condition. They are already safe.
6. Remove the prefer-later-defaults patch from Kconfiglib.
Testing was done with a Python script that lists all Kconfig
symbols/choices with multiple defaults, along with a whitelist of fixed
symbols. The script also verifies that there are no "unreachable"
defaults hidden by defaults without conditions
As an additional test, zephyr/.config was generated before and after the
change for several samples and checked to be identical (after sorting).
This commit includes some default-related cleanups as well:
- Simplify some symbol definitions, e.g. where a default has 'if FOO'
when the symbol already has 'depends on FOO'.
- Remove some redundant 'default ""' for string symbols. This is the
implicit default.
Piggyback fixes for swapped ranges on BT_L2CAP_RX_MTU and
BT_L2CAP_TX_MTU (caused by confusing inconsistency).
Piggyback some fixes for style nits too, e.g. unindented help texts.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-30 10:57:47 +02:00
|
|
|
source "drivers/i2c/Kconfig.esp32"
|
2024-10-25 09:30:58 -07:00
|
|
|
source "drivers/i2c/Kconfig.gd32"
|
Kconfig: Use the first default with a satisfied condition
Up until now, Zephyr has patched Kconfig to use the last 'default' with
a satisfied condition, instead of the first one. I'm not sure why the
patch was added (it predates Kconfiglib), but I suspect it's related to
Kconfig.defconfig files.
There are at least three problems with the patch:
1. It's inconsistent with how Kconfig works in other projects, which
might confuse newcomers.
2. Due to oversights, earlier 'range' properties are still preferred,
as well as earlier 'default' properties on choices.
In addition to being inconsistent, this makes it impossible to
override 'range' properties and choice 'default' properties if the
base definition of the symbol/choice already has 'range'/'default'
properties.
I've seen errors caused by the inconsistency, and I suspect there
are more.
3. A fork of Kconfiglib that adds the patch needs to be maintained.
Get rid of the patch and go back to standard Kconfig behavior, as
follows:
1. Include the Kconfig.defconfig files first instead of last in
Kconfig.zephyr.
2. Include boards/Kconfig and arch/<arch>/Kconfig first instead of
last in arch/Kconfig.
3. Include arch/<arch>/soc/*/Kconfig first instead of last in
arch/<arch>/Kconfig.
4. Swap a few other 'source's to preserve behavior for some scattered
symbols with multiple definitions.
Swap 'source's in some no-op cases too, where it might match the
intent.
5. Reverse the defaults on symbol definitions that have more than one
default.
Skip defaults that are mutually exclusive, e.g. where each default
has an 'if <some board>' condition. They are already safe.
6. Remove the prefer-later-defaults patch from Kconfiglib.
Testing was done with a Python script that lists all Kconfig
symbols/choices with multiple defaults, along with a whitelist of fixed
symbols. The script also verifies that there are no "unreachable"
defaults hidden by defaults without conditions
As an additional test, zephyr/.config was generated before and after the
change for several samples and checked to be identical (after sorting).
This commit includes some default-related cleanups as well:
- Simplify some symbol definitions, e.g. where a default has 'if FOO'
when the symbol already has 'depends on FOO'.
- Remove some redundant 'default ""' for string symbols. This is the
implicit default.
Piggyback fixes for swapped ranges on BT_L2CAP_RX_MTU and
BT_L2CAP_TX_MTU (caused by confusing inconsistency).
Piggyback some fixes for style nits too, e.g. unindented help texts.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-30 10:57:47 +02:00
|
|
|
source "drivers/i2c/Kconfig.gpio"
|
2025-01-05 13:46:45 +01:00
|
|
|
source "drivers/i2c/Kconfig.i2c_emul"
|
2024-10-25 09:30:58 -07:00
|
|
|
source "drivers/i2c/Kconfig.ifx_cat1"
|
|
|
|
|
source "drivers/i2c/Kconfig.ifx_xmc4"
|
2024-12-24 14:33:29 +08:00
|
|
|
source "drivers/i2c/Kconfig.it51xxx"
|
2020-12-22 21:29:02 +08:00
|
|
|
source "drivers/i2c/Kconfig.it8xxx2"
|
2019-07-09 15:37:17 +02:00
|
|
|
source "drivers/i2c/Kconfig.litex"
|
2020-05-14 16:35:27 +02:00
|
|
|
source "drivers/i2c/Kconfig.lpc11u6x"
|
2024-10-25 09:30:58 -07:00
|
|
|
source "drivers/i2c/Kconfig.max32"
|
|
|
|
|
source "drivers/i2c/Kconfig.mchp_mss"
|
|
|
|
|
source "drivers/i2c/Kconfig.mcux"
|
2020-08-17 11:41:30 +08:00
|
|
|
source "drivers/i2c/Kconfig.npcx"
|
2024-10-25 09:30:58 -07:00
|
|
|
source "drivers/i2c/Kconfig.nrfx"
|
|
|
|
|
source "drivers/i2c/Kconfig.numaker"
|
2024-10-20 23:57:57 +05:30
|
|
|
source "drivers/i2c/Kconfig.omap"
|
2024-10-25 09:30:58 -07:00
|
|
|
source "drivers/i2c/Kconfig.rcar"
|
2025-01-05 13:46:45 +01:00
|
|
|
source "drivers/i2c/Kconfig.renesas_ra"
|
2024-12-16 12:54:53 +07:00
|
|
|
source "drivers/i2c/Kconfig.renesas_rz"
|
2025-04-24 11:58:21 +08:00
|
|
|
source "drivers/i2c/Kconfig.rts5912"
|
2024-10-25 09:30:58 -07:00
|
|
|
source "drivers/i2c/Kconfig.sam0"
|
|
|
|
|
source "drivers/i2c/Kconfig.sam_twihs"
|
|
|
|
|
source "drivers/i2c/Kconfig.sbcon"
|
2023-02-03 13:40:00 +01:00
|
|
|
source "drivers/i2c/Kconfig.sc18im704"
|
2024-10-25 09:30:58 -07:00
|
|
|
source "drivers/i2c/Kconfig.sedi"
|
|
|
|
|
source "drivers/i2c/Kconfig.sifive"
|
2022-11-10 15:54:31 +01:00
|
|
|
source "drivers/i2c/Kconfig.smartbond"
|
2024-10-25 09:30:58 -07:00
|
|
|
source "drivers/i2c/Kconfig.stm32"
|
2025-01-15 13:29:19 +01:00
|
|
|
source "drivers/i2c/Kconfig.sy1xx"
|
2024-10-25 09:30:58 -07:00
|
|
|
source "drivers/i2c/Kconfig.tca954x"
|
|
|
|
|
source "drivers/i2c/Kconfig.test"
|
2025-03-31 21:34:48 +03:00
|
|
|
source "drivers/i2c/Kconfig.wch"
|
2024-10-25 09:30:58 -07:00
|
|
|
source "drivers/i2c/Kconfig.xec"
|
2023-03-07 16:24:57 -06:00
|
|
|
source "drivers/i2c/Kconfig.xilinx_axi"
|
2025-01-05 13:46:45 +01:00
|
|
|
# zephyr-keep-sorted-stop
|
Kconfig: Use the first default with a satisfied condition
Up until now, Zephyr has patched Kconfig to use the last 'default' with
a satisfied condition, instead of the first one. I'm not sure why the
patch was added (it predates Kconfiglib), but I suspect it's related to
Kconfig.defconfig files.
There are at least three problems with the patch:
1. It's inconsistent with how Kconfig works in other projects, which
might confuse newcomers.
2. Due to oversights, earlier 'range' properties are still preferred,
as well as earlier 'default' properties on choices.
In addition to being inconsistent, this makes it impossible to
override 'range' properties and choice 'default' properties if the
base definition of the symbol/choice already has 'range'/'default'
properties.
I've seen errors caused by the inconsistency, and I suspect there
are more.
3. A fork of Kconfiglib that adds the patch needs to be maintained.
Get rid of the patch and go back to standard Kconfig behavior, as
follows:
1. Include the Kconfig.defconfig files first instead of last in
Kconfig.zephyr.
2. Include boards/Kconfig and arch/<arch>/Kconfig first instead of
last in arch/Kconfig.
3. Include arch/<arch>/soc/*/Kconfig first instead of last in
arch/<arch>/Kconfig.
4. Swap a few other 'source's to preserve behavior for some scattered
symbols with multiple definitions.
Swap 'source's in some no-op cases too, where it might match the
intent.
5. Reverse the defaults on symbol definitions that have more than one
default.
Skip defaults that are mutually exclusive, e.g. where each default
has an 'if <some board>' condition. They are already safe.
6. Remove the prefer-later-defaults patch from Kconfiglib.
Testing was done with a Python script that lists all Kconfig
symbols/choices with multiple defaults, along with a whitelist of fixed
symbols. The script also verifies that there are no "unreachable"
defaults hidden by defaults without conditions
As an additional test, zephyr/.config was generated before and after the
change for several samples and checked to be identical (after sorting).
This commit includes some default-related cleanups as well:
- Simplify some symbol definitions, e.g. where a default has 'if FOO'
when the symbol already has 'depends on FOO'.
- Remove some redundant 'default ""' for string symbols. This is the
implicit default.
Piggyback fixes for swapped ranges on BT_L2CAP_RX_MTU and
BT_L2CAP_TX_MTU (caused by confusing inconsistency).
Piggyback some fixes for style nits too, e.g. unindented help texts.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-30 10:57:47 +02:00
|
|
|
|
2015-10-26 15:56:02 -04:00
|
|
|
config I2C_INIT_PRIORITY
|
2018-02-28 11:27:46 +01:00
|
|
|
int "Init priority"
|
2022-03-11 15:32:34 -06:00
|
|
|
default KERNEL_INIT_PRIORITY_DEVICE
|
2015-10-26 15:56:02 -04:00
|
|
|
help
|
2017-04-24 11:06:58 +02:00
|
|
|
I2C device driver initialization priority.
|
2015-10-26 15:56:02 -04:00
|
|
|
|
2018-09-17 13:24:08 -05:00
|
|
|
|
|
|
|
|
module = I2C
|
|
|
|
|
module-str = i2c
|
|
|
|
|
source "subsys/logging/Kconfig.template.log_config"
|
2016-01-28 15:16:53 -02:00
|
|
|
|
2018-12-12 14:42:39 +01:00
|
|
|
config I2C_GECKO
|
|
|
|
|
bool "Gecko I2C driver"
|
2022-07-20 15:44:42 -05:00
|
|
|
default y
|
|
|
|
|
depends on DT_HAS_SILABS_GECKO_I2C_ENABLED
|
2018-12-12 16:30:00 +01:00
|
|
|
select SOC_GECKO_I2C
|
2024-11-22 13:59:36 +02:00
|
|
|
select PINCTRL if SOC_FAMILY_SILABS_S2
|
2018-12-12 14:42:39 +01:00
|
|
|
help
|
|
|
|
|
Enable the SiLabs Gecko I2C bus driver.
|
|
|
|
|
|
2020-05-10 12:25:38 -03:00
|
|
|
config I2C_SAM_TWIM
|
|
|
|
|
bool "Atmel SAM (TWIM) I2C driver"
|
2022-07-20 15:44:42 -05:00
|
|
|
default y
|
|
|
|
|
depends on DT_HAS_ATMEL_SAM_I2C_TWIM_ENABLED
|
2024-10-31 19:08:31 +01:00
|
|
|
select PINCTRL
|
2020-05-10 12:25:38 -03:00
|
|
|
help
|
|
|
|
|
Enable Atmel SAM MCU Family (TWIM) I2C bus driver.
|
|
|
|
|
|
2018-02-28 11:27:46 +01:00
|
|
|
config I2C_SAM_TWI
|
|
|
|
|
bool "Atmel SAM (TWI) I2C driver"
|
2022-07-20 15:44:42 -05:00
|
|
|
default y
|
|
|
|
|
depends on DT_HAS_ATMEL_SAM_I2C_TWI_ENABLED
|
2024-10-31 19:08:31 +01:00
|
|
|
select PINCTRL
|
2016-11-28 17:37:30 -08:00
|
|
|
help
|
2018-02-28 11:27:46 +01:00
|
|
|
Enable Atmel SAM MCU Family (TWI) I2C bus driver.
|
2016-11-28 17:37:30 -08:00
|
|
|
|
2018-02-28 11:27:46 +01:00
|
|
|
config I2C_MCUX
|
|
|
|
|
bool "MCUX I2C driver"
|
2022-07-20 15:44:42 -05:00
|
|
|
default y
|
|
|
|
|
depends on DT_HAS_NXP_KINETIS_I2C_ENABLED
|
2022-03-07 10:59:15 -06:00
|
|
|
select PINCTRL
|
2016-08-11 17:15:51 -07:00
|
|
|
help
|
2018-02-28 11:27:46 +01:00
|
|
|
Enable the mcux I2C driver.
|
2016-08-11 17:15:51 -07:00
|
|
|
|
2019-01-16 15:11:45 -06:00
|
|
|
config I2C_MCUX_LPI2C
|
|
|
|
|
bool "MCUX LPI2C driver"
|
2022-07-20 15:44:42 -05:00
|
|
|
default y
|
2024-11-24 15:02:38 +07:00
|
|
|
depends on DT_HAS_NXP_LPI2C_ENABLED
|
2022-07-20 15:44:42 -05:00
|
|
|
depends on CLOCK_CONTROL
|
2023-04-19 16:41:53 +02:00
|
|
|
select PINCTRL
|
2019-01-16 15:11:45 -06:00
|
|
|
help
|
|
|
|
|
Enable the mcux LPI2C driver.
|
|
|
|
|
|
2022-06-13 12:10:22 +02:00
|
|
|
config I2C_MCUX_LPI2C_BUS_RECOVERY
|
|
|
|
|
bool "Bus recovery support"
|
|
|
|
|
depends on I2C_MCUX_LPI2C && PINCTRL
|
|
|
|
|
select I2C_BITBANG
|
|
|
|
|
help
|
|
|
|
|
Enable LPI2C driver bus recovery support via GPIO bitbanging.
|
|
|
|
|
|
2018-07-03 17:20:19 +01:00
|
|
|
config I2C_IMX
|
|
|
|
|
bool "i.MX I2C driver"
|
2022-07-20 15:44:42 -05:00
|
|
|
default y
|
|
|
|
|
depends on DT_HAS_FSL_IMX21_I2C_ENABLED
|
2024-09-25 13:02:41 +00:00
|
|
|
select PINCTRL
|
2018-07-03 17:20:19 +01:00
|
|
|
help
|
|
|
|
|
Enable the i.MX I2C driver.
|
|
|
|
|
|
2018-02-28 11:27:46 +01:00
|
|
|
config I2C_CC32XX
|
|
|
|
|
bool "CC32XX I2C driver"
|
2022-07-20 15:44:42 -05:00
|
|
|
default y
|
|
|
|
|
depends on DT_HAS_TI_CC32XX_I2C_ENABLED
|
2023-06-12 13:57:52 +02:00
|
|
|
select PINCTRL
|
2016-11-28 17:37:30 -08:00
|
|
|
help
|
2018-02-28 11:27:46 +01:00
|
|
|
Enable the CC32XX I2C driver.
|
2016-11-28 17:37:30 -08:00
|
|
|
|
2018-02-28 11:27:46 +01:00
|
|
|
config I2C_BITBANG
|
|
|
|
|
bool
|
2016-08-11 17:15:51 -07:00
|
|
|
help
|
2018-02-28 11:27:46 +01:00
|
|
|
Enable library used for software driven (bit banging) I2C support
|
2016-08-11 17:15:51 -07:00
|
|
|
|
2018-02-28 11:27:46 +01:00
|
|
|
config I2C_NIOS2
|
|
|
|
|
bool "Nios-II I2C driver"
|
2022-07-20 15:44:42 -05:00
|
|
|
default y
|
|
|
|
|
depends on DT_HAS_ALTR_NIOS2_I2C_ENABLED
|
2016-08-11 17:15:51 -07:00
|
|
|
help
|
2018-02-28 11:27:46 +01:00
|
|
|
Enable the Nios-II I2C driver.
|
2016-08-11 17:15:51 -07:00
|
|
|
|
2019-04-01 21:09:44 +02:00
|
|
|
config I2C_RV32M1_LPI2C
|
|
|
|
|
bool "RV32M1 LPI2C driver"
|
2022-07-20 15:44:42 -05:00
|
|
|
default y
|
|
|
|
|
depends on DT_HAS_OPENISA_RV32M1_LPI2C_ENABLED
|
|
|
|
|
depends on CLOCK_CONTROL
|
2023-04-19 16:45:15 +02:00
|
|
|
select PINCTRL
|
2019-04-01 21:09:44 +02:00
|
|
|
help
|
|
|
|
|
Enable the RV32M1 LPI2C driver.
|
|
|
|
|
|
2023-11-01 18:32:05 +05:30
|
|
|
config GPIO_I2C_SWITCH
|
|
|
|
|
bool "GPIO controlled I2C bus switch"
|
|
|
|
|
default y
|
|
|
|
|
depends on DT_HAS_GPIO_I2C_SWITCH_ENABLED
|
|
|
|
|
help
|
|
|
|
|
Enable GPIO controlled I2C bus switch driver.
|
|
|
|
|
|
2024-12-12 15:21:46 +08:00
|
|
|
config I2C_NXP_II2C
|
|
|
|
|
bool "NXP i.MX8M serial I2C driver"
|
|
|
|
|
default y
|
|
|
|
|
depends on DT_HAS_NXP_II2C_ENABLED
|
|
|
|
|
help
|
|
|
|
|
Enable the NXP II2C driver.
|
|
|
|
|
|
2017-04-24 11:06:58 +02:00
|
|
|
endif # I2C
|
