Home
last modified time | relevance | path

Searched +full:layer +full:- +full:primary (Results 1 – 25 of 37) sorted by relevance

12

/Documentation/devicetree/bindings/display/
Dxylon,logicvc-display.yaml1 # 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 …]
/Documentation/firmware-guide/acpi/apei/
Doutput_format.rst1 .. SPDX-License-Identifier: GPL-2.0
24 [primary][, containment warning][, reset][, threshold exceeded]\
55 [cache error][, TLB error][, bus error][, micro-architectural error]
81 unknown | no error | single-bit ECC | multi-bit ECC | \
82 single-symbol chipkill ECC | multi-symbol chipkill ECC | master abort | \
101 aer_layer=<aer layer string>, aer_agent=<aer agent string>
106 downstream switch port | PCIe to PCI/PCI-X bridge | \
107 PCI/PCI-X to PCIe bridge | root complex integrated endpoint device | \
121 Replay Timer Timeout | Advisory Non-Fatal
124 <aer layer string> :=
[all …]
/Documentation/PCI/endpoint/
Dpci-endpoint-cfs.rst1 .. SPDX-License-Identifier: GPL-2.0
17 The PCI Endpoint Core layer creates pci_ep directory in the mounted configfs
20 mount -t configfs none /sys/kernel/config
73 ... primary/
79 Non-transparent bridge), symlink of endpoint controller connected to primary
80 interface should be added in 'primary' directory and symlink of endpoint
138 [1] Documentation/PCI/endpoint/pci-endpoint.rst
/Documentation/networking/
Dmulti-pf-netdev.rst1 .. SPDX-License-Identifier: GPL-2.0
5 Multi-PF Netdev
11 - `Background`_
12 - `Overview`_
13 - `mlx5 implementation`_
14 - `Channels distribution`_
15 - `Observability`_
16 - `Steering`_
17 - `Mutually exclusive features`_
22 The Multi-PF NIC technology enables several CPUs within a multi-socket server to connect directly to
[all …]
Dip-sysctl.rst1 .. SPDX-License-Identifier: GPL-2.0
10 ip_forward - BOOLEAN
11 - 0 - disabled (default)
12 - not 0 - enabled
20 ip_default_ttl - INTEGER
25 ip_no_pmtu_disc - INTEGER
27 fragmentation-required ICMP is received, the PMTU to this
38 accept fragmentation-needed errors if the underlying protocol
48 Possible values: 0-3
52 min_pmtu - INTEGER
[all …]
Dkcm.rst1 .. SPDX-License-Identifier: GPL-2.0
14 +------------+ +------------+ +------------+ +------------+
16 +------------+ +------------+ +------------+ +------------+
18 +-----------+ | | +----------+
20 +----------------------------------+
22 +----------------------------------+
24 +---------+ | | | ------------+
26 +----------+ +----------+ +----------+ +----------+ +----------+
28 +----------+ +----------+ +----------+ +----------+ +----------+
30 +----------+ +----------+ +----------+ +----------+ +----------+
[all …]
Dbonding.rst1 .. SPDX-License-Identifier: GPL-2.0
11 Corrections, HA extensions: 2000/10/03-15:
13 - Willy Tarreau <willy at meta-x.org>
14 - Constantine Gavrilov <const-g at xpert.com>
15 - Chad N. Tindel <ctindel at ieee dot org>
16 - Janice Girouard <girouard at us dot ibm dot com>
17 - Jay Vosburgh <fubar at us dot ibm dot com>
22 - Mitch Williams <mitch.a.williams at intel.com>
35 the original tools from extreme-linux and beowulf sites will not work
119 -----------------------------------------------
[all …]
/Documentation/core-api/
Dswiotlb.rst1 .. SPDX-License-Identifier: GPL-2.0
7 swiotlb is a memory buffer allocator used by the Linux kernel DMA layer. It is
10 the DMA layer calls swiotlb to allocate a temporary memory buffer that conforms
17 the DMA layer of the DMA attributes of the devices they are managing, and use
19 These APIs use the device DMA attributes and kernel-wide settings to determine
20 if bounce buffering is necessary. If so, the DMA layer manages the allocation,
30 ---------------
33 only provide 32-bit DMA addresses. By allocating bounce buffer memory below
40 directed to guest memory that is unencrypted. CoCo VMs set a kernel-wide option
43 the Linux kernel DMA layer does "sync" operations to cause the CPU to copy the
[all …]
/Documentation/arch/s390/
Dcds.rst9 - Ingo Adlung
10 - Cornelia Huck
12 Copyright, IBM Corp. 1999-2002
21 processing, shared versus non-shared interrupt processing, DMA versus port
30 Operation manual (IBM Form. No. SA22-7201).
33 functional layer was introduced that provides generic I/O access methods to
36 The common device support layer comprises the I/O support routines defined
42 described in Documentation/arch/s390/driver-model.rst.
49 * All drivers must define a ccw_driver (see driver-model.txt) and the associated
56 * The channel device layer is gone.
[all …]
/Documentation/block/
Dpr.rst2 Block layer support for Persistent Reservations
12 For a more detailed reference please refer to the SCSI Primary
23 --------------------------------------------------
25 - PR_WRITE_EXCLUSIVE
29 - PR_EXCLUSIVE_ACCESS
33 - PR_WRITE_EXCLUSIVE_REG_ONLY
37 - PR_EXCLUSIVE_ACCESS_REG_ONLY
40 - PR_WRITE_EXCLUSIVE_ALL_REGS
49 - PR_EXCLUSIVE_ACCESS_ALL_REGS
58 ----------------------------------
[all …]
/Documentation/filesystems/
Dinotify.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Inotify - A Powerful yet Simple File Change Notification System
13 - Deleted obsoleted interface, just refer to manpages for user interface.
23 This solves the primary problem with dnotify: keeping the file open pins
29 What is the design decision behind using an-fd-per-instance as opposed to
30 an fd-per-watch?
33 An fd-per-watch quickly consumes more file descriptors than are allowed,
35 select()-able. Yes, root can bump the per-process fd limit and yes, users
38 spaces is thus sensible. The current design is what user-space developers
41 thousand times is silly. If we can implement user-space's preferences
[all …]
/Documentation/fb/
Dviafb.rst6 --------
15 ---------------
34 ----------------------
47 - 640x480 (default)
48 - 720x480
49 - 800x600
50 - 1024x768
53 - 8, 16, 32 (default:32)
56 - 60, 75, 85, 100, 120 (default:60)
59 - 0 : expansion (default)
[all …]
/Documentation/admin-guide/
Ddevices.rst13 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>` document).
15 "BLOCK LAYER" in the MAINTAINERS file to find the right maintainers
63 --------------------------------------
81 /dev/nfsd socksys symbolic Required by iBCS-2
82 /dev/X0R null symbolic Required by iBCS-2
85 Note: ``/dev/X0R`` is <letter X>-<digit 0>-<letter R>.
100 /dev/scd? sr? hard Alternate SCSI CD-ROM name
114 /dev/cdrom CD-ROM device symbolic Current CD-ROM device
115 /dev/cdwriter CD-writer symbolic Current CD-writer device
124 exists, ``/dev/modem`` should point to the appropriate primary TTY device
[all …]
Ddevices.txt1 0 Unnamed devices (e.g. non-device mounts)
7 2 = /dev/kmem OBSOLETE - replaced by /proc/kcore
11 6 = /dev/core OBSOLETE - replaced by /proc/kcore
18 12 = /dev/oldmem OBSOLETE - replaced by /proc/vmcore
31 2 char Pseudo-TTY masters
37 Pseudo-tty's are named as follows:
40 the 1st through 16th series of 16 pseudo-ttys each, and
44 These are the old-style (BSD) PTY devices; Unix98
106 3 char Pseudo-TTY slaves
112 These are the old-style (BSD) PTY devices; Unix98
[all …]
/Documentation/userspace-api/media/dvb/
Dfe_property_parameters.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
15 .. _DTV-UNDEFINED:
24 .. _DTV-TUNE:
33 .. _DTV-CLEAR:
42 .. _DTV-FREQUENCY:
57 of the transponder/channel. The exception is for ISDB-T, where
60 #. For ISDB-T, the channels are usually transmitted with an offset of
65 #. In ISDB-Tsb, the channel consists of only one or three segments the
69 .. _DTV-MODULATION:
88 ATSC (version 1) 8-VSB and 16-VSB.
[all …]
/Documentation/gpu/amdgpu/display/
Dsingle-display-mpo.svg1 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
2 <!-- Created with Inkscape (http://www.inkscape.org/) -->
7 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
10 xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
17 inkscape:version="0.92.5 (2060ec1f9f, 2020-04-08)"
18 sodipodi:docname="single-display-mpo.svg">
31 d="M 5.77,0 -2.88,5 V -5 Z"
32 …style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1.00000003pt;stro…
34 inkscape:connector-curvature="0" />
46 d="M 0,0 5,-5 -12.5,0 5,5 Z"
[all …]
/Documentation/isdn/
Dinterface_capi.rst9 COMMON-ISDN-API (CAPI) is an application programming interface standard used
10 to access ISDN equipment connected to basic rate interfaces (BRI) and primary
13 Kernel CAPI operates as a dispatching layer between CAPI applications and CAPI
74 ----------------------
78 the following non-private fields, all to be set by the driver before calling
82 the name of the driver, as a zero-terminated ASCII string
84 the revision number of the driver, as a zero-terminated ASCII string
87 -------------------
91 all controller specific lower layer interface and callback functions to
94 It contains the following non-private fields:
[all …]
/Documentation/networking/dsa/
Ddsa.rst22 An Ethernet switch typically comprises multiple front-panel ports and one
27 gateways, or even top-of-rack switches. This host Ethernet controller will
36 For each front-panel port, DSA creates specialized network devices which are
37 used as controlling and data-flowing endpoints for use by the Linux networking
46 - what port is this frame coming from
47 - what was the reason why this frame got forwarded
48 - how to send CPU originated traffic to specific ports
52 on Port-based VLAN IDs).
57 - the "cpu" port is the Ethernet switch facing side of the management
61 - the "dsa" port(s) are just conduits between two or more switches, and as such
[all …]
/Documentation/misc-devices/
Dibmvmc.rst1 .. SPDX-License-Identifier: GPL-2.0+
21 https://openpowerfoundation.org/wp-content/uploads/2016/05/LoPAPR_DRAFT_v11_24March2016_cmt1.pdf
27 Console (HMC) - based system management.
29 The primary hardware management solution that is developed by IBM relies
31 packaged as an external tower or rack-mounted personal computer. In a
33 processor-based systems.
36 ----------------------
44 POWER8 or newer processor-based server that is virtualized by PowerVM.
57 - Logical Partitioning Configuration
58 - Start, and stop actions for individual partitions
[all …]
/Documentation/driver-api/
Dntb.rst5 NTB (Non-Transparent Bridge) is a type of PCI-Express bridge chip that connects
6 the separate memory systems of two or more computers to the same PCI-Express
9 scratchpad and message registers. Scratchpad registers are read-and-writable
22 hardware drivers. The term "client" is used here to mean an upper layer
36 ----------------------------------------
38 Primary purpose of NTB is to share some peace of memory between at least two
50 | dma-mapped |-ntb_mw_set_trans(addr) |
52 | (addr) |<======| MW xlat addr |<====| MW base addr |<== memory-mapped IO
53 |------------| |--------------| | |--------------|
68 | dma-mapped | | | MW base addr |<== memory-mapped IO
[all …]
/Documentation/admin-guide/nfs/
Dnfsroot.rst10 Updated 2006 by Nico Schottelius <nico-kernel-nfsroot@schottelius.org>
18 In order to use a diskless system, such as an X-terminal or printer server for
19 example, it is necessary for the root filesystem to be present on a non-disk
21 Documentation/filesystems/ramfs-rootfs-initramfs.rst), a ramdisk (see
22 Documentation/admin-guide/initrd.rst) or a filesystem mounted via NFS. The
34 built-in during configuration. Once this has been selected, the nfsroot
54 This is necessary to enable the pseudo-NFS-device. Note that it's not a
59 nfsroot=[<server-ip>:]<root-dir>[,<nfs-options>]
63 <server-ip> Specifies the IP address of the NFS server.
68 <root-dir> Name of the directory on the server to mount as root.
[all …]
/Documentation/admin-guide/blockdev/
Dzram.rst2 zram: Compressed RAM-based block devices
8 The zram module creates RAM-based block devices named /dev/zram<id>
20 There are several ways to configure and manage zram device(-s):
23 b) using zramctl utility, provided by util-linux (util-linux@vger.kernel.org).
28 In order to get a better idea about zramctl please consult util-linux
29 documentation, zramctl man-page or `zramctl --help`. Please be informed
30 that zram maintainers do not develop/maintain util-linux or zramctl, should
31 you have any questions please contact util-linux@vger.kernel.org
45 -EBUSY an attempt to modify an attribute that cannot be changed once
47 -ENOMEM zram was not able to allocate enough memory to fulfil your
[all …]
/Documentation/dev-tools/
Dkgdb.rst15 Kdb is simplistic shell-style interface which you can use on a system
22 kernel built-ins or in kernel modules if the code was built with
40 kgdb I/O modules compiled as built-ins or loadable kernel modules in the
46 - In order to enable compilation of kdb, you must first enable kgdb.
48 - The kgdb test compile options are described in the kgdb test suite
52 ------------------------------
55 :menuselection:`Kernel hacking --> Kernel debugging` and select
73 certain regions of the kernel's memory space as read-only. If kgdb
93 -----------------------------
108 If you want to use a PS/2-style keyboard with kdb, you would select
[all …]
/Documentation/PCI/
Dpci.rst1 .. SPDX-License-Identifier: GPL-2.0
7 :Authors: - Martin Mares <mj@ucw.cz>
8 - Grant Grundler <grundler@parisc-linux.org>
11 Since each CPU architecture implements different chip-sets and PCI devices
18 by Jonathan Corbet, Alessandro Rubini, and Greg Kroah-Hartman.
26 "Linux PCI" <linux-pci@atrey.karlin.mff.cuni.cz> mailing list.
37 the PCI layer and supports online insertion/removal of devices [thus
38 supporting hot-pluggable PCI, CardBus, and Express-Card in a single driver].
45 - Enable the device
46 - Request MMIO/IOP resources
[all …]
/Documentation/driver-api/usb/
Dgadget.rst11 This document presents a Linux-USB "Gadget" kernel mode API, for use
17 - Supports USB 2.0, for high speed devices which can stream data at
20 - Handles devices with dozens of endpoints just as well as ones with
21 just two fixed-function ones. Gadget drivers can be written so
24 - Flexible enough to expose more complex USB device capabilities such
28 - USB "On-The-Go" (OTG) support, in conjunction with updates to the
29 Linux-USB host side.
31 - Sharing data structures and API models with the Linux-USB host side
32 API. This helps the OTG support, and looks forward to more-symmetric
36 - Minimalist, so it's easier to support new device controller hardware.
[all …]

12