Searched full:interpretation (Results 1 – 25 of 25) sorted by relevance
7 * interpretation by the xtensa-int-handlers.py script. Literally all
162 interpretation depends on the driver. This is used only for drivers169 Output pin selection for the bias voltage. The actual interpretation
405 LOG_INF("Interpretation marked finished"); in test_rx_long_rec_cb()439 LOG_INF("Interpretation finished"); in ZTEST()440 zassert_ok(ret, "Incoming packet interpretation timeout"); in ZTEST()441 zassert_is_null(ep_received_override_cb, "Seems like interpretation callback failed"); in ZTEST()
68 * @brief Callback API for updating channels without an RGB interpretation.
36 * 2) Avoid incompatible changes that affect the interpretation of existing
68 #define PCIE_EXT_CAP_ID_ARI 0x000EU /**< Alternate Routing-ID Interpretation */
104 interpretation of contact state to active/inactive status.
217 * by this subtle, but very different interpretation. in setup()
63 See the ``maxim_ds3231.h`` for interpretation of the integer value and
56 /* No special interpretation of output bytes. in native_tty_termios_defaults_set()
162 Additional points of clarity / TSC interpretation have been added below. The
39 * INTERPRETATION
64 { PCIE_EXT_CAP_ID_ARI, "Alternate Routing-ID Interpretation" },
248 * ``ZEP-642`` - Inconsistent interpretation of pwm_pin_set_values arguments among drivers
197 The actual interpretation of this depends on the hardware and is so far only
154 * :github:`16799` - Bluetooth: L2CAP: Interpretation of SCID and DCID in Disconnect is wrong354 * :github:`16799` - Bluetooth: L2CAP: Interpretation of SCID and DCID in Disconnect is wrong
958 * :github:`16799` - Bluetooth: L2CAP: Interpretation of SCID and DCID in Disconnect is wrong
151 * See the JESD216 specification for the interpretation of these
270 * Macro to extract the status value of CC2 line. Interpretation of this value depends on the272 * For value interpretation look at the CC_STATUS Register Definition in the TCPCI specification.
55 * See the datasheet for interpretation of these bits.
166 interpretation. **Ready** is a thread state, and **Running** is a
87 * The actual type and interpretation of the switch handle is specified
10 augmented with information from bindings and include some interpretation of11 properties. Some of this interpretation is based on conventions established872 with some interpretation of devicetree properties. There's a one-to-one
603 abstract interpretation to gain information about the code's control flow and
2775 * As an interpretation of the specification, padding PDUs will in isoal_tx_framed_event_prepare_handle()
