| /Zephyr-latest/ |
| D | LICENSE | 12 "Licensor" shall mean the copyright owner or entity authorized by
16 other entities that control, are controlled by, or are under common
18 "control" means (i) the power, direct or indirect, to cause the
19 direction or management of such entity, whether by contract or
20 otherwise, or (ii) ownership of fifty percent (50%) or more of the
21 outstanding shares, or (iii) beneficial ownership of such entity.
23 "You" (or "Your") shall mean an individual or Legal Entity
31 transformation or translation of a Source form, including but
35 "Work" shall mean the work of authorship, whether in Source or
37 copyright notice that is included in or attached to the work
[all …]
|
| D | CODE_OF_CONDUCT.md | 7 size, visible or invisible disability, ethnicity, sex characteristics, gender
9 nationality, personal appearance, race, caste, color, religion, or sexual
30 * The use of sexualized language or imagery, and sexual attention or advances of
32 * Trolling, insulting or derogatory comments, and personal or political attacks
33 * Public or private harassment
34 * Publishing others' private information, such as a physical or email address,
44 or harmful.
46 Community leaders have the right and responsibility to remove, edit, or reject
56 posting via an official social media account, or acting as an appointed
57 representative at an online or offline event.
[all …]
|
| /Zephyr-latest/boards/adi/max32672fthr/doc/ |
| D | index.rst | 36 - Dual- or Single-Supply Operation, 1.7V to 3.6V
52 - Wake from LPUART or LPTMR
138 | 5 | P0_11 | GPIO or Analog Input (AIN3 channel). …
140 | 6 | P0_12 | GPIO or Analog Input (AIN4 channel). …
142 | 7 | P0_13 | GPIO or Analog Input (AIN5 channel). …
144 | 8 | P0_22 | GPIO or ADC_TRIG signal. …
146 | 9 | P0_27 | GPIO or QERR signal. …
148 | 10 | P0_26 | GPIO or QDIR signal. …
150 | 11 | P0_16 | GPIO or SPI1 clock signal. …
152 | 12 | P0_15 | GPIO or SPI1 MOSI signal. …
[all …]
|
| /Zephyr-latest/tests/ztest/fail/ |
| D | README.rst | 11 :ref:`native_sim <native_sim>` or :ref:`unit_testing <ztest_unit_testing>`
13 - ``ztest_test_fail()`` during either the ``after`` or ``teardown`` phase of the test suite
14 - ``ztest_test_skip()`` during either the ``after`` or ``teardown`` phase of the test suite
15 - ``ztest_test_pass()`` during either the ``after`` or ``teardown`` phase of the test suite
17 Note that these can be called indirectly through failed asserts or assumptions.
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | video.rst | 14 A video device is the abstraction of a hardware or software video function,
15 which can produce, process, consume or transform video data. The video API is
22 Each video device can have one or more endpoints. Output endpoints configure
32 endpoint for filling (input ep) or consuming (output ep) operation, once
34 release or reuse.
41 controls available which can be generic, related to a device class or vendor
|
| D | fuel_gauge.rst | 21 or present-time current/voltage.
23 Properties are fetched by the client one at a time using :c:func:`fuel_gauge_get_prop`, or fetched
26 Properties are set by the client one at a time using :c:func:`fuel_gauge_set_prop`, or set in a
34 or sleep mode due to its utility in reducing battery drain while devices are stored or shipped.
|
| D | charger.rst | 8 A charger device, or charger peripheral, is a device used to take external power provided to the
10 The charger device can exist as a module, an integrated circuit, or as a functional block in a power
26 A charge cycle is initiated or terminated using :c:func:`charger_charge_enable`.
31 Fundamentally, a property is a configurable setting, state, or quantity that a charger device can
35 or present-time current/voltage.
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | overview.rst | 10 isolated from other user mode threads and from the kernel. A flawed or
11 malicious user mode thread cannot leak or modify the private data/resources
12 of another thread or the kernel, and cannot interfere with or
13 control another user mode thread or the kernel.
18 could otherwise silently or spectacularly corrupt the system.
21 protocols, and filesystems such that malicious third-party code or data
22 cannot compromise the kernel or other threads.
26 isolated from each other if one crashes or is otherwise compromised.
34 - We prevent access to memory not specifically granted, or incorrect access to
48 by a supervisor thread, or thread stacks used to handle system call
[all …]
|
| /Zephyr-latest/drivers/sensor/microchip/mchp_tach_xec/ |
| D | Kconfig | 26 bool "Configure 9 tach edges or 4 tach periods"
29 bool "Configure 5 tach edges or 2 tach periods"
32 bool "Configure 3 tach edges or 1 tach period"
35 bool "Configure 2 tach edges or 1/2 tach period"
|
| /Zephyr-latest/soc/altr/zephyr_nios2f/cpu/ |
| D | ghrd_10m50da.qpf | 7 # (including device programming or simulation files), and any
8 # associated documentation or information are expressly subject
11 # the Altera MegaCore Function License Agreement, or other
14 # devices manufactured by Altera and sold by Altera or its
|
| /Zephyr-latest/doc/project/ |
| D | dev_env_and_tools.rst | 18 and linked to any relevant :ref:`bug or feature tracking issues<bug_reporting>`
22 submitting a change or an enhancement to any Zephyr component, a developer
35 or timezone. We have developers and contributors from across the globe. When
41 addressed with general reviews and do not need to be queued for a maintainer or
43 and a decision by the TSC or the Security working group. To summarize the above,
58 should belong to. A project maintainers or TSC member monitoring the inflow of
82 Trivial changes are those that appear obvious enough and do not require maintainer or code-owner
83 involvement. Such changes should not change the logic or the design of a
84 subsystem or component. For example a trivial change can be:
91 - Sample modifications to support additional configuration or boards etc.
[all …]
|
| D | proposals.rst | 15 A request for the implementation or inclusion of a new unit of functionality
25 A request or plan to port an existing feature or enhancement to a particular
27 architecture, SoC or board to adding an implementation of a peripheral driver
31 A label to group other GitHub issues that are part of a single feature or unit
42 and a proposed design or implementation.
59 by any project member or the community. You should contact an assigned owner if
60 you'd like to discuss or contribute to that feature's implementation
74 or more
98 and fixes that need to go into a specific release or milestone.
101 project' next release (or the next few releases). So it acts as more of a
[all …]
|
| /Zephyr-latest/doc/services/file_system/ |
| D | index.rst | 11 specific API or internal functions by introducing file system registration
14 In Zephyr, any file system implementation or library can be plugged into or
27 while formatting or mounting a disk.
41 - ``FS_FATFS`` is the file system type like FATFS or LittleFS.
58 or SPI connected FLASH, or LittleFS in flash, depending on the sample configuration.
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | dlist.rst | 9 constant-time removal and insertion (at all points: before or after
10 the head, tail or any internal node). To do this, the list stores two
16 or :c:macro:`SYS_DLIST_STATIC_INIT` before use. The :c:type:`sys_dnode_t` struct
19 above). It must be initialized in zeroed/bss memory or with
26 appropriate (i.e. for empty lists, or nodes at the endpoints of the
30 :c:func:`sys_dlist_remove`, by adding a node to the head or tail of a list
31 with :c:func:`sys_dlist_prepend` and :c:func:`sys_dlist_append`, or by
46 :c:func:`sys_dnode_is_linked`, which will affirmatively return whether or
47 not a node is currently linked into a dlist or not (via an
66 * An insertion or deletion never needs to check for the special case
[all …]
|
| /Zephyr-latest/samples/ |
| D | sample_definition_and_criteria.rst | 9 A sample is a concise Zephyr application that provides an accessible overview of one or
10 more features, subsystems, or modules. This includes kernel services, drivers, protocols, etc.
11 Samples should be limited in scope and should focus only on demonstrating non-trivial or
12 essential aspects of the subsystem(s) or module(s) being highlighted.
19 1. Samples must not be used to test features or verify platforms
62 the harness is set to ``ztest`` or ``console``.
65 ``extra_args`` or ``extra_configs`` options in the YAML file to build the
69 never be used to test functionality of the subsystem or module the sample
72 operation can be verified using ``extra_args`` or
79 * Make use of ``integration_platforms`` to limit the scope when there are timing or
[all …]
|
| /Zephyr-latest/soc/intel/intel_adsp/cavs/ |
| D | asm_ldo_management.h | 39 or \state, \ay, \state
50 or \state, \ay, \state
62 or \ax, \az, \ax
81 or \ax, \ax, \az
101 or \ax, \ax, \az
|
| /Zephyr-latest/dts/xtensa/espressif/esp32/ |
| D | esp32_d0wd_v3.dtsi | 14 /* Add flash or psram on board or application level */
|
| /Zephyr-latest/dts/arm/nordic/ |
| D | nrf91_peripherals.dtsi | 151 * This i2c node can be either TWIM or TWIS, for the user to pick:
152 * compatible = "nordic,nrf-twim" or
167 * This i2c node can be either TWIM or TWIS, for the user to pick:
168 * compatible = "nordic,nrf-twim" or
183 * This i2c node can be either TWIM or TWIS, for the user to pick:
184 * compatible = "nordic,nrf-twim" or
199 * This i2c node can be either TWIM or TWIS, for the user to pick:
200 * compatible = "nordic,nrf-twim" or
215 * This spi node can be either SPIM or SPIS, for the user to pick:
216 * compatible = "nordic,nrf-spim" or
[all …]
|
| D | nrf52832.dtsi | 114 /* uart can be either UART or UARTE, for the user to pick */
115 /* compatible = "nordic,nrf-uarte" or "nordic,nrf-uart"; */
124 * This i2c node can be TWI, TWIM, or TWIS,
126 * compatible = "nordic,nrf-twi" or
127 * "nordic,nrf-twim" or
142 * This spi node can be SPI, SPIM, or SPIS,
144 * compatible = "nordic,nrf-spi" or
145 * "nordic,nrf-spim" or
160 * This i2c node can be TWI, TWIM, or TWIS,
162 * compatible = "nordic,nrf-twi" or
[all …]
|
| /Zephyr-latest/samples/bluetooth/hap_ha/ |
| D | README.rst | 5 Advertise and await connection from a Hearing Aid Unicast Client or Remote Controller.
12 or Hearing Aid Remote Controller (HARC).
17 * BlueZ running on the host, or
|
| /Zephyr-latest/subsys/net/ |
| D | Kconfig.template.log_config.default.net | 25 Only write to log when NET_ERR or LOG_ERR is used.
30 Write to log with NET_WARN or LOG_WRN in addition to previous level.
35 Write to log with NET_INFO or LOG_INF in addition to previous levels.
40 Write to log with NET_DBG or LOG_DBG in addition to previous levels.
|
| D | Kconfig.template.log_config.net | 24 Only write to log when NET_ERR or LOG_ERR is used.
29 Write to log with NET_WARN or LOG_WRN in addition to previous level.
34 Write to log with NET_INFO or LOG_INF in addition to previous levels.
39 Write to log with NET_DBG or LOG_DBG in addition to previous levels.
|
| /Zephyr-latest/boards/nxp/common/ |
| D | segger-ecc-systemview.rst | 8 Note that when using SEGGER SystemView or RTT with this SOC, the RTT control
9 block address must be set manually within SystemView or the RTT Viewer. The
11 symbol, which can be found using a debugger or by examining the ``zephyr.map``
|
| /Zephyr-latest/doc/contribute/ |
| D | proposals_and_rfcs.rst | 16 they intend to make "substantial" changes to Zephyr or its documentation. Some
23 - The introduction of new idiomatic usage or conventions, even if they do not
38 - Rephrasing, reorganizing or refactoring
39 - Addition or removal of warnings
40 - Addition of new boards, SoCs or drivers to existing subsystems
50 either disagreement or not enough voiced opinions in order to proceed. Make sure
51 to either label it appropriately or include it in the corresponding GitHub
|
| /Zephyr-latest/drivers/i2s/ |
| D | Kconfig.sam_ssc | 31 an output or an input depending on whether the receiver is working
32 in master or slave mode.
42 an output or an input depending on whether the receiver is working
43 in master or slave mode.
|
