Home
last modified time | relevance | path

Searched refs:respect (Results 1 – 25 of 25) sorted by relevance

/Zephyr-latest/boards/shields/weact_ov2640_cam_module/boards/
Dmini_stm32h743.overlay7 /* AHB clocks must respect the minimum ratio AHB / DCMI_PIXCLK of 2.5 (AN5020 - Rev 3).
/Zephyr-latest/arch/arm/core/mpu/
DKconfig59 for respect alignment. But that needs carefully configure MPU region
68 size is configured by users, it must also respect the power of
/Zephyr-latest/arch/arm/core/cortex_m/
Drelay_vector_table.ld11 * Therefore, vector_relay_table must respect the alignment requirements
/Zephyr-latest/drivers/sensor/sensirion/sht3xd/
DKconfig61 Repeatability modes differ with respect to measurement duration,
/Zephyr-latest/arch/arm/core/
Dvector_table.ld11 * exc_vector_table must respect the alignment requirements of VTOR.TBLOFF
/Zephyr-latest/doc/project/
Dindex.rst39 with respect to the development process workflow.
Dproject_roles.rst47 * Responsibility to respect the rules of the community.
71 respect to accepting and merging a pull request. However, Contributors comments
/Zephyr-latest/tests/arch/arm/arm_thread_swap/
DREADME.txt36 - the mode variable with respect to the user mode flag always indicates
/Zephyr-latest/samples/drivers/virtualization/ivshmem/doorbell/
DREADME.rst128 ``write_shared_memory`` script; failing to respect the shared memory size
206 (ii) make sure writes always respect the shared memory region size.
/Zephyr-latest/doc/hardware/peripherals/edac/
Dibecc.rst64 implement desired policy with respect for handling those memory errors. Error
/Zephyr-latest/boards/weact/stm32g431_core/doc/
Dindex.rst23 The internal USB DFU boot loader may not work correctly with machines that respect USB
/Zephyr-latest/
DCODE_OF_CONDUCT.md71 All community leaders are obligated to respect the privacy and security of the
/Zephyr-latest/doc/build/dts/
Dbindings-upstream.rst130 :ref:`DTS_ROOT <dts_root>`. The devicetree tooling will respect these
/Zephyr-latest/doc/develop/languages/cpp/
Dindex.rst149 with respect to code style, compiler warnings, static analyzers and
/Zephyr-latest/doc/kernel/data_structures/
Dring_buffers.rst168 Depending on usage (particularly with respect to number of concurrent
/Zephyr-latest/doc/security/
Dsecurity-overview.rst363 - **Adherence to the Coding Conventions** with respect to coding style,
443 These points shall be evaluated with respect to their impact on the
/Zephyr-latest/doc/kernel/services/other/
Dfloat.rst123 is enabled, the following rules apply with respect to lazy stacking:
/Zephyr-latest/doc/releases/
Drelease-notes-2.5.rst622 * Fixed getaddrinfo() to respect socket type hints.
1231 * :github:`30686` - getaddrinfo() does not respect socket type
1654 * :github:`28723` - Does not respect python virtualenv
1726 * :github:`27785` - memory domain arch implementation not correct with respect to SMP on ARC
Drelease-notes-1.10.rst226 * :github:`1487` - net/lib/dns doesn't respect CONFIG_NET_IPV6=n
Drelease-notes-3.1.rst1218 - :github:`44725` - drivers: can: stm32: can_add_rx_filter() does not respect CONFIG_CAN_MAX_FILTER
Drelease-notes-2.4.rst1096 * :github:`27785` - memory domain arch implementation not correct with respect to SMP on ARC
Drelease-notes-3.2.rst2496 * :github:`44725` - drivers: can: stm32: can_add_rx_filter() does not respect CONFIG_CAN_MAX_FILTER
Drelease-notes-1.14.rst1516 …ATMEL SAM family UART and USART - functions u(s)art_sam_irq_is_pending doesn't respect IRQ settings
/Zephyr-latest/doc/kernel/usermode/
Dsyscalls.rst385 There is one exception in place, with respect to large data buffers which are
/Zephyr-latest/kernel/
DKconfig786 atomic with respect to the irq_lock being released. That