xref: /linux/drivers/platform/chrome/wilco_ec/Kconfig (revision b787bb126cbcd73754bcbc055ae9f804ac576e4a)
17b3d4f44SNick Crewsconfig WILCO_EC
27b3d4f44SNick Crews	tristate "ChromeOS Wilco Embedded Controller"
37b3d4f44SNick Crews	depends on ACPI && X86 && CROS_EC_LPC_MEC
47b3d4f44SNick Crews	help
57b3d4f44SNick Crews	  If you say Y here, you get support for talking to the ChromeOS
67b3d4f44SNick Crews	  Wilco EC over an eSPI bus. This uses a simple byte-level protocol
77b3d4f44SNick Crews	  with a checksum.
87b3d4f44SNick Crews
97b3d4f44SNick Crews	  To compile this driver as a module, choose M here: the
107b3d4f44SNick Crews	  module will be called wilco_ec.
11*b787bb12SNick Crews
12*b787bb12SNick Crewsconfig WILCO_EC_DEBUGFS
13*b787bb12SNick Crews	tristate "Enable raw access to EC via debugfs"
14*b787bb12SNick Crews	depends on WILCO_EC
15*b787bb12SNick Crews	help
16*b787bb12SNick Crews	  If you say Y here, you get support for sending raw commands to
17*b787bb12SNick Crews	  the Wilco EC via debugfs.  These commands do not do any byte
18*b787bb12SNick Crews	  manipulation and allow for testing arbitrary commands.  This
19*b787bb12SNick Crews	  interface is intended for debug only and will not be present
20*b787bb12SNick Crews	  on production devices.
21