Lines Matching +full:start +full:- +full:of +full:- +full:frame
5 * SPDX-License-Identifier: Apache-2.0
12 * @note All references to the standard in this file cite IEEE 802.15.4-2020.
38 * @details This API provides a common representation of vendor-specific
41 * is of interest to driver maintainers only.
43 * The IEEE 802.15.4 driver API consists of two separate parts:
44 * - a basic, mostly PHY-level driver API to be implemented by all drivers,
45 * - several optional MAC-level extension points to offload performance
51 * offloading to vendor-specific hardware or firmware features may be required
53 * subprotocols (e.g. fast enough ACK packages, precise timing of timed TX/RX in
56 * Whether or not MAC-level offloading extension points need to be implemented
60 * @note All section, table and figure references are to the IEEE 802.15.4-2020
67 * @name IEEE 802.15.4-2020, Section 6: MAC functional description
73 * of the timing parameters in definition of the MAC are in units of PHY symbols.
90 * @name IEEE 802.15.4-2020, Section 8: MAC services
95 * The number of PHY symbols forming a superframe slot when the superframe order
96 * is equal to zero, see sections 8.4.2, table 8-93, aBaseSlotDuration and
102 * The number of slots contained in any superframe, see section 8.4.2,
103 * table 8-93, aNumSuperframeSlots.
108 * The number of PHY symbols forming a superframe when the superframe order is
109 * equal to zero, see section 8.4.2, table 8-93, aBaseSuperframeDuration.
115 * MAC PIB attribute aUnitBackoffPeriod, see section 8.4.2, table 8-93, in symbol
122 * Default macResponseWaitTime in multiples of aBaseSuperframeDuration as
123 * defined in section 8.4.3.1, table 8-94.
131 * @name IEEE 802.15.4-2020, Section 10: General PHY requirements
139 * bands and channels of at least one IEEE 802.15.4 PHY.
141 * Channel page and number assignments have developed over several versions of
143 * about peculiarities of channel pages and channel numbering:
144 * - The 2006 version of the standard had a read-only phyChannelsSupported PHY
146 * bitmap. This attribute was removed in later versions of the standard as the
147 * number of channels increased beyond what could be represented by a bit map.
149 * combination of channel pages and ranges instead.
150 * - In the 2020 version of the standard, 13 channel pages are explicitly
154 * (section 8.4.3.4, table 8-100) or channel page fields used in the SRM
156 * - ASK PHY (channel page one) was deprecated in the 2015 version of the
157 * standard. The 2020 version of the standard is a bit ambivalent whether
158 * channel page one disappeared as well or should be interpreted as O-QPSK now
161 * - For some PHYs the standard doesn't clearly specify a channel page, namely
162 * the GFSK, RS-GFSK, CMB and TASK PHYs. These are all rather new and left out
171 * Channel page zero supports the 2.4G channels of the O-QPSK PHY and
173 * editions of the standard. For channel page zero, 16 channels are
174 * available in the 2450 MHz band (channels 11-26, O-QPSK), 10 in the
175 * 915 MHz band (channels 1-10, BPSK), and 1 in the 868 MHz band
185 /** Formerly ASK PHY - deprecated in IEEE 802.15.4-2015 */
188 /** O-QPSK PHY - 868 MHz and 915 MHz bands, see section 10.1.3.3 */
191 /** CSS PHY - 2450 MHz band, see section 10.1.3.4 */
194 /** UWB PHY - SubG, low and high bands, see section 10.1.3.5 */
197 /** O-QPSK PHY - 780 MHz band, see section 10.1.3.2 */
200 /** reserved - not currently assigned */
203 /** MSK PHY - 780 MHz and 2450 MHz bands, see sections 10.1.3.6, 10.1.3.7 */
210 * SUN FSK/OFDM/O-QPSK PHYs - predefined bands, operating modes and
216 * SUN FSK/OFDM/O-QPSK PHYs - generic modulation and channel
221 /** O-QPSK PHY - 2380 MHz band, see section 10.1.3.10 */
246 * @brief Pointer to an array of channel range structures.
249 * of the interface.
253 /** @brief The number of currently available channel ranges. */
277 * @param drv_attr name of the local static variable to be declared for the
299 * @name IEEE 802.15.4-2020, Section 11: PHY services
305 * table 11-1.
310 * PHY PIB attribute aTurnaroundTime for SUN, RS-GFSK, TVWS, and LECIM FSK PHY,
311 * in PHY symbols, see section 11.3, table 11-1.
317 * PHY PIB attribute aCcaTime, in PHY symbols, all PHYs except for SUN O-QPSK,
318 * see section 11.3, table 11-1.
327 * @name IEEE 802.15.4-2020, Section 12: O-QPSK PHY
331 /** O-QPSK 868Mhz band symbol period, see section 12.3.3 */
335 * O-QPSK 780MHz, 915MHz, 2380MHz and 2450MHz bands symbol period,
344 * @name IEEE 802.15.4-2020, Section 13: BPSK PHY
358 * @name IEEE 802.15.4-2020, Section 15: HRP UWB PHY
361 * (T_psym), see section 11.3, table 11-1 and section 15.2.5, table 15-4
364 * repetition frequency must also be known, see the 'UwbPrf' parameter of the
365 * MCPS-DATA.request primitive (section 8.3.2, table 8-88) and the preamble
366 * parameters for HRP-ERDEV length 91 codes (IEEE 802.15.4z, section 15.2.6.2,
367 * table 15-7b).
380 /** @brief represents the nominal pulse rate frequency of an HRP UWB PHY */
382 /** standard modes, see section 8.3.2, table 8-88. */
389 * enhanced ranging device (ERDEV) modes not specified in table 8-88,
390 * see IEEE 802.15.4z, section 15.1, section 15.2.6.2, table 15-7b,
412 * @name IEEE 802.15.4-2020, Section 19: SUN FSK PHY
416 /** SUN FSK 863Mhz and 915MHz band symbol periods, see section 19.1, table 19-1 */
442 * The following capabilities describe features of the underlying radio
458 * Note: Some of these offloading capabilities may be mandatory in
459 * practice to stay within timing requirements of certain IEEE 802.15.4
464 /** Frame checksum verification supported */
467 /** Filtering of PAN ID, extended and short address supported */
473 /** CSMA-CA procedure supported on TX */
493 * - "Sleeping" is a well defined term in Zephyr related to internal
496 * - Currently all OT-capable drivers have the "sleep to TX"
500 * - The `start()`/`stop()` API of a net device controls the
502 * -ENETDOWN when calling `tx()` while their operational state is
505 * - A migration path has been defined in #63670 for actual removal of
506 * this capability in favor of a standard compliant
527 * scheduling of timed transmissions on selective tx channel.
541 /** @brief Number of bits used by ieee802154_hw_caps type. */
544 /** @brief This and higher values are specific to the protocol- or driver-specific extensions. */
566 * synchronously switched of due to a call to `stop()` or an RX slot
576 /** Frame had invalid checksum */
612 /** Initial value of frame counter associated with the key, see section 9.4.3 */
614 /** Indicates if per-key frame counter should be used, see section 9.4.3 */
616 /** Key Identifier Mode, see section 9.4.2.3, Table 9-7 */
658 /** Number of modes defined in ieee802154_tx_mode. */
661 /** This and higher values are specific to the protocol- or driver-specific extensions. */
665 /** IEEE 802.15.4 Frame Pending Bit table address matching mode. */
679 * Indicates how the driver should set the Frame Pending bit in ACK
683 * specified. Otherwise, Frame Pending bit should be set to ``1`` (see
692 * Indicates whether to set ACK Frame Pending bit for specific address
693 * or not. Disabling the Frame Pending bit with no address provided
725 * Updates MAC keys, key index and the per-key frame counter for drivers
726 * supporting transmit security offloading, see section 9.5, tables 9-9
727 * and 9-10. The key configuration SHALL NOT be accepted if the frame
728 * counter (in case frame counter per key is true) is not strictly
729 * larger than the current frame counter associated with the same key,
738 * Sets the current MAC frame counter value associated with the
740 * section 9.5, table 9-8, secFrameCounter.
742 * @warning The frame counter MUST NOT be accepted if it is not
743 * strictly greater than the current frame counter associated with the
745 * replay protection provided by the frame counter may be compromised.
746 * Drivers SHALL return -EINVAL in case the configured frame counter
755 * Sets the current MAC frame counter value if the provided value is greater than
772 * @details The start and duration parameters of the RX slot are
773 * relative to the network subsystem's local clock. If the start
774 * parameter of the RX slot is -1 then any previously configured RX
775 * slot SHALL be canceled immediately. If the start parameter is any
778 * either been removed or re-configured to point to a future start
784 * or future RX slot is configured when calling `start()` then the
788 * The driver SHALL take care to start/stop the receiver autonomously,
794 * after the RX slot. If the driver interface is "DOWN" when the start
795 * time of an RX slot arrives, then the RX slot SHALL not be observed
801 * start of the RX slot. If the driver is "UP" while the RX slot is
807 * PIB attribute macRxOnWhenIdle (see section 8.4.3.1, table 8-94) to
823 * @details Configures the CSL period in units of 10 symbol periods.
827 * configuration call SHALL return -ENOTSUP.
829 * See section 7.4.2.3 and section 8.4.3.6, table 8-104, macCslPeriod.
847 * appropriate pre-filled CSL IE and the CSL phase set to an
849 * injected on-the-fly by the driver at runtime as outlined in 2.
851 * of the specific CSL receiver to which it SHALL inject CSL IEs. If
861 * configured RX slot) nor SHALL a frame be transmitted concurrently.
863 * The expected RX time SHALL point to the end of SFD of an ideally
864 * timed RX frame in an arbitrary past or future CSL channel sample,
865 * i.e. whose "end of SFD" arrives exactly at the locally predicted
872 * + PHY-specific PHR duration in ns
874 * startOfMhrNs = start of MHR of the frame containing the
877 * cslPhase = (startOfMhrNs - cslAnchorPointNs)
882 * inject that IE on-the-fly into outgoing enhanced ACK frames if the
886 * each CSL channel sample early enough before its start time. The
887 * size of the CSL channel sample SHALL take relative clock drift and
890 * SHR of a legitimate RX frame is guaranteed to land inside the
894 * integer number of CSL periods SHALL point to a fixed offset of the
898 * + N * (cslPeriod * 10 * PHY-specific symbol period in ns)
900 * expectedRxTimeNs_N - rxSlot_N.start == const for all N
903 * SHOULD validate the offset of the expected RX time inside each RX
910 * Configure and start a CSL receiver:
914 * | EXPECTED_RX_TIME (end of SFD of a perfectly timed RX frame
920 * -----------------------------------------------[-CSL channel sample ]----+
923 * +--------------------- loop ---------+
930 * ---------------------
939 * -----------------------------------------------[-CSL channel sample ]----+
942 * +--------------------- loop ---------+
952 * Configure a timepoint at which an RX frame is expected to arrive.
955 * the network subsystem's local clock at which an RX frame's end of SFD
956 * (i.e. equivalently its end of SHR, start of PHR, or in the case of
961 * This parameter MAY be used to offload parts of timing sensitive TDMA
962 * (e.g. TSCH, beacon-enabled PAN including DSME), low-energy (e.g.
965 * arrival time of a frame can be predicted within a well-defined time
971 * - CSL phase (i.e. time to the next expected CSL transmission) or anchor
974 * to calculate the "start of MHR" ("first symbol of MAC", see section
977 * - In TSCH the expected RX time MAY be set to macTsRxOffset +
981 * - In ranging applications, time difference of arrival (TDOA) MAY be
983 * against the assumed synchronized time at which the ranging frame
986 * In case of periodic protocols (e.g. CSL channel samples, periodic
987 * beacons of a single PAN, periodic ranging "blinks"), a single
990 * subtracting multiples of the RX period. See e.g. the CSL
994 * their local representation of a distributed network clock by deriving
995 * synchronization instants related to a remote representation of the
1014 * the standard. IEs for all other frame types SHALL be provided by L2.
1016 * The driver shall return -ENOTSUP in the following cases:
1017 * - It does not support the @ref IEEE802154_HW_RX_TX_ACK,
1018 * - It does not support header IE injection,
1019 * - It cannot inject the runtime fields on-the-fly required for the
1024 * because they require on-the-fly timing information injection are:
1025 * - CSL IE (0x1a)
1026 * - Rendezvous Time IE (0x1d)
1027 * - Time Correction IE (0x1e)
1029 * Drivers accepting this configuration option SHALL check the list of
1030 * configured IEs for each outgoing enhanced ACK frame, select the ones
1031 * appropriate for the received frame based on their element ID, inject
1032 * any required runtime information on-the-fly and include the selected
1033 * IEs into the enhanced ACK frame's MAC header.
1049 * configured IE/address combinations or return -ENOMEM if no
1054 * implies that repetition of the same header IE/address combination is
1067 * If any of the deleted configurations didn't previously exist, then
1088 * Enable/disable RxOnWhenIdle MAC PIB attribute (Table 8-94).
1090 * Since there is no clear guidance in IEEE 802.15.4 specification about the definition of
1092 * to determine next radio state (false --> off, true --> receive) in the following
1094 * - Finalization of a regular frame reception task, provided that:
1095 * - The frame is received without errors and passes the filtering and it's not an
1097 * - ACK is not requested or transmission of ACK is not possible due to internal
1099 * - Finalization of a frame transmission or transmission of an ACK frame, when ACK is not
1100 * requested in the transmitted frame.
1101 * - Finalization of the reception operation of a requested ACK due to:
1102 * - ACK timeout expiration.
1103 * - Reception of an invalid ACK or not an ACK frame.
1104 * - Reception of the proper ACK, unless the transmitted frame was a Data Request Command
1105 * and the frame pending bit on the received ACK is set to true. In this case the radio
1107 * triggers an idle period start.
1108 * - Finalization of a stand alone CCA task.
1109 * - Finalization of a CCA operation with busy result during CSMA/CA procedure.
1110 * - Finalization of an Energy Detection task.
1111 * - Finalization of a scheduled radio reception window
1116 /** Number of types defined in ieee802154_config_type. */
1119 /** This and higher values are specific to the protocol- or driver-specific extensions. */
1124 * Configuring an RX slot with the start parameter set to this value will cancel
1127 #define IEEE802154_CONFIG_RX_SLOT_NONE -1LL
1130 * Configuring an RX slot with this start parameter while the driver is "down",
1132 * with this start value while the driver is "up" will immediately switch RX off
1134 * a slot with a future start parameter is configured and that start time
1171 * @details Pointer to an array containing a list of keys used
1191 * network subsystem's local clock defining the start of
1196 * Configuring an rx_slot with the start attribute set
1197 * to -1 will cancel and delete any previously active rx
1200 net_time_t start; member
1203 * Nanosecond resolution duration of the RX window
1204 * relative to the above RX window start time during
1210 * receiver, no matter what the start parameter.
1236 * figure 7-21
1240 * on-the-fly, see the list in @ref
1293 * Retrieves a pointer to the array of supported channel ranges within
1306 /** Number of attributes defined in ieee802154_attr. */
1309 /** This and higher values are specific to the protocol- or
1310 * driver-specific extensions.
1326 * driver and valid throughout the lifetime of the driver instance.
1330 /* TODO: Implement configuration of phyCurrentPage once drivers
1342 * @note Currently none of the Zephyr drivers implements more
1345 * attribute phyCurrentPage, section 11.3, table 11-2) is
1346 * considered to be read-only, fixed and "well known" via the
1356 * the life of the interface.
1359 * phyCurrentPage PHY PIB attribute, see the description of
1365 * often zero-based, fixed channel range.
1371 * * SUN and LECIM PHYs specify a large number of bands and
1373 * ranges each. Some of these ranges are not zero-based or
1381 * switching between sub-ranges within the same channel page
1396 * @note Currently none of the Zephyr HRP UWB drivers implements
1398 * will be set and the current PRF (UwbPrf, MCPS-DATA.request,
1399 * section 8.3.2, table 8-88) is considered to be read-only,
1418 * @retval -ENOENT if the attribute could not be resolved
1428 value->phy_supported_channel_pages = phy_supported_channel_page; in ieee802154_attr_get_channel_page_and_range()
1432 value->phy_supported_channels = phy_supported_channels; in ieee802154_attr_get_channel_page_and_range()
1436 return -ENOENT; in ieee802154_attr_get_channel_page_and_range()
1446 * vendor-specific driver hardware or firmware offers offloading opportunities.
1448 * @details While L1-level driver features are exclusively implemented by
1453 * driver-independent L2 layer for all L2/MAC features especially if these
1454 * features are not implemented in vendor hardware/firmware by a majority of
1455 * existing in-tree drivers. If, however, a driver offers offloading
1465 * packets, "DOWN" otherwise (see precise definitions of the corresponding
1471 * after a call to `start()` returned zero or `-EALREADY`. Upper layers assume
1473 * `-EALREADY`.
1474 * * The driver SHALL block `start()`/`stop()` calls until the interface fully
1479 * * Drivers are responsible of guaranteeing atomicity of state changes.
1480 * Appropriate means of synchronization SHALL be implemented (locking, atomic
1490 * start of the RX slot or until a scheduled packet needs to be transmitted.
1495 * operation returns zero. This state is active until either `start()` or
1496 * `stop()` is called. If `continuous_carrier()` returns a non-zero value then
1498 * * If calls to `start()`/`stop()` return any other value than zero or
1499 * `-EALREADY`, upper layers will consider the interface to be in a
1504 * the "UP" state and return `-ENETDOWN` in any other state. See the
1505 * function-level API documentation below for further details.
1507 * @note In case of devices that support timed RX/TX, the "UP" state is not
1509 * IEEE802154_CONFIG_RX_SLOT) is configured before calling `start()` then the
1520 * therefore mandatory to place it at the top of the driver API struct so
1528 * @note Implementations SHALL be **isr-ok** and MUST NOT **sleep**. MAY
1539 * @brief Clear Channel Assessment - Check channel's activity
1541 * @note Implementations SHALL be **isr-ok** and MAY **sleep**. SHALL
1542 * return -ENETDOWN unless the interface is "UP".
1547 * @retval -EBUSY The channel is busy.
1548 * @retval -EWOULDBLOCK The operation is called from ISR context but
1550 * @retval -ENETDOWN The interface is not "UP".
1551 * @retval -ENOTSUP CCA is not supported by this driver.
1552 * @retval -EIO The CCA procedure could not be executed.
1559 * @note Implementations SHALL be **isr-ok** and MAY **sleep**. SHALL
1560 * return -EIO unless the interface is either "UP" or "DOWN".
1563 * @param channel the number of the channel to be set in CPU byte order
1566 * @retval -EALREADY The previous channel is the same as the requested
1568 * @retval -EINVAL The given channel is not within the range of valid
1569 * channels of the driver's current channel page, see the
1571 * @retval -EWOULDBLOCK The operation is called from ISR context but
1573 * @retval -ENOTSUP The given channel is within the range of valid
1574 * channels of the driver's current channel page but unsupported by the
1576 * @retval -EIO The channel could not be set.
1585 * @note Implementations SHALL be **isr-ok** and MAY **sleep**. SHALL
1586 * return -EIO unless the interface is either "UP" or "DOWN".
1590 * @param type the type of entity to be added/removed from the filter
1595 * @retval -EINVAL The given filter entity or filter entity type
1597 * @retval -EWOULDBLOCK The operation is called from ISR context but
1599 * @retval -ENOTSUP Setting/removing this filter or filter type
1601 * @retval -EIO Error while setting/removing the filter.
1611 * @note Implementations SHALL be **isr-ok** and MAY **sleep**. SHALL
1612 * return -EIO unless the interface is either "UP" or "DOWN".
1618 * @retval -EINVAL The given dbm value is invalid or not supported by
1620 * @retval -EWOULDBLOCK The operation is called from ISR context but
1622 * @retval -EIO The TX power could not be set.
1627 * @brief Transmit a packet fragment as a single frame
1629 * @details Depending on the level of offloading features supported by
1630 * the driver, the frame MAY not be fully encrypted/authenticated or it
1631 * MAY not contain an FCS. It is the responsibility of L2
1632 * implementations to prepare the frame according to the offloading
1638 * pre-allocated and pre-filled such that the driver does not have to
1646 * any of the timed TX modes with appropriate timing information
1647 * pre-filled in the IE such that drivers do not have to parse and
1648 * manipulate IEs at all unless the frame is generated by the driver
1651 * In case any of the timed TX modes is supported and used (see @ref
1653 * take responsibility of scheduling and sending the packet at the
1662 * @warning The driver SHALL NOT take ownership of the given network
1663 * packet and frame (fragment) buffer. Any data required by the driver
1664 * including the actual frame content must be read synchronously and
1665 * copied internally if needed at a later time (e.g. the contents of IEs
1666 * required for protocol configuration, states of frame counters,
1668 * re-used or released by upper layers immediately after the function
1672 * **isr-ok** - especially when timed TX, CSMA/CA, retransmissions,
1673 * auto-ACK or any other offloading feature is supported that implies
1674 * considerable idle waiting time. SHALL return `-ENETDOWN` unless the
1683 * and receive an ACK on that channel if the frame requested it. After
1686 * It is responsibility of an upper layer to set the required radio channel
1688 * This feature allows CSL transmissions as stated in IEEE 802.15.4-2020
1690 * a switch of the radio channel as late as possible before transmission without
1695 * @param mode the transmission mode, some of which require specific
1699 * with the frame data to be transmitted
1701 * @retval 0 The frame was successfully sent or scheduled. If the driver
1702 * supports ACK offloading and the frame requested acknowledgment (AR bit
1705 * @retval -EINVAL Invalid packet (e.g. an expected IE is missing or the
1707 * @retval -EBUSY The frame could not be sent because the medium was
1709 * @retval -ENOMSG The frame was not confirmed by an ACK packet (TX ACK
1711 * @retval -ENOBUFS The frame could not be scheduled due to missing
1713 * @retval -ENETDOWN The interface is not "UP".
1714 * @retval -ENOTSUP The given TX mode is not supported.
1715 * @retval -EIO The frame could not be sent due to some unspecified
1722 * @brief Start the device.
1725 * operation returns with zero or `-EALREADY`. The interface is placed
1730 * @note Implementations SHALL be **isr-ok** and MAY **sleep**. MAY be
1737 * @retval -EALREADY The driver was already "UP".
1738 * @retval -EWOULDBLOCK The operation is called from ISR context but
1740 * @retval -EIO The driver could not be started.
1742 int (*start)(const struct device *dev); member
1748 * operation returns with zero or `-EALREADY`. The driver switches off
1754 * @note Implementations SHALL be **isr-ok** and MAY **sleep**. MAY be
1761 * @retval -EWOULDBLOCK The operation is called from ISR context but
1763 * @retval -EALREADY The driver was already "DOWN".
1764 * @retval -EIO The driver could not be stopped.
1770 * @brief Start continuous carrier wave transmission.
1773 * continuous carrier. To leave this mode, `start()` or `stop()` should
1778 * **isr-ok**. MAY be called in any interface state once the driver is
1784 * @retval -EALREADY The driver was already in "TESTING" state and
1786 * @retval -EIO not started
1791 * @brief Start modulated carrier wave transmission.
1799 * **isr-ok**. MAY be called in any interface state once the driver is
1807 * @retval -EALREADY The driver was already in "TESTING" state and
1809 * @retval -EIO not started
1821 * @note Implementations SHALL be **isr-ok** and MAY **sleep**. MAY be
1825 * ieee802154_config_type. In this case the operation returns `-EACCES`.
1833 * @retval -EINVAL The configuration parameters are invalid for the
1835 * @retval -ENOTSUP The given configuration type is not supported by
1837 * @retval -EACCES The given configuration type is supported by this
1840 * @retval -ENOMEM The configuration cannot be saved due to missing
1842 * @retval -ENOENT The resource referenced in the configuration
1844 * @retval -EWOULDBLOCK The operation is called from ISR context but
1846 * @retval -EIO An internal error occurred while trying to configure the
1860 * @note Implementations SHALL be **isr-ok** and MAY **sleep**. SHALL
1861 * return `-ENETDOWN` unless the interface is "UP".
1864 * @param duration duration of energy scan in ms
1869 * @retval -EBUSY the energy detection scan could not be scheduled at
1871 * @retval -EALREADY a previous energy detection scan has not finished
1873 * @retval -ENETDOWN The interface is not "UP".
1874 * @retval -ENOTSUP This driver does not support energy scans.
1875 * @retval -EIO The energy detection procedure could not be executed.
1889 * capabilities. Implementations SHALL be **isr-ok** and MUST NOT
1896 * -1 if an error occurred or the operation is not supported
1902 * deviation from the nominal frequency) of the network subsystem's
1906 * The deviation is given in units of PPM (parts per million).
1913 * **isr-ok** and MUST NOT **sleep**. MAY be called in any interface
1923 * @brief Get the value of a driver specific attribute.
1926 * MAC (L2) layer. It is reserved to non-boolean (i.e. scalar or
1931 * @note Implementations SHALL be **isr-ok** and MUST NOT **sleep**. MAY
1939 * @retval -ENOENT The driver does not provide the requested attribute.
1941 * content of the value attribute is undefined.
1965 * @brief Check if the AR flag is set on the frame inside the given @ref
1976 return (*frag->data & IEEE802154_AR_FLAG_SET); in ieee802154_is_ar_flag_set()
1995 * fast and re-usable generic implementation of this callback for
1998 * Note: This function is part of Zephyr's 802.15.4 stack driver -> L2
1999 * "inversion-of-control" adaptation API and must be implemented by all
2017 * @details Drivers must call this function as part of their own initialization
2020 * Note: This function is part of Zephyr's 802.15.4 stack driver -> L2
2021 * "inversion-of-control" adaptation API and must be implemented by all