| /Linux-v5.15/Documentation/ABI/testing/ |
| 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 …]
|
| D | sysfs-class-chromeos | 5 Show the EC flash information.
19 Tell the EC to reboot in various ways. Options are:
26 - "hibernate": Hibernate the EC.
33 Show the information about the EC software and hardware.
|
| 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)
|
| 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`):
|
| D | sysfs-bus-iio-cros-ec | 25 This attribute is exposed by the CrOS EC sensors driver and
26 represents the sensor ID as exposed by the EC. This ID is used
|
| D | sysfs-class-power-wilco | 25 through EC's private PID. Swiching to a different mode will
26 be denied by Wilco EC when Long Life mode is enabled.
|
| /Linux-v5.15/drivers/platform/chrome/ |
| D | Kconfig | 59 Controller (EC) providing keyboard, battery and power services.
61 protocol for talking to the EC is defined by the bus driver.
72 EC through an I2C bus. This uses a simple byte-level protocol with
80 If you say Y here, you get support for talking to the ChromeOS EC
82 checksum. Also since there's no addition EC-to-host interrupt, this
93 If you say Y here, you get support for talking to the ChromeOS EC
106 If you say Y here, you get support for talking to the ChromeOS EC
107 through a SPI bus, using a byte-level protocol. Since the EC's
115 If you say Y here, you get support for talking to the ChromeOS EC
116 over an LPC bus, including the LPC Microchip EC (MEC) variant.
[all …]
|
| /Linux-v5.15/drivers/platform/chrome/wilco_ec/ |
| D | Kconfig | 8 Wilco EC over an eSPI bus. This uses a simple byte-level protocol
15 tristate "Enable raw access to EC via debugfs"
19 the Wilco EC via debugfs. These commands do not do any byte
25 tristate "Enable event forwarding from EC to userspace"
28 If you say Y here, you get support for the EC to send events
29 (such as power state changes) to userspace. The EC sends the events
34 tristate "Enable querying telemetry data from EC"
37 If you say Y here, you get support to query EC telemetry data from
|
| /Linux-v5.15/drivers/iio/common/cros_ec_sensors/ |
| 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
|
| /Linux-v5.15/drivers/platform/surface/aggregator/ |
| D | Kconfig | 10 embedded controller (EC) found on 5th- and later-generation Microsoft
14 Depending on the device in question, this EC provides varying
16 - EC access from ACPI via Surface ACPI Notify (5th- and 6th-generation)
25 is the device responsible for the communication with the EC, and a
26 basic kernel interface exposing the EC functionality to other client
27 drivers, i.e. allowing them to make requests to the EC and receive
33 Note: While 4th-generation Surface devices also make use of a SAM EC,
67 received from the EC, dropped data, and communication timeouts.
|
| /Linux-v5.15/Documentation/hwmon/ |
| D | nct6683.rst | 36 Limit register locations on Intel boards with EC firmware version 1.0
61 Intel DH87RL NCT6683D EC firmware version 1.0 build 04/03/13
62 Intel DH87MC NCT6683D EC firmware version 1.0 build 04/03/13
63 Intel DB85FL NCT6683D EC firmware version 1.0 build 04/03/13
64 ASRock X570 NCT6683D EC firmware version 1.0 build 06/28/19
65 MSI B550 NCT6687D EC firmware version 1.0 build 05/07/20
|
| /Linux-v5.15/Documentation/driver-api/surface_aggregator/clients/ |
| 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 …]
|
| 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-v5.15/Documentation/driver-api/surface_aggregator/ |
| 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.
|
| D | ssh.rst | 25 embedded Surface Aggregator Module controller (SAM or EC), found on newer
224 - Target ID for outgoing (host to EC) commands.
228 - Target ID for incoming (EC to host) commands.
246 the EC as well as by the EC to send responses and events back to the host.
248 EC in response to a request), and events (sent by the EC without a preceding
280 the EC when setting up and enabling an event source (via the
281 enable-event-source request). The EC then uses the specified request ID for
289 (``TID``). This target ID is split into output (host to EC) and input (EC to
295 field, as responses are generally sent from the EC to the host).
298 by target category and command ID alone, the EC may require specific
[all …]
|
| D | client.rst | 50 All communication with the SAM EC is handled via the |ssam_controller|
51 representing that EC to the kernel. Drivers targeting a non-SSAM device (and
133 hubs, that have no real representation on the SAM EC and are solely used on
137 a specific device functionality, but has no meaning to the SAM EC. The
160 communication with the EC. There are a couple of ways to define and execute
163 that the caller provides an argument to the SAM EC and receives a response.
168 EC is provided in little-endian format and, similarly, any response payload
189 * they do not correspond to an actual SAM/EC request.
312 To receive events from the SAM EC, an event notifier must be registered for
321 should be enabled, and finally, flags describing how the EC will send these
|
| 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-v5.15/arch/arm64/boot/dts/rockchip/ |
| D | rk3399-gru.dtsi | 28 * - Rails that only connect to the EC (or devices that the EC talks to)
39 * - The EC controls the enable and the EC always enables a rail as
57 /* EC turns on w/ lpddr_pwr_en; always on for AP */
96 /* EC turns on w/ pp5000_en; always on for AP */
114 /* EC turns on w/ ap_core_en; always on for AP */
143 /* EC turns on w/ ap_core_en; always on for AP */
172 /* EC turns on w/ ap_core_en; always on for AP */
192 /* EC turns on w/ pp900_ddrpll_en */
196 /* EC turns on w/ pp900_pll_en */
200 /* EC turns on w/ pp900_pmu_en */
[all …]
|
| 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 */
|
| D | rk3399-gru-scarlet.dtsi | 18 /* EC turns on w/ pp1250_s3_en; always on for AP */
47 /* EC turns on w/ pp900_s0_en; always on for AP */
83 /* EC turns on w/ pp900_s3_en; always on for AP */
92 /* EC turns on pp1800_s3_en */
109 /* EC turns on pp3300_s0_en */
113 /* EC turns on pp3300_s3_en */
207 /* EC turns on; alias for pp1800_s0 */
|
| /Linux-v5.15/drivers/staging/nvec/ |
| 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
|
| D | Kconfig | 14 tristate "Keyboard on nVidia compliant EC"
24 tristate "PS2 on nVidia EC"
|
| /Linux-v5.15/drivers/platform/olpc/ |
| D | Kconfig | 23 Include support for the OLPC XO Embedded Controller (EC). The EC
|
| /Linux-v5.15/drivers/edac/ |
| D | mce_amd.c | 645 u16 ec = EC(m->status); in decode_mc0_mce()
755 u16 ec = EC(m->status); in decode_mc1_mce()
901 u16 ec = EC(m->status); in decode_mc2_mce()
912 u16 ec = EC(m->status); in decode_mc3_mce()
943 u16 ec = EC(m->status); in decode_mc4_mce()
1000 u16 ec = EC(m->status); in decode_mc5_mce()
|
| /Linux-v5.15/Documentation/x86/ |
| D | zero-page.rst | 39 1EC/001 ALL secure_boot Secure boot is enabled in the firmware
44 D00/1EC ALL eddbuf EDD data (array of struct edd_info)
|
