Searched full:naming (Results 1 – 25 of 83) sorted by relevance
1234
4 # naming convention: "nrf5x" must appear somewhere in the board name
10 * File Naming information.
14 * Naming convention: nsi_host_<fun>() where <func> is the name of the equivalent
56 /* Persisting with "wpa_cli" naming for compatibility with Wi-Fi
82 /* SAME51 naming */ in pwm_sam0_set_cycles()86 /* SAMD21 naming */ in pwm_sam0_set_cycles()
20 /* Some SoCs use a slightly different naming scheme */
12 /* Naming of the ETH PTP Config Status changes depending on the stm32 serie */
11 * because there is naming conflicts between host and zephyr network stacks.
49 /* alternate naming */142 /* alternate naming */
30 it's related namespace. As such, the disk name follows NVMe naming which is nvme<k>n<n> where k is …
15 * Variable naming according to LoRaWAN specification:
51 needs to follow a new structure to avoid confusion. Using a consistent naming
20 and &uart_rx_p0_0_u1c1. These nodes are pre-defined and their naming convention is designed
38 * function. These must follow a naming convention. For a system call
188 * Naming concept: lr _<...> => local request machine194 * Naming concept: rr_<...> => remote request machine200 * Naming concept: lp_<...> => local initiated procedure, rp_<...> => remote initiated procedure
95 Naming conventions237 You may use the ``zephyr,`` prefix when naming a devicetree compatible that is
19 * and the naming is from the perspective of the DSP: the "in"
12 * because there is naming conflicts between host and zephyr network stacks.
90 Created your own rulset file for ECLAIR with the following naming format:
110 * Code generation naming:112 * More C keywords are now capitalized to avoid naming collision.115 …* A fix was made to the naming of bstr elements with a .size specifier, which might mean that thes…390 structs, enums and defines that used the ``bt_audio_codec_qos`` name. To use the new naming simply
57 # Translation for the core-isa.h vs. linker section naming conventions
105 template API. With the exception of symbol naming ("sflist" instead
105 **In-code** and **In-text** are the naming contexts of a given status:
36 the unit in Zephyr, that may have different naming in device
15 * There exist minor differences between SAM MCU family members in naming
