| /linux/Documentation/ABI/testing/ |
| H A D | debugfs-cros-ec | 5 If the EC supports the CONSOLE_READ command type, this file
6 can be used to grab the EC logs. The kernel polls for the log
14 This file dumps the EC panic information from the previous
16 type is supported by the EC.
31 A u32 providing the time since EC booted in ms. This is
32 is used for synchronizing the AP host time with the EC
34 by the EC or there is a communication problem.
43 an EC with this feature will return a summary of SLP_S0
45 the most recent response from the AP's resume message to the EC.
49 received. Bit 31 is set if the EC attempted to wake the
[all …]
|
| H A D | debugfs-wilco-ec | 18 Write and read raw mailbox commands to the EC.
21 bytes will be sent to the EC. Then, you can read the bytes of
32 // Request EC info type 3 (EC firmware build date)
|
| H A D | debugfs-ec | 6 General information like which GPE is assigned to the EC and whether
8 Knowing the EC GPE one can watch the amount of HW events related to
9 the EC here (XY -> GPE number from `/sys/kernel/debug/ec/*/gpe`):
|
| H A D | sysfs-class-power-wilco | 25 through EC's private PID. Switching to a different mode will
26 be denied by Wilco EC when Long Life mode is enabled.
|
| H A D | sysfs-class-chromeos-driver-cros-ec-vbc | 6 small nvram space on some EC implementations.
|
| /linux/drivers/iio/common/cros_ec_sensors/ |
| H A D | Kconfig | 6 tristate "ChromeOS EC Sensors Core"
11 Base module for the ChromeOS EC Sensors module.
17 tristate "ChromeOS EC Contiguous Sensors"
22 presented by the ChromeOS EC Sensor hub.
26 tristate "ChromeOS EC Sensor for lid angle"
31 This module is loaded when the EC can calculate the angle between the base
35 tristate "ChromeOS EC Activity Sensors"
38 Module to handle activity events presented by the ChromeOS EC sensor hub.
|
| /linux/drivers/platform/chrome/ |
| H A D | Kconfig | 81 Controller (EC) providing keyboard, battery and power services.
83 protocol for talking to the EC is defined by the bus driver.
94 EC through an I2C bus. This uses a simple byte-level protocol with
102 If you say Y here, you get support for talking to the ChromeOS EC
104 checksum. Also since there's no addition EC-to-host interrupt, this
115 If you say Y here, you get support for talking to the ChromeOS EC
128 If you say Y here, you get support for talking to the ChromeOS EC
129 through a SPI bus, using a byte-level protocol. Since the EC's
137 If you say Y here, you get support for talking to the ChromeOS EC
148 If you say Y here, you get support for talking to the ChromeOS EC
[all …]
|
| /linux/drivers/platform/chrome/wilco_ec/ |
| H A D | Kconfig | 9 Wilco EC over an eSPI bus. This uses a simple byte-level protocol
16 tristate "Enable raw access to EC via debugfs"
20 the Wilco EC via debugfs. These commands do not do any byte
26 tristate "Enable event forwarding from EC to userspace"
29 If you say Y here, you get support for the EC to send events
30 (such as power state changes) to userspace. The EC sends the events
35 tristate "Enable querying telemetry data from EC"
38 If you say Y here, you get support to query EC telemetry data from
|
| /linux/Documentation/wmi/devices/ |
| H A D | uniwill-laptop.rst | 10 Many notebooks manufactured by Uniwill (either directly or as ODM) provide a EC interface
14 EC WMI interface description
17 The EC WMI interface description can be decoded from the embedded binary MOF (bmof)
71 This WMI method is used to communicate with the EC. The ``Data`` argument holds the following
79 The first 8 bits of the ``Return`` value contain the data returned by the EC when reading.
80 The special value ``0xFEFEFEFE`` is used to indicate a communication failure with the EC.
87 Reverse-Engineering the EC WMI interface
90 .. warning:: Randomly poking the EC can potentially cause damage to the machine and other unwanted
93 The EC behind the ``GetSetULong`` method is used by the OEM software supplied by the manufacturer.
97 The EC can be accessed under Windows using powershell (requires admin privileges):
[all …]
|
| /linux/drivers/platform/surface/aggregator/ |
| H A D | Kconfig | 11 embedded controller (EC) found on 5th- and later-generation Microsoft
15 Depending on the device in question, this EC provides varying
17 - EC access from ACPI via Surface ACPI Notify (5th- and 6th-generation)
26 is the device responsible for the communication with the EC, and a
27 basic kernel interface exposing the EC functionality to other client
28 drivers, i.e. allowing them to make requests to the EC and receive
34 Note: While 4th-generation Surface devices also make use of a SAM EC,
68 received from the EC, dropped data, and communication timeouts.
|
| /linux/Documentation/driver-api/surface_aggregator/clients/ |
| H A D | dtx.rst | 22 events. Commands are sent to the EC and may have a different implications in
23 different contexts. Events are sent by the EC upon some internal state
25 initiated by the EC.
44 The command is accepted by the EC as a valid command and acknowledged
45 (following the standard communication protocol), but the EC does not act
72 Note that the detachment process is governed fully by the EC. The
73 ``surface_dtx`` driver only relays events from the EC to user-space and
74 commands from user-space to the EC, i.e. it does not influence this process.
80 1. The EC turns on the indicator led on the detach-button, sends a
87 to the EC via IOCTLs provided by this driver.
[all …]
|
| H A D | cdev.rst | 8 User-Space EC Interface (cdev)
13 the SAM EC. It is intended to be used for development and debugging, and
36 essence, callbacks, called when the EC sends an event. They are, in this
41 Notifiers themselves do not enable events on the EC. Thus, it may additionally
44 globally, for the EC and all of its clients (regardless of userspace or
155 ``SSAM_CDEV_EVENT_ENABLE`` IOCTL, before the EC will send them.
|
| /linux/Documentation/driver-api/surface_aggregator/ |
| H A D | overview.rst | 8 embedded controller (EC) on Microsoft Surface devices. It has been originally
19 between host and EC (as detailed below). On 5th (Surface Pro 2017, Surface
48 The type of communication interface between host and EC depends on the
49 generation of the Surface device. On 4th generation devices, host and EC
69 types: Requests, messages sent from host to EC that may trigger a direct
70 response from the EC (explicitly associated with the request), and events
71 (sometimes also referred to as notifications), sent from EC to host without
74 of multiple dedicated requests before they are sent by the EC.
|
| H A D | ssh.rst | 26 embedded Surface Aggregator Module controller (SAM or EC), found on newer
247 the EC as well as by the EC to send responses and events back to the host.
249 EC in response to a request), and events (sent by the EC without a preceding
281 the EC when setting up and enabling an event source (via the
282 enable-event-source request). The EC then uses the specified request ID for
299 target category and command ID alone, the EC may require specific target ID and
312 (although via a python and thus a user-space program), it seems that the EC
324 is exceeded. This is done by the EC for frames with a timeout of one second,
334 the EC is sent again, e.g. due to the host not receiving an |ACK|, the EC
336 by the EC. As an example: Sending two frames with ``SEQ=0`` and ``SEQ=1``
|
| H A D | client.rst | 52 All communication with the SAM EC is handled via the |ssam_controller|
53 representing that EC to the kernel. Drivers targeting a non-SSAM device (and
135 hubs, that have no real representation on the SAM EC and are solely used on
139 a specific device functionality, but has no meaning to the SAM EC. The
162 communication with the EC. There are a couple of ways to define and execute
165 that the caller provides an argument to the SAM EC and receives a response.
170 EC is provided in little-endian format and, similarly, any response payload
191 * they do not correspond to an actual SAM/EC request.
314 To receive events from the SAM EC, an event notifier must be registered for
325 should be enabled, and finally, flags describing how the EC will send these
|
| H A D | internal.rst | 71 around command-type packet payloads, i.e. requests (sent from host to EC),
72 responses of the EC to those requests, and events (sent from EC to host).
82 EC for use in other kernel drivers.
163 re-submitted to this queue due to timeouts or NAK packets sent by the EC.
171 packet) by the EC.
185 the EC, the packet is added to the pending set. Next, the packet's data is
189 unsequenced, i.e. does not require an ACK by the EC, the packet is completed
194 from the EC in parallel. This limit is currently set to one (see
201 Any data received from the EC is put into a FIFO buffer for further
294 separates responses to requests from events, which are also sent by the EC
[all …]
|
| /linux/arch/arm64/boot/dts/rockchip/ |
| H A D | rk3399-gru.dtsi | 27 * - Rails that only connect to the EC (or devices that the EC talks to)
38 * - The EC controls the enable and the EC always enables a rail as
56 /* EC turns on w/ lpddr_pwr_en; always on for AP */
95 /* EC turns on w/ pp5000_en; always on for AP */
113 /* EC turns on w/ ap_core_en; always on for AP */
142 /* EC turns on w/ ap_core_en; always on for AP */
171 /* EC turns on w/ ap_core_en; always on for AP */
191 /* EC turns on w/ pp900_ddrpll_en */
195 /* EC turns on w/ pp900_pll_en */
199 /* EC turns on w/ pp900_pmu_en */
[all …]
|
| H A D | rk3399-gru-chromebook.dtsi | 15 /* EC turns on w/ pp900_ap_en; always on for AP */
24 /* EC turns on w/ pp900_usb_en */
28 /* EC turns on w/ pp900_pcie_en */
58 /* EC turns on w/ ppvar_centerlogic_en; always on for AP */
85 /* EC turns on w/ ppvar_logic_en; always on for AP */
162 /* EC turns on w/ pp3300_usb_en_l */
|
| H A D | rk3399-gru-scarlet.dtsi | 20 /* EC turns on w/ pp1250_s3_en; always on for AP */
49 /* EC turns on w/ pp900_s0_en; always on for AP */
85 /* EC turns on w/ pp900_s3_en; always on for AP */
94 /* EC turns on pp1800_s3_en */
111 /* EC turns on pp3300_s0_en */
115 /* EC turns on pp3300_s3_en */
208 /* EC turns on; alias for pp1800_s0 */
|
| /linux/drivers/staging/nvec/ |
| H A D | README | 4 embedded controller (EC) via I2C bus. The EC is an I2C master while the host
5 processor is the I2C slave. Requests from the host processor to the EC are
|
| H A D | Kconfig | 14 tristate "Keyboard on nVidia compliant EC"
24 tristate "PS2 on nVidia EC"
|
| /linux/drivers/platform/olpc/ |
| H A D | Kconfig | 23 Include support for the OLPC XO Embedded Controller (EC). The EC
|
| /linux/Documentation/firmware-guide/acpi/ |
| H A D | chromeos-acpi-device.rst | 67 - Recovery button was pressed when EC firmware booted. (required if EC EEPROM is
138 Active EC Firmware
159 * - Active EC firmware
161 - The EC firmware which was used during boot.
166 Set to 0 if EC firmware is always read-only.
|
| /linux/Documentation/arch/x86/ |
| H A D | zero-page.rst | 41 1EC/001 ALL secure_boot Secure boot is enabled in the firmware
46 D00/1EC ALL eddbuf EDD data (array of struct edd_info)
|
| /linux/drivers/usb/typec/ucsi/ |
| H A D | Kconfig | 73 tristate "UCSI Driver for ChromeOS EC"
79 This driver enables UCSI support for a ChromeOS EC. The EC is
|