blob: c287a9ae4fdd56690444c44a2f6e57269e50cb5a [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001menu "Dallas's 1-wire bus"
2
3config W1
4 tristate "Dallas's 1-wire support"
5 ---help---
Evgeniy Polyakov46e07f62006-04-03 12:01:12 +04006 Dallas' 1-wire bus is useful to connect slow 1-pin devices
Linus Torvalds1da177e2005-04-16 15:20:36 -07007 such as iButtons and thermal sensors.
Evgeniy Polyakov77859252005-05-20 22:33:25 +04008
Linus Torvalds1da177e2005-04-16 15:20:36 -07009 If you want W1 support, you should say Y here.
10
11 This W1 support can also be built as a module. If so, the module
12 will be called wire.ko.
13
Evgeniy Polyakov46e07f62006-04-03 12:01:12 +040014config W1_CON
Evgeniy Polyakov30841712006-04-27 19:40:27 +040015 depends on CONNECTOR && W1
Evgeniy Polyakov46e07f62006-04-03 12:01:12 +040016 bool "Userspace communication over connector"
17 default y
18 --- help ---
19 This allows to communicate with userspace using connector [Documentation/connector].
20 There are three types of messages between w1 core and userspace:
21 1. Events. They are generated each time new master or slave device found
22 either due to automatic or requested search.
Matt LaPlante09509602006-10-03 22:31:37 +020023 2. Userspace commands. Includes read/write and search/alarm search commands.
Evgeniy Polyakov46e07f62006-04-03 12:01:12 +040024 3. Replies to userspace commands.
25
Evgeniy Polyakovbd529cf2005-12-06 13:38:28 +030026source drivers/w1/masters/Kconfig
27source drivers/w1/slaves/Kconfig
Evgeniy Polyakov0a25e4d2005-08-17 15:24:37 +040028
Linus Torvalds1da177e2005-04-16 15:20:36 -070029endmenu