1*012bfdf0SJan Engelhardtmenuconfig W1 21da177e4SLinus Torvalds tristate "Dallas's 1-wire support" 3*012bfdf0SJan Engelhardt depends on HAS_IOMEM 41da177e4SLinus Torvalds ---help--- 546e07f6eSEvgeniy Polyakov Dallas' 1-wire bus is useful to connect slow 1-pin devices 61da177e4SLinus Torvalds such as iButtons and thermal sensors. 71da177e4SLinus Torvalds 81da177e4SLinus Torvalds If you want W1 support, you should say Y here. 91da177e4SLinus Torvalds 101da177e4SLinus Torvalds This W1 support can also be built as a module. If so, the module 111da177e4SLinus Torvalds will be called wire.ko. 121da177e4SLinus Torvalds 13*012bfdf0SJan Engelhardtif W1 14*012bfdf0SJan Engelhardt 1546e07f6eSEvgeniy Polyakovconfig W1_CON 16*012bfdf0SJan Engelhardt depends on CONNECTOR 1746e07f6eSEvgeniy Polyakov bool "Userspace communication over connector" 1846e07f6eSEvgeniy Polyakov default y 1946e07f6eSEvgeniy Polyakov --- help --- 2046e07f6eSEvgeniy Polyakov This allows to communicate with userspace using connector [Documentation/connector]. 2146e07f6eSEvgeniy Polyakov There are three types of messages between w1 core and userspace: 2246e07f6eSEvgeniy Polyakov 1. Events. They are generated each time new master or slave device found 2346e07f6eSEvgeniy Polyakov either due to automatic or requested search. 2409509603SMatt LaPlante 2. Userspace commands. Includes read/write and search/alarm search commands. 2546e07f6eSEvgeniy Polyakov 3. Replies to userspace commands. 2646e07f6eSEvgeniy Polyakov 27bd529cfbSEvgeniy Polyakovsource drivers/w1/masters/Kconfig 28bd529cfbSEvgeniy Polyakovsource drivers/w1/slaves/Kconfig 290a25e4d5SEvgeniy Polyakov 30*012bfdf0SJan Engelhardtendif # W1 31