8636a1f967
The Kconfig lexer supports special characters such as '.' and '/' in the parameter context. In my understanding, the reason is just to support bare file paths in the source statement. I do not see a good reason to complicate Kconfig for the room of ambiguity. The majority of code already surrounds file paths with double quotes, and it makes sense since file paths are constant string literals. Make it treewide consistent now. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Acked-by: Wolfram Sang <wsa@the-dreams.de> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org> Acked-by: Ingo Molnar <mingo@kernel.org>
32 lines
974 B
Plaintext
32 lines
974 B
Plaintext
menuconfig W1
|
|
tristate "Dallas's 1-wire support"
|
|
depends on HAS_IOMEM
|
|
---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.
|
|
|
|
if W1
|
|
|
|
config W1_CON
|
|
depends on CONNECTOR
|
|
bool "Userspace communication over connector"
|
|
default y
|
|
---help---
|
|
This allows to communicate with userspace using connector. For more
|
|
information see <file:Documentation/connector/connector.txt>.
|
|
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 commands.
|
|
3. Replies to userspace commands.
|
|
|
|
source "drivers/w1/masters/Kconfig"
|
|
source "drivers/w1/slaves/Kconfig"
|
|
|
|
endif # W1
|