Home
last modified time | relevance | path

Searched refs:EC (Results 1 – 25 of 92) sorted by relevance

1234

/linux/Documentation/ABI/testing/
A Ddebugfs-cros-ec5 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
49 received. Bit 31 is set if the EC attempted to wake the
51 Callers can use this to detect a wake from the EC due to
[all …]
A Dsysfs-class-chromeos5 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.
A Ddebugfs-wilco-ec18 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)
A Ddebugfs-ec6 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`):
/linux/drivers/platform/chrome/
A DKconfig127 ChromeOS EC communication protocol helpers.
140 tristate "ChromeOS EC miscdevice"
145 ChromeOS EC from userspace via a character device.
162 tristate "ChromeOS EC vboot context support"
173 tristate "Export ChromeOS EC internals in DebugFS"
177 This option exposes the ChromeOS EC device internals to
184 tristate "ChromeOS EC MEMS Sensor Hub"
189 turn query the EC and register the sensors.
202 information from ChromeOS EC.
208 tristate "ChromeOS EC Type-C Connector Control"
[all …]
/linux/drivers/platform/chrome/wilco_ec/
A DKconfig8 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/drivers/iio/common/cros_ec_sensors/
A DKconfig6 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/Documentation/devicetree/bindings/sound/
A Dgoogle,cros-ec-codec.yaml7 title: Audio codec controlled by ChromeOS EC
13 Google's ChromeOS EC codec is a digital mic codec provided by the
14 Embedded Controller (EC) and is controlled via a host-command
15 interface. An EC codec node should only be found inside the "codecs"
29 Physical base address and length of shared memory region from EC.
37 Shared memory region to EC. A "shared-dma-pool".
/linux/Documentation/devicetree/bindings/pwm/
A Dgoogle,cros-ec-pwm.yaml7 title: PWM controlled by ChromeOS EC
14 Google's ChromeOS EC PWM is a simple PWM attached to the Embedded Controller
15 (EC) and controlled via a host-command interface.
16 An EC PWM node should be only found as a sub-node of the EC node (see
/linux/drivers/platform/surface/aggregator/
A DKconfig10 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/Documentation/driver-api/surface_aggregator/clients/
A Ddtx.rst23 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
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.
115 successfully. If the EC fails to open the latch, e.g. due to hardware
306 - EC canceled detachment process.
[all …]
/linux/Documentation/hwmon/
A Dnct6683.rst36 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/Documentation/devicetree/bindings/i2c/
A Dgoogle,cros-ec-i2c-tunnel.yaml8 title: I2C bus that tunnels through the ChromeOS EC (cros-ec)
16 On some ChromeOS board designs we've got a connection to the EC
18 other side of the EC (like a battery and PMIC). To get access to
19 those devices we need to tunnel our i2c commands through the EC.
32 description: The EC bus we'd like to talk to.
/linux/Documentation/driver-api/surface_aggregator/
A Doverview.rst8 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.
A Dssh.rst25 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
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
332 the EC is sent again, e.g. due to the host not receiving an |ACK|, the EC
[all …]
/linux/arch/arm64/boot/dts/rockchip/
A Drk3399-gru.dtsi28 * - 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
192 /* EC turns on w/ pp900_ddrpll_en */
196 /* EC turns on w/ pp900_pll_en */
200 /* EC turns on w/ pp900_pmu_en */
204 /* EC turns on w/ pp1800_s0_en_l */
212 /* EC turns on w/ pp1800_lid_en_l */
216 /* EC turns on w/ lpddr_pwr_en */
220 /* EC turns on w/ pp1800_pmu_en_l */
224 /* EC turns on w/ pp1800_usb_en_l */
[all …]
A Drk3399-gru-chromebook.dtsi15 /* 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 */
/linux/Documentation/devicetree/bindings/display/bridge/
A Dgoogle,cros-ec-anx7688.yaml7 title: ChromeOS EC ANX7688 HDMI to DP Converter through Type-C Port
14 ChromeOS EC ANX7688 is a display bridge that converts HDMI 2.0 to
18 the EC and therefore its node should be a child of an EC I2C tunnel node
/linux/Documentation/devicetree/bindings/iio/proximity/
A Dgoogle,cros-ec-mkbp-proximity.yaml8 title: ChromeOS EC MKBP Proximity Sensor
16 Google's ChromeOS EC sometimes has the ability to detect user proximity.
17 This is implemented on the EC as near/far logic and exposed to the OS
/linux/drivers/staging/nvec/
A DREADME4 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
/linux/Documentation/devicetree/bindings/input/
A Dgoogle,cros-ec-keyb.yaml8 title: ChromeOS EC Keyboard
16 Google's ChromeOS EC Keyboard is a simple matrix keyboard
17 implemented on a separate EC (Embedded Controller) device. It provides
18 a message for reading key scans from the EC. These are then converted
31 if the EC does not have its own logic or hardware for this.
/linux/Documentation/devicetree/bindings/mfd/
A Dgoogle,cros-ec.yaml15 Google's ChromeOS EC is a microcontroller which talks to the AP and
17 The EC can be connected through various interfaces (I2C, SPI, and others)
24 For implementations of the EC is connected through I2C.
27 For implementations of the EC is connected through SPI.
30 For implementations of the EC is connected through RPMSG.
57 Some implementations of the EC include a small nvram space used to
A Dnetronix,ntxec.yaml13 This EC is found in e-book readers of multiple brands (e.g. Kobo, Tolino), and
22 - description: The I2C address of the EC
31 The EC can signal interrupts via a GPIO line
/linux/drivers/platform/olpc/
A DKconfig23 Include support for the OLPC XO Embedded Controller (EC). The EC
/linux/Documentation/devicetree/bindings/regulator/
A Dgoogle,cros-ec-regulator.yaml7 title: ChromeOS EC controlled voltage regulators
25 description: Identifier for the voltage regulator to ChromeOS EC.

Completed in 33 milliseconds

1234