1# SPDX-License-Identifier: GPL-2.0-only
 2config WILCO_EC
 3	tristate "ChromeOS Wilco Embedded Controller"
 4	depends on X86 || COMPILE_TEST
 5	depends on ACPI && CROS_EC_LPC && LEDS_CLASS
 6	help
 7	  If you say Y here, you get support for talking to the ChromeOS
 8	  Wilco EC over an eSPI bus. This uses a simple byte-level protocol
 9	  with a checksum.
10
11	  To compile this driver as a module, choose M here: the
12	  module will be called wilco_ec.
13
14config WILCO_EC_DEBUGFS
15	tristate "Enable raw access to EC via debugfs"
16	depends on WILCO_EC
17	help
18	  If you say Y here, you get support for sending raw commands to
19	  the Wilco EC via debugfs.  These commands do not do any byte
20	  manipulation and allow for testing arbitrary commands.  This
21	  interface is intended for debug only and will not be present
22	  on production devices.
23
24config WILCO_EC_EVENTS
25	tristate "Enable event forwarding from EC to userspace"
26	depends on WILCO_EC
27	help
28	  If you say Y here, you get support for the EC to send events
29	  (such as power state changes) to userspace. The EC sends the events
30	  over ACPI, and a driver queues up the events to be read by a
31	  userspace daemon from /dev/wilco_event using read() and poll().
32
33config WILCO_EC_TELEMETRY
34	tristate "Enable querying telemetry data from EC"
35	depends on WILCO_EC
36	help
37	  If you say Y here, you get support to query EC telemetry data from
38	  /dev/wilco_telem0 using write() and then read().