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