# SPDX-License-Identifier: GPL-2.0-only config [31mCONFIG_WILCO_EC[0m tristate "ChromeOS Wilco Embedded Controller" depends on [31mCONFIG_ACPI[0m && [31mCONFIG_X86[0m && [31mCONFIG_CROS_EC_LPC[0m help If you say Y here, you get support for talking to the ChromeOS Wilco EC over an eSPI bus. This uses a simple byte-level protocol with a checksum. To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will be called wilco_ec. config [31mCONFIG_WILCO_EC_DEBUGFS[0m tristate "Enable raw access to EC via debugfs" depends on [31mCONFIG_WILCO_EC[0m help If you say Y here, you get support for sending raw commands to the Wilco EC via debugfs. These commands do not do any byte manipulation and allow for testing arbitrary commands. This interface is intended for debug only and will not be present on production devices. config [31mCONFIG_WILCO_EC_EVENTS[0m tristate "Enable event forwarding from EC to userspace" depends on [31mCONFIG_WILCO_EC[0m help If you say Y here, you get support for the EC to send events (such as power state changes) to userspace. The EC sends the events over [31mCONFIG_ACPI[0m, and a driver queues up the events to be read by a userspace daemon from /dev/wilco_event using read() and poll(). config [31mCONFIG_WILCO_EC_TELEMETRY[0m tristate "Enable querying telemetry data from EC" depends on [31mCONFIG_WILCO_EC[0m help If you say Y here, you get support to query EC telemetry data from /dev/wilco_telem0 using write() and then read(). |