Lines Matching refs:L2
3 L2 Layer Management
13 The L2 stack is designed to hide the whole networking link-layer part
19 object and the generic API provided by the L2 layer in
22 Only the L2 layer can talk to the device driver, linked to the net_if
23 object. The L2 layer dictates the API provided by the device driver,
26 Currently, there are L2 layers for :ref:`Ethernet <ethernet_interface>`,
31 L2 layer API
34 In order to create an L2 layer, or a driver for a specific L2 layer,
36 how the L2 layer is supposed to behave.
38 more details. The generic L2 API has these functions:
44 buffer along to the L2 stack's ``recv()`` function for handling.
45 The L2 stack does what it needs to do with the packet, for example, parsing
48 ``NET_OK`` if the packet was fully consumed by the L2, or ``NET_CONTINUE``
60 - ``get_flags()``: This function will return the capabilities of an L2 driver,
61 for example whether the L2 supports multicast or promiscuous mode.
80 Implementing a network device driver depends on the L2 stack it
114 Device drivers for IEEE 802.15.4 L2 work basically the same as for
119 which overloads :c:struct:`net_if_api`. This is because 802.15.4 L2 needs more from the device
137 IEEE 802.15.4 L2 implementation provides a generic :c:func:`ieee802154_send`
146 Interaction between IEEE 802.15.4 radio device drivers and L2 is bidirectional:
148 - L2 -> L1: Methods as :c:func:`ieee802154_send` and several IEEE 802.15.4 net
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
158 MAC (L2) and PHY (L1) whenever reverse information transfer or close co-operation
159 between hardware and L2 is required. During driver initialization, for example,
161 as well as other hardware-related configuration to L2. Similarly, drivers may
162 indicate performance or timing critical radio events to L2 that require close
164 from L1 into L2 are not implemented as methods in :c:struct:`ieee802154_radio_api`
167 clearly state which functions must be implemented by all L2 stacks as part
168 of the L1 -> L2 "inversion-of-control" adaptation API.
172 within the PHY (L1) layer implemented independently of any specific L2 stack, see for