0001 # SPDX-License-Identifier: GPL-2.0-only
0002 config WILCO_EC
0003 tristate "ChromeOS Wilco Embedded Controller"
0004 depends on X86 || COMPILE_TEST
0005 depends on ACPI && CROS_EC_LPC && LEDS_CLASS
0006 help
0007 If you say Y here, you get support for talking to the ChromeOS
0008 Wilco EC over an eSPI bus. This uses a simple byte-level protocol
0009 with a checksum.
0010
0011 To compile this driver as a module, choose M here: the
0012 module will be called wilco_ec.
0013
0014 config WILCO_EC_DEBUGFS
0015 tristate "Enable raw access to EC via debugfs"
0016 depends on WILCO_EC
0017 help
0018 If you say Y here, you get support for sending raw commands to
0019 the Wilco EC via debugfs. These commands do not do any byte
0020 manipulation and allow for testing arbitrary commands. This
0021 interface is intended for debug only and will not be present
0022 on production devices.
0023
0024 config WILCO_EC_EVENTS
0025 tristate "Enable event forwarding from EC to userspace"
0026 depends on WILCO_EC
0027 help
0028 If you say Y here, you get support for the EC to send events
0029 (such as power state changes) to userspace. The EC sends the events
0030 over ACPI, and a driver queues up the events to be read by a
0031 userspace daemon from /dev/wilco_event using read() and poll().
0032
0033 config WILCO_EC_TELEMETRY
0034 tristate "Enable querying telemetry data from EC"
0035 depends on WILCO_EC
0036 help
0037 If you say Y here, you get support to query EC telemetry data from
0038 /dev/wilco_telem0 using write() and then read().
