Home
last modified time | relevance | path

Searched full:layer (Results 1 – 25 of 357) sorted by relevance

12345678910>>...15

/Documentation/networking/caif/
DLinux-CAIF.txt22 * CAIF Socket Layer and GPRS IP Interface.
24 * CAIF Link Layer, implemented as NET devices.
44 +--> ! HSI ! ! TTY ! ! USB ! <- Link Layer (Net Devices)
53 CAIF Core Protocol Layer
56 CAIF Core layer implements the CAIF protocol as defined by ST-Ericsson.
58 each layer described in the specification is implemented as a separate layer.
59 The architecture is inspired by the design patterns "Protocol Layer" and
65 - Layered architecture (a la Streams), each layer in the CAIF
67 - Clients must call configuration function to add PHY layer.
68 - Clients must implement CAIF layer to consume/produce
[all …]
/Documentation/gpu/
Dkomeda-kms.rst22 Layer section in Overview of D71 like display IPs
24 Layer is the first pipeline stage, which prepares the pixel data for the next
33 The usage of scaler is very flexible and can be connected to layer output
34 for layer scaling, or connected to compositor and scale the whole display
46 Writeback Layer (wb_layer)
48 Writeback layer does the opposite things of Layer, which connects to compiz
64 compared with Layer, like if Layer supports 4K input size, the scaler only can
66 introduces Layer Split, which splits the whole image to two half parts and feeds
73 Similar to Layer Split, but Splitter is used for writeback, which splits the
120 "Layer-0" -> "Scaler-0"
[all …]
/Documentation/media/
Dfrontend.h.rst.exceptions6 # Group layer A-C symbols together
7 replace define DTV_ISDBT_LAYERA_FEC dtv-isdbt-layer-fec
8 replace define DTV_ISDBT_LAYERB_FEC dtv-isdbt-layer-fec
9 replace define DTV_ISDBT_LAYERC_FEC dtv-isdbt-layer-fec
10 replace define DTV_ISDBT_LAYERA_MODULATION dtv-isdbt-layer-modulation
11 replace define DTV_ISDBT_LAYERB_MODULATION dtv-isdbt-layer-modulation
12 replace define DTV_ISDBT_LAYERC_MODULATION dtv-isdbt-layer-modulation
13 replace define DTV_ISDBT_LAYERA_SEGMENT_COUNT dtv-isdbt-layer-segment-count
14 replace define DTV_ISDBT_LAYERB_SEGMENT_COUNT dtv-isdbt-layer-segment-count
15 replace define DTV_ISDBT_LAYERC_SEGMENT_COUNT dtv-isdbt-layer-segment-count
[all …]
/Documentation/ABI/testing/
Dsysfs-bus-usb-lvstest1 Link Layer Validation Device is a standard device for testing of Super
2 Speed Link Layer tests. These nodes are available in sysfs only when lvs
10 for Link Layer Validation device. It is needed for TD.7.06.
16 Set "U1 timeout" for the downstream port where Link Layer
24 Set "U2 timeout" for the downstream port where Link Layer
32 Write to this node to issue "Reset" for Link Layer Validation
39 Write to this node to issue "U3 entry" for Link Layer
46 Write to this node to issue "U3 exit" for Link Layer
53 with Link Layer Validation device. It is needed for TD.7.34.
58 Write to this node to issue "Warm Reset" for Link Layer Validation
/Documentation/scsi/
Dufs.txt10 2.1 Application Layer
11 2.2 UFS Transport Protocol(UTP) layer
12 2.3 UFS Interconnect(UIC) Layer
28 on MIPI M-PHY physical layer standard. UFS uses MIPI M-PHY as the
29 physical layer and MIPI Unipro as the link layer.
50 2.1 Application Layer
52 The Application layer is composed of UFS command set layer(UCS),
55 protocol for versions 1.0 and 1.1 of UFS protocol layer.
67 2.2 UFS Transport Protocol(UTP) layer
69 UTP layer provides services for
[all …]
Dlibsas.txt1 SAS Layer
4 The SAS Layer is a management infrastructure which manages
8 phy/OOB/link management, the SAS layer is concerned with:
11 SAS Layer processes),
23 events to the SAS layer.
25 The SAS Layer does most SAS tasks as outlined in the SAS 1.1
28 The sas_ha_struct describes the SAS LLDD to the SAS layer.
29 Most of it is used by the SAS Layer but a few fields need to
58 are managed by the SAS layer. So the phys are initialized
60 updated by the SAS layer.
[all …]
/Documentation/networking/
Dx25.txt5 Packet Layer and a LAPB module to allow for "normal" X.25 to be run using
12 Packet Layer is concerned, the link layer was being performed by a lower
13 layer of the Linux kernel and therefore it did not concern itself with
21 the Packet Layer but there will be no confusion since the class of device
27 option appeared, XOT. This allows X.25 Packet Layer frames to operate over
28 the Internet using TCP/IP as a reliable link layer. RFC1613 specifies the
Dppp_generic.txt33 be linked to each ppp network interface unit. The generic layer is
42 functions used to communicate between the generic PPP layer and PPP
45 Each channel has to provide two functions to the generic PPP layer,
48 * start_xmit() is called by the generic layer when it has a frame to
52 later time when it can accept frames again, and the generic layer
62 The generic PPP layer provides seven functions to channels:
65 notify the PPP generic layer of its presence. For example, setting
85 generic layer to this channel. The channel should provide some way
93 Connecting a channel to the ppp generic layer is initiated from the
94 channel code, rather than from the generic layer. The channel is
[all …]
Dx25-iface.txt6 Layer and the X.25 device driver. They are designed to allow for the easy
7 setting of the LAPB mode from within the Packet Layer.
13 needs to be passed to and from the Packet Layer for proper operation.
20 Packet Layer to Device Driver
44 Device Driver to Packet Layer
73 The X.25 packet layer protocol depends on a reliable datalink service.
79 netif_rx(skb2), skb2 might be delivered to the network layer
84 The X.25 packet layer protocol will detect this and reset the virtual
85 call in question. But many upper layer protocols are not designed to
Dphonet.txt27 uint8_t pn_media; /* Media type (link-layer identifier) */
36 On Linux, the link-layer header includes the pn_media byte (see below).
37 The next 7 bytes are part of the network-layer header.
42 network layer with 6 bits of address space and 10 bits for transport
49 Link layer
52 Phonet links are always point-to-point links. The link layer header
57 link-layer header operations structure is provided. It sets the
60 Linux Phonet network interfaces support a dedicated link layer packets
66 there is no link-layer header, so there is no Phonet media type byte.
72 Network layer
Dstrparser.txt7 application layer protocol running over a data stream. The stream
8 parser works in conjunction with an upper layer in the kernel to provide
9 kernel support for application layer messages. For instance, Kernel
41 strparser that is allocated by the upper layer. sk is the TCP
49 and no new messages are delivered to the upper layer.
59 error, and it is called from the upper layer to stop parsing
80 The upper layer calls strp_tcp_data_ready when data is ready on
100 in the stream. The upper layer must implement this function. It
102 next application layer message in the stream.
/Documentation/driver-api/driver-model/
Doverview.rst45 Other bus layers are encouraged to do what has been done for the PCI layer.
63 The PCI bus layer freely accesses the fields of struct device. It knows about
71 downstream driver would break. On the other hand, if only the bus layer
72 (and not the device layer) accesses the struct device, it is only the bus
73 layer that needs to change.
107 This directory may be populated at each layer of discovery - the global layer,
108 the bus layer, or the device layer.
110 The global layer currently creates two files - 'name' and 'power'. The
115 The bus layer may also create files for the devices it finds while probing the
116 bus. For example, the PCI layer currently creates 'irq' and 'resource' files
/Documentation/ABI/stable/
Dsysfs-transport-srp12 Description: Number of seconds the SCSI layer will wait after a transport
13 layer error has been observed before removing a target port.
21 Description: Number of seconds the SCSI layer will wait after a transport
22 layer error has been observed before failing I/O. Zero means
37 Description: Number of seconds the SCSI layer will wait after a reconnect
51 Description: State of the transport layer used for communication with the
52 remote port. "running" if the transport layer is operational;
53 "blocked" if a transport layer error has been encountered but
/Documentation/devicetree/bindings/firmware/
Dintel,stratix10-svc.txt1 Intel Service Layer Driver for Stratix10 SoC
11 Layer 3) can interface with SDM. All software entities running on other
15 Intel Stratix10 service layer driver, running at privileged exception level
16 (EL1, Exception Layer 1), interfaces with the service providers and provides
17 the services for FPGA configuration, QSPI, Crypto and warm reset. Service layer
/Documentation/media/uapi/dvb/
Dfrontend-property-terrestrial-systems.rst126 segments, that it can have up to 3 layer sharing those segments, and
149 - :ref:`DTV_ISDBT_LAYER_ENABLED <DTV-ISDBT-LAYER-ENABLED>`
161 - :ref:`DTV_ISDBT_LAYERA_FEC <DTV-ISDBT-LAYER-FEC>`
163 - :ref:`DTV_ISDBT_LAYERA_MODULATION <DTV-ISDBT-LAYER-MODULATION>`
165 - :ref:`DTV_ISDBT_LAYERA_SEGMENT_COUNT <DTV-ISDBT-LAYER-SEGMENT-COUNT>`
167 - :ref:`DTV_ISDBT_LAYERA_TIME_INTERLEAVING <DTV-ISDBT-LAYER-TIME-INTERLEAVING>`
169 - :ref:`DTV_ISDBT_LAYERB_FEC <DTV-ISDBT-LAYER-FEC>`
171 - :ref:`DTV_ISDBT_LAYERB_MODULATION <DTV-ISDBT-LAYER-MODULATION>`
173 - :ref:`DTV_ISDBT_LAYERB_SEGMENT_COUNT <DTV-ISDBT-LAYER-SEGMENT-COUNT>`
175 - :ref:`DTV_ISDBT_LAYERB_TIME_INTERLEAVING <DTV-ISDBT-LAYER-TIME-INTERLEAVING>`
[all …]
/Documentation/admin-guide/
Dpnp.rst13 otherwise unconfigurable devices. The Linux Plug and Play Layer provides these
112 The Unified Plug and Play Layer
116 called the Plug and Play Layer. This layer is responsible for the exchange of
121 The following functions are available from the Plug and Play Layer:
133 use this function to remove a PnP protocol from the Plug and Play Layer
136 adds a PnP driver to the Plug and Play Layer
144 removes a PnP driver from the Plug and Play Layer
169 2. the protocol must inform the PnP Layer of a device's current configuration
176 use this function to add a PnP device to the PnP layer
185 call this to remove a device from the Plug and Play Layer.
/Documentation/block/
Dwriteback_cache_control.rst15 The Linux block layer provides two simple mechanisms that let filesystems
61 flags themselves without any help from the block layer.
68 support required, the block layer completes empty REQ_PREFLUSH requests before
71 driver needs to tell the block layer that it supports flushing caches by
79 layer. For devices that also support the FUA bit the block layer needs
86 layer turns it into an empty REQ_OP_FLUSH request after the actual write.
/Documentation/driver-api/usb/
Dwriting_musb_glue_layer.rst2 Writing a MUSB Glue Layer
21 As a self-taught exercise I have written an MUSB glue layer for the
23 kernel source tree. This layer can be found at
25 basics of the ``jz4740.c`` glue layer, explaining the different pieces and
26 what needs to be done in order to write your own device glue layer.
61 | aka "Glue Layer" |
68 As outlined above, the glue layer is actually the platform specific code
72 subsystem, the MUSB glue layer needs first to register itself with the
74 about which device the glue layer supports and which functions to call
80 a :c:type:`platform_driver` structure defined in the glue layer as::
[all …]
/Documentation/netlabel/
Dintroduction.rst16 layer, and the kernel security module API.
31 Communication Layer
34 The communication layer exists to allow NetLabel configuration and monitoring
35 from user space. The NetLabel communication layer uses a message based
/Documentation/devicetree/bindings/regulator/
Duniphier-regulator.txt9 This regulator controls VBUS and belongs to USB3 glue layer. Before using
11 this layer. These clocks and resets should be described in each property.
21 - clocks: A list of phandles to the clock gate for USB3 glue layer.
26 - resets: A list of phandles to the reset control for USB3 glue layer.
/Documentation/filesystems/
Doverlayfs.txt180 When renaming a directory that is on the lower layer or merged (i.e. the
181 directory was not created on the upper layer to start with) overlayfs can
238 Because lower layer redirects cannot be verified with the index, enabling
239 NFS export support on an overlay filesystem with no upper layer requires
285 top, lower2 the middle and lower3 the bottom layer.
322 a very common practice. An overlay mount may use the same lower layer
323 path as another overlay mount and it may use a lower layer path that is
324 beneath or above the path of another overlay lower layer path.
326 Using an upper layer path and/or a workdir path that are already used by
330 upper layer and/or workdir path the behavior of the overlay is undefined,
[all …]
Dindex.rst6 comprehensive information on how the Linux virtual filesystem (VFS) layer
13 See these manuals for documentation about the VFS layer itself and how its
31 Documentation for the support code within the filesystem layer for use in
Djournalling.rst10 The journalling layer is easy to use. You need to first of all create a
21 journal file. The journalling layer expects the space for the journal
40 the modification of each of the buffers with calls to the journal layer,
57 journalling layer to copy the unmodified
72 Unfortunately there a couple of ways the journal layer can cause a
109 With journal commit callbacks you can ask the journalling layer to call
112 layer for calling the callback by simply setting
140 buffer to tell the journalling layer about them.
145 The journalling layer uses typedefs to 'hide' the concrete definitions
146 of the structures used. As a client of the JBD2 layer you can just rely
/Documentation/driver-api/
Dscsi.rst38 The SCSI subsystem uses a three layer design, with upper, mid, and low
41 layer driver, one lower layer driver, and the SCSI midlayer.
43 The SCSI upper layer provides the interface between userspace and the
45 The SCSI lower layer contains drivers for specific hardware devices.
47 In between is the SCSI mid-layer, analogous to a network routing layer
48 such as the IPv4 stack. The SCSI mid-layer routes a packet based data
49 protocol between the upper layer's /dev nodes and the corresponding
50 devices in the lower layer. It manages command queues, provides error
54 SCSI upper layer
57 The upper layer supports the user-kernel interface by providing device
[all …]
/Documentation/devicetree/bindings/crypto/
Dpicochip-spacc.txt4 IPSEC and femtocell layer 2 ciphering.
8 "picochip,spacc-l2" for the femtocell layer 2 ciphering engine.

12345678910>>...15