Searched full:protocol (Results 1 – 25 of 493) sorted by relevance
12345678910>>...20
| /Documentation/netlabel/ |
| D | introduction.rst | 15 is composed of three main components, the protocol engines, the communication
18 Protocol Engines
21 The protocol engines are responsible for both applying and retrieving the
23 security attributes and those on the host are required then the protocol
25 refrain from calling the protocol engines directly, instead they should use
28 Detailed information about each NetLabel protocol engine can be found in this
36 protocol built on top of the Generic NETLINK transport mechanism. The exact
44 The purpose of the NetLabel security module API is to provide a protocol
45 independent interface to the underlying NetLabel protocol engines. In addition
46 to protocol independence, the security module API is designed to be completely
|
| D | cipso_ipv4.rst | 2 NetLabel CIPSO/IPv4 Protocol Engine
12 The NetLabel CIPSO/IPv4 protocol engine is based on the IETF Commercial
22 The CIPSO/IPv4 protocol engine applies the CIPSO IP option to packets by
34 The CIPSO/IPv4 protocol engine validates every CIPSO IP option it finds at the
44 The CIPSO/IPv4 protocol engine contains a mechanism to translate CIPSO security
56 CIPSO/IPv4 protocol engine supports this caching mechanism.
|
| /Documentation/devicetree/bindings/firmware/ |
| D | arm,scmi.yaml | 8 title: System Control and Management Interface (SCMI) Message Protocol
144 protocol@11:
145 $ref: '#/$defs/protocol-node'
158 protocol@12:
159 $ref: '#/$defs/protocol-node'
166 protocol@13:
167 $ref: '#/$defs/protocol-node'
187 protocol@14:
188 $ref: '#/$defs/protocol-node'
201 protocol@15:
[all …]
|
| D | nxp,imx95-scmi.yaml | 14 protocol@81:
15 $ref: '/schemas/firmware/arm,scmi.yaml#/$defs/protocol-node'
22 protocol@84:
23 $ref: '/schemas/firmware/arm,scmi.yaml#/$defs/protocol-node'
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | arm,mhuv2.yaml | 38 and the entire window shall be used in doorbell protocol. Optionally, data
93 one of the transport protocol being implemented over some channel
96 The first field of a tuple signifies the transfer protocol, 0 is reserved
97 for doorbell protocol, and 1 is reserved for data-transfer protocol.
101 the protocol would be used and should be set to a non zero value. For
102 doorbell protocol this field signifies the number of 32-bit channel
103 windows that implement the doorbell protocol. For data-transfer protocol,
105 the data-transfer protocol.
119 windows are used in doorbell protocol (64 doorbells), followed by 1, 5 and
120 7 windows (separately) used in data-transfer protocol.
[all …]
|
| /Documentation/userspace-api/media/rc/ |
| D | rc-protos.rst | 9 IR is encoded as a series of pulses and spaces, using a protocol. These
12 across different devices for a given protocol.
27 how scancodes are encoded for each protocol.
32 This IR protocol uses manchester encoding to encode 14 bits. There is a
36 protocol, or the manchester BPF decoder.
182 The jvc protocol is much like nec, without the inverted values. It is
191 The sony protocol is a pulse-width encoding. There are three variants,
218 The sony protocol is a pulse-width encoding. There are three variants,
245 The sony protocol is a pulse-width encoding. There are three variants,
278 The nec protocol encodes an 8 bit address and an 8 bit command. It is
[all …]
|
| D | rc-sysfs-nodes.rst | 43 Writing "+proto" will add a protocol to the list of enabled protocols.
45 Writing "-proto" will remove a protocol from the list of enabled
52 Write fails with ``EINVAL`` if an invalid protocol combination or unknown
53 protocol name is used.
68 This value may be reset to 0 if the current protocol is altered.
84 This value may be reset to 0 if the current protocol is altered.
97 Note that protocol variants are listed, so ``nec``, ``sony``, ``rc-5``, ``rc-6``
100 Note that all protocol variants are listed.
102 The enabled wakeup protocol is shown in [] brackets.
104 Only one protocol can be selected at a time.
[all …]
|
| /Documentation/trace/ |
| D | sys-t.rst | 7 The MIPI SyS-T protocol driver can be used with STM class devices to
11 In order to use the MIPI SyS-T protocol driver with your STM device,
14 Now, you can select which protocol driver you want to use when you create
25 If the protocol name is omitted, the STM class will chose whichever
26 protocol driver was loaded first.
30 # cat /config/stp-policy/dummy_stm.0:p_sys-t.my-policy/protocol
33 Now, with the MIPI SyS-T protocol driver, each policy node in the
35 parameters specific to the protocol:
56 can pass before we need to include a protocol (not transport, aka STP)
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-rc | 30 Writing "+proto" will add a protocol to the list of enabled
33 Writing "-proto" will remove a protocol from the list of enabled
40 Write fails with EINVAL if an invalid protocol combination or
41 unknown protocol name is used.
56 This value may be reset to 0 if the current protocol is altered.
73 This value may be reset to 0 if the current protocol is altered.
85 Note that protocol variants are listed, so "nec", "sony",
89 The enabled wakeup protocol is shown in [] brackets.
91 Only one protocol can be selected at a time.
97 Write fails with EINVAL if an invalid protocol combination or
[all …]
|
| D | debugfs-cxl | 43 (RO) Prints the CXL protocol error types made available by
50 0x1000 CXL.cache Protocol Correctable
51 0x2000 CXL.cache Protocol Uncorrectable non-fatal
52 0x4000 CXL.cache Protocol Uncorrectable fatal
53 0x8000 CXL.mem Protocol Correctable
54 0x10000 CXL.mem Protocol Uncorrectable non-fatal
55 0x20000 CXL.mem Protocol Uncorrectable fatal
66 CXL protocol error into $dport_dev ($dport_dev will be a device
|
| D | sysfs-class-net-dsa | 7 tagging protocol used by the DSA network devices that are
9 On write, this file changes the tagging protocol of the
11 driver. Changing the tagging protocol must be done with the DSA
|
| /Documentation/networking/caif/ |
| D | linux_caif.rst | 17 CAIF is a MUX protocol used by ST-Ericsson cellular modems for
32 * CAIF Core Protocol Implementation
47 ! +------+ <- CAIF Core Protocol
63 CAIF Core Protocol Layer
66 CAIF Core layer implements the CAIF protocol as defined by ST-Ericsson.
67 It implements the CAIF protocol stack in a layered approach, where
69 The architecture is inspired by the design patterns "Protocol Layer" and
70 "Protocol Packet".
91 The CAIF protocol can be divided into two parts: Support functions and Protocol
94 - CFPKT CAIF Packet. Implementation of CAIF Protocol Packet. The
[all …]
|
| /Documentation/arch/x86/ |
| D | boot.rst | 4 The Linux/x86 Boot Protocol
14 Currently, the following versions of the Linux/x86 boot protocol exist.
20 Protocol 2.00 (Kernel 1.3.73) Added bzImage and initrd support, as
26 Protocol 2.01 (Kernel 1.3.76) Added a heap overrun warning.
28 Protocol 2.02 (Kernel 2.4.0-test3-pre3) New command line protocol.
35 Protocol 2.03 (Kernel 2.4.18-pre1) Explicitly makes the highest possible
38 Protocol 2.04 (Kernel 2.6.14) Extend the syssize field to four bytes.
40 Protocol 2.05 (Kernel 2.6.20) Make protected mode kernel relocatable.
43 Protocol 2.06 (Kernel 2.6.22) Added a field that contains the size of
46 Protocol 2.07 (Kernel 2.6.24) Added paravirtualised boot protocol.
[all …]
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-intro.rst | 9 Control protocol. This protocol allows different devices connected by an
10 HDMI cable to communicate. The protocol for CEC version 1.4 is defined
17 and is based on the ancient AV.link protocol used in old SCART
18 connectors. The protocol closely resembles a crazy Rube Goldberg
20 messages, especially those part of the HEAC protocol layered on top of
|
| /Documentation/networking/ |
| D | sctp.rst | 10 SCTP (Stream Control Transmission Protocol) is a IP based, message oriented,
11 reliable transport protocol, with congestion control, support for
13 RFC2960 defines the core protocol. The IETF SIGTRAN working group originally
14 developed the SCTP protocol and later handed the protocol over to the
|
| D | vxlan.rst | 7 The VXLAN protocol is a tunnelling protocol designed to solve the
12 number of vendors. The protocol runs over UDP using a single
64 encapsulation protocol is NIC specific):
72 perform protocol-aware offloads, like checksum validation offload of
73 inner frames (only needed by NICs without protocol-agnostic offloads)
|
| /Documentation/driver-api/ |
| D | i2c.rst | 5 the "Inter-IC" bus, a simple bus protocol which is widely used where low
26 are functions to perform various I2C protocol operations; at this writing
29 The System Management Bus (SMBus) is a sibling protocol. Most SMBus
31 for SMBus, and it standardizes particular protocol messages and idioms.
33 SMBus controllers don't support all the protocol options that an I2C
34 controller will. There are functions to perform various SMBus protocol
|
| /Documentation/driver-api/mei/ |
| D | iamt.rst | 21 - Selective network isolation of Ethernet and IP protocol flows based
26 starting with Release 6.0) over HTTP/S or WS-Management protocol over
57 using a protocol called Intel AMT Port Forwarding Protocol (Intel APF protocol).
58 The protocol is used to maintain multiple sessions with Intel AMT from a
61 See the protocol specification in the Intel AMT Software Development Kit (SDK)
65 => "Description of the Intel AMT Port Forwarding (APF) Protocol"
|
| /Documentation/admin-guide/blockdev/ |
| D | paride.rst | 22 and the communication protocol provides operations for reading and writing
60 The second component is a set of low-level protocol drivers for each of the
97 You can actually select all the protocol modules, and allow the pata_parport
100 For the "brand-name" products listed above, here are the protocol
104 Manufacturer Model Protocol
120 All parports and all protocol drivers are probed automatically unless probe=0
126 # echo "port protocol mode unit delay" >/sys/bus/pata_parport/new_device
132 protocol protocol name (or "auto" for all protocols)
133 mode mode number (protocol-specific) or -1 for probe
149 Probe parport0 using protocol epat and mode 4 (EPP-16)::
[all …]
|
| /Documentation/devicetree/bindings/reset/ |
| D | ti,sci-reset.yaml | 17 through a protocol called TI System Control Interface (TI-SCI protocol).
19 This reset controller node uses the TI SCI protocol to perform the reset
41 protocol documentation for the values to be used for different devices.
|
| /Documentation/devicetree/bindings/clock/ |
| D | ti,sci-clk.yaml | 17 through a protocol called TI System Control Interface (TI-SCI protocol).
19 This clock controller node uses the TI SCI protocol to perform various clock
40 protocol documentation for the values to be used for different devices.
|
| /Documentation/i2c/ |
| D | smbus-protocol.rst | 2 The SMBus Protocol
5 The following is a summary of the SMBus protocol. It applies to
6 all revisions of the protocol (1.0, 1.1, and 2.0).
7 Certain protocol features which are not supported by
10 Some adapters understand only the SMBus (System Management Bus) protocol,
11 which is a subset from the I2C protocol. Fortunately, many devices use
16 I2C protocol). This makes it possible to use the device driver on both
21 Below is a list of SMBus protocol operations, and the functions executing
22 them. Note that the names used in the SMBus protocol specifications usually
24 single data byte, the functions using SMBus protocol operation names execute
[all …]
|
| /Documentation/filesystems/smb/ |
| D | cifsroot.rst | 12 support over the SMB protocol via cifs.ko.
16 network by utilizing SMB or CIFS protocol.
24 deprecated version of the protocol but it has been extended to support
26 recommended version of the protocol (SMB3) have not been fully
42 server min protocol = NT1
53 the root file system via SMB protocol.
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | sci-pm-domain.yaml | 20 through a protocol called TI System Control Interface (TI-SCI protocol).
23 controller. Since this relies on the TI SCI protocol to communicate with
44 protocol documentation for the values to be used for different devices.
|
| /Documentation/crypto/ |
| D | api-kpp.rst | 1 Key-agreement Protocol Primitives (KPP) Cipher Algorithm Definitions
7 Key-agreement Protocol Primitives (KPP) Cipher API
11 :doc: Generic Key-agreement Protocol Primitives API
16 Key-agreement Protocol Primitives (KPP) Cipher Request Handle
|
12345678910>>...20