Home
last modified time | relevance | path

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

123456

/Zephyr-Core-3.5.0/subsys/mgmt/ec_host_cmd/backends/
Dec_host_cmd_backend_shi.h13 * Byte codes returned by EC over SPI interface.
15 * These can be used by the AP to debug the EC interface, and to determine
16 * when the EC is not in a state where it will ever get around to responding
19 * Example of sequence of bytes read from EC for a current good transfer:
22 * 3. - - EC starts handling CS# interrupt
24 * 5. EC_SHI_PROCESSING - EC starts processing request; AP is clocking in
26 * 6. - - EC finishes processing and sets up response
31 * 11 - - EC processes CS# interrupt and sets up DMA for
41 * Then the EC found an error in the request, or was not ready for the request
43 * because the EC is unable to tell when the AP is done sending its request.
[all …]
/Zephyr-Core-3.5.0/samples/tfm_integration/psa_crypto/
Duser.pem1 -----BEGIN EC PARAMETERS-----
3 -----END EC PARAMETERS-----
4 -----BEGIN EC PRIVATE KEY-----
8 -----END EC PRIVATE KEY-----
/Zephyr-Core-3.5.0/boards/arm/google_kukui/
DKconfig.board1 # Google Kukui EC
7 bool "Google Kukui EC"
10 This is the EC (Embedded Controller) inside a Lenovo Chromebook
11 Duet and 10e Chromebook Tablet. The EC handles battery charging,
Dgoogle_kukui.dts12 model = "Google Kukui EC";
13 compatible = "google,kukui-ec", "st,stm32f098";
DKconfig.defconfig1 # Google Kukui EC
Dgoogle_kukui.yaml2 name: Google Kukui EC
/Zephyr-Core-3.5.0/soc/arm/microchip_mec/common/reg/
Dmec_acpi_ec.h40 /* ACPI_PM1 RT/EC Status 1 */
45 /* ACPI_PM1 RT/EC Status 2 */
55 /* ACPI_PM1 RT/EC Enable 1 */
60 /* ACPI_PM1 RT/EC Enable 2 */
68 /* ACPI_PM1 RT/EC Control 1 */
73 /* ACPI_PM1 RT/EC Control 2 */
82 /* ACPI_PM1 RT/EC Control 21 */
87 /* ACPI_PM1 RT/EC Control 22 */
92 /* ACPI_PM1 EC PM Status register */
97 /** @brief ACPI EC Registers (ACPI_EC) */
/Zephyr-Core-3.5.0/drivers/espi/
DKconfig.npcx7 bool "Nuvoton NPCX embedded controller (EC) ESPI driver"
18 This is the port size used by the Host and EC to communicate over
20 notice the valid value in npcx ec series for this option is 8/16/32/
24 int "Host I/O peripheral port size for ec host command in npcx series"
28 This is the port size used by the Host and EC to communicate over
30 Please notice the valid value in npcx ec series for this option is
48 EC can accept 1/2/4 bytes of Port 80 data written from the Host in an
DKconfig109 This is the port number used by the Host and EC to communicate over
120 bool "Host peripheral device support EC host command subsystem"
122 Enables Embedded Controller (EC) host command subsystem via eSPI
136 This is the port number used by the Host and EC to communicate over
149 hex "Host I/O peripheral port number for ec host command data"
153 This is the port number used by the Host and EC to communicate over
154 the eSPI peripheral channel to send EC host command data and its
160 hex "Host I/O peripheral port number for ec host command parameters"
164 This is the port number used by the Host and EC to communicate over
DKconfig.xec91 This is the port size used by the Host and EC to communicate over
95 int "Host I/O peripheral port size for ec host command in MEC172X series"
99 This is the port size used by the Host and EC to communicate over
114 bool "SoC ACPI EC 2 over eSPI"
120 bool "SoC ACPI EC 3 over eSPI"
126 bool "SoC ACPI EC 4 over eSPI"
172 bool "Read ACPI EC Event Data in IBF ISR"
175 Enable reading event data in ACPI EC IBF ISR. This is used in OS
DKconfig.it8xxx228 prompt "H2RAM space for ec host command"
125 With this option enabled, EC will send IRQ12 signal to host when the
/Zephyr-Core-3.5.0/soc/x86/intel_ish/utils/
Dbuild_ish_firmware.py7 """Script to pack EC binary with manifest header.
9 Package ecos main FW binary (kernel) and AON task binary into final EC binary
25 help="EC kernel binary to pack, \
26 usually ec.RW.bin or ec.RW.flat.",
29 help="EC aontask binary to pack, \
58 print(" Packing EC image file for ISH")
/Zephyr-Core-3.5.0/subsys/mgmt/ec_host_cmd/
DKconfig17 module-str = ec-host-commands
21 int "Stack size for the EC host command handler thread"
25 int "Buffer size in bytes for TX buffer shared by all EC host commands"
38 int "Buffer size in bytes for RX buffer shared by all EC host commands"
/Zephyr-Core-3.5.0/boards/arm/google_dragonclaw/doc/
Dindex.rst34 follow the `Chromium EC Flashing Documentation`_.
49 .. _Chromium EC Flashing Documentation:
50 https://chromium.googlesource.com/chromiumos/platform/ec#Flashing-via-the-servo-debug-board
/Zephyr-Core-3.5.0/dts/bindings/kscan/
Dite,it8xxx2-kscan.yaml21 when the interrupt is triggered in EC low power mode, it can wakeup
22 EC or not. Via this controller, we set the wakeup trigger edge,
/Zephyr-Core-3.5.0/drivers/flash/
Dflash_ite_it8xxx2.c111 * ECINDAR3-0 are EC-indirect memory address registers. in ramcode_flash_follow_mode()
124 /* Writing 0 to EC-indirect memory data register */ in ramcode_flash_follow_mode()
157 /* Writing 0 to EC-indirect memory data register */ in ramcode_flash_fsce_high()
220 /* enter EC-indirect follow mode */ in ramcode_flash_cmd_write_enable()
226 /* exit EC-indirect follow mode */ in ramcode_flash_cmd_write_enable()
234 /* enter EC-indirect follow mode */ in ramcode_flash_cmd_write_disable()
240 /* exit EC-indirect follow mode */ in ramcode_flash_cmd_write_disable()
275 /* enter EC-indirect follow mode */ in ramcode_flash_cmd_write()
309 /* exit EC-indirect follow mode */ in ramcode_flash_cmd_write()
325 /* enter EC-indirect follow mode */ in ramcode_flash_cmd_erase()
[all …]
/Zephyr-Core-3.5.0/samples/drivers/misc/timeaware_gpio/src/
Dmain.c30 uint64_t tm, ts, ec, ret; in main() local
68 tgpio_pin_read_ts_ec(tgpio_dev, TGPIO_PIN_IN, &ts, &ec); in main()
69 printk("[TGPIO] timestamp: %016llx, event count: %016llx\n", ts, ec); in main()
/Zephyr-Core-3.5.0/boards/arm/google_kukui/doc/
Dindex.rst3 Google Kukui EC
13 Zephyr has support for the STM32-based embedded controller (EC) on-board.
75 `Chromium EC Flashing Documentation`_ for more information.
87 .. _Chromium EC Flashing Documentation:
88 https://chromium.googlesource.com/chromiumos/platform/ec#Flashing-via-the-servo-debug-board
/Zephyr-Core-3.5.0/soc/riscv/riscv-ite/it8xxx2/
Dsoc.c87 * EC div = 6 (FND / 6 = 8 mhz)
119 /* JTAG and EC */ in chip_run_pll_sequence()
213 * interrupt to restore clocks. With this interrupt, EC will not defer in riscv_idle()
228 * it means that EC waked-up by the above issue not an in riscv_idle()
251 * The EC processor(CPU) cannot be in the k_cpu_idle() during in arch_cpu_idle()
253 * the EC processor would be clock gated. in arch_cpu_idle()
298 /* bit3: UART1 belongs to the EC side. */ in ite_it8xxx2_init()
316 /* bit3: UART2 belongs to the EC side. */ in ite_it8xxx2_init()
/Zephyr-Core-3.5.0/samples/boards/google_kukui/
Dsample.yaml6 tags: ec
/Zephyr-Core-3.5.0/soc/arm/nuvoton_npcx/common/
Dsoc_clock.h170 * low-frequency timer before ec entered deep idle state.
176 * system timer by low-frequency timer after ec left deep idle state.
189 * @brief Function to configure system sleep settings. After ec received "wfi"
190 * instruction, ec will enter sleep/deep sleep state for better power
193 * @param is_deep A boolean indicating ec enters deep sleep or sleep state
/Zephyr-Core-3.5.0/dts/bindings/espi/
Dmicrochip,xec-espi-host-dev.yaml57 If bits[14:2] of the address written by the Host to the EC address
59 of the EC address selects which of the two memory regions is accessed.
/Zephyr-Core-3.5.0/boards/arm/olimex_lora_stm32wl_devkit/
Dolimex_lora_stm32wl_devkit_D.overlay2 * Copyright (c) 2023 Kenneth J. Miller <ken@miller.ec>
/Zephyr-Core-3.5.0/boards/arm/npcx7m6fb_evb/doc/
Dindex.rst63 on-chip PLL to generate a resulting EC clock rate of 15 MHz. See Processor clock
86 `Chromium EC Flashing Documentation`_ for more information.
106 .. _Chromium EC Flashing Documentation:
107 https://chromium.googlesource.com/chromiumos/platform/ec#Flashing-via-the-servo-debug-board
/Zephyr-Core-3.5.0/soc/arm/nuvoton_npcx/npcx4/
DKconfig.soc1 # Nuvoton NPCX4 EC series

123456