Searched +full:right +full:- +full:aligned (Results 1 – 25 of 53) sorted by relevance
123
| /Documentation/input/ |
| D | gamepad.rst | 1 ---------------------------
3 ---------------------------
11 having user-space deal with different button-mappings for each gamepad, this
25 | <===DP===> |SE| |ST| (W) -|- (E) | |
35 D-Pad Left Right Action Pad
43 - Action-Pad
44 4 buttons in diamonds-shape (on the right side). The buttons are
47 - D-Pad (Direction-pad)
48 4 buttons (on the left side) that point up, down, left and right.
49 - Menu-Pad
[all …]
|
| D | multi-touch-protocol.rst | 4 Multi-touch (MT) Protocol
7 :Copyright: |copy| 2009-2010 Henrik Rydberg <rydberg@euromail.se>
11 ------------
13 In order to utilize the full power of the new multi-touch and multi-user
16 document describes the multi-touch (MT) protocol which allows kernel
30 --------------
34 packet. Since these events are ignored by current single-touch (ST)
48 All drivers mark the end of a multi-touch transfer by calling the usual
67 the ABS_MT_TRACKING_ID of the associated slot. A non-negative tracking id
68 is interpreted as a contact, and the value -1 denotes an unused slot. A
[all …]
|
| /Documentation/translations/ |
| D | index.rst | 21 ----------
34 immediately to all translations. Translations' maintainers - and
35 contributors - follow the evolution of the official documentation and they
36 maintain translations aligned as much as they can. For this reason there is
38 translation does not sound right compared to what you read in the code, please
39 inform the translation maintainer and - if you can - check also the English
|
| /Documentation/devicetree/bindings/media/ |
| D | video-interface-devices.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/media/video-interface-devices.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacopo Mondi <jacopo@jmondi.org>
11 - Sakari Ailus <sakari.ailus@linux.intel.com>
14 flash-leds:
15 $ref: /schemas/types.yaml#/definitions/phandle-array
17 An array of phandles, each referring to a flash LED, a sub-node of the LED
20 lens-focus:
[all …]
|
| /Documentation/process/ |
| D | code-of-conduct.rst | 11 our community a harassment-free experience for everyone, regardless of age, body
13 expression, level of experience, education, socio-economic status, nationality,
48 Maintainers have the right and responsibility to remove, edit, or reject
50 not aligned to this Code of Conduct, or to ban temporarily or permanently any
59 representing a project or community include using an official project e-mail
80 available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
|
| D | stable-api-nonsense.rst | 8 Greg Kroah-Hartman <greg@kroah.com>
27 -----------------
38 -----
41 to worry about the in-kernel interfaces changing. For the majority of
59 -----------------------
61 binary interface would naturally happen too, right? Wrong. Please
64 - Depending on the version of the C compiler you use, different kernel
71 - Depending on what kernel build options you select, a wide range of
74 - different structures can contain different fields
75 - Some functions may not be implemented at all, (i.e. some locks
[all …]
|
| /Documentation/filesystems/ |
| D | erofs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 EROFS - Enhanced Read-Only File System
10 EROFS filesystem stands for Enhanced Read-Only File System. It aims to form a
11 generic read-only filesystem solution for various read-only use cases instead
17 random-access friendly high-performance filesystem to get rid of unneeded I/O
18 amplification and memory-resident overhead compared to similar approaches.
22 - read-only storage media or
24 - part of a fully trusted read-only solution, which means it needs to be
25 immutable and bit-for-bit identical to the official golden image for
28 - hope to minimize extra storage space with guaranteed end-to-end performance
[all …]
|
| /Documentation/iio/ |
| D | iio_devbuf.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 Devices with buffer support feature an additional sub-directory in the
25 ----------
31 ----------
34 be written last, after length and selection of scan elements. Writing a non-zero
39 -------------
49 Non-blocking read will retrieve the available samples from the buffer even if
55 --------------
57 Read-only attribute indicating the bytes of data available in the buffer. In the
63 -------------
[all …]
|
| /Documentation/virt/kvm/arm/ |
| D | mmio-guard.rst | 1 .. SPDX-License-Identifier: GPL-2.0
20 the right thing.
27 This relies on a set of hypercalls defined in the KVM-specific range,
43 Arguments: r1-r3 Reserved / Must be zero
44 Return Values: (int64) NOT_SUPPORTED(-1) on error, or
56 Return Values: (int64) NOT_SUPPORTED(-1) on error, or
64 Arguments: (uint64) The base of the PG-sized IPA range
66 MMIO. Must be aligned to the PG size
71 Return Values: (int64) NOT_SUPPORTED(-1) on error, or
85 Arguments: (uint64) The base of the PG-sized IPA range
[all …]
|
| /Documentation/fb/ |
| D | pxafb.rst | 10 modprobe pxafb options=vmem:2M,mode:640x480-8,passive
14 video=pxafb:vmem:2M,mode:640x480-8,passive
21 mode:XRESxYRES[-BPP]
37 right:RIGHT == LCCR1_ELW + 1
87 PXA27x and later processors support overlay1 and overlay2 on-top of the
88 base framebuffer (although under-neath the base is also possible). They
89 support palette and no-palette RGB formats, as well as YUV formats (only
96 1. overlay can start at a 32-bit word aligned position within the base
98 is encoded into var->nonstd (no, var->xoffset and var->yoffset are
104 var->xres_virtual * var->yres_virtual * bpp
[all …]
|
| /Documentation/virt/kvm/x86/ |
| D | msr.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 KVM-specific MSRs
16 ---------------
24 4-byte alignment physical address of a memory area which must be
42 An odd version indicates an in-progress update.
53 Note that although MSRs are per-CPU entities, the effect of this
63 4-byte aligned physical address of a memory area which must be in
80 updates of this structure is arbitrary and implementation-dependent.
89 An odd version indicates an in-progress update.
104 tsc-related quantity to nanoseconds
[all …]
|
| /Documentation/devicetree/bindings/net/pcs/ |
| D | snps,dw-xpcs.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/pcs/snps,dw-xpcs.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Serge Semin <fancer.lancer@gmail.com>
17 optionally synthesized with a vendor-specific interface connected to
23 right to the system IO memory space.
28 - description: Synopsys DesignWare XPCS with none or unknown PMA
29 const: snps,dw-xpcs
30 - description: Synopsys DesignWare XPCS with Consumer Gen1 3G PMA
[all …]
|
| /Documentation/arch/sparc/oradax/ |
| D | dax-hv-api.txt | 3 Publication date 2017-09-25 08:21
5 Extracted via "pdftotext -f 547 -l 572 -layout sun4v_20170925.pdf"
16 live-migration and other system management activities.
20 …high speed processoring of database-centric operations. The coprocessors may support one or more of
28 …e Completion Area and, unless execution order is specifically restricted through the use of serial-
45 …device node in the guest MD (Section 8.24.17, “Database Analytics Accelerators (DAX) virtual-device
51 36.1.1.1. "ORCL,sun4v-dax" Device Compatibility
54 • No-op/Sync
81 36.1.1.2. "ORCL,sun4v-dax-fc" Device Compatibility
82 … "ORCL,sun4v-dax-fc" is compatible with the "ORCL,sun4v-dax" interface, and includes additional CCB
[all …]
|
| /Documentation/arch/riscv/ |
| D | boot.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 RISC-V Kernel Boot Requirements and Constraints
10 This document describes what the RISC-V kernel expects from bootloaders and
16 Pre-kernel Requirements and Constraints
19 The RISC-V kernel expects the following of bootloaders and platform firmware:
22 --------------
24 The RISC-V kernel expects:
30 ---------
32 The RISC-V kernel expects:
37 -------------------------------------
[all …]
|
| /Documentation/driver-api/ |
| D | ioctl.rst | 12 so this documentation tries to help developers get it right.
18 the ioctl system call. While this can be any 32-bit number that uniquely
22 ``include/uapi/asm-generic/ioctl.h`` provides four macros for defining
36 An 8-bit number, often a character literal, specific to a subsystem
37 or driver, and listed in Documentation/userspace-api/ioctl/ioctl-number.rst
40 An 8-bit number identifying the specific command, unique for a give
45 encodes the ``sizeof(data_type)`` value in a 13-bit or 14-bit integer,
74 handler returns either -ENOTTY or -ENOIOCTLCMD, which also results in
75 -ENOTTY being returned from the system call. Some subsystems return
76 -ENOSYS or -EINVAL here for historic reasons, but this is wrong.
[all …]
|
| D | uio-howto.rst | 5 :Author: Hans-Jürgen Koch Linux developer, Linutronix
6 :Date: 2006-12-11
12 ------------
18 -------
39 - The device has memory that can be mapped. The device can be
42 - The device usually generates interrupts.
44 - The device does not fit into one of the standard kernel subsystems.
47 ---------------
54 --------
56 Find something wrong with this document? (Or perhaps something right?) I
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-yuv-planar.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. planar-yuv:
12 - Semi-planar formats use two planes. The first plane is the luma plane and
16 - Fully planar formats use three planes to store the Y, Cb and Cr components
26 and applications that support the multi-planar API, described in
27 :ref:`planar-apis`. Unless explicitly documented as supporting non-contiguous
31 Semi-Planar YUV Formats
46 For non-contiguous formats, no constraints are enforced by the format on the
57 .. flat-table:: Overview of Semi-Planar YUV Formats
58 :header-rows: 1
[all …]
|
| D | ext-ctrls-camera.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _camera-controls:
13 .. _camera-control-id:
23 .. _v4l2-exposure-auto-type:
28 enum v4l2_exposure_auto_type -
37 .. flat-table::
38 :header-rows: 0
39 :stub-columns: 0
41 * - ``V4L2_EXPOSURE_AUTO``
42 - Automatic exposure time, automatic iris aperture.
[all …]
|
| /Documentation/userspace-api/netlink/ |
| D | specs.rst | 1 .. SPDX-License-Identifier: BSD-3-Clause
17 - the C uAPI header
18 …- documentation of the protocol as a ReST file - see :ref:`Documentation/networking/netlink_spec/i…
19 - policy tables for input attribute validation
20 - operation tables
25 See :doc:`intro-specs` for a practical starting guide.
28 ``((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)``
40 - ``genetlink`` - most streamlined, should be used by all new families
41 - ``genetlink-c`` - superset of ``genetlink`` with extra attributes allowing
45 - ``genetlink-legacy`` - Generic Netlink catch all schema supporting quirks of
[all …]
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | st,stm32-adc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/iio/adc/st,stm32-adc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 STM32 ADC is a successive approximation analog-to-digital converter.
13 stored in a left-aligned or right-aligned 32-bit data register.
17 voltage goes beyond the user-defined, higher or lower thresholds.
22 - Fabrice Gasnier <fabrice.gasnier@foss.st.com>
27 - st,stm32f4-adc-core
28 - st,stm32h7-adc-core
[all …]
|
| /Documentation/crypto/ |
| D | userspace-if.rst | 5 ------------
9 crypto API high level discussion for the in-kernel use cases applies
21 Some details of the in-kernel kernel crypto API aspects do not apply to
29 ------------------------------
34 - Message digest including keyed message digest (HMAC, CMAC)
36 - Symmetric ciphers
38 - AEAD ciphers
40 - Random Number Generators
56 A cipher is accessed with the same name as done for the in-kernel API
83 In-place Cipher operation
[all …]
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-bus-iio | 3 Contact: linux-iio@vger.kernel.org
14 Contact: linux-iio@vger.kernel.org
26 Contact: linux-iio@vger.kernel.org
50 What: /sys/.../iio:deviceX/scan_elements/in_voltageY-voltageZ_en
62 Contact: linux-iio@vger.kernel.org
86 Contact: linux-iio@vger.kernel.org
89 and hence the form in which it is read from user-space.
102 signed 48 bit integer stored in a 64 bit location aligned to
103 a 64 bit boundary. To obtain the clean value, shift right 2
141 what is enabled and may not be contiguous. Thus for user-space
[all …]
|
| /Documentation/dev-tools/ |
| D | kmsan.rst | 1 .. SPDX-License-Identifier: GPL-2.0
19 -------------------
27 --------------
32 BUG: KMSAN: uninit-value in test_uninit_kmsan_check_memory+0x1be/0x380 [kmsan_test]
36 kunit_generic_run_threadfn_adapter+0x6d/0xc0 lib/kunit/try-catch.c:28
45 kunit_generic_run_threadfn_adapter+0x6d/0xc0 lib/kunit/try-catch.c:28
53 Bytes 4-7 of 8 are uninitialized
56 CPU: 0 PID: 6731 Comm: kunit_try_catch Tainted: G B E 5.16.0-rc3+ #104
57 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
71 - in a condition, e.g. ``if (v) { ... }``;
[all …]
|
| /Documentation/trace/ |
| D | user_events.rst | 2 user_events: User-based Event Tracing
8 --------
20 requires CAP_PERFMON due to the event persisting, otherwise -EPERM is returned.
36 -----------
74 This must be 4 (32-bit) or 8 (64-bit). 64-bit values are only allowed to be
75 used on 64-bit kernels, however, 32-bit can be used on all kernels.
79 support for lower versions of the kernel. If a flag is not supported -EINVAL
83 must be naturally aligned and write accessible within the user program.
93 -EPERM is returned.
106 instead of "user_events". This prevents single-format event names conflicting
[all …]
|
| /Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 27 Please check the I-D abstract listing contained in each Internet Draft
46 mandatory access controls and multi-level security. These systems are
88 once in a datagram. All multi-octet fields in the option are defined to be
91 +----------+----------+------//------+-----------//---------+
93 +----------+----------+------//------+-----------//---------+
118 should assume that the DOI identifier field is not aligned on any particular
124 corresponding ASCII representations. Non-related groups of systems may
148 actual security information to be passed. All multi-octet fields in a tag
151 all tags, as well as fields within a tag, are not aligned on any particular
171 +----------+----------+--------//--------+
[all …]
|
123