Home
last modified time | relevance | path

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

12345678910>>...69

/linux/Documentation/devicetree/bindings/display/
H A 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 …]
/linux/drivers/net/ethernet/microchip/sparx5/
H A Dsparx5_qos.c95 static u32 sparx5_lg_get_leak_time(struct sparx5 *sparx5, u32 layer, u32 group) in sparx5_lg_get_leak_time() argument
99 value = spx5_rd(sparx5, HSCH_HSCH_TIMER_CFG(layer, group)); in sparx5_lg_get_leak_time()
103 static void sparx5_lg_set_leak_time(struct sparx5 *sparx5, u32 layer, u32 group, in sparx5_lg_set_leak_time() argument
107 HSCH_HSCH_TIMER_CFG(layer, group)); in sparx5_lg_set_leak_time()
110 static u32 sparx5_lg_get_first(struct sparx5 *sparx5, u32 layer, u32 group) in sparx5_lg_get_first() argument
114 value = spx5_rd(sparx5, HSCH_HSCH_LEAK_CFG(layer, group)); in sparx5_lg_get_first()
118 static u32 sparx5_lg_get_next(struct sparx5 *sparx5, u32 layer, u32 group, in sparx5_lg_get_next() argument
128 static u32 sparx5_lg_get_last(struct sparx5 *sparx5, u32 layer, u32 group) in sparx5_lg_get_last() argument
132 itr = sparx5_lg_get_first(sparx5, layer, group); in sparx5_lg_get_last()
135 next = sparx5_lg_get_next(sparx5, layer, group, itr); in sparx5_lg_get_last()
[all …]
/linux/drivers/media/dvb-frontends/
H A Dmb86a20s.c377 unsigned layer) in mb86a20s_get_modulation() argument
381 [0] = 0x86, /* Layer A */ in mb86a20s_get_modulation()
382 [1] = 0x8a, /* Layer B */ in mb86a20s_get_modulation()
383 [2] = 0x8e, /* Layer C */ in mb86a20s_get_modulation()
386 if (layer >= ARRAY_SIZE(reg)) in mb86a20s_get_modulation()
388 rc = mb86a20s_writereg(state, 0x6d, reg[layer]); in mb86a20s_get_modulation()
409 unsigned layer) in mb86a20s_get_fec() argument
414 [0] = 0x87, /* Layer A */ in mb86a20s_get_fec()
415 [1] = 0x8b, /* Layer B */ in mb86a20s_get_fec()
416 [2] = 0x8f, /* Layer C */ in mb86a20s_get_fec()
[all …]
/linux/drivers/net/ethernet/amazon/ena/
H A Dena_com.h425 * @ena_dev: ENA communication layer struct
436 * @ena_dev: ENA communication layer struct
443 * @ena_dev: ENA communication layer struct
450 * @ena_dev: ENA communication layer struct
458 * @ena_dev: ENA communication layer struct
463 * @ena_dev: ENA communication layer struct
470 * @ena_dev: ENA communication layer struct
478 * @ena_dev: ENA communication layer struct
483 * @ena_dev: ENA communication layer struct
488 * @ena_dev: ENA communication layer struct
[all …]
/linux/Documentation/driver-api/surface_aggregator/
H A 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 …]
/linux/Documentation/hid/
H A 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 …]
/linux/drivers/gpu/drm/xlnx/
H A Dzynqmp_disp.h36 * enum zynqmp_dpsub_layer_id - Layer identifier
37 * @ZYNQMP_DPSUB_LAYER_VID: Video layer
38 * @ZYNQMP_DPSUB_LAYER_GFX: Graphics layer
53 u32 *zynqmp_disp_layer_drm_formats(struct zynqmp_disp_layer *layer,
55 u32 *zynqmp_disp_live_layer_formats(struct zynqmp_disp_layer *layer,
57 void zynqmp_disp_layer_enable(struct zynqmp_disp_layer *layer);
58 void zynqmp_disp_layer_disable(struct zynqmp_disp_layer *layer);
59 void zynqmp_disp_layer_set_format(struct zynqmp_disp_layer *layer,
61 void zynqmp_disp_layer_set_live_format(struct zynqmp_disp_layer *layer,
63 int zynqmp_disp_layer_update(struct zynqmp_disp_layer *layer,
/linux/Documentation/networking/
H A 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 …]
H A 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
H A 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
/linux/Documentation/userspace-api/media/dvb/
H A 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 …]
/linux/Documentation/scsi/
H A 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 …]
H A 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 …]
/linux/drivers/platform/surface/aggregator/
H A Dssh_request_layer.h3 * SSH request transport layer.
26 * Indicates that the request transport layer has been shut down or is
34 * struct ssh_rtl_ops - Callback operations for request transport layer.
36 * specified function takes the request layer, received command
46 * struct ssh_rtl - SSH request transport layer.
47 * @ptl: Underlying packet transport layer.
48 * @state: State(-flags) of the transport layer.
63 * @ops: Request layer operations.
104 * ssh_rtl_get_device() - Get device associated with request transport layer.
105 * @rtl: The request transport layer.
[all …]
H A Dssh_packet_layer.h3 * SSH packet transport layer.
28 * Indicates that the packet transport layer has been shut down or is
36 * struct ssh_ptl_ops - Callback operations for packet transport layer.
38 * the packet layer on which the packet has been received and
46 * struct ssh_ptl - SSH packet transport layer.
48 * @state: State(-flags) of the transport layer.
75 * @ops: Packet layer operations.
145 * ssh_ptl_get_device() - Get device associated with packet transport layer.
146 * @ptl: The packet transport layer.
148 * Return: Returns the device on which the given packet transport layer builds
[all …]
/linux/Documentation/ABI/testing/
H A 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
/linux/include/uapi/linux/
H A Datmsap.h19 * Layer 2 protocol identifiers
26 #define ATM_L2_X25_LL 0x06 /* ITU-T X.25, link layer */
41 * Layer 3 protocol identifiers
46 #define ATM_L3_X25 0x06 /* ITU-T X.25, packet layer */
50 #define ATM_L3_T70 0x0a /* ITU-T T.70 minimum network layer */
59 * High layer identifiers
66 #define ATM_HL_HLP 0x03 /* high layer profile - UNI 3.0 only */
101 #define ATM_MAX_HLI 8 /* maximum high-layer information length */
105 unsigned char l2_proto; /* layer 2 protocol */
114 unsigned char l3_proto; /* layer 3 protocol */
[all …]
/linux/drivers/base/regmap/
H A Dregmap-spi-avmm.c22 * The transfer protocol contains 3 layers: transaction layer, packet layer
23 * and physical layer.
32 * the transaction layer.
35 * describes the packet layer.
38 * physical layer.
42 * to byte stream layer by layer. It formats the register addr, value and
43 * length to the transaction layer request, then converts the request to packet
44 * layer bytes stream and then to physical layer bytes stream. Finally the
101 * In transaction layer,
115 /* tx & rx share one transaction layer buffer */
[all …]
/linux/drivers/net/ipa/
H A Dipa_gsi.h19 * This called from the GSI layer to notify the IPA layer that a
28 * This called from the GSI layer to notify the IPA layer that a
41 * This called from the GSI layer to notify the IPA layer that some
54 * This called from the GSI layer to notify the IPA layer that the hardware
/linux/Documentation/filesystems/
H A Doverlayfs.rst200 When renaming a directory that is on the lower layer or merged (i.e. the
201 directory was not created on the upper layer to start with) overlayfs can
257 Because lower layer redirects cannot be verified with the index, enabling
258 NFS export support on an overlay filesystem with no upper layer requires
323 upper layer based on underlying filesystem permissions, again including
360 themselves be idmapped. The overlay mount idmapping and any layer idmapping
361 compose, an underlying id is first mapped according to the relevant layer
378 top, lower2 the middle and lower3 the bottom layer.
380 Note: directory names containing colons can be provided as lower layer by
386 be configured as lower layer using the "lowerdir+" mount options and the
[all …]
/linux/tools/lib/perf/include/internal/
H A Drc_check.h25 * are paired with a put. Reference count checking adds a malloc-ed layer of
45 /* Strip the indirection layer. */
48 /* Frees the object and the indirection layer. */
51 /* A get operation adding the indirection layer. */
54 /* A put operation removing the indirection layer. */
85 /* Strip the indirection layer. */
88 /* Frees the object and the indirection layer. */
95 /* A get operation adding the indirection layer. */
98 /* A put operation removing the indirection layer. */
/linux/Documentation/ABI/stable/
H A 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
/linux/drivers/gpu/drm/logicvc/
H A Dlogicvc_of.c33 { "layer", LOGICVC_LAYER_ALPHA_LAYER },
67 .name = "xylon,background-layer",
78 .name = "xylon,layer-depth",
82 .name = "xylon,layer-colorspace",
90 .name = "xylon,layer-alpha-mode",
98 .name = "xylon,layer-base-offset",
101 .name = "xylon,layer-buffer-offset",
104 .name = "xylon,layer-primary",
184 return !of_node_cmp(of_node->name, "layer"); in logicvc_of_node_is_layer()
/linux/Documentation/driver-api/usb/
H A 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 …]
/linux/Documentation/block/
H A 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 …]

12345678910>>...69