Home
last modified time | relevance | path

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

12345678910>>...18

/Documentation/devicetree/bindings/display/
Dxylon,logicvc-display.yaml25 In version 3 of the controller, each layer has fixed memory offset and address
103 xylon,background-layer:
106 The last layer is used to display a black background (C_USE_BACKGROUND).
107 The layer must still be registered.
126 "^layer@[0-9]+$":
133 xylon,layer-depth:
135 description: Layer depth (C_LAYER_X_DATA_WIDTH).
137 xylon,layer-colorspace:
143 description: Layer colorspace (C_LAYER_X_TYPE).
145 xylon,layer-alpha-mode:
[all …]
/Documentation/networking/caif/
Dlinux_caif.rst31 * CAIF Socket Layer and GPRS IP Interface.
33 * CAIF Link Layer, implemented as NET devices.
54 +--> ! HSI ! ! TTY ! ! USB ! <- Link Layer (Net Devices)
63 CAIF Core Protocol Layer
66 CAIF Core layer implements the CAIF protocol as defined by ST-Ericsson.
68 each layer described in the specification is implemented as a separate layer.
69 The architecture is inspired by the design patterns "Protocol Layer" and
78 - Layered architecture (a la Streams), each layer in the CAIF
80 - Clients must call configuration function to add PHY layer.
81 - 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/userspace-api/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/hid/
Damd-sfh-hid.rst45 AMD HID Transport Layer
49 sensor data. The layer, which binds each device (AMD SFH HID driver) identifies the device type and
50 registers with the HID core. Transport layer attaches a constant "struct hid_ll_driver" object with
52 used by HID core to communicate with the device. AMD HID Transport layer implements the synchronous…
54 AMD HID Client Layer
56 This layer is responsible to implement HID requests and descriptors. As firmware is OS agnostic, HID
57 client layer fills the HID request structure and descriptors. HID client layer is complex as it is
58 interface between MP2 PCIe layer and HID. HID client layer initializes the MP2 PCIe layer and holds
59 the instance of MP2 layer. It identifies the number of sensors connected using MP2-PCIe layer. Based
61 enumeration of each sensor, client layer fills the HID Descriptor structure and HID input report
[all …]
/Documentation/driver-api/surface_aggregator/
Dinternal.rst63 Lower-level packet transport is implemented in the *packet transport layer
65 infrastructure of the kernel. As the name indicates, this layer deals with
70 Above this sits the *request transport layer (RTL)*. This layer is centered
76 The *controller* layer is building on top of this and essentially decides
81 ``RQID``). This layer basically provides a fundamental interface to the SAM
84 While the controller layer already provides an interface for other kernel
97 Packet Transport Layer
100 The packet transport layer is represented via |ssh_ptl| and is structured
107 managed by the packet transport layer, which is essentially the lowest layer
114 transport layer, as well as a reference to the buffer containing the data to
[all …]
/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/scsi/
Dufs.rst12 2.1 Application Layer
13 2.2 UFS Transport Protocol (UTP) layer
14 2.3 UFS Interconnect (UIC) Layer
32 on the MIPI M-PHY physical layer standard. UFS uses MIPI M-PHY as the
33 physical layer and MIPI Unipro as the link layer.
60 2.1 Application Layer
63 The Application layer is composed of the UFS command set layer (UCS),
66 protocol for versions 1.0 and 1.1 of the UFS protocol layer.
83 2.2 UFS Transport Protocol (UTP) layer
86 The UTP layer provides services for
[all …]
Dlibsas.rst4 SAS Layer
7 The SAS Layer is a management infrastructure which manages
11 phy/OOB/link management, the SAS layer is concerned with:
14 SAS Layer processes),
26 events to the SAS layer.
28 The SAS Layer does most SAS tasks as outlined in the SAS 1.1
31 The sas_ha_struct describes the SAS LLDD to the SAS layer.
32 Most of it is used by the SAS Layer but a few fields need to
66 are managed by the SAS layer. So the phys are initialized
68 updated by the SAS layer.
[all …]
/Documentation/networking/
Dx25.rst9 Packet Layer and a LAPB module to allow for "normal" X.25 to be run using
16 Packet Layer is concerned, the link layer was being performed by a lower
17 layer of the Linux kernel and therefore it did not concern itself with
25 the Packet Layer but there would be no confusion since the class of device
29 option appeared, XOT. This allows X.25 Packet Layer frames to operate over
30 the Internet using TCP/IP as a reliable link layer. RFC1613 specifies the
Dppp_generic.rst37 be linked to each ppp network interface unit. The generic layer is
46 functions used to communicate between the generic PPP layer and PPP
49 Each channel has to provide two functions to the generic PPP layer,
52 * start_xmit() is called by the generic layer when it has a frame to
56 later time when it can accept frames again, and the generic layer
66 The generic PPP layer provides seven functions to channels:
69 notify the PPP generic layer of its presence. For example, setting
89 generic layer to this channel. The channel should provide some way
97 Connecting a channel to the ppp generic layer is initiated from the
98 channel code, rather than from the generic layer. The channel is
[all …]
Dx25-iface.rst11 Layer and the X.25 device driver. They are designed to allow for the easy
12 setting of the LAPB mode from within the Packet Layer.
18 needs to be passed to and from the Packet Layer for proper operation.
25 Packet Layer to Device Driver
49 Device Driver to Packet Layer
76 Packet Layer and the device driver.
79 the device driver to the Packet Layer, the device driver should not
Dphonet.rst32 uint8_t pn_media; /* Media type (link-layer identifier) */
41 On Linux, the link-layer header includes the pn_media byte (see below).
42 The next 7 bytes are part of the network-layer header.
47 network layer with 6 bits of address space and 10 bits for transport
54 Link layer
57 Phonet links are always point-to-point links. The link layer header
62 link-layer header operations structure is provided. It sets the
65 Linux Phonet network interfaces support a dedicated link layer packets
71 there is no link-layer header, so there is no Phonet media type byte.
77 Network layer
/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/userspace-api/media/dvb/
Dfrontend-property-terrestrial-systems.rst119 segments, that it can have up to 3 layer sharing those segments, and
142 - :ref:`DTV_ISDBT_LAYER_ENABLED <DTV-ISDBT-LAYER-ENABLED>`
154 - :ref:`DTV_ISDBT_LAYERA_FEC <DTV-ISDBT-LAYER-FEC>`
156 - :ref:`DTV_ISDBT_LAYERA_MODULATION <DTV-ISDBT-LAYER-MODULATION>`
158 - :ref:`DTV_ISDBT_LAYERA_SEGMENT_COUNT <DTV-ISDBT-LAYER-SEGMENT-COUNT>`
160 - :ref:`DTV_ISDBT_LAYERA_TIME_INTERLEAVING <DTV-ISDBT-LAYER-TIME-INTERLEAVING>`
162 - :ref:`DTV_ISDBT_LAYERB_FEC <DTV-ISDBT-LAYER-FEC>`
164 - :ref:`DTV_ISDBT_LAYERB_MODULATION <DTV-ISDBT-LAYER-MODULATION>`
166 - :ref:`DTV_ISDBT_LAYERB_SEGMENT_COUNT <DTV-ISDBT-LAYER-SEGMENT-COUNT>`
168 - :ref:`DTV_ISDBT_LAYERB_TIME_INTERLEAVING <DTV-ISDBT-LAYER-TIME-INTERLEAVING>`
[all …]
/Documentation/block/
Dblk-mq.rst22 any layer on the storage stack. One example of such optimization technique
50 queues. When the request arrives at the block layer, it will try the shortest
53 layer or if we want to try to merge requests. In both cases, requests will be
68 block layer through the data structure struct bio. The block layer
87 There are several schedulers implemented by the block layer, each one following
107 buffer), and are the last step of the block layer submission code before the
109 block layer removes requests from the associated software queues and tries to
114 next time the block layer runs a queue, it will send the requests laying at the
124 Neither the block layer nor the device protocols guarantee
133 is generated by the block layer and later reused by the device driver, removing
[all …]
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/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/filesystems/
Doverlayfs.rst192 When renaming a directory that is on the lower layer or merged (i.e. the
193 directory was not created on the upper layer to start with) overlayfs can
249 Because lower layer redirects cannot be verified with the index, enabling
250 NFS export support on an overlay filesystem with no upper layer requires
301 upper layer based on underlying filesystem permissions, again including
364 top, lower2 the middle and lower3 the bottom layer.
366 Note: directory names containing colons can be provided as lower layer by
372 be configured as lower layer using the "lowerdir+" mount options and the
377 In the latter case, colons in lower layer directory names will be escaped
417 1) metadata from a file in the upper layer
[all …]
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
171 buffer to tell the journalling layer about them.
176 The journalling layer uses typedefs to 'hide' the concrete definitions
177 of the structures used. As a client of the JBD2 layer you can just rely
/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/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 …]

12345678910>>...18