1*4882a593Smuzhiyun# SPDX-License-Identifier: GPL-2.0-only 2*4882a593Smuzhiyunmenuconfig W1 3*4882a593Smuzhiyun tristate "Dallas's 1-wire support" 4*4882a593Smuzhiyun depends on HAS_IOMEM 5*4882a593Smuzhiyun help 6*4882a593Smuzhiyun Dallas' 1-wire bus is useful to connect slow 1-pin devices 7*4882a593Smuzhiyun such as iButtons and thermal sensors. 8*4882a593Smuzhiyun 9*4882a593Smuzhiyun If you want W1 support, you should say Y here. 10*4882a593Smuzhiyun 11*4882a593Smuzhiyun This W1 support can also be built as a module. If so, the module 12*4882a593Smuzhiyun will be called wire. 13*4882a593Smuzhiyun 14*4882a593Smuzhiyunif W1 15*4882a593Smuzhiyun 16*4882a593Smuzhiyunconfig W1_CON 17*4882a593Smuzhiyun depends on CONNECTOR 18*4882a593Smuzhiyun bool "Userspace communication over connector" 19*4882a593Smuzhiyun default y 20*4882a593Smuzhiyun help 21*4882a593Smuzhiyun This allows to communicate with userspace using connector. For more 22*4882a593Smuzhiyun information see <file:Documentation/driver-api/connector.rst>. 23*4882a593Smuzhiyun There are three types of messages between w1 core and userspace: 24*4882a593Smuzhiyun 1. Events. They are generated each time new master or slave device found 25*4882a593Smuzhiyun either due to automatic or requested search. 26*4882a593Smuzhiyun 2. Userspace commands. Includes read/write and search/alarm search commands. 27*4882a593Smuzhiyun 3. Replies to userspace commands. 28*4882a593Smuzhiyun 29*4882a593Smuzhiyunsource "drivers/w1/masters/Kconfig" 30*4882a593Smuzhiyunsource "drivers/w1/slaves/Kconfig" 31*4882a593Smuzhiyun 32*4882a593Smuzhiyunendif # W1 33