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