Home
last modified time | relevance | path

Searched +full:left +full:- +full:aligned (Results 1 – 25 of 44) sorted by relevance

12

/Documentation/input/
Dgamepad.rst1 ---------------------------
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 …]
Dmulti-touch-protocol.rst4 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
62 important. Event filtering and finger tracking is left to user space [#f3]_.
67 the ABS_MT_TRACKING_ID of the associated slot. A non-negative tracking id
[all …]
/Documentation/arch/sparc/oradax/
Ddax-hv-api.txt3 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/userspace-api/media/v4l/
Dselection-api-configuration.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
15 time the cropping/composing rectangles may have to be aligned, and both
20 :ref:`constraint flags <v4l2-selection-flags>`.
26 See figure :ref:`sel-targets-capture` for examples of the selection
30 The range of coordinates of the top left corner, width and height of
32 target. It is recommended for the driver developers to put the top/left
36 The top left corner, width and height of the source rectangle, that is
51 coordinates are expressed in pixels. The rectangle's top/left corner
63 :ref:`constraint flags <v4l2-selection-flags>`.
91 All coordinates are expressed in pixels. The top/left corner is always
[all …]
Dcrop.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
6 Image Cropping, Insertion and Scaling -- the CROP API
12 <selection-api>`. The new API should be preferred in most cases,
15 equivalent in the SELECTION API. See :ref:`selection-vs-crop` for a
62 .. _crop-scale:
64 .. kernel-figure:: crop.svg
74 For capture devices the coordinates of the top left corner, width and
81 :ref:`vbi-hsync`). Vertically ITU-R line numbers of the first field
82 (see ITU R-525 line numbering for :ref:`525 lines <vbi-525>` and for
83 :ref:`625 lines <vbi-625>`), multiplied by two if the driver
[all …]
Dpixfmt-yuv-planar.rst1 .. 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 …]
Dext-ctrls-camera.rst1 .. 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/devicetree/bindings/media/
Dvideo-interface-devices.yaml1 # 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/virt/kvm/devices/
Darm-vgic.rst1 .. SPDX-License-Identifier: GPL-2.0
9 - KVM_DEV_TYPE_ARM_VGIC_V2 ARM Generic Interrupt Controller v2.0
13 controller, requiring emulated user-space devices to inject interrupts to the
18 device and guest ITS devices, see arm-vgic-v3.txt. It is not possible to
26 KVM_VGIC_V2_ADDR_TYPE_DIST (rw, 64-bit)
29 This address needs to be 4K aligned and the region covers 4 KByte.
31 KVM_VGIC_V2_ADDR_TYPE_CPU (rw, 64-bit)
34 This address needs to be 4K aligned and the region covers 8 KByte.
39 -E2BIG Address outside of addressable IPA range
40 -EINVAL Incorrectly aligned address
[all …]
Dvcpu.rst1 .. SPDX-License-Identifier: GPL-2.0
9 kvm_device_attr as other devices, but targets VCPU-wide settings and controls.
19 ---------------------------------------
27 -EBUSY The PMU overflow interrupt is already set
28 -EFAULT Error reading interrupt number
29 -ENXIO PMUv3 not supported or the overflow interrupt not set
31 -ENODEV KVM_ARM_VCPU_PMU_V3 feature missing from VCPU
32 -EINVAL Invalid PMU overflow interrupt number supplied or
33 trying to set the IRQ number without using an in-kernel
43 ---------------------------------------
[all …]
/Documentation/devicetree/bindings/usb/
Dchipidea,usb2-common.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/chipidea,usb2-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Xu Yang <xu.yang_2@nxp.com>
25 clock-names:
31 power-domains:
37 reset-names:
40 "#reset-cells":
45 itc-setting:
[all …]
/Documentation/fb/
Dpxafb.rst10 modprobe pxafb options=vmem:2M,mode:640x480-8,passive
14 video=pxafb:vmem:2M,mode:640x480-8,passive
21 mode:XRESxYRES[-BPP]
35 left:LEFT == LCCR1_BLW + 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/core-api/
Ddma-isa-lpc.rst12 ------------------------
16 #include <linux/dma-mapping.h>
20 bus addresses (see Documentation/core-api/dma-api.rst for details).
28 -----------------
37 The DMA-able address space is the lowest 16 MB of _physical_ memory.
45 allocate the memory during boot-up it's a good idea to also pass
52 -------------------
66 --------
69 8-bit transfers and the upper four are for 16-bit transfers.
72 channel 4 is used to give DMA access for the second controller (0-3).
[all …]
Dxarray.rst1 .. SPDX-License-Identifier: GPL-2.0+
15 next or previous entry in a cache-efficient manner. In contrast to a
17 order to grow the array. It is more memory-efficient, parallelisable
18 and cache friendly than a doubly-linked list. It takes advantage of
28 Normal pointers may be stored in the XArray directly. They must be 4-byte
29 aligned, which is true for any pointer returned from kmalloc() and
30 alloc_page(). It isn't true for arbitrary user-space pointers,
54 the range. Storing to any index will store to all of them. Multi-index
63 allocated ones. A freshly-initialised XArray contains a ``NULL``
82 returns ``-EBUSY`` if the entry is not empty.
[all …]
/Documentation/virt/kvm/x86/
Dmsr.rst1 .. 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/admin-guide/mm/
Dnommu-mmap.rst2 No-MMU memory mapping support
5 The kernel has limited support for memory mapping under no-MMU conditions, such
16 The behaviour is similar between the MMU and no-MMU cases, but not identical;
21 In the MMU case: VM regions backed by arbitrary pages; copy-on-write
24 In the no-MMU case: VM regions backed by arbitrary contiguous runs of
31 the no-MMU case doesn't support these, behaviour is identical to
39 In the no-MMU case:
41 - If one exists, the kernel will re-use an existing mapping to the
45 - If possible, the file mapping will be directly on the backing device
50 - If the backing device can't or won't permit direct sharing,
[all …]
/Documentation/networking/
Dcan_ucan_protocol.rst5 UCAN is the protocol used by the microcontroller-based USB-CAN
6 adapter that is integrated on System-on-Modules from Theobroma Systems
9 The UCAN protocol has been designed to be hardware-independent.
11 internally. All multi-byte integers are encoded as Little Endian.
44 ------------
51 ``wLength`` * Host to Device - Number of bytes to transmit
52 * Device to Host - Maximum Number of bytes to
58 --------------
64 ---------------
75 ------------------
[all …]
/Documentation/trace/
Duser_events.rst2 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/devicetree/bindings/iio/adc/
Dst,stm32-adc.yaml1 # 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/kbuild/
Dgendwarfksyms.rst18 -----
23 Usage: gendwarfksyms [options] elf-object-file ... < symbol-list
26 -d, --debug Print debugging information
27 --dump-dies Dump DWARF DIE contents
28 --dump-die-map Print debugging information about die_map changes
29 --dump-types Dump type strings
30 --dump-versions Dump expanded type strings used for symbol versions
31 -s, --stable Support kABI stability features
32 -T, --symtypes file Write a symtypes file
33 -h, --help Print this message
[all …]
/Documentation/dev-tools/
Dkmsan.rst1 .. 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
65 ``test_uninit_kmsan_check_memory()``). The tool shows the bytes which were left
[all …]
Dkasan.rst1 .. SPDX-License-Identifier: GPL-2.0
8 --------
11 designed to find out-of-bounds and use-after-free bugs.
16 2. Software Tag-Based KASAN
17 3. Hardware Tag-Based KASAN
23 Software Tag-Based KASAN or SW_TAGS KASAN, enabled with CONFIG_KASAN_SW_TAGS,
26 using it for testing on memory-restricted devices with real workloads.
28 Hardware Tag-Based KASAN or HW_TAGS KASAN, enabled with CONFIG_KASAN_HW_TAGS,
29 is the mode intended to be used as an in-field memory bug detector or as a
37 The Generic and the Software Tag-Based modes are commonly referred to as the
[all …]
/Documentation/netlabel/
Ddraft-ietf-cipso-ipsecurity-01.txt27 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 …]
/Documentation/crypto/
Ddescore-readme.rst1 .. SPDX-License-Identifier: GPL-2.0
13 ------------------------------------------------------------------------------
15 des - fast & portable DES encryption & decryption.
42 2. PORTABILITY to any byte-addressable host with a 32bit unsigned C type
43 3. Plug-compatible replacement for KERBEROS's low-level routines.
46 register-starved machines. My discussions with Richard Outerbridge,
51 up in a parameterized fashion so it can easily be modified by speed-daemon
58 compile on a SPARCStation 1 (cc -O4, gcc -O2):
60 this code (byte-order independent):
62 - 30us per encryption (options: 64k tables, no IP/FP)
[all …]
/Documentation/process/
Dmaintainer-tip.rst1 .. SPDX-License-Identifier: GPL-2.0
7 ---------------------
11 aggregation tree for several sub-maintainer trees. The tip tree gitweb URL
16 - **x86 architecture**
22 x86-specific KVM and XEN patches.
30 mail alias which distributes mails to the x86 top-level maintainer
32 ``linux-kernel@vger.kernel.org``, otherwise your mail ends up only in
35 - **Scheduler**
37 Scheduler development takes place in the -tip tree, in the
38 sched/core branch - with occasional sub-topic trees for
[all …]

12