Lines Matching +full:pre +full:- +full:declared

13 The L2 stack is designed to hide the whole networking link-layer part
15 through a :c:struct:`net_if` declared in
27 :ref:`IEEE 802.15.4 Soft-MAC <ieee802154_interface>`, :ref:`CANBUS <can_api>`,
28 :ref:`OpenThread <thread_protocol_interface>`, Wi-Fi, and a dummy layer example
40 - ``recv()``: All device drivers, once they receive a packet which they put
46   the link layer header, or handling link-layer only packets. The ``recv()``
51 - ``send()``: Similar to receive function, the network stack will call this
52   function to actually send a network packet. All relevant link-layer content
57 - ``enable()``: This function is used to enable/disable traffic over a network
60 - ``get_flags()``: This function will return the capabilities of an L2 driver,
71 - The driver_api pointer must point to a valid :c:struct:`net_if_api`
74 - The network device driver must use :c:macro:`NET_DEVICE_INIT_INSTANCE()`
90 On reception, it is up to the device driver to fill-in the network packet with
106 .. code-block:: c
118 - It requires a dedicated device driver API: :c:struct:`ieee802154_radio_api`,
121   declared in :zephyr_file:`include/zephyr/net/ieee802154_radio.h`. Each and every
123   relevantly filled-in API structure.
125 - Sending a packet is slightly different than in Ethernet. Most IEEE 802.15.4
132   medium access (e.g. CSMA/CA), frame retransmission, encryption and other pre-processing
141   encrypted and otherwise pre-processed fragment buffers, sending one buffer
148 - L2 -> L1: Methods as :c:func:`ieee802154_send` and several IEEE 802.15.4 net
150   radio link or re-configure the driver at runtime. These incoming calls will
153 - L1 -> L2: There are several situations in which the driver needs to initiate
154   calls into the L2/MAC layer. Zephyr's IEEE 802.15.4 L1 -> L2 adaptation API
155   employs an "inversion-of-control" pattern in such cases avoids duplication of
158   MAC (L2) and PHY (L1) whenever reverse information transfer or close co-operation
161   as well as other hardware-related configuration to L2. Similarly, drivers may
165   but are standalone functions declared and documented as such in
168   of the L1 -> L2 "inversion-of-control" adaptation API.
178 .. code-block:: c