Home
last modified time | relevance | path

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

123

/openbmc/u-boot/drivers/input/
H A DKconfig42 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 Dncsid_internals.md15 - **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
H A Dncsid_test_arch.dot22 ec [label="EC" fillcolor="black" fontcolor="white"];
H A Dncsid_arch.dot27 ec [label="EC" fillcolor="black" fontcolor="white"];
/openbmc/u-boot/doc/
H A DREADME.i2c12 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/u-boot/doc/device-tree-bindings/input/
H A 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
/openbmc/qemu/scripts/coccinelle/
H A Duse-error_fatal.cocci5 expression ERR, EC, FAIL;
19 - exit(EC);
/openbmc/u-boot/doc/device-tree-bindings/misc/
H A Dcros-ec.txt15 - 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
H A Dintel-lpc.txt62 /* Enable EC SMI source */
/openbmc/u-boot/arch/arm/dts/
H A Drk3399-gru.dtsi29 * - 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 …]
H 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 */
/openbmc/u-boot/drivers/misc/
H A DKconfig74 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/openbmc-test-automation/redfish/managers/
H A Dtest_certificate.robot145 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
181 Client EC ${EMPTY} ${invalid_value} error
277 # key_pair_algorithm CSR key pair algorithm ("EC" or "RSA")
297 IF '${key_pair_algorithm}' == 'EC'
/openbmc/u-boot/board/google/
H A DKconfig19 solid state drive. There is a Chrome OS EC connected on LPC,
41 OS EC on this model.
52 Chrome OS EC connected on LPC, and it provides a 2560x1700 high
/openbmc/openbmc/poky/bitbake/lib/toaster/tests/browser/
H A Dtest_layerdetails_page.py17 from selenium.webdriver.support import expected_conditions as EC unknown
169 wait.until(EC.text_to_be_present_in_element(
173 wait.until(EC.text_to_be_present_in_element(
/openbmc/u-boot/board/google/chromebook_samus/
H A DKconfig30 bool "Enable early post to Chrome OS EC"
/openbmc/u-boot/board/google/chromebook_link/
H A DKconfig31 bool "Enable early post to Chrome OS EC"
/openbmc/openbmc-test-automation/redfish/dmtf_tools/
H A Dtest_redfishtool_certificate.robot164 Server EC ${EMPTY} prime256v1 ok
165 Server EC ${EMPTY} secp521r1 ok
166 Server EC ${EMPTY} secp384r1 ok
176 Client EC ${EMPTY} prime256v1 ok
177 Client EC ${EMPTY} secp521r1 ok
178 Client EC ${EMPTY} secp384r1 ok
208 # key_pair_algorithm CSR key pair algorithm ("EC" or "RSA").
225 IF '${key_pair_algorithm}' == 'EC'
/openbmc/u-boot/arch/arm/mach-rockchip/rk3288/
H A DKconfig9 WiFi. It includes a Chrome OS EC (Cortex-M3) to provide access to
29 EC (Cortex-M3) to provide access to the keyboard and battery
40 EC (Cortex-M3) to provide access to the keyboard and battery
/openbmc/google-misc/subprojects/nemora-postd/
H A Devent_message.proto35 // send out codes faster than the EC handles them. While standard values are
/openbmc/u-boot/drivers/i2c/
H A DKconfig29 tristate "Chrome OS EC tunnel I2C bus"
33 the other side of the Chrome OS EC to the I2C bus connected there.
34 This will work whatever the interface used to talk to the EC (SPI,
39 bool "Provide access to LDOs on the Chrome OS EC"
44 the EC. On some unfortunate models (e.g. Spring) the pass-through
47 regulators, via the EC. We implement this as an I2C bus which
/openbmc/u-boot/arch/x86/dts/
H A Dchromebook_samus.dts553 /* Enable EC SMI source */
556 /* EC-SCI is GPIO36 */
618 * the EC
H A Dchromebook_link.dts418 /* Enable EC SMI source */
481 * the EC
/openbmc/u-boot/arch/arm/mach-rockchip/rk3399/
H A DKconfig62 display. It includes a Chrome OS EC (Cortex-M3) to provide access to
/openbmc/webui-vue/src/views/SecurityAndAccess/Certificates/
H A DModalGenerateCsr.vue265 <template v-if="v$.form.keyPairAlgorithm.$model === 'EC'">
416 keyPairAlgorithmOptions: ['EC', 'RSA'],
471 return this.form.keyPairAlgorithm === 'EC';

123