Home
last modified time | relevance | path

Searched full:interpret (Results 1 – 23 of 23) sorted by relevance

/Zephyr-Core-3.5.0/arch/common/
Dfill_with_zeros.ld14 * e.g. because MCU can interpret the pattern as a configuration data.
Dsw_isr_common.c134 /* Some architectures don't/can't interpret flags or priority and have
/Zephyr-Core-3.5.0/dts/bindings/mtd/
Datmel,at2x-base.yaml28 The device will interpret this signal as active-low.
/Zephyr-Core-3.5.0/arch/riscv/core/
Dsemihost.c14 * interpret the trap sequence if these instructions are placed across two
/Zephyr-Core-3.5.0/include/zephyr/net/
Dconn_mgr_connectivity_impl.h84 * It is up to the connectivity implementation to interpret optname. Options can be
105 * It is up to the connectivity implementation to interpret optname. Options can be
Dptp_time.h79 * and interpret timestamps accordingly. Applications must further ensure that
Dnet_pkt.h130 * to interpret the results.
/Zephyr-Core-3.5.0/drivers/sensor/mchp_tach_xec/
Dtach_mchp_xec.c84 /* We interpret a fan stopped or jammed as 0 */ in tach_xec_sample_fetch()
/Zephyr-Core-3.5.0/drivers/counter/
Dcounter_cmos.c155 * The order is a bit awkward because we need to interpret in get_value()
/Zephyr-Core-3.5.0/drivers/interrupt_controller/
Dintc_dw_ace.c49 * mask indexes that only the driver can interpret. If
/Zephyr-Core-3.5.0/doc/build/dts/
Dintro-input-output.rst96 A library layered on top of dtlib that uses bindings to interpret
/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/
Dgatt-pics.rst80 TSPC_GATT_3_27 False Read and Interpret Characteristic Presentation Format (O)
81 TSPC_GATT_3_28 False Read and Interpret Characteristic Aggregate Format (C.6)
/Zephyr-Core-3.5.0/doc/hardware/peripherals/
Dsensor.rst36 A newer experimental (may change) API that can interpret raw sensor data is
/Zephyr-Core-3.5.0/subsys/bluetooth/common/
DKconfig238 sending vendor commands to controller which may interpret them in
/Zephyr-Core-3.5.0/subsys/bluetooth/controller/ll_sw/nordic/lll/
Dlll_df.c326 * It makes possible to correctly interpret PDU content by Radio peripheral.
/Zephyr-Core-3.5.0/arch/sparc/core/
Dinterrupt_trap.S32 * - z_sparc_enter_irq() knows how to interpret this interrupt request level.
/Zephyr-Core-3.5.0/doc/kernel/
Dtimeutil.rst18 Time. These systems interpret time in different ways and may have
/Zephyr-Core-3.5.0/subsys/shell/
Dshell_cmds.c21 "backspace and delete button. This command forces shell to interpret" \
/Zephyr-Core-3.5.0/doc/connectivity/networking/conn_mgr/
Dimplementation.rst284 …ssociate, it would be acceptable for the connectivity implementation to interpret this as an unexp…
/Zephyr-Core-3.5.0/drivers/spi/
Dspi_xec_qmspi_ldma.c480 * If the TX buffer pointer is NULL interpret byte length as the number
/Zephyr-Core-3.5.0/doc/
Dzephyr.doxyfile.in195 # If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the
204 # If the JAVADOC_BANNER tag is set to YES then doxygen will interpret a line
214 # If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first
/Zephyr-Core-3.5.0/subsys/net/lib/http/
Dhttp_parser.c1871 * will interpret that as saying that this message has in parser_execute()
/Zephyr-Core-3.5.0/doc/releases/
Drelease-notes-3.2.rst1372 * Updated cbprintf static packaging to interpret ``unsigned char *`` as a pointer