Searched full:identified (Results 1 – 25 of 87) sorted by relevance
1234
/Zephyr-latest/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-latest/samples/drivers/uart/passthrough/ |
D | README.rst | 21 #. One UART interface, identified as Zephyr's console. 22 #. A second UART connected to something interesting (e.g: GPS), identified as
|
/Zephyr-latest/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-latest/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-latest/dts/bindings/spi/ |
D | st,stm32h7-spi.yaml | 8 This version of STM32 SPI hardware block could be identified by the
|
/Zephyr-latest/tests/drivers/gpio/gpio_basic_api/ |
D | README.txt | 6 identified through a test-specific devicetree binding in the `dts/`
|
/Zephyr-latest/include/zephyr/bluetooth/audio/ |
D | has.h | 232 * Client method to find a Hearing Access Service on a server identified by @p conn. 273 * Client procedure to set preset identified by @p index as active. 315 * This callback is called when the client requests to select preset identified by 332 * This callback is called when the name of the preset identified by @p index has changed. 463 * Function used to set the preset identified by the @p index as the active preset. 496 * Change the name of the preset identified by @p index.
|
/Zephyr-latest/ |
D | CONTRIBUTING.rst | 18 use other licensing and are clearly identified.
|
/Zephyr-latest/include/zephyr/linker/ |
D | utils.h | 22 * @return True if address identified within read only section.
|
/Zephyr-latest/doc/hardware/peripherals/ |
D | video.rst | 39 A video control is accessed and identified by a CID (control identifier). It
|
/Zephyr-latest/tests/drivers/i2c/i2c_target_api/ |
D | README.txt | 38 Presence of this required hardware configuration is identified by the
|
/Zephyr-latest/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-latest/include/zephyr/drivers/interrupt_controller/ |
D | gicv3_its.h | 12 * EventID from a device, identified by its DeviceID, determines a corresponding INTID for
|
/Zephyr-latest/include/zephyr/bluetooth/mesh/ |
D | dfd.h | 41 /** The AppKey identified by the AppKey Index is not known to the node.
|
/Zephyr-latest/doc/kernel/services/threads/ |
D | nothread.rst | 42 * Specifically identified drivers in certain subsystems, listed below.
|
/Zephyr-latest/doc/develop/sca/ |
D | codechecker.rst | 58 - By default, CodeChecker identified issues will not fail the build, set this option to fail
|
/Zephyr-latest/include/zephyr/drivers/firmware/scmi/ |
D | util.h | 137 * Each SCMI protocol is identified by a struct scmi_protocol 270 * Each SCMI protocol is identified by an ID. Each
|
/Zephyr-latest/drivers/firmware/scmi/ |
D | mailbox.h | 99 * (identified by the `scmi` node)
|
/Zephyr-latest/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-latest/include/zephyr/settings/ |
D | settings.h | 77 /**< Get values handler of settings items identified by keyword names. 90 /**< Set value handler of settings items identified by keyword names. 146 /**< Get values handler of settings items identified by keyword names. 159 /**< Set value handler of settings items identified by keyword names.
|
/Zephyr-latest/arch/arc/core/ |
D | thread.c | 345 * the same CPU identified by <id>. in arc_vpx_lock() 365 * the CPU identified by <id>, and that it is the same CPU in arc_vpx_unlock()
|
/Zephyr-latest/doc/develop/west/ |
D | why.rst | 13 identified to avoid the common pitfalls of tools of this kind.
|
/Zephyr-latest/include/zephyr/logging/ |
D | log_instance.h | 107 * Instance is identified by @p _module_name and @p _inst_name.
|
/Zephyr-latest/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 186 security issue categorization and management. A problem identified as 546 are present. After a threat has been identified, a corresponding threat
|
1234