Home
last modified time | relevance | path

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

123

/Linux-v5.4/Documentation/ABI/testing/
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
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 …]
Dsysfs-class-chromeos5 Show the EC flash information.
19 Tell the EC to reboot in various ways. Options are:
25 "hibernate": Hibernate the EC.
32 Show the information about the EC software and hardware.
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
31 // Request EC info type 3 (EC firmware build date)
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):
Dsysfs-bus-iio-cros-ec25 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
Dsysfs-class-chromeos-driver-cros-ec-vbc6 small nvram space on some EC implementations.
Dsysfs-class-chromeos-driver-cros-ec-lightbar13 The lightbar is controlled by an embedded controller (EC),
16 from interfering with the other EC functions, the rate at
/Linux-v5.4/drivers/platform/chrome/wilco_ec/
DKconfig7 Wilco EC over an eSPI bus. This uses a simple byte-level protocol
14 tristate "Enable raw access to EC via debugfs"
18 the Wilco EC via debugfs. These commands do not do any byte
24 tristate "Enable event forwarding from EC to userspace"
27 If you say Y here, you get support for the EC to send events
28 (such as power state changes) to userspace. The EC sends the events
33 tristate "Enable querying telemetry data from EC"
36 If you say Y here, you get support to query EC telemetry data from
/Linux-v5.4/drivers/iio/common/cros_ec_sensors/
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-v5.4/Documentation/devicetree/bindings/pwm/
Dgoogle,cros-ec-pwm.txt1 * PWM controlled by ChromeOS EC
3 Google's ChromeOS EC PWM is a simple PWM attached to the Embedded Controller
4 (EC) and controlled via a host-command interface.
6 An EC PWM node should be only found as a sub-node of the EC node (see
/Linux-v5.4/drivers/platform/chrome/
DKconfig69 Controller (EC) providing keyboard, battery and power services.
71 protocol for talking to the EC is defined by the bus driver.
82 EC through an I2C bus. This uses a simple byte-level protocol with
90 If you say Y here, you get support for talking to the ChromeOS EC
92 checksum. Also since there's no addition EC-to-host interrupt, this
103 If you say Y here, you get support for talking to the ChromeOS EC
116 If you say Y here, you get support for talking to the ChromeOS EC
117 through a SPI bus, using a byte-level protocol. Since the EC's
125 If you say Y here, you get support for talking to the ChromeOS EC
126 over an LPC bus, including the LPC Microchip EC (MEC) variant.
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/sound/
Dgoogle,cros-ec-codec.txt1 * Audio codec controlled by ChromeOS EC
3 Google's ChromeOS EC codec is a digital mic codec provided by the
4 Embedded Controller (EC) and is controlled via a host-command interface.
6 An EC codec node should only be found as a sub-node of the EC node (see
/Linux-v5.4/Documentation/devicetree/bindings/mfd/
Dcros-ec.txt3 Google's ChromeOS EC is a Cortex-M device which talks to the AP and
6 The EC can be connect through various means (I2C, SPI, LPC, RPMSG) and the
8 its own driver which connects to the top level interface-agnostic EC driver.
24 - google,cros-ec-spi-pre-delay: Some implementations of the EC need a little
28 - google,cros-ec-spi-msg-delay: Some implementations of the EC require some
30 between transactions is not long enough the EC may not be able to respond
33 for the time required by the EC to get back into a state in which new data
41 - google,has-vbc-nvram: Some implementations of the EC include a small
/Linux-v5.4/Documentation/devicetree/bindings/i2c/
Di2c-cros-ec-tunnel.txt1 I2C bus that tunnels through the ChromeOS EC (cros-ec)
3 On some ChromeOS board designs we've got a connection to the EC (embedded
5 the EC (like a battery and PMIC). To get access to those devices we need
6 to tunnel our i2c commands through the EC.
14 - google,remote-bus: The EC bus we'd like to talk to.
/Linux-v5.4/Documentation/devicetree/bindings/input/
Dcros-ec-keyb.txt1 ChromeOS EC Keyboard
3 Google's ChromeOS EC Keyboard is a simple matrix keyboard implemented on
4 a separate EC (Embedded Controller) device. It provides a message for reading
5 key scans from the EC. These are then converted into keycodes for processing
15 keyboard. This is recommended if the EC does not have its own logic or
/Linux-v5.4/arch/arm64/boot/dts/rockchip/
Drk3399-gru.dtsi23 * - Rails that only connect to the EC (or devices that the EC talks to)
34 * - The EC controls the enable and the EC always enables a rail as
52 /* EC turns on w/ lpddr_pwr_en; always on for AP */
91 /* EC turns on w/ pp5000_en; always on for AP */
109 /* EC turns on w/ ap_core_en; always on for AP */
138 /* EC turns on w/ ap_core_en; always on for AP */
167 /* EC turns on w/ ap_core_en; always on for AP */
187 /* EC turns on w/ pp900_ddrpll_en */
191 /* EC turns on w/ pp900_pll_en */
195 /* EC turns on w/ pp900_pmu_en */
[all …]
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 */
Drk3399-gru-scarlet.dtsi18 /* 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.4/drivers/staging/nvec/
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
DKconfig14 tristate "Keyboard on nVidia compliant EC"
24 tristate "PS2 on nVidia EC"
/Linux-v5.4/Documentation/hwmon/
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
/Linux-v5.4/drivers/platform/olpc/
DKconfig23 Include support for the OLPC XO Embedded Controller (EC). The EC
/Linux-v5.4/drivers/edac/
Dmce_amd.c545 u16 ec = EC(m->status); in decode_mc0_mce()
655 u16 ec = EC(m->status); in decode_mc1_mce()
801 u16 ec = EC(m->status); in decode_mc2_mce()
812 u16 ec = EC(m->status); in decode_mc3_mce()
843 u16 ec = EC(m->status); in decode_mc4_mce()
900 u16 ec = EC(m->status); in decode_mc5_mce()
/Linux-v5.4/Documentation/x86/
Dzero-page.rst39 1EC/001 ALL secure_boot Secure boot is enabled in the firmware
44 D00/1EC ALL eddbuf EDD data (array of struct edd_info)
/Linux-v5.4/Documentation/devicetree/bindings/iio/chemical/
Datlas,ec-sm.txt1 * Atlas Scientific EC-SM OEM sensor

123