| /Zephyr-latest/include/zephyr/drivers/firmware/scmi/ |
| D | util.h | 11 * Contains various utility macros and macros used for protocol and
19 * @brief Build protocol name from its ID
21 * Given a protocol ID, this macro builds the protocol
23 * construct with the given protocol ID.
25 * @param proto protocol ID in decimal format
27 * @return protocol name
34 /** @brief Check if a protocol node has an associated channel
36 * This macro, when applied to a protocol node, checks if
43 * @param node_id protocol node identifier
58 * Given a node_id for a protocol, this macro declares the SCMI
[all …]
|
| D | clk.h | 9 * @brief SCMI clock protocol helpers
15 #include <zephyr/drivers/firmware/scmi/protocol.h>
36 * @brief Clock protocol command message IDs
61 * @param proto pointer to SCMI clock protocol data
74 * @param proto pointer to SCMI clock protocol data
86 * @param proto pointer to SCMI clock protocol data
|
| D | protocol.h | 9 * @brief SCMI protocol generic functions and structures
28 * @param proto protocol ID
72 * @brief SCMI protocol structure
75 /** protocol ID */
81 /** protocol private data */
111 * @param proto pointer to SCMI protocol
|
| /Zephyr-latest/drivers/firmware/scmi/ |
| D | Kconfig | 7 bool "Helper functions for SCMI clock protocol"
11 Enable support for SCMI clock protocol helper functions.
24 bool "Helper functions for SCMI pinctrl protocol"
29 Enable support for SCMI pinctrl protocol helper functions.
48 What this means is that each protocol will have its channels
51 allocation scheme (i.e: use protocol-specific channels if
52 they exist, otherwise use base protocol channels).
|
| D | mailbox.h | 18 /* get a `struct device` for a protocol's shared memory area */
34 /* define private data for a protocol TX channel */
55 * Optionally define a mailbox channel for a protocol. This is optional
56 * because a protocol might not have a dedicated channel.
63 /* define a TX channel for a protocol node. This is preferred over
71 /* define and validate base protocol TX channel */
94 * 1) Goes through all protocol nodes (children of the `scmi` node)
96 * `struct scmi_mbox_channel` if the protocol has a dedicated channel.
98 * 2) Creates aforementioned structures for the base protocol
|
| /Zephyr-latest/drivers/net/ |
| D | nsos.h | 13 /* Protocol families. */
14 #define NSOS_MID_PF_UNSPEC 0 /**< Unspecified protocol family. */
15 #define NSOS_MID_PF_INET 1 /**< IP protocol family version 4. */
16 #define NSOS_MID_PF_INET6 2 /**< IP protocol family version 6. */
17 #define NSOS_MID_PF_UNIX 6 /**< Unix protocol. */
22 #define NSOS_MID_AF_INET NSOS_MID_PF_INET /**< IP protocol family version 4. */
23 #define NSOS_MID_AF_INET6 NSOS_MID_PF_INET6 /**< IP protocol family version 6. */
24 #define NSOS_MID_AF_UNIX NSOS_MID_PF_UNIX /**< Unix protocol. */
27 /** Protocol numbers from IANA/BSD */
29 NSOS_MID_IPPROTO_IP = 0, /**< IP protocol (pseudo-val for setsockopt() */
[all …]
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | ppp.rst | 3 Point-to-Point Protocol (PPP) Support
13 `Point-to-Point Protocol
15 layer (layer 2) communications protocol used to establish a direct connection
18 protocol.
27 * LCP (Link Control Protocol,
31 * IPCP (IP Control Protocol,
33 * IPV6CP (IPv6 Control Protocol,
|
| D | thread.rst | 3 Thread protocol
14 technology over IEEE 802.15.4 protocol. IP connectivity lets you easily connect
20 Thread protocol can be found at
23 Zephyr integrates an open source Thread protocol implementation called OpenThread,
53 OpenThread L2 uses Zephyr's protocol agnostic IEEE 802.15.4 driver API
64 stack together with Zephyr's IEEE 802.15.4 protocol agnostic driver API. This
|
| D | lldp.rst | 3 Link Layer Discovery Protocol
13 The Link Layer Discovery Protocol (LLDP) is a vendor-neutral link layer
14 protocol used by network devices for advertising their identity, capabilities,
|
| D | ptp.rst | 3 Precision Time Protocol (PTP)
13 PTP is a network protocol implemented in the application layer, used to synchronize
15 The stack supports the protocol and procedures as defined in the `IEEE 1588-2019 standard`_
16 (IEEE Standard for a Precision Clock Synchronization Protocol
19 Its accuracy is achieved by using hardware timestamping of the protocol packets.
49 UDP IPv4 transport protocol, yes
50 UDP IPv6 transport protocol, yes
51 IEEE 802.3 (Ethernet) transport protocol,
|
| /Zephyr-latest/subsys/sd/ |
| D | Kconfig | 9 bool "MMC protocol support"
11 Enable MMC protocol support. Required for eMMC cards to function.
14 bool "SDMMC protocol support"
16 Enable SDMMC protocol support. Required for SD memory cards to
20 bool "SDIO protocol support"
22 Enable SDIO protocol support. Required for SD I/O cards to function.
97 bool "Ultra high speed SD card protocol support"
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | arm-scmi.rst | 17 Agent, platform, protocol and transport
31 #. Protocol
32 A protocol is a set of messages grouped by functionality. Intuitively, a message
48 where each of these protocols is identified by an unique protocol ID
52 **0x80-0xFF** protocol ID range for vendor-specific protocols.
142 Clock management protocol
145 This protocol is used to perform clock management operations. This is done
155 Pin Control protocol
158 This protocol is used to perform pin configuration operations. This is done
163 The support for this protocol **does not** include a definition for
[all …]
|
| /Zephyr-latest/drivers/sdhc/ |
| D | Kconfig | 41 to enable UHS portion of protocol stack.
47 Enables SPI protocol in SD protocol stack
53 required. Enables native protocol in SD protocol stack.
|
| /Zephyr-latest/samples/subsys/mgmt/osdp/ |
| D | README.rst | 3 Open Supervised Device Protocol (OSDP)
6 Open Supervised Device Protocol (OSDP) is an IEC standard (IEC 60839-11-5)
11 OSDP describes the communication protocol for interfacing one or more Peripheral
13 communication channel. Nevertheless, this protocol can be used to transfer
18 used as a general communication protocol for devices in a secure way without
|
| /Zephyr-latest/subsys/canbus/ |
| D | Kconfig.canopen | 5 bool "CANopen protocol support"
9 Enable CANopen (EN 50325-4) (CiA 301) protocol
11 protocol stack.
|
| /Zephyr-latest/subsys/net/l2/ppp/ |
| D | link.c | 22 if (proto->protocol == PPP_LCP) { in lcp_up()
37 if (proto->protocol == PPP_CCP || proto->protocol == PPP_ECP) { in do_network()
50 if (proto->protocol == PPP_CCP || proto->protocol == PPP_ECP || in do_network()
51 proto->protocol >= 0xC000) { in do_network()
87 if (proto->protocol == auth_proto) { in do_auth()
|
| D | ppp_internal.h | 38 /** Protocol handler information. */
40 /** Protocol init function */
54 /** Enable this protocol */
57 /** Disable this protocol */
60 /** PPP protocol number */
61 uint16_t protocol; member
83 enum ppp_protocol_type protocol,
96 .protocol = proto, \
110 const char *ppp_option2str(enum ppp_protocol_type protocol, int type);
137 uint16_t protocol);
[all …]
|
| /Zephyr-latest/samples/modules/thrift/hello/client/src/ |
| D | main.cpp | 16 #include <thrift/protocol/TBinaryProtocol.h>
17 #include <thrift/protocol/TCompactProtocol.h>
25 using namespace apache::thrift::protocol;
68 std::shared_ptr<TProtocol> protocol; in main() local
110 protocol = std::make_shared<TCompactProtocol>(transport); in main()
112 protocol = std::make_shared<TBinaryProtocol>(transport); in main()
115 HelloClient client(protocol); in main()
|
| /Zephyr-latest/doc/connectivity/canbus/ |
| D | isotp.rst | 3 ISO-TP Transport Protocol
13 ISO-TP is a transport protocol defined in the ISO-Standard ISO15765-2 Road
15 Part2: Transport protocol and network layer services. As its name already
20 This transport protocol extends the limited payload data size for classical
24 size of the CAN frame. The header of those segments is called Protocol Control
|
| /Zephyr-latest/subsys/logging/backends/ |
| D | Kconfig.spinel | 5 bool "OpenThread dedicated Spinel protocol backend"
9 When enabled, backend will use OpenThread dedicated SPINEL protocol for logging.
10 This protocol is byte oriented and wraps given messages into serial frames.
|
| /Zephyr-latest/doc/services/modbus/ |
| D | index.rst | 6 Modbus is an industrial messaging protocol. The protocol is specified
23 `MODBUS Protocol Specifications`_.
39 .. _`MODBUS Protocol Specifications`: https://www.modbus.org/specs.php
|
| /Zephyr-latest/include/zephyr/drivers/sip_svc/ |
| D | sip_svc_agilex_mailbox.h | 13 * protocol handler. SDM Mailbox protocol will be embedded in
14 * Arm SiP Services SMC protocol and sent to/from SDM via Arm
|
| /Zephyr-latest/dts/bindings/usb/ |
| D | zephyr,hid-device.yaml | 17 protocol-code:
20 This property corresponds to the protocol codes defined in Chapter 4.3
25 - keyboard: Device supports boot interface and keyboard protocol
26 - mouse: Device supports boot interface and mouse protocol
|
| /Zephyr-latest/doc/services/debugging/ |
| D | mipi_stp_decoder.rst | 6 The MIPI System Trace Protocol (MIPI STP) was developed as a generic base protocol that can
7 be shared by multiple application-specific trace protocols. It serves as a wrapper protocol
14 One example where protocol is used is ARM Coresight STM (System Trace Macrocell) where data
|
| /Zephyr-latest/modules/thrift/src/thrift/server/ |
| D | TSimpleServer.h | 50 const std::shared_ptr<apache::thrift::protocol::TProtocolFactory> &protocolFactory);
57 const std::shared_ptr<apache::thrift::protocol::TProtocolFactory> &protocolFactory);
66 const std::shared_ptr<apache::thrift::protocol::TProtocolFactory>
68 const std::shared_ptr<apache::thrift::protocol::TProtocolFactory>
78 const std::shared_ptr<apache::thrift::protocol::TProtocolFactory>
80 const std::shared_ptr<apache::thrift::protocol::TProtocolFactory>
|
