Home
last modified time | relevance | path

Searched full:whether (Results 1 – 25 of 562) sorted by relevance

12345678910>>...23

/Zephyr-Core-3.6.0/arch/arm/include/cortex_m/
Dcmse.h58 * Evaluates whether a specified memory location can be read according to the
67 * for unprivileged access, regardless of whether the current
77 * Evaluates whether a specified memory location can be read/written according
87 * for unprivileged access, regardless of whether the current
97 * Evaluates whether a memory address range, specified by its base address
109 * for unprivileged access, regardless of whether the current
119 * Evaluates whether a memory address range, specified by its base address
131 * for unprivileged access, regardless of whether the current
148 * Evaluates whether a given object can be read according to the
166 * Evaluates whether a given object can be read according to the
[all …]
Dexception.h56 * ESF, whether the processor was in handler mode before entering
62 * whether we are in a nested exception; we rely on the
188 * @brief Assess whether a debug monitor event should be treated as an error
191 * evaluates whether this needs to be considered as a processor error.
/Zephyr-Core-3.6.0/drivers/watchdog/
DKconfig.xlnx20 Controls whether the Xilinx AXI Timebase WDT driver exposes a HWINFO
21 API which allows determining whether the WDT initiated the last
/Zephyr-Core-3.6.0/dts/bindings/crypto/
Dnordic,nrf-ccm.yaml20 Indicates whether the CCM peripheral supports the extended length
27 Indicates whether the CCM peripheral supports the headermask register to
/Zephyr-Core-3.6.0/tests/drivers/entropy/api/src/
Dmain.c18 * -# Verify whether buffer overflow occurred or not.
19 * -# Verify whether buffer completely filled or not.
91 /* Check whether 20% or more of buffer still filled with default in get_entropy()
93 * to buffer. Recheck random_entropy and verify whether 20% or more in get_entropy()
/Zephyr-Core-3.6.0/drivers/i2s/
DKconfig.sam_ssc30 an output or an input depending on whether the receiver is working
41 an output or an input depending on whether the receiver is working
/Zephyr-Core-3.6.0/samples/tfm_integration/psa_crypto/src/
Dutil_sformat.h21 /** Whether or not to render ASCII equivalents. */
23 /** Whether or not to add address labels to the output. */
/Zephyr-Core-3.6.0/arch/arc/core/secureshield/
Dsecure_sys_services.c22 * to decide whether the access is valid.
37 * to decide whether the access is valid.
63 * apply one. Necessary check should be done to decide whether the apply is
/Zephyr-Core-3.6.0/doc/build/dts/
Ddt-vs-kconfig.rst7 source code. Whether to use devicetree or Kconfig for a particular purpose can
16 image. Examples include whether to add networking support, which drivers are
33 * Whether or not to include **software support** for UART in the build is
/Zephyr-Core-3.6.0/samples/bluetooth/broadcast_audio_sink/
DKconfig7 bool "Whether to wait for a Broadcast Assistant"
16 bool "Whether to scan for Broadcast Sources without Broadcast Assistant"
/Zephyr-Core-3.6.0/arch/arm/core/cortex_m/
Ddebug.c18 * @brief Assess whether a debug monitor event should be treated as an error
21 * evaluates whether this needs to be considered as a processor error.
28 /* Assess whether this debug exception was triggered in z_arm_debug_monitor_event_error_check()
/Zephyr-Core-3.6.0/doc/develop/api/
Dterminology.rst19 effect whether invoked from interrupt or thread context
48 a consequence of a higher-priority thread being made ready. Whether the
127 whether it is being invoked from interrupt or thread context.
162 :c:func:`k_is_pre_kernel` when determining whether it can fulfill its
191 not affect whether the operation will be completed before the function
/Zephyr-Core-3.6.0/subsys/usb/device_next/
Dusbd_ch9.h13 * @brief Check whether USB device is in default state.
25 * @brief Check whether USB device is in address state.
37 * @brief Check whether USB device is in configured state.
/Zephyr-Core-3.6.0/tests/bluetooth/df/connection_cte_tx_params/
Dprj.conf5 # It does not matter for the test whether central or peripheral is used.
/Zephyr-Core-3.6.0/doc/hardware/cache/
Dindex.rst19 set whether we plan to support and use the caches in Zephyr or not.
44 whether the cache operations are implemented at arch level or using an
/Zephyr-Core-3.6.0/tests/boards/mec15xxevb_assy6853/i2c_api/src/
Dmain.c23 * - check read data whether correct
58 /* check read data whether correct */ in ZTEST()
/Zephyr-Core-3.6.0/tests/boards/mec172xevb_assy6906/i2c_api/src/
Dmain.c23 * - check read data whether correct
58 /* check read data whether correct */ in ZTEST()
/Zephyr-Core-3.6.0/dts/bindings/watchdog/
Dti,cc13xx-cc26xx-watchdog.yaml20 Whether the watchdog triggers a Non-Maskable Interrupt or a standard one
/Zephyr-Core-3.6.0/drivers/flash/
DKconfig.rv32m114 have an impact on the overall system performance - whether
DKconfig.lpc15 have an impact on the overall system performance - whether
/Zephyr-Core-3.6.0/drivers/sensor/adxl367/
DKconfig83 compared directly to a user set threshold to determine whether
92 compared directly to a user set threshold to determine whether
/Zephyr-Core-3.6.0/samples/userspace/prod_consumer/src/
Dsample_driver.h54 * Set whether the sample driver will respond to interrupts
57 * @param active Whether to activate/deactivate interrupts
/Zephyr-Core-3.6.0/doc/connectivity/networking/api/
Dnet_timeout.rst41 again to determine whether the timeout has completed, or whether there is
/Zephyr-Core-3.6.0/subsys/bluetooth/mesh/
Dsubnet.h190 * @returns Whether any of the credentials got a @c true return from the
212 * @param new_key Whether the Key Refresh event was received on the new key
215 * @returns Whether the Key Refresh event caused a change.
219 /** @brief Check whether the Subnet has the refreshed keys.
223 * @returns Whether the Subnet's second key is valid.
/Zephyr-Core-3.6.0/modules/thrift/src/thrift/transport/
DTSSLSocket.h70 * Set whether to use client or server side SSL handshake protocol.
79 * Determine whether the SSL socket is server or client mode.
102 * Determines whether SSL Socket is libevent safe or not.
314 * Determine whether the socket is in server or client mode.
403 * Determine whether the peer should be granted access or not. It's called
418 * Determine whether the peer should be granted access or not. It's called
436 * Determine whether the peer should be granted access or not. It's called

12345678910>>...23