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