Searched full:naming (Results 1 – 25 of 67) sorted by relevance
123
23 Disk name as per file system naming guidelines.
27 Disk name as per file system naming guidelines.
4 # naming convention: "nrf5x" must appear somewhere in the board name
10 * File Naming information.
10 *File Naming information.
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 */
14 * Naming convention: nsi_hots_<fun>() where <func> is the name of the equivalent
37 The naming must follow: <from-line-number>_<to-line-number>, for example:
29 it's related namespace. As such, the disk name follows NVMe naming which is nvme<k>n<n> where k is …
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
89 Naming conventions231 You may use the ``zephyr,`` prefix when naming a devicetree compatible that is
12 * because there is naming conflicts between host and zephyr network stacks.
11 * because there is naming conflicts between host and zephyr network stacks.
105 template API. With the exception of symbol naming ("sflist" instead
581 /* random suffix to avoid naming conflict */ \593 /* random suffix to avoid naming conflict */ \605 /* random suffix to avoid naming conflict */ \
33 * Fix different naming conventions for SAMD20
15 * There exist minor differences between SAM MCU family members in naming
45 /* naming order is intentional. eru1 maps to a lower address than eru0 */
28 * offset. This annotation allows for naming only certain statistics, in stats_get_name()
17 * naming are conventional per existing academic and didactic
102 required. In order to make things consistent, a naming convention has been424 associated pin control configuration is based on variable naming conventions.
48 /** ICANN Rules for TLD naming */
