Searched full:identified (Results 1 – 25 of 68) sorted by relevance
123
| /Zephyr-Core-3.5.0/doc/project/ |
| D | issues.rst | 19 It could happen that the issue being reported is identified as a regression,
33 * Once the bisection is over and a culprit identified, verify manually the result.
|
| D | modifying_contributions.rst | 52 Developers should try to limit the above practice to pull requests identified
|
| /Zephyr-Core-3.5.0/dts/bindings/spi/ |
| D | st,stm32h7-spi.yaml | 8 This version of STM32 SPI hardware block could be identified by the
|
| /Zephyr-Core-3.5.0/tests/drivers/regulator/fixed/dts/bindings/ |
| D | test-regulator-fixed.yaml | 15 Identity of a GPIO that is shorted to the GPIO identified in the test
|
| /Zephyr-Core-3.5.0/tests/drivers/uart/uart_mix_fifo_poll/ |
| D | README.txt | 16 UART receives loopback data and validates if for each stream (identified by ID)
|
| /Zephyr-Core-3.5.0/tests/drivers/gpio/gpio_basic_api/ |
| D | README.txt | 6 identified through a test-specific devicetree binding in the `dts/`
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/services/ |
| D | Kconfig.dis | 77 made by the vendor identified with the Vendor ID field. The vendors
87 which defines the version of the product identified by the Vendor ID and
|
| /Zephyr-Core-3.5.0/include/zephyr/bluetooth/audio/ |
| D | has.h | 203 * Client method to find a Hearing Access Service on a server identified by @p conn.
244 * Client procedure to set preset identified by @p index as active.
286 * This callback is called when the client requests to select preset identified by
303 * This callback is called when the name of the preset identified by @p index has changed.
431 * Function used to set the preset identified by the @p index as the active preset.
464 * Change the name of the preset identified by @p index.
|
| /Zephyr-Core-3.5.0/include/zephyr/linker/ |
| D | utils.h | 22 * @return True if address identified within read only section.
|
| /Zephyr-Core-3.5.0/ |
| D | CONTRIBUTING.rst | 18 use other licensing and are clearly identified.
|
| /Zephyr-Core-3.5.0/tests/drivers/i2c/i2c_target_api/ |
| D | README.txt | 38 Presence of this required hardware configuration is identified by the
|
| /Zephyr-Core-3.5.0/doc/hardware/peripherals/ |
| D | video.rst | 39 A video control is accessed and identified by a CID (control identifier). It
|
| /Zephyr-Core-3.5.0/include/zephyr/drivers/interrupt_controller/ |
| D | gicv3_its.h | 12 * EventID from a device, identified by its DeviceID, determines a corresponding INTID for
|
| /Zephyr-Core-3.5.0/include/zephyr/bluetooth/mesh/ |
| D | dfd.h | 41 /** The AppKey identified by the AppKey Index is not known to the node.
|
| /Zephyr-Core-3.5.0/share/sysbuild/cmake/modules/ |
| D | sysbuild_extensions.cmake | 11 # All CMake cache variables are stored in a custom target which is identified by
50 # identified by image.
59 # will lookup PROJECT_NAME from the CMakeCache identified by `my_sample` and
63 # will lookup PROJECT_NAME from the CMakeCache identified by `my_sample` and
67 # will lookup CONFIG_FOO from the KConfig identified by `my_sample` and
|
| /Zephyr-Core-3.5.0/doc/kernel/services/threads/ |
| D | nothread.rst | 42 * Specifically identified drivers in certain subsystems, listed below.
|
| /Zephyr-Core-3.5.0/include/zephyr/settings/ |
| D | settings.h | 72 /**< Get values handler of settings items identified by keyword names.
85 /**< Set value handler of settings items identified by keyword names.
138 /**< Get values handler of settings items identified by keyword names.
151 /**< Set value handler of settings items identified by keyword names.
|
| /Zephyr-Core-3.5.0/doc/develop/west/ |
| D | why.rst | 13 identified to avoid the common pitfalls of tools of this kind.
|
| /Zephyr-Core-3.5.0/doc/develop/languages/cpp/ |
| D | index.rst | 29 on the suffix (extension) of the files. Files identified with either a **cpp**
|
| /Zephyr-Core-3.5.0/include/zephyr/logging/ |
| D | log_instance.h | 107 * Instance is identified by @p _module_name and @p _inst_name.
|
| /Zephyr-Core-3.5.0/doc/safety/ |
| D | safety_overview.rst | 219 #. On the main branch, the safety scope of the project should be identified, which typically
252 circumstances, specifically when something has been identified during the certification process
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/host/ |
| D | keys.h | 133 * @brief Find key identified by type, ID and address
|
| /Zephyr-Core-3.5.0/doc/hardware/porting/ |
| D | shields.rst | 147 GPIOs accessed by the shield peripherals must be identified using the
|
| /Zephyr-Core-3.5.0/lib/os/ |
| D | heap.h | 23 /* Chunks are identified by their offset in 8 byte units from the
|
| /Zephyr-Core-3.5.0/doc/security/ |
| D | security-overview.rst | 32 relevant sub-modules is created, threats are identified, and
77 changes are identified, they will be added to this document through the
550 are present. After a threat has been identified, a corresponding threat
|
123
