30841711c8
If w1 is not enabled, w1_con should not appear in configuration, even if no logic is turned on without w1. W1_CON should depend on W1 also. Signed-off-by: Randy Dunlap <rdunlap@xenotime.net> Signed-off-by: Evgeniy Polyakov <johnpol@2ka.mipt.ru> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
29 lines
925 B
Text
29 lines
925 B
Text
menu "Dallas's 1-wire bus"
|
|
|
|
config W1
|
|
tristate "Dallas's 1-wire support"
|
|
---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.ko.
|
|
|
|
config W1_CON
|
|
depends on CONNECTOR && W1
|
|
bool "Userspace communication over connector"
|
|
default y
|
|
--- help ---
|
|
This allows to communicate with userspace using connector [Documentation/connector].
|
|
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 comamnds.
|
|
3. Replies to userspace commands.
|
|
|
|
source drivers/w1/masters/Kconfig
|
|
source drivers/w1/slaves/Kconfig
|
|
|
|
endmenu
|