Lines Matching +full:i2c +full:- +full:protocol

1 # SPDX-License-Identifier: GPL-2.0-only
26 	  If you have an ACPI-compatible Chromebook, say Y or M here.
31 	depends on I2C && DMI && X86
33 	  This driver instantiates i2c and smbus devices such as
47 	  The range of memory used is 0xf00000-0x1000000, traditionally
67 	depends on I2C
73 	  devices that have multiple drop-in options for one component.
83 	  protocol for talking to the EC is defined by the bus driver.
89 	tristate "ChromeOS Embedded Controller (I2C)"
90 	depends on CROS_EC && I2C
94 	  EC through an I2C bus. This uses a simple byte-level protocol with
103 	  through rpmsg. This uses a simple byte-level protocol with a
104 	  checksum. Also since there's no addition EC-to-host interrupt, this
117 	  ISH Transport protocol (ISH-TP). This uses a simple byte-level
118 	  protocol with a checksum.
129 	  through a SPI bus, using a byte-level protocol. Since the EC's
131 	  'pre-amble' bytes before the response actually starts.
138 	  through a UART, using a byte-level protocol.
150 	  This uses a simple byte-level protocol with a checksum. This is
160 	  ChromeOS EC communication protocol helpers.
247 	tristate "ChromeOS EC Type-C Connector Control"
259 	  called cros-ec-typec.
263 	depends on HID && I2C && PM
266 	  human presence sensor (HPS), attached via I2C. The driver supports a
267 	  sensor connected to the I2C bus and exposes it as a character device.
284 	tristate "ChromeOS Type-C power delivery event notifier"
288 	  If you say Y here, you get support for Type-C PD event notifications
303 	  This driver provides the support needed for the in-built electronic
309 	tristate "ChromeOS EC Type-C Switch Control"
313 	  If you say Y here, you get support for configuring the ChromeOS EC Type-C
323 	tristate "Kunit tests for ChromeOS EC protocol" if !KUNIT_ALL_TESTS
328 	  Kunit tests for ChromeOS EC protocol.