Searched full:their (Results 1 – 25 of 566) sorted by relevance
12345678910>>...23
| /Zephyr-Core-3.6.0/doc/project/ |
| D | modifying_contributions.rst | 12 of the pull requests are responsible for amending their original commits
19 * a developer cherry-picks commits submitted by other contributors into their
40 * clarify in their pull request the reason for cherry-picking the patches,
41 instead of assisting in getting the patches merged in their original
43 * invite the original author of the patches to their pull request review.
61 * submit the modified patches as their *own* work (i.e. with their
69 to indicate that they do not wish their patches to be amended,
70 inside their original branch or pull request, by other Zephyr developers.
|
| /Zephyr-Core-3.6.0/subsys/logging/ |
| D | Kconfig.filtering | 33 Forces a minimum log level for all modules. Modules use their
35 the level specified by this option instead of their default or
50 Forces a maximal log level for all modules. Modules saturates their
52 the level specified by this option instead of their default or
|
| /Zephyr-Core-3.6.0/drivers/mm/ |
| D | mm_drv_common.h | 117 * Drivers do not have to implement their own sys_mm_drv_map_region()
120 * Or the drivers can implement their own sys_mm_drv_map_region(), then
143 * Drivers do not have to implement their own sys_mm_drv_map_array()
146 * Or the drivers can implement their own sys_mm_drv_map_array(), then
169 * Drivers do not have to implement their own sys_mm_drv_unmap_region()
172 * Or the drivers can implement their own sys_mm_drv_unmap_region(), then
192 * Drivers do not have to implement their own sys_mm_drv_remap_region()
195 * Or the drivers can implement their own sys_mm_drv_remap_region(), then
219 * Drivers do not have to implement their own sys_mm_drv_move_region()
222 * Or the drivers can implement their own sys_mm_drv_move_region(), then
[all …]
|
| /Zephyr-Core-3.6.0/lib/posix/options/getopt/ |
| D | Kconfig | 10 Different shell backends are use their own instance of getopt to
23 Different shell backends are using their own instance of getopt to
|
| /Zephyr-Core-3.6.0/dts/bindings/adc/ |
| D | st,stm32-adc.yaml | 78 values created with STM32_ADC_RES macro or similar. Their order is not
92 Rounded up if needed. Order is important: their index matches their binary
|
| /Zephyr-Core-3.6.0/lib/hash/ |
| D | Kconfig.hash_map | 25 The main disadvantage of Separate-Chaining Hashmaps are that their
36 The main advantage of Open-Addressing Hashmaps are due to their
|
| /Zephyr-Core-3.6.0/include/zephyr/dt-bindings/memory-attr/ |
| D | memory-attr.h | 30 * Software can define their own memory attributes if needed using the
41 * Architectures can define their own memory attributes if needed using the
|
| /Zephyr-Core-3.6.0/samples/bluetooth/mtu_update/ |
| D | README.rst | 35 update their MTU. The MTU is not a negotiated value, the client and the server
36 will exchange their MTUs and choose the minimum of the two. Thus the two MTU can
58 :alt: Diagram of the MTUs and their corresponding Kconfig symbols
60 Diagram of the MTUs and their corresponding Kconfig symbols
|
| /Zephyr-Core-3.6.0/arch/x86/core/ |
| D | common.S | 11 * at their 32-bit entry points to cover common ground.
33 * can't actually disable them, but we mask all their interrupt
|
| /Zephyr-Core-3.6.0/doc/hardware/peripherals/ |
| D | gnss.rst | 12 process GNSS signals to determine their position, or more
13 specifically, their antennas position. They usually
|
| /Zephyr-Core-3.6.0/samples/bluetooth/hci_uart/boards/ |
| D | bbc_microbit.conf | 5 # Revert values set in prj.conf, set them to their Kconfig default value
|
| D | nrf51_blenano.conf | 5 # Revert values set in prj.conf, set them to their Kconfig default value
|
| /Zephyr-Core-3.6.0/boards/posix/native_sim/ |
| D | cmdline_common.h | 10 * To support native_posix drivers which register their own arguments
|
| D | cmdline.c | 8 * To support native_posix drivers or tests which register their own arguments
|
| D | cmdline.h | 18 * To support native_posix drivers or tests which register their own arguments
|
| /Zephyr-Core-3.6.0/doc/connectivity/bluetooth/api/mesh/ |
| D | health_srv.rst | 8 faults in the mesh node and map the mesh nodes to their physical location.
42 application to run their attention calling behavior:
|
| /Zephyr-Core-3.6.0/drivers/spi/ |
| D | Kconfig.mcux_flexcomm | 19 that enable dma channels in their device tree node.
|
| D | Kconfig.gd32 | 26 that enable dma channels in their device tree node.
|
| /Zephyr-Core-3.6.0/doc/kernel/object_cores/ |
| D | index.rst | 17 Objects of the same type are linked together via their respective object
18 cores to form a singly linked list. Each object core also links to the their
39 their projects.
120 automatically have their object cores initialized when the object is
121 initialized. However, developers that wish to add their own objects into the
|
| /Zephyr-Core-3.6.0/subsys/mgmt/ec_host_cmd/ |
| D | Kconfig | 33 Some backend layers can define their own buffer, so the size can be zero to
46 Some backend layers can define their own buffer, so the size can be zero to
|
| /Zephyr-Core-3.6.0/drivers/adc/ |
| D | Kconfig.stm32 | 24 that enable dma channels in their device tree node.
|
| /Zephyr-Core-3.6.0/samples/subsys/console/getchar/src/ |
| D | main.c | 15 printk("Start typing characters to see their hex codes printed\n"); in main()
|
| /Zephyr-Core-3.6.0/boards/arc/emsdp/ |
| D | Kconfig.board | 12 their software for the ARC EM processor family and ARC EM Subsystems.
|
| /Zephyr-Core-3.6.0/drivers/ethernet/ |
| D | Kconfig.sam_gmac | 34 routed to appropriate queues based on their priority.
67 filled in with incoming data. Their number has to be large enough to fit
|
| /Zephyr-Core-3.6.0/dts/bindings/usb/ |
| D | usb-controller.yaml | 16 via DT, USB controllers should use their maximum
|
12345678910>>...23
