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