Squashed backup commit (no shallow-clone history issues) of xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2 branch, upstream commit 9eece662e) plus all fixes applied to get everpal_defconfig building clean against a modern (GCC 15.2.0) toolchain -- see the previous commit message on the lineage-23.2 branch (also in this repo history is not available here since this is a squashed snapshot; full incremental history lives in the local DL380 checkout and the upstream GitHub remote). Upstream: https://github.com/xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2)
32 lines
970 B
Plaintext
32 lines
970 B
Plaintext
menuconfig W1
|
|
tristate "Dallas's 1-wire support"
|
|
depends on HAS_IOMEM
|
|
---help---
|
|
Dallas' 1-wire bus is useful to connect slow 1-pin devices
|
|
such as iButtons and thermal sensors.
|
|
|
|
If you want W1 support, you should say Y here.
|
|
|
|
This W1 support can also be built as a module. If so, the module
|
|
will be called wire.
|
|
|
|
if W1
|
|
|
|
config W1_CON
|
|
depends on CONNECTOR
|
|
bool "Userspace communication over connector"
|
|
default y
|
|
---help---
|
|
This allows to communicate with userspace using connector. For more
|
|
information see <file:Documentation/connector/connector.txt>.
|
|
There are three types of messages between w1 core and userspace:
|
|
1. Events. They are generated each time new master or slave device found
|
|
either due to automatic or requested search.
|
|
2. Userspace commands. Includes read/write and search/alarm search commands.
|
|
3. Replies to userspace commands.
|
|
|
|
source drivers/w1/masters/Kconfig
|
|
source drivers/w1/slaves/Kconfig
|
|
|
|
endif # W1
|