Home
last modified time | relevance | path

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

123

/Zephyr-latest/doc/connectivity/usb/host/api/
Duhc.rst7 :zephyr_file:`include/zephyr/drivers/usb/uhc.h` and referred to
/Zephyr-latest/doc/connectivity/usb/device/api/
Dusb_dc.rst7 :zephyr_file:`include/zephyr/drivers/usb/usb_dc.h` and sometimes referred to
/Zephyr-latest/boards/shields/p3t1755dp_ard_i3c/boards/
Dfrdm_mcxn236.overlay10 * to the J9 on the MCXN236 referred below.
Dmimxrt1180_evk_mimxrt1189_cm7.overlay10 * to the J50 on the RT1180 referred below.
Dmimxrt1180_evk_mimxrt1189_cm33.overlay10 * to the J50 on the RT1180 referred below.
/Zephyr-latest/boards/nordic/thingy53/doc/
Dindex.rst16 Armv8-M Security Extension, running at up to 128 MHz, referred to as
19 a fixed 64 MHz, referred to as the **network core**.
/Zephyr-latest/doc/connectivity/usb/device_next/api/
Dudc.rst7 :zephyr_file:`include/zephyr/drivers/usb/udc.h` and referred to
/Zephyr-latest/boards/nordic/nrf54h20dk/doc/
Dindex.rst20 Extensions, running at up to 320 MHz, referred to as the **application core**
22 Extensions, running at up to 256 MHz, referred to as the **radio core**.
23 * a Nordic VPR RISC-V core, referred to as the **ppr core** (Peripheral
/Zephyr-latest/boards/nxp/mimxrt1180_evk/
Dboard.cmake11 # Details about the usage of SPT on MIMXRT1180-EVK board can be referred on chapter 7 of getting st…
/Zephyr-latest/boards/nordic/nrf5340_audio_dk/doc/
Dindex.rst48 referred to as the **application core**.
50 running at a fixed 64 MHz, referred to as the **network core**.
/Zephyr-latest/doc/hardware/peripherals/
Dfuel_gauge.rst33 specific payload will do a battery cutoff. This battery cutoff is often referred to as ship, shelf,
Dcharger.rst13 The action of charging a battery pack is referred to as a charge cycle. When the charge cycle is
/Zephyr-latest/boards/bbc/microbit/doc/
Dindex.rst6 The Micro Bit (also referred to as BBC Micro Bit, stylized as micro:bit) is an
/Zephyr-latest/boards/raspberrypi/rpi_pico2/doc/
Dindex.rst7 …://www.raspberrypi.com/documentation/microcontrollers/pico-series.html>`_ is referred to as Pico 2.
/Zephyr-latest/boards/bbc/microbit_v2/doc/
Dindex.rst6 The Micro Bit (also referred to as BBC Micro Bit, stylized as micro:bit) is an
/Zephyr-latest/drivers/ethernet/dwc_xgmac/
DKconfig17 This is a driver for the Synopsys DesignWare XGMAC, also referred to
/Zephyr-latest/doc/kernel/services/synchronization/
Devents.rst29 a bitwise fashion. When overwriting the existing set of events, this is referred
30 to as setting. When adding to them in a bitwise fashion, this is referred to as
/Zephyr-latest/drivers/ethernet/
DKconfig.dwmac13 This is a driver for the Synopsys DesignWare MAC, also referred to
/Zephyr-latest/doc/develop/manifest/external/
Dcannectivity.rst12 The firmware implements the Geschwister Schneider USB/CAN device protocol (often referred to as
/Zephyr-latest/doc/develop/languages/c/
Dindex.rst27 1999 release of the ISO C standard (ISO/IEC 9899:1999, hereinafter referred to
39 release of the ISO C standard (ISO/IEC 9899:2011, hereinafter referred to as
/Zephyr-latest/boards/raytac/mdbt53v_db_40/doc/
Dindex.rst15 Armv8-M Security Extension, running at up to 128 MHz, referred to as
18 at a fixed 64 MHz, referred to as the **network core**.
/Zephyr-latest/boards/raytac/mdbt53_db_40/doc/
Dindex.rst15 Armv8-M Security Extension, running at up to 128 MHz, referred to as
18 at a fixed 64 MHz, referred to as the **network core**.
/Zephyr-latest/boards/intel/adsp/doc/
Dintel_adsp_generic.rst32 otherwise stated. You will be referred to the documentation for your specific
165 :zephyr_file:`soc/intel/intel_adsp/tools/cavstool.py` (referred to as the
178 (referred to as its "log port") and services requests on port 10000
181 script (referred to as "cAVS tool client"). It also uses ports 9999 and 10000 on
/Zephyr-latest/boards/others/promicro_nrf52840/doc/
Dindex.rst4 Also referred to as Pro Micro, Promicro, SuperMini nRF52840 boards.
/Zephyr-latest/doc/services/device_mgmt/
Dota.rst12 are still commonly referred to as OTA updates. This approach requires server

123