Home
last modified time | relevance | path

Searched full:ec (Results 1 – 25 of 70) sorted by relevance

123

/Documentation/devicetree/bindings/mfd/
Dgoogle,cros-ec.yaml4 $id: http://devicetree.org/schemas/mfd/google,cros-ec.yaml#
14 Google's ChromeOS EC is a microcontroller which talks to the AP and
16 The EC can be connected through various interfaces (I2C, SPI, and others)
23 For implementations of the EC connected through I2C.
24 const: google,cros-ec-i2c
26 For implementations of the EC connected through SPI.
27 const: google,cros-ec-spi
31 - const: google,cros-ec-fp
32 - const: google,cros-ec-spi
34 For implementations of the EC connected through RPMSG.
[all …]
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
54 ec: embedded-controller@43 {
69 pwms = <&ec 0 50000>;
/Documentation/ABI/testing/
Ddebugfs-cros-ec1 What: /sys/kernel/debug/<cros-ec-device>/console_log
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
10 What: /sys/kernel/debug/<cros-ec-device>/panicinfo
14 This file dumps the EC panic information from the previous
16 type is supported by the EC.
18 What: /sys/kernel/debug/<cros-ec-device>/pdinfo
27 What: /sys/kernel/debug/<cros-ec-device>/uptime
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
[all …]
Dsysfs-class-chromeos1 What: /sys/class/chromeos/<ec-device-name>/flashinfo
5 Show the EC flash information.
7 What: /sys/class/chromeos/<ec-device-name>/kb_wake_angle
15 What: /sys/class/chromeos/<ec-device-name>/reboot
19 Tell the EC to reboot in various ways. Options are:
26 - "hibernate": Hibernate the EC.
29 What: /sys/class/chromeos/<ec-device-name>/version
33 Show the information about the EC software and hardware.
Ddebugfs-ec1 What: /sys/kernel/debug/ec/*/{gpe,use_global_lock,io}
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`):
13 ftp://ftp.suse.com/pub/people/trenn/sources/ec/
Dsysfs-class-chromeos-driver-cros-ec-lightbar1 What: /sys/class/chromeos/<ec-device-name>/lightbar/brightness
9 What: /sys/class/chromeos/<ec-device-name>/lightbar/interval_msec
13 The lightbar is controlled by an embedded controller (EC),
16 from interfering with the other EC functions, the rate at
26 What: /sys/class/chromeos/<ec-device-name>/lightbar/led_rgb
45 What: /sys/class/chromeos/<ec-device-name>/lightbar/program
51 What: /sys/class/chromeos/<ec-device-name>/lightbar/sequence
62 What: /sys/class/chromeos/<ec-device-name>/lightbar/userspace_control
70 What: /sys/class/chromeos/<ec-device-name>/lightbar/version
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)
Dsysfs-class-chromeos-driver-cros-ec-vbc1 What: /sys/class/chromeos/<ec-device-name>/vbc/vboot_context
6 small nvram space on some EC implementations.
/Documentation/devicetree/bindings/i2c/
Dgoogle,cros-ec-i2c-tunnel.yaml5 $id: http://devicetree.org/schemas/i2c/google,cros-ec-i2c-tunnel.yaml#
8 title: I2C bus that tunnels through the ChromeOS EC (cros-ec)
15 On some ChromeOS board designs we've got a connection to the EC
17 other side of the EC (like a battery and PMIC). To get access to
18 those devices we need to tunnel our i2c commands through the EC.
20 The node for this device should be under a cros-ec node like
21 google,cros-ec-spi or google,cros-ec-i2c.
28 const: google,cros-ec-i2c-tunnel
31 description: The EC bus we'd like to talk to.
46 cros-ec@0 {
[all …]
/Documentation/devicetree/bindings/pwm/
Dgoogle,cros-ec-pwm.yaml4 $id: http://devicetree.org/schemas/pwm/google,cros-ec-pwm.yaml#
7 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
17 Documentation/devicetree/bindings/mfd/google,cros-ec.yaml).
27 - const: google,cros-ec-pwm
30 - const: google,cros-ec-pwm-type
47 cros-ec@0 {
48 compatible = "google,cros-ec-spi";
[all …]
/Documentation/devicetree/bindings/sound/
Dgoogle,cros-ec-codec.yaml4 $id: http://devicetree.org/schemas/sound/google,cros-ec-codec.yaml#
7 title: Audio codec controlled by ChromeOS EC
14 Google's ChromeOS EC codec is a digital mic codec provided by the
15 Embedded Controller (EC) and is controlled via a host-command
16 interface. An EC codec node should only be found inside the "codecs"
17 subnode of a cros-ec node.
18 (see Documentation/devicetree/bindings/mfd/google,cros-ec.yaml).
25 const: google,cros-ec-codec
33 Physical base address and length of shared memory region from EC.
41 Shared memory region to EC. A "shared-dma-pool".
[all …]
Dmt8183-mt6358-ts3a227-max98357.txt12 - mediatek,ec-codec: the phandle of EC codecs.
13 See google,cros-ec-codec.txt for more details.
21 mediatek,ec-codec = <&ec_codec>;
/Documentation/devicetree/bindings/extcon/
Dextcon-usbc-cros-ec.yaml4 $id: http://devicetree.org/schemas/extcon/extcon-usbc-cros-ec.yaml#
7 title: ChromeOS EC USB Type-C cable and accessories detection
16 The node for this device must be under a cros-ec node like google,cros-ec-spi
17 or google,cros-ec-i2c.
21 const: google,extcon-usbc-cros-ec
40 cros-ec@0 {
41 compatible = "google,cros-ec-spi";
46 compatible = "google,extcon-usbc-cros-ec";
51 compatible = "google,extcon-usbc-cros-ec";
/Documentation/devicetree/bindings/chrome/
Dgoogle,cros-ec-typec.yaml4 $id: http://devicetree.org/schemas/chrome/google,cros-ec-typec.yaml#
7 title: Google Chrome OS EC(Embedded Controller) Type C port driver.
14 Chrome OS devices have an Embedded Controller(EC) which has access to
17 cros-ec node like google,cros-ec-spi.
21 const: google,cros-ec-typec
46 cros_ec: ec@0 {
47 compatible = "google,cros-ec-spi";
52 compatible = "google,cros-ec-typec";
/Documentation/devicetree/bindings/display/bridge/
Dgoogle,cros-ec-anx7688.yaml4 $id: http://devicetree.org/schemas/display/bridge/google,cros-ec-anx7688.yaml#
7 title: ChromeOS EC ANX7688 HDMI to DP Converter through Type-C Port
13 ChromeOS EC ANX7688 is a display bridge that converts HDMI 2.0 to
16 (See google,cros-ec.yaml). It is accessed using I2C tunneling through
17 the EC and therefore its node should be a child of an EC I2C tunnel node
18 (See google,cros-ec-i2c-tunnel.yaml).
22 const: google,cros-ec-anx7688
54 compatible = "google,cros-ec-i2c-tunnel";
60 compatible = "google,cros-ec-anx7688";
/Documentation/devicetree/bindings/iio/proximity/
Dgoogle,cros-ec-mkbp-proximity.yaml4 $id: http://devicetree.org/schemas/iio/proximity/google,cros-ec-mkbp-proximity.yaml#
7 title: ChromeOS EC MKBP Proximity Sensor
14 Google's ChromeOS EC sometimes has the ability to detect user proximity.
15 This is implemented on the EC as near/far logic and exposed to the OS
20 const: google,cros-ec-mkbp-proximity
33 compatible = "google,cros-ec-mkbp-proximity";
/Documentation/devicetree/bindings/regulator/
Dgoogle,cros-ec-regulator.yaml4 $id: http://devicetree.org/schemas/regulator/google,cros-ec-regulator.yaml#
7 title: ChromeOS EC controlled voltage regulators
21 const: google,cros-ec-regulator
25 description: Identifier for the voltage regulator to ChromeOS EC.
39 cros_ec: ec@0 {
40 compatible = "google,cros-ec-spi";
47 compatible = "google,cros-ec-regulator";
/Documentation/devicetree/bindings/input/
Dgoogle,cros-ec-keyb.yaml5 $id: http://devicetree.org/schemas/input/google,cros-ec-keyb.yaml#
8 title: ChromeOS EC Keyboard
15 Google's ChromeOS EC Keyboard is a simple matrix keyboard
16 implemented on a separate EC (Embedded Controller) device. It provides
17 a message for reading key scans from the EC. These are then converted
24 - description: ChromeOS EC with only buttons/switches
25 const: google,cros-ec-keyb-switches
26 - description: ChromeOS EC with keyboard and possibly buttons/switches
27 const: google,cros-ec-keyb
32 if the EC does not have its own logic or hardware for this.
[all …]
/Documentation/devicetree/bindings/remoteproc/
Dmtk,scp.yaml60 cros-ec-rpmsg:
61 $ref: /schemas/mfd/google,cros-ec.yaml
128 cros-ec-rpmsg:
129 $ref: /schemas/mfd/google,cros-ec.yaml
224 cros-ec-rpmsg {
225 compatible = "google,cros-ec-rpmsg";
226 mediatek,rpmsg-name = "cros-ec-rpmsg";
246 cros-ec-rpmsg {
247 compatible = "google,cros-ec-rpmsg";
248 mediatek,rpmsg-name = "cros-ec-rpmsg";
[all …]
/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
64 ASRock X570 NCT6683D EC firmware version 1.0 build 06/28/19
65 ASRock X670E NCT6686D EC firmware version 1.0 build 05/19/22
66 MSI B550 NCT6687D EC firmware version 1.0 build 05/07/20
67 MSI X670-P NCT6687D EC firmware version 0.0 build 09/27/22
Dasus_ec_sensors.rst39 chip and the ACPI embedded controller (EC) registers. Some of the sensors
40 are only available via the EC.
57 Sensor values are read from EC registers, and to avoid race with the board
59 methods access the EC.
/Documentation/driver-api/surface_aggregator/clients/
Ddtx.rst22 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 …]
/Documentation/devicetree/bindings/platform/
Dlenovo,yoga-c630-ec.yaml4 $id: http://devicetree.org/schemas/platform/lenovo,yoga-c630-ec.yaml#
14 (EC) which handles things such as battery and USB Type-C. This binding
15 describes the interface, on an I2C bus, to this EC.
19 const: lenovo,yoga-c630-ec
60 compatible = "lenovo,yoga-c630-ec";
Dacer,aspire1-ec.yaml4 $id: http://devicetree.org/schemas/platform/acer,aspire1-ec.yaml#
19 const: acer,aspire1-ec
45 compatible = "acer,aspire1-ec";
/Documentation/driver-api/surface_aggregator/
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.

123