| /Zephyr-latest/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-latest/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-latest/doc/connectivity/networking/api/ |
| D | net_linkaddr.rst | 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_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
|
| D | net_l2.rst | 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.
46 the link layer header, or handling link-layer only packets. The ``recv()``
[all …]
|
| D | lldp.rst | 13 The Link Layer Discovery Protocol (LLDP) is a vendor-neutral link layer
|
| D | ppp.rst | 15 layer (layer 2) communications protocol used to establish a direct connection
|
| /Zephyr-latest/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-latest/drivers/firmware/scmi/ |
| D | Kconfig | 45 bool "Transport layer has static channels"
47 Enable this if the SCMI transport layer uses static channels.
50 transport layer drivers which can use the default channel
55 int "SCMI transport layer initialization priority"
|
| /Zephyr-latest/drivers/display/ |
| D | display_renesas_lcdc.c | 65 lcdc_smartbond_layer_cfg layer; member
176 data->layer.color_format = in display_smartbond_configure()
178 data->layer.stride = in display_smartbond_configure()
179 da1469x_lcdc_stride_calculation(data->layer.color_format, config->x_res); in display_smartbond_configure()
181 ret = da1469x_lcdc_layer_configure(&data->layer); in display_smartbond_configure()
475 src += (y * data->layer.stride); in display_smartbond_read()
510 src += data->layer.stride; in display_smartbond_read()
537 dst += (y * data->layer.stride); in display_smartbond_write()
579 dst += data->layer.stride; in display_smartbond_write()
666 .layer.start_x = 0, \
[all …]
|
| /Zephyr-latest/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-latest/subsys/net/ |
| D | Kconfig | 9 bool "Link layer and networking (including IP)"
14 This option enables generic link layer and networking support
|
| /Zephyr-latest/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 …]
|
| D | op_agg_srv.rst | 12 a sequence of access layer messages.
20 to encrypt the sequence of access layer messages sent to the Opcodes Aggregator Server.
|
| /Zephyr-latest/tests/bluetooth/controller/common/ |
| D | Kconfig | 4 # The link layer requires a corresponding device tree node to be enabled
|
| /Zephyr-latest/drivers/mipi_dbi/ |
| D | mipi_dbi_smartbond.c | 66 lcdc_smartbond_layer_cfg layer; member
336 lcdc_smartbond_layer_cfg *layer = &data->layer; in mipi_dbi_smartbond_write_display() local
375 LCDC_SMARTBOND_LAYER_CONFIG(layer, framebuf, 0, 0, desc->width, desc->height, in mipi_dbi_smartbond_write_display()
378 ret = da1469x_lcdc_layer_configure(layer); in mipi_dbi_smartbond_write_display()
|
| /Zephyr-latest/modules/ |
| D | Kconfig.libmetal | 11 This option enables the libmetal HAL abstraction layer
|
| /Zephyr-latest/boards/native/doc/ |
| D | arch_soc.rst | 14 The native simulator in combination with the POSIX architecture and the inf_clock SOC layer,
41 with focus on their radio (e.g. BT LE) and utilize the `BabbleSim`_ physical layer
188 :ref:`the architecture section's architecture layer paragraph <posix_arch_design_archl>`
397 Arch layer
405 layer and the native simulator CPU threading emulation (NCT).
407 This layer together with the NCT maps each Zephyr thread into one POSIX pthread, and emulates a
426 SOC layer
429 This SOC layer is mainly a very thin layer on top of the native simulator CPU emulation layer,
431 initialization of the arch layer, and calling into the Zephyr boot (:c:func:`z_cstart()`) during
435 a few other hooks it expects the board layer to provide.
[all …]
|
| /Zephyr-latest/drivers/w1/ |
| D | Kconfig | 52 bool "1-Wire network layer"
55 Enable 1-wire network layer
|
| /Zephyr-latest/subsys/net/lib/shell/ |
| D | events.c | 393 uint32_t layer; in event_mon_handler() local
402 layer = NET_MGMT_GET_LAYER(msg.event); in event_mon_handler()
403 if (layer == NET_MGMT_LAYER_L2) { in event_mon_handler()
406 } else if (layer == NET_MGMT_LAYER_L3) { in event_mon_handler()
410 } else if (layer == NET_MGMT_LAYER_L4) { in event_mon_handler()
|
| /Zephyr-latest/doc/connectivity/lora_lorawan/ |
| D | index.rst | 13 LoRa acts as the physical layer (PHY) based on the chirp spread spectrum
16 LoRaWAN (for Long Range Wide Area Network) defines a networking layer
|
| /Zephyr-latest/doc/services/portability/ |
| D | cmsis_rtos_v1.rst | 7 hardware abstraction layer for the ARM Cortex-M processor series and defines
|
| /Zephyr-latest/soc/microchip/miv/polarfire/ |
| D | Kconfig | 38 bool "Microchip Polarfire SOC hardware abstracton layer"
|
| /Zephyr-latest/doc/services/pm/ |
| D | overview.rst | 11 Thus a coherent abstraction is presented to the rest of the OS and the application layer.
|
| /Zephyr-latest/samples/net/zperf/ |
| D | CMakeLists.txt | 13 # Relocate key networking stack components and L2 layer to RAM
|
