Searched full:layer (Results 1 – 25 of 487) sorted by relevance
12345678910>>...20
| /Zephyr-Core-3.7.0/subsys/usb/device_next/class/ |
| D | Kconfig.bt | 5 bool "Bluetooth HCI USB Transport Layer"
9 Bluetooth HCI USB Transport Layer
17 Bluetooth HCI USB Transport Layer TX thread priority.
23 Bluetooth HCI USB Transport Layer TX thread stack size.
29 Bluetooth HCI USB Transport Layer RX thread priority.
|
| /Zephyr-Core-3.7.0/subsys/net/l2/virtual/ |
| D | Kconfig | 7 Add a virtual L2 layer driver. This is needed if you have a L2
8 layer that depends on other L2 layer. Like running VPN on top of
22 int "Max length of the virtual L2 layer name"
31 module-str = Log level for virtual L2 layer
|
| /Zephyr-Core-3.7.0/doc/connectivity/networking/api/ |
| D | net_linkaddr.rst | 3 Link Layer Address Handling
13 The link layer addresses are set for network interfaces so that L2
14 connectivity works correctly in the network stack. Typically the link layer
16 layer address length is 8 bytes.
|
| D | net_l2.rst | 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,
28 :ref:`OpenThread <thread_protocol_interface>`, Wi-Fi, and a dummy layer example
31 L2 layer API
34 In order to create an L2 layer, or a driver for a specific L2 layer,
35 one needs to understand how the L3 layer interacts with it and
36 how the L2 layer is supposed to behave.
[all …]
|
| D | lldp.rst | 3 Link Layer Discovery Protocol
13 The Link Layer Discovery Protocol (LLDP) is a vendor-neutral link layer
|
| D | net_mgmt.rst | 14 layer code itself, to call defined network routines at any level in
36 mask that tells which stack layer is targeted, if a ``net_if`` object is
53 pair of layer and code, whereas on the command part it will be a mask of
73 layer and layer code. A callback handler function **must** check
79 multiple listeners registered, one for each layer being listened.
80 The callback handler function can be shared between different layer events.
82 (False positives can occur for events which have the same layer and
83 layer code.)
176 the targeted layer or eventually, if l2 is the layer, on the
177 technology as well. For instance, all IP layer management request code
|
| /Zephyr-Core-3.7.0/subsys/net/lib/capture/ |
| D | sll.h | 21 uint16_t sll_hatype; /* Link-layer address type */
22 uint16_t sll_halen; /* Link-layer address length */
23 uint8_t sll_addr[SLL_ADDRLEN]; /* Link-layer address */
35 uint16_t sll2_hatype; /* Link-layer address type */
37 uint8_t sll2_halen; /* Link-layer address length */
38 uint8_t sll2_addr[SLL_ADDRLEN]; /* Link-layer address */
|
| /Zephyr-Core-3.7.0/subsys/net/l2/canbus/ |
| D | Kconfig | 5 bool "CANBUS RAW l2 layer"
7 Add a CANBUS L2 layer driver. This is the layer for SOCKET CAN.
|
| /Zephyr-Core-3.7.0/doc/hardware/peripherals/ |
| D | w1.rst | 40 * The link layer handles basic communication functions such as bus reset,
42 It is the only hardware-dependent layer in Zephyr.
43 This layer is supported by a driver using the Zephyr :ref:`uart_api` interface,
47 * The 1-Wire network layer handles all means for slave identification and bus
57 * Transport layer and Presentation layer functions are not implemented in the
75 1-Wire data link layer
80 1-Wire network layer
|
| /Zephyr-Core-3.7.0/subsys/usb/usb_c/ |
| D | usbc_prl.h | 95 * @brief Start the PRL Layer state machine. This is only called from the
110 * @brief Suspends the PRL Layer state machine. This is only called from the
118 * @brief Reset the PRL Layer state machine
125 * @brief Run the PRL Layer state machine. This is called from the subsystems
160 * @brief Instructs the Protocol Layer to send a Power Delivery control message
170 * @brief Instructs the Protocol Layer to send a Power Delivery data message
180 * @brief Instructs the Protocol Layer to execute a hard reset
187 * @brief Query if the Protocol Layer is running
191 * @retval TRUE if the Protocol Layer is running
192 * @retval FALSE if the Protocol Layer is not running
|
| D | usbc_prl.c | 18 * @brief USB Power Delivery Protocol Layer (PRL)
25 * @brief Protocol Layer Flags
47 * cleared when the message is sent to the TCPC layer.
57 * @brief Protocol Layer Transmission States
87 * @brief Protocol Layer Hard Reset States
136 * @brief Test if the Protocol Layer State Machines are running
149 * @brief Directs the Protocol Layer to perform a hard reset. This function
167 * @brief Instructs the Protocol Layer that a hard reset is complete.
179 * @brief Directs the Protocol Layer to construct and transmit a Power Delivery
199 * @brief Directs the Protocol Layer to construct and transmit a Power Delivery
[all …]
|
| D | usbc_tc_common_internal.h | 64 * @brief TC Layer State Machine Object
67 /** TC layer state machine context */
71 /** TC layer flags */
132 * @brief Run the TC Layer state machine. This is called from the subsystems
141 * @brief Checks if the TC Layer is in an Attached state
145 * @retval true if TC Layer is in an Attached state, else false
|
| D | usbc_stack.h | 21 * @brief Each layer of the stack is composed of state machines that can be
65 /* Type-C layer data */
74 /* Policy Engine layer data */
83 /* Protocol Layer data */
85 /** Protocol Receive Layer state machine object */
87 /** Protocol Transmit Layer state machine object */
89 /** Protocol Hard Reset Layer state machine object */
91 /** Enables or Disables the Protocol Layer state machine */
93 /** The state of the Protocol Layer state machine */
|
| /Zephyr-Core-3.7.0/include/zephyr/drivers/serial/ |
| D | uart_async_to_irq.h | 17 * @brief UART Asynchronous to Interrupt driven API adaptation layer
28 /** @brief Data structure used by the adaptation layer.
34 /** @brief Configuration structure used by the adaptation layer.
110 /** @brief Initialize the adaptation layer.
112 * @param data Data associated with the given adaptation layer instance.
125 * @retval -EINVAL if adaption layer has wrong configuration.
135 * @retval -EINVAL if adaption layer has wrong configuration.
143 * @brief Structure used by the adaptation layer.
155 /** Async API used by the a2i layer. */
168 /** @brief Asynchronous API used by the adaptation layer. */
[all …]
|
| /Zephyr-Core-3.7.0/subsys/net/l2/ |
| D | Kconfig | 4 menu "Link layer options"
7 bool "Dummy l2 layer"
10 Add a dummy L2 layer driver. This is usually only needed when
64 module-str = Log level for Wi-Fi management layer
|
| /Zephyr-Core-3.7.0/subsys/net/ip/ |
| D | nbr.h | 25 /* The neighbors are tracked by link layer address. This is not part
30 /** Link layer address */
149 * @param lladdr Neighbor link layer address
157 * @brief Link a neighbor to specific link layer address.
160 * @param lladdr Neighbor link layer address
167 * @brief Unlink a neighbor from specific link layer address.
169 * @param lladdr Neighbor link layer address
176 * @param idx Link layer address index in ll table.
177 * @return Pointer to link layer address storage, NULL if not found
|
| /Zephyr-Core-3.7.0/dts/bindings/display/ |
| D | st,stm32-ltdc.yaml | 55 description: First pixel in x direction on layer 0. Defaults to 0.
59 description: Last pixel in x direction on layer 0. Defaults to width.
63 description: First pixel in y direction on layer 0. Defaults to 0.
67 description: Last pixel in y direction on layer 0. Defaults to height.
|
| /Zephyr-Core-3.7.0/doc/connectivity/bluetooth/api/mesh/ |
| D | sar_cfg.rst | 6 Segmentation and reassembly (SAR) provides a way of handling larger upper transport layer messages
8 reassembly mechanism is used by the lower transport layer.
10 The lower transport layer defines how the upper transport layer PDUs are segmented and reassembled
11 into multiple Lower Transport PDUs, and sends them to the lower transport layer on a peer device.
13 which do not fit into a single Lower Transport PDU, the lower transport layer performs segmentation,
17 The lower transport layer on the receiving device reassembles the segments into a single Upper
19 lower transport layer of the receiving node, while an unsegmented message delivery is not
21 sent as a single-segment segmented message when acknowledgment by the lower transport layer is
25 The transport layer is able to transport up to 32 segments with its SAR mechanism, with a maximum
44 SAR does not impose extra overhead on the access layer payload per segment.
[all …]
|
| /Zephyr-Core-3.7.0/modules/ |
| D | Kconfig.syst | 12 bool "STP Transport Layer for MIPI SyS-T"
15 Transport Layer for MIPI SyS-T
|
| /Zephyr-Core-3.7.0/include/zephyr/net/ |
| D | net_linkaddr.h | 84 * when we have to store the link layer address.
102 * @brief Compare two link layer addresses.
104 * @param lladdr1 Pointer to a link layer address
105 * @param lladdr2 Pointer to a link layer address
125 * @brief Set the member data of a link layer address storage structure.
|
| D | net_l2.h | 25 * @brief Network Layer 2 abstraction layer
26 * @defgroup net_l2 Network L2 Abstraction Layer
59 * This function is used by net core to get iface's L2 layer parsing
65 * This function is used by net core to push a packet to lower layer
|
| /Zephyr-Core-3.7.0/subsys/bluetooth/mesh/ |
| D | access.h | 85 * Register a callback function to act as a hook for receiving mesh model layer messages
95 * Send a mesh model layer message out into the mesh network without having instantiated
109 /** @brief Initialize the Access layer.
115 /** @brief Suspend the Access layer.
119 /** @brief Reset the Access layer.
|
| /Zephyr-Core-3.7.0/drivers/wifi/esp32/ |
| D | Kconfig.esp32 | 79 and then delivers it to the high layer TCP/IP stack. The dynamic RX buffer
80 is freed after the higher layer has successfully received the data frame.
101 frame sent by the TCP/IP layer.
128 For each transmitted data frame from the higher layer TCP/IP stack,
130 especially UDP applications, the upper layer can deliver frames faster
131 than WiFi layer can transmit.
158 For each transmitted frame from the higher layer TCP/IP stack,
160 especially UDP applications, the upper layer can deliver frames faster
161 than WiFi layer can transmit. In these cases, we may run out of TX
|
| /Zephyr-Core-3.7.0/doc/connectivity/bluetooth/ |
| D | bluetooth-le-host.rst | 151 a common layer for all communication over Bluetooth connections, however
168 * - Upper layer
169 - Layer above L2CAP, it exchanges data in form of SDUs. It may be an
172 * - Lower layer
173 - Layer below L2CAP, it exchanges data in form of PDUs (or fragments). It is
177 - Packet of data that L2CAP exchanges with the upper layer.
192 - Maximum size of an SDU that the upper layer is capable of accepting.
195 - Maximum payload size that the L2CAP layer is capable of accepting.
213 layer or delivered to the upper layer as its payload.
273 over LE connections. A more detailed description of this layer and the
|
| /Zephyr-Core-3.7.0/drivers/usb/udc/ |
| D | udc_common.h | 345 * submit both setup and data buffer to upper layer.
359 * submit both setup and data buffer to upper layer.
371 * submit both setup and status buffer to upper layer.
382 * Submit both status transaction to upper layer.
406 * - Upper layer may not allocate buffers but remove or release buffers
408 * be enqueued by the upper layer.
414 * upper layer. Upper layer should either halt control endpoint or
416 * notification to upper layer when the status transaction is finished.
441 * the chain of s-in to upper layer. Upper layer should either halt control
443 * notification to upper layer when the status transaction is finished.
[all …]
|
12345678910>>...20
