| /linux/drivers/gpu/drm/logicvc/ |
| H A D | logicvc_layer.c | 1 // SPDX-License-Identifier: GPL-2.0+
3 * Copyright (C) 2019-2022 Bootlin
86 struct drm_device *drm_dev = drm_plane->dev; in logicvc_plane_atomic_check()
87 struct logicvc_layer *layer = logicvc_layer(drm_plane); in logicvc_plane_atomic_check() local
96 if (!new_state->crtc) in logicvc_plane_atomic_check()
99 crtc_state = drm_atomic_get_existing_crtc_state(new_state->state, in logicvc_plane_atomic_check()
100 new_state->crtc); in logicvc_plane_atomic_check()
102 return -EINVAL; in logicvc_plane_atomic_check()
104 if (new_state->crtc_x < 0 || new_state->crtc_y < 0) { in logicvc_plane_atomic_check()
106 "Negative on-CRTC positions are not supported.\n"); in logicvc_plane_atomic_check()
[all …]
|
| H A D | logicvc_of.c | 1 // SPDX-License-Identifier: GPL-2.0+
3 * Copyright (C) 2019-2022 Bootlin
14 { "lvds-4bits", LOGICVC_DISPLAY_INTERFACE_LVDS_4BITS },
15 { "lvds-3bits", LOGICVC_DISPLAY_INTERFACE_LVDS_3BITS },
33 { "layer", LOGICVC_LAYER_ALPHA_LAYER },
40 .name = "xylon,display-interface",
48 .name = "xylon,display-colorspace",
56 .name = "xylon,display-depth",
60 .name = "xylon,row-stride",
67 .name = "xylon,background-layer",
[all …]
|
| /linux/Documentation/devicetree/bindings/display/ |
| H A D | xylon,logicvc-display.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/display/xylon,logicvc-display.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Paul Kocialkowski <paul.kocialkowski@bootlin.com>
16 with Xilinx Zynq-7000 SoCs and Xilinx FPGAs.
20 synthesis time. As a result, many of the device-tree bindings are meant to
24 Layers are declared in the "layers" sub-node and have dedicated configuration.
25 In version 3 of the controller, each layer has fixed memory offset and address
32 - xylon,logicvc-3.02.a-display
[all …]
|
| /linux/block/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
3 # Block layer core configuration
6 bool "Enable the block layer" if EXPERT
11 Provide block layer support for the kernel.
13 Disable this option to remove the block layer support from the
18 - block device files will become unusable
19 - some filesystems (such as ext3) will become unavailable.
22 they make use of various block layer definitions and facilities.
55 bool "Block layer SG support v4 helper lib"
64 bool "Block layer data integrity support"
[all …]
|
| /linux/Documentation/scsi/ |
| H A D | lpfc.rst | 1 .. SPDX-License-Identifier: GPL-2.0
15 The proposed modifications to the transport layer for FC remote ports
20 The driver now requires a 2.6.12 (if pre-release, 2.6.12-rc1) or later
26 The following information is provided for additional background on the
39 errored by the driver, the mid-layer would exhaust its retries, and the
41 re-enable the device.
45 queuing is unnecessary as the block layer already performs the
56 The proposed patch was posted to the linux-scsi mailing list. The patch
57 is contained in the 2.6.10-rc2 (and later) patch kits. As such, this
71 At this time, the driver requires the 2.6.12 (if pre-release, 2.6.12-rc1)
|
| /linux/drivers/gpu/drm/amd/display/dc/inc/hw/ |
| H A D | mpc.h | 2 * Copyright 2012-15 Advanced Micro Devices, Inc.
30 * that performs blending of multiple planes, using global and per-pixel alpha.
31 * It also performs post-blending color correction operations according to the
36 * supporting "M MPC inputs -> N MPC outputs" flexible composition
39 * - Programmable blending structure to allow software controlled blending and
41 * - Programmable window location of each DPP in active region of display;
42 * - Combining multiple DPP pipes in one active region when a single DPP pipe
44 * - Combining multiple DPP from different SLS with blending;
45 * - Stereo formats from single DPP in top-bottom or side-by-side modes;
46 * - Stereo formats from 2 DPPs;
[all …]
|
| /linux/Documentation/driver-api/nfc/ |
| H A D | nfc-hci.rst | 5 - Author: Eric Lapuyade, Samuel Ortiz
6 - Contact: eric.lapuyade@intel.com, samuel.ortiz@intel.com
9 -------
11 The HCI layer implements much of the ETSI TS 102 622 V10.2.0 specification. It
12 enables easy writing of HCI-based NFC drivers. The HCI layer runs as an NFC Core
17 ---
21 they are translated in a sequence of HCI commands sent to the HCI layer in the
30 - one for executing commands : nfc_hci_msg_tx_work(). Only one command
32 - one for dispatching received events and commands : nfc_hci_msg_rx_work().
35 --------------------------
[all …]
|
| /linux/Documentation/admin-guide/ |
| H A D | syscall-user-dispatch.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Background chapter
8 ----------
11 calls of only a part of their process - the part that has the
12 incompatible code - while being able to execute native syscalls without
21 multiple-personality application can then flip the switch without
22 invoking the kernel, when crossing the compatibility layer API
27 The goal of this design is to provide very quick compatibility layer
29 personality every time the compatibility layer executes. Instead, a
40 non-native applications, it must function on syscalls whose invocation
[all …]
|
| /linux/drivers/gpu/drm/stm/ |
| H A D | ltdc.c | 1 // SPDX-License-Identifier: GPL-2.0
15 #include <linux/media-bus-format.h>
46 #define CRTC_MASK GENMASK(NB_CRTC - 1, 0)
61 #define LAY_OFS (ldev->caps.layer_ofs)
65 #define LTDC_LCR 0x0004 /* Layer Count */
75 #define LTDC_BCCR 0x002C /* Background Color Configuration */
86 /* Layer register offsets */
87 #define LTDC_L1C0R (ldev->caps.layer_regs[0]) /* L1 configuration 0 */
88 #define LTDC_L1C1R (ldev->caps.layer_regs[1]) /* L1 configuration 1 */
89 #define LTDC_L1RCR (ldev->caps.layer_regs[2]) /* L1 reload control */
[all …]
|
| /linux/Documentation/block/ |
| H A D | blk-mq.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Multi-Queue Block IO Queueing Mechanism (blk-mq)
7 The Multi-Queue Block IO Queueing Mechanism is an API to enable fast storage
15 Background section in Introduction
16 ----------
22 any layer on the storage stack. One example of such optimization technique
26 However, with the development of Solid State Drives and Non-Volatile Memories
30 in those devices' design, the multi-queue mechanism was introduced.
36 to different CPUs) wanted to perform block IO. Instead of this, the blk-mq API
42 ---------
[all …]
|
| H A D | inline-encryption.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 Background chapter
19 keys directly in low-level I/O requests. However, most inline encryption
22 low-level I/O request then just contains a keyslot index and data unit number.
28 managed by the block layer, not the kernel crypto API.
30 Inline encryption hardware is also very different from "self-encrypting drives",
31 such as those based on the TCG Opal or ATA Security standards. Self-encrypting
32 drives don't provide fine-grained control of encryption and provide no way to
34 provides fine-grained control of encryption, including the choice of key and
43 layered devices like device-mapper and loopback (i.e. we want to be able to use
[all …]
|
| /linux/drivers/md/ |
| H A D | dm-cache-policy.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
11 #include "dm-cache-block-types.h"
13 #include <linux/device-mapper.h>
15 /*----------------------------------------------------------------*/
51 * Returns 0 if in cache (cblock will be set), -ENOENT if not, < 0 for
52 * other errors (-EWOULDBLOCK would be typical). data_dir should be
66 * This method is optional (policy-internal will fallback to using
75 * Retrieves background work. Returns -ENODATA when there's no
76 * background work.
102 * Returns -ENODATA if cblock is not mapped.
[all …]
|
| /linux/include/linux/mtd/ |
| H A D | blktrans.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * Copyright © 2003-2010 David Woodhouse <dwmw2@infradead.org>
54 void (*background)(struct mtd_blktrans_dev *dev); member
56 /* Block layer ioctls */
81 * module_mtd_blktrans() - Helper macro for registering a mtd blktrans driver
|
| /linux/Documentation/driver-api/media/drivers/ |
| H A D | pvrusb2.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 Background chapter
9 ----------
13 Its history started with the reverse-engineering effort by Björn
29 1. Low level wire-protocol implementation with the device.
37 4. A "context" layer which manages instancing of driver, setup,
38 tear-down, arbitration, and interaction with high level
45 The most important shearing layer is between the top 2 layers. A
61 --------
70 --------------------------------------
[all …]
|
| /linux/drivers/gpu/drm/xlnx/ |
| H A D | zynqmp_disp.c | 1 // SPDX-License-Identifier: GPL-2.0
5 * Copyright (C) 2017 - 2020 Xilinx, Inc.
8 * - Hyun Woo Kwon <hyun.kwon@xilinx.com>
9 * - Laurent Pinchart <laurent.pinchart@ideasonboard.com>
19 #include <linux/dma-mapping.h>
21 #include <linux/media-bus-format.h>
34 * --------
39 * +------------------------------------------------------------+
40 * +--------+ | +----------------+ +-----------+ |
41 * | DPDMA | --->| | --> | Video | Video +-------------+ |
[all …]
|
| /linux/drivers/gpu/drm/arm/ |
| H A D | malidp_hw.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
4 * (C) COPYRIGHT 2013-2016 ARM Limited. All rights reserved.
25 /* Mali DP layer IDs */
43 u8 layer; /* bitmask of layers supporting it */ member
62 u16 id; /* layer ID */
66 s16 yuv2rgb_offset; /* offset to the YUV->RGB matrix entries */
123 /* list of supported pixel formats for each layer */
132 /* Unlike DP550/650, DP500 has 3 stride registers in its video layer. */
195 * @param hwdev - malidp_hw_device structure containing the HW description
196 * @param addrs - array of addresses for each plane
[all …]
|
| /linux/Documentation/filesystems/nfs/ |
| H A D | rpc-server-gss.rst | 13 - RFC2203 v1: https://tools.ietf.org/rfc/rfc2203.txt
14 - RFC5403 v2: https://tools.ietf.org/rfc/rfc5403.txt
18 - RFC7861 v3: https://tools.ietf.org/rfc/rfc7861.txt
20 Background chapter
35 - initial context establishment
36 - integrity/privacy protection (signing and encrypting of individual
39 The former is more complex and policy-independent, but less
40 performance-sensitive. The latter is simpler and needs to be very fast.
42 Therefore, we perform per-packet integrity and privacy protection in the
51 nfs-utils package.
[all …]
|
| /linux/drivers/gpu/drm/sti/ |
| H A D | sti_mixer.c | 1 // SPDX-License-Identifier: GPL-2.0
18 /* Module parameter to set the background color of the mixer */
20 MODULE_PARM_DESC(bkgcolor, "Value of the background color 0xRRGGBB");
56 switch (mixer->id) { in sti_mixer_to_str()
68 return readl(mixer->regs + reg_id); in sti_mixer_reg_read()
74 writel(val, mixer->regs + reg_id); in sti_mixer_reg_write()
77 #define DBGFS_DUMP(reg) seq_printf(s, "\n %-25s 0x%08X", #reg, \
131 seq_puts(s, "---"); in mixer_dbg_crb()
134 if (i < GAM_MIXER_NB_DEPTH_LEVEL - 1) in mixer_dbg_crb()
145 seq_printf(s, "-0x%08X", (int)readl(addr + i * 4)); in mixer_dbg_mxn()
[all …]
|
| /linux/Documentation/target/ |
| H A D | tcmu-design.rst | 9 a) Background
19 2) Writing a user pass-through handler
29 TCM is another name for LIO, an in-kernel iSCSI target (server).
38 built-in modules are implemented entirely as kernel code.
40 Background section in Design
41 ----------
52 use case that other non-kernel target solutions, such as tgt, are able
55 in these non-traditional networked storage systems, while still only
65 kernel, another approach is to create a userspace pass-through
70 --------
[all …]
|
| /linux/drivers/gpu/drm/sun4i/ |
| H A D | sun8i_mixer.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
11 #include <linux/dma-mapping.h>
91 /* for DE2 VI layer which ignores alpha */
100 /* for DE2 VI layer which ignores alpha */
109 /* for DE2 VI layer which ignores alpha */
118 /* for DE2 VI layer which ignores alpha */
127 /* for DE2 VI layer which ignores alpha */
136 /* for DE2 VI layer which ignores alpha */
145 /* for DE2 VI layer which ignores alpha */
154 /* for DE2 VI layer which ignores alpha */
[all …]
|
| H A D | sun4i_backend.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
6 * Maxime Ripard <maxime.ripard@free-electrons.com>
14 #include <linux/dma-mapping.h>
35 /* backend <-> TCON muxing selection done in backend */
55 regmap_write(engine->regs, SUN4I_BACKEND_OCCTL_REG, in sun4i_backend_apply_color_correction()
59 regmap_write(engine->regs, SUN4I_BACKEND_OCRCOEF_REG(i), in sun4i_backend_apply_color_correction()
68 regmap_update_bits(engine->regs, SUN4I_BACKEND_OCCTL_REG, in sun4i_backend_disable_color_correction()
78 regmap_write(engine->regs, SUN4I_BACKEND_REGBUFFCTL_REG, in sun4i_backend_commit()
84 int layer, bool enable) in sun4i_backend_layer_enable() argument
88 DRM_DEBUG_DRIVER("%sabling layer %d\n", enable ? "En" : "Dis", in sun4i_backend_layer_enable()
[all …]
|
| /linux/Documentation/networking/devlink/ |
| H A D | devlink-health.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Background chapter
49 auto-dump is set and there is no other dump which is already stored)
52 - Auto-recovery configuration
53 - Grace period vs. time passed since last recover
63 json-like format. The API allows the driver to add nested attributes such as
69 the data using SKBs to the netlink layer, it fragments the data between
85 .. list-table:: List of devlink health interfaces
88 * - Name
89 - Description
[all …]
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | switch.rst | 2 dm-switch
5 The device-mapper switch target creates a device that supports an
6 arbitrary mapping of fixed-size regions of I/O across a fixed set of
11 number of fixed-sized address regions but there is no simple pattern
13 dm-stripe.
15 Background subtitle
16 ----------
42 A device-mapper table already lets you map different regions of a
48 Using this device-mapper switch target we can now build a two-layer
51 Upper Tier - Determine which array member the I/O should be sent to.
[all …]
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | blkio-controller.rst | 11 and based on user options switch IO policies in the background.
15 generic block layer and can be used on leaf nodes as well as higher
22 -----------------------------
27 Enable throttling in block layer::
33 mount -t cgroup -o blkio none /sys/fs/cgroup/blkio
92 Enable block device throttling support in block layer.
98 --------------------------------
106 see Documentation/block/bfq-iosched.rst.
110 weight. For more details, see Documentation/block/bfq-iosched.rst.
152 are further divided by the type of operation - read or write, sync
[all …]
|
| /linux/Documentation/networking/ |
| H A D | rds.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 This readme tries to provide some background on the hows and whys of RDS,
14 http://oss.oracle.com/pipermail/rds-devel/2007-November/000228.html
22 cluster - so in a cluster with N processes you need N sockets, in contrast
23 to N*N if you use a connection-oriented socket transport like TCP.
25 RDS is not Infiniband-specific; it was designed to support different
29 The high-level semantics of RDS from the application's point of view are
39 transport has to be IP-based. In fact, RDS over IB uses a
59 a active-active HA scenario), but only as long as the address
72 to create RDS sockets. SOL_RDS is the socket-level to be used
[all …]
|