| /linux-6.1.9/drivers/gpu/drm/display/ |
| D | drm_hdmi_helper.c | 90 #define EC(x) ((x) << 2) macro
94 #define HDMI_COLORIMETRY_SMPTE_170M_YCC (C(1) | EC(0) | ACE(0))
95 #define HDMI_COLORIMETRY_BT709_YCC (C(2) | EC(0) | ACE(0))
96 #define HDMI_COLORIMETRY_XVYCC_601 (C(3) | EC(0) | ACE(0))
97 #define HDMI_COLORIMETRY_XVYCC_709 (C(3) | EC(1) | ACE(0))
98 #define HDMI_COLORIMETRY_SYCC_601 (C(3) | EC(2) | ACE(0))
99 #define HDMI_COLORIMETRY_OPYCC_601 (C(3) | EC(3) | ACE(0))
100 #define HDMI_COLORIMETRY_OPRGB (C(3) | EC(4) | ACE(0))
101 #define HDMI_COLORIMETRY_BT2020_CYCC (C(3) | EC(5) | ACE(0))
102 #define HDMI_COLORIMETRY_BT2020_RGB (C(3) | EC(6) | ACE(0))
[all …]
|
| /linux-6.1.9/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`):
|
| /linux-6.1.9/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-6.1.9/drivers/platform/chrome/ |
| 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
127 over an LPC bus, including the LPC Microchip EC (MEC) variant.
[all …]
|
| /linux-6.1.9/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-6.1.9/Documentation/devicetree/bindings/sound/ |
| D | 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"
30 Physical base address and length of shared memory region from EC.
38 Shared memory region to EC. A "shared-dma-pool".
|
| /linux-6.1.9/Documentation/devicetree/bindings/pwm/ |
| D | 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
|
| /linux-6.1.9/drivers/platform/surface/aggregator/ |
| 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.
|
| /linux-6.1.9/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
|
| D | asus_ec_sensors.rst | 33 chip and the ACPI embedded controller (EC) registers. Some of the sensors
34 are only available via the EC.
51 Sensor values are read from EC registers, and to avoid race with the board
53 methods access the EC.
|
| /linux-6.1.9/Documentation/devicetree/bindings/i2c/ |
| D | 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.
31 description: The EC bus we'd like to talk to.
|
| /linux-6.1.9/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 …]
|
| /linux-6.1.9/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 …]
|
| /linux-6.1.9/Documentation/devicetree/bindings/input/ |
| D | 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
26 - description: ChromeOS EC with keyboard and possibly buttons/switches
32 if the EC does not have its own logic or hardware for this.
|
| /linux-6.1.9/Documentation/devicetree/bindings/iio/proximity/ |
| D | google,cros-ec-mkbp-proximity.yaml | 8 title: ChromeOS EC MKBP Proximity Sensor
15 Google's ChromeOS EC sometimes has the ability to detect user proximity.
16 This is implemented on the EC as near/far logic and exposed to the OS
|
| /linux-6.1.9/Documentation/devicetree/bindings/display/bridge/ |
| D | 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
17 the EC and therefore its node should be a child of an EC I2C tunnel node
|
| /linux-6.1.9/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 …]
|
| /linux-6.1.9/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
|
| /linux-6.1.9/Documentation/devicetree/bindings/mfd/ |
| D | netronix,ntxec.yaml | 13 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
|
| D | 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 is connected through I2C.
26 For implementations of the EC is connected through SPI.
29 For implementations of the EC is connected through RPMSG.
52 Some implementations of the EC include a small nvram space used to
|
| /linux-6.1.9/drivers/platform/olpc/ |
| D | Kconfig | 23 Include support for the OLPC XO Embedded Controller (EC). The EC
|