| /openbmc/linux/drivers/gpu/drm/display/ |
| H A D | drm_hdmi_helper.c | 88 #define EC(x) ((x) << 2) macro
92 #define HDMI_COLORIMETRY_SMPTE_170M_YCC (C(1) | EC(0) | ACE(0))
93 #define HDMI_COLORIMETRY_BT709_YCC (C(2) | EC(0) | ACE(0))
94 #define HDMI_COLORIMETRY_XVYCC_601 (C(3) | EC(0) | ACE(0))
95 #define HDMI_COLORIMETRY_XVYCC_709 (C(3) | EC(1) | ACE(0))
96 #define HDMI_COLORIMETRY_SYCC_601 (C(3) | EC(2) | ACE(0))
97 #define HDMI_COLORIMETRY_OPYCC_601 (C(3) | EC(3) | ACE(0))
98 #define HDMI_COLORIMETRY_OPRGB (C(3) | EC(4) | ACE(0))
99 #define HDMI_COLORIMETRY_BT2020_CYCC (C(3) | EC(5) | ACE(0))
100 #define HDMI_COLORIMETRY_BT2020_RGB (C(3) | EC(6) | ACE(0))
[all …]
|
| /openbmc/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 | 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.
|
| 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`):
|
| /openbmc/linux/drivers/platform/chrome/wilco_ec/ |
| H A 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
|
| /openbmc/linux/drivers/platform/chrome/ |
| H A D | Kconfig | 70 Controller (EC) providing keyboard, battery and power services.
72 protocol for talking to the EC is defined by the bus driver.
83 EC through an I2C bus. This uses a simple byte-level protocol with
91 If you say Y here, you get support for talking to the ChromeOS EC
93 checksum. Also since there's no addition EC-to-host interrupt, this
104 If you say Y here, you get support for talking to the ChromeOS EC
117 If you say Y here, you get support for talking to the ChromeOS EC
118 through a SPI bus, using a byte-level protocol. Since the EC's
126 If you say Y here, you get support for talking to the ChromeOS EC
136 If you say Y here, you get support for talking to the ChromeOS EC
[all …]
|
| /openbmc/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
|
| /openbmc/u-boot/drivers/input/ |
| H A D | Kconfig | 42 bool "Enable Chrome OS EC keyboard support"
45 Most ARM Chromebooks use an EC to provide access to the keyboard.
46 Messages are used to request key scans from the EC and these are
50 bool "Enable Chrome OS EC keyboard support in SPL"
53 Most ARM Chromebooks use an EC to provide access to the keyboard.
54 Messages are used to request key scans from the EC and these are
58 bool "Enable Chrome OS EC keyboard support in TPL"
61 Most ARM Chromebooks use an EC to provide access to the keyboard.
62 Messages are used to request key scans from the EC and these are
|
| /openbmc/google-misc/subprojects/ncsid/doc/ |
| H A D | ncsid_internals.md | 15 - **EC**. This is the code borrowed from EC. The three state machines are pretty
16 much copied from EC code.
29 ## EC State Machines
31 NC-SId reuses the state machines from EC. They are treated like black boxes.
55 not a part of EC state machines' state:
57 - State Parameters. These structures are allocated outside of EC State Machines,
58 but their content is fully managed by EC State Machines.
79 This component coordinates the interaction between EC State Machines and is also
80 heavily based on EC code. It uses `net::SockIO` interface to interact with the
101 To allow some fairly sophisticated unit-tests, EC State Machines as well as
|
| /openbmc/u-boot/doc/ |
| H A D | README.i2c | 12 AP (Application Processor, meaning the main CPU) and one driven by the EC
19 meaning the AP's, and 'their' claim GPIO, meaning the EC's. This terminology
25 GPIO lines are shared between the AP and EC to manage the bus. The AP and EC
28 - AP_CLAIM: output from AP, signalling to the EC that the AP wants the bus
29 - EC_CLAIM: output from EC, signalling to the AP that the EC wants the bus
48 The same algorithm applies on the EC.
57 In general the traffic is fairly light, and in particular the EC wants access
|
| /openbmc/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.
|
| /openbmc/linux/Documentation/hwmon/ |
| H A 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
|
| H A D | asus_ec_sensors.rst | 37 chip and the ACPI embedded controller (EC) registers. Some of the sensors
38 are only available via the EC.
55 Sensor values are read from EC registers, and to avoid race with the board
57 methods access the EC.
|
| H A D | oxp-sensors.rst | 18 out the EC registers and values to write to since the EC layout and model is
19 different. Aya Neo devices preceding the AIR may not be supportable as the EC
58 to let the EC control de fan speed. Read this attribute to see current status.
|
| /openbmc/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 …]
|
| /openbmc/u-boot/doc/device-tree-bindings/input/ |
| H A D | cros-ec-keyb.txt | 1 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
|
| /openbmc/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.
|
| /openbmc/u-boot/arch/arm/dts/ |
| H A D | rk3399-gru.dtsi | 29 * - Rails that only connect to the EC (or devices that the EC talks to)
40 * - The EC controls the enable and the EC always enables a rail as
58 /* EC turns on w/ lpddr_pwr_en; always on for AP */
97 /* EC turns on w/ pp5000_en; always on for AP */
115 /* EC turns on w/ ap_core_en; always on for AP */
144 /* EC turns on w/ ap_core_en; always on for AP */
173 /* EC turns on w/ ap_core_en; always on for AP */
193 /* EC turns on w/ pp900_ddrpll_en */
197 /* EC turns on w/ pp900_pll_en */
201 /* EC turns on w/ pp900_pmu_en */
[all …]
|
| /openbmc/linux/arch/arm64/boot/dts/rockchip/ |
| H A 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 …]
|
| /openbmc/u-boot/drivers/misc/ |
| H A D | Kconfig | 74 Enable command-line access to the Chrome OS EC (Embedded
76 a number of sub-commands for performing EC tasks such as
78 and talking to the I2C bus behind the EC (if there is one).
81 bool "Enable Chrome OS EC"
83 Enable access to the Chrome OS EC. This is a separate
90 bool "Enable Chrome OS EC I2C driver"
93 Enable I2C access to the Chrome OS EC. This is used on older
95 changed to SPI. The EC will accept commands across the I2C using
99 bool "Enable Chrome OS EC LPC driver"
102 Enable I2C access to the Chrome OS EC. This is used on x86
[all …]
|
| /openbmc/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
|
| /openbmc/u-boot/doc/device-tree-bindings/misc/ |
| H A D | cros-ec.txt | 15 - ec-interrupt : Selects the EC interrupt, defined as a GPIO according
18 containing all 0xff will not be written, since we assume that the EC
22 to the EC (e.g. i2c, spi, lpc). The reg property (as usual) will indicate
|
| /openbmc/qemu/scripts/coccinelle/ |
| H A D | use-error_fatal.cocci | 5 expression ERR, EC, FAIL;
19 - exit(EC);
|
| /openbmc/openbmc-test-automation/redfish/managers/ |
| H A D | test_certificate.robot | 145 Server EC ${EMPTY} prime256v1 ok
146 Server EC ${EMPTY} secp521r1 ok
147 Server EC ${EMPTY} secp384r1 ok
157 Client EC ${EMPTY} prime256v1 ok
158 Client EC ${EMPTY} secp521r1 ok
159 Client EC ${EMPTY} secp384r1 ok
170 Server EC ${EMPTY} ${invalid_value} error
180 Client EC ${EMPTY} ${invalid_value} error
276 # key_pair_algorithm CSR key pair algorithm ("EC" or "RSA")
293 … Run Keyword If '${key_pair_algorithm}' == 'EC' Remove From Dictionary ${payload} KeyBitLength
|