17b3d4f44SNick Crewsconfig WILCO_EC
27b3d4f44SNick Crews	tristate "ChromeOS Wilco Embedded Controller"
327944495SArnd Bergmann	depends on ACPI && X86 && CROS_EC_LPC && CROS_EC_LPC_MEC
47b3d4f44SNick Crews	help
57b3d4f44SNick Crews	  If you say Y here, you get support for talking to the ChromeOS
67b3d4f44SNick Crews	  Wilco EC over an eSPI bus. This uses a simple byte-level protocol
77b3d4f44SNick Crews	  with a checksum.
87b3d4f44SNick Crews
97b3d4f44SNick Crews	  To compile this driver as a module, choose M here: the
107b3d4f44SNick Crews	  module will be called wilco_ec.
11b787bb12SNick Crews
12b787bb12SNick Crewsconfig WILCO_EC_DEBUGFS
13b787bb12SNick Crews	tristate "Enable raw access to EC via debugfs"
14b787bb12SNick Crews	depends on WILCO_EC
15b787bb12SNick Crews	help
16b787bb12SNick Crews	  If you say Y here, you get support for sending raw commands to
17b787bb12SNick Crews	  the Wilco EC via debugfs.  These commands do not do any byte
18b787bb12SNick Crews	  manipulation and allow for testing arbitrary commands.  This
19b787bb12SNick Crews	  interface is intended for debug only and will not be present
20b787bb12SNick Crews	  on production devices.
21f7b0bc5eSNick Crews
22f7b0bc5eSNick Crewsconfig WILCO_EC_EVENTS
23f7b0bc5eSNick Crews	tristate "Enable event forwarding from EC to userspace"
24f7b0bc5eSNick Crews	depends on WILCO_EC
25f7b0bc5eSNick Crews	help
26f7b0bc5eSNick Crews	  If you say Y here, you get support for the EC to send events
27f7b0bc5eSNick Crews	  (such as power state changes) to userspace. The EC sends the events
28f7b0bc5eSNick Crews	  over ACPI, and a driver queues up the events to be read by a
29f7b0bc5eSNick Crews	  userspace daemon from /dev/wilco_event using read() and poll().
30