11da177e4SLinus Torvaldsmenu "Dallas's 1-wire bus" 21da177e4SLinus Torvalds 31da177e4SLinus Torvaldsconfig W1 41da177e4SLinus Torvalds tristate "Dallas's 1-wire support" 51da177e4SLinus Torvalds ---help--- 646e07f6eSEvgeniy Polyakov Dallas' 1-wire bus is useful to connect slow 1-pin devices 71da177e4SLinus Torvalds such as iButtons and thermal sensors. 81da177e4SLinus Torvalds 91da177e4SLinus Torvalds If you want W1 support, you should say Y here. 101da177e4SLinus Torvalds 111da177e4SLinus Torvalds This W1 support can also be built as a module. If so, the module 121da177e4SLinus Torvalds will be called wire.ko. 131da177e4SLinus Torvalds 1446e07f6eSEvgeniy Polyakovconfig W1_CON 1530841711SEvgeniy Polyakov depends on CONNECTOR && W1 1646e07f6eSEvgeniy Polyakov bool "Userspace communication over connector" 1746e07f6eSEvgeniy Polyakov default y 1846e07f6eSEvgeniy Polyakov --- help --- 1946e07f6eSEvgeniy Polyakov This allows to communicate with userspace using connector [Documentation/connector]. 2046e07f6eSEvgeniy Polyakov There are three types of messages between w1 core and userspace: 2146e07f6eSEvgeniy Polyakov 1. Events. They are generated each time new master or slave device found 2246e07f6eSEvgeniy Polyakov either due to automatic or requested search. 2346e07f6eSEvgeniy Polyakov 2. Userspace commands. Includes read/write and search/alarm search comamnds. 2446e07f6eSEvgeniy Polyakov 3. Replies to userspace commands. 2546e07f6eSEvgeniy Polyakov 26bd529cfbSEvgeniy Polyakovsource drivers/w1/masters/Kconfig 27bd529cfbSEvgeniy Polyakovsource drivers/w1/slaves/Kconfig 280a25e4d5SEvgeniy Polyakov 291da177e4SLinus Torvaldsendmenu 30