| /linux-5.10/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
41 Most gamepads have the following features:
43 - Action-Pad
44 4 buttons in diamonds-shape (on the right side). The buttons are
45 differently labeled on most devices so we define them as NORTH,
47 - D-Pad (Direction-pad)
[all …]
|
| D | event-codes.rst | 1 .. _input-event-codes:
36 - Used as markers to separate events. Events may be separated in time or in
41 - Used to describe state changes of keyboards, buttons, or other key-like
46 - Used to describe relative axis value changes, e.g. moving the mouse 5 units
51 - Used to describe absolute axis value changes, e.g. describing the
56 - Used to describe miscellaneous input data that do not fit into other types.
60 - Used to describe binary state input switches.
64 - Used to turn LEDs on devices on and off.
68 - Used to output sound to devices.
72 - Used for autorepeating devices.
[all …]
|
| /linux-5.10/Documentation/process/ |
| D | botching-up-ioctls.rst | 5 From: https://blog.ffwll.ch/2013/11/botching-up-ioctls.html
13 Which is nice, since there's no more insanity in the form of fake-generic, but
18 lessons learned while botching the job for the drm/i915 driver. Most of these
19 only cover technicalities and not the big-picture issues like what the command
25 -------------
28 will need to add a 32-bit compat layer:
33 * Align everything to the natural size and use explicit padding. 32-bit
34 platforms don't necessarily align 64-bit values to 64-bit boundaries, but
35 64-bit platforms do. So we always need padding to the natural size to get
36 this right.
[all …]
|
| D | applying-patches.rst | 11 This document is obsolete. In most cases, rather than using ``patch``
54 in the patch file when applying it (the ``-p1`` argument to ``patch`` does
57 To revert a previously applied patch, use the -R argument to patch.
60 patch -p1 < ../patch-x.y.z
64 patch -R -p1 < ../patch-x.y.z
76 patch -p1 < path/to/patch-x.y.z
82 Patch can also get the name of the file to use via the -i argument, like
85 patch -p1 -i path/to/patch-x.y.z
91 xzcat path/to/patch-x.y.z.xz | patch -p1
92 bzcat path/to/patch-x.y.z.gz | patch -p1
[all …]
|
| D | 4.Coding.rst | 3 Getting the code right
6 While there is much to be said for a solid and community-oriented design
14 will shift toward doing things right and the tools which can help in that
19 ---------
25 :ref:`Documentation/process/coding-style.rst <codingstyle>`. For much of
26 that time, the policies described in that file were taken as being, at most,
38 strangely-formatted code.
43 giving up a degree of control in a number of ways - including control over
49 as a way of getting their name into the kernel changelogs - or both. But
59 80-column limit, for example), just do it.
[all …]
|
| D | 5.Posting.rst | 13 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`,
14 :ref:`Documentation/process/submitting-drivers.rst <submittingdrivers>`
15 and :ref:`Documentation/process/submit-checklist.rst <submitchecklist>`.
19 ------------
25 consider posting in-progress work, or even making a git tree available so
31 patches which are known to be half-baked, but those who do will come in
32 with the idea that they can help you drive the work in the right direction.
36 -----------------------
41 - Test the code to the extent that you can. Make use of the kernel's
43 combinations of configuration options, use cross-compilers to build for
[all …]
|
| /linux-5.10/Documentation/x86/ |
| D | kernel-stacks.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Kernel stacks on x86-64 bit
10 Most of the text from Keith Owens, hacked by AK
37 per CPU interrupt nest counter. This is needed because x86-64 "IST"
48 An IST is selected by a non-zero value in the IST field of an
49 interrupt-gate descriptor. When an interrupt occurs and the hardware
53 will switch back to the per-thread stack. If software wants to allow
62 IST events with the same code to be nested. However in most cases, the
70 Used for interrupt 8 - Double Fault Exception (#DF).
79 Used for non-maskable interrupts (NMI).
[all …]
|
| /linux-5.10/arch/ia64/include/asm/uv/ |
| D | uv_hub.h | 23 * M - The low M bits of a physical address represent the offset
28 * N - Number of bits in the node portion of a socket physical
31 * NASID - network ID of a router, Mbrick or Cbrick. Nasid values of
33 * equal to 0. Most addressing macros that target UV hub chips
34 * right shift the NASID by 1 to exclude the always-zero bit.
37 * GNODE - NASID right shifted by 1 bit. Most mmrs contain gnodes instead
40 * PNODE - the low N bits of the GNODE. The PNODE is the most useful variant
45 * +--------------------------------+---------------------+
47 * +--------------------------------+---------------------+
48 * |<-------53 - M bits --->|<--------M bits ----->
[all …]
|
| /linux-5.10/fs/reiserfs/ |
| D | README | 21 a check in the mail to you (for non-trivial improvements) when he
25 right to decline to allow him to license your code contribution other
56 distributors wanting them out of sync.:-) Please try to remember to
64 recompile your kernel, most of the time. The errors you get will be
73 the software component development power of the internet. Be the most
92 to work the way he did, he is one of the most selfless men I know.
94 Yura helps with benchmarking, coding hashes, and block pre-allocation
131 Chris Mason dived right into our code, and in just a few months produced
148 Jeff Mahoney, of SuSE, contributed a few cleanup fixes, most notably
|
| /linux-5.10/Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 Git source-code management system. Git is a powerful tool with a lot of
9 features; as is often the case with such tools, there are right and wrong
30 - Changing the parent (starting) commit upon which a series of patches is
36 - Changing the history of a set of patches by fixing (or deleting) broken
48 - History that has been exposed to the world beyond your private system
54 That said, there are always exceptions. Some trees (linux-next being
61 - Do not rebase a branch that contains history created by others. If you
67 - Do not reparent a tree without a good reason to do so. Just being on a
71 - If you must reparent a repository, do not pick some random kernel commit
[all …]
|
| /linux-5.10/include/uapi/linux/ |
| D | falloc.h | 1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
6 #define FALLOC_FL_PUNCH_HOLE 0x02 /* de-allocates range */
20 * granularity of the operation. Most will limit operations to
26 * considered an illegal operation - just use ftruncate(2) if you need
35 * unwritten extents - even though file system may choose to zero out the
48 * shifted towards right by len bytes to create a hole. As such, this
52 * of the operation. Most will limit operations to filesystem block size
57 * the file is considered an illegal operation - just use ftruncate(2) or
66 * copy-on-write.
69 * granularity of the operation. Most will limit operations to filesystem
[all …]
|
| /linux-5.10/Documentation/driver-api/media/drivers/ |
| D | pvrusb2.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 ----------
13 Its history started with the reverse-engineering effort by Björn
29 1. Low level wire-protocol implementation with the device.
38 tear-down, arbitration, and interaction with high level
45 The most important shearing layer is between the top 2 layers. A
54 right now the V4L high level interface is the most complete, the
56 functions, and there's no reason I see right now why it shouldn't be
57 possible to produce a DVB high level interface that can sit right
61 --------
[all …]
|
| /linux-5.10/tools/testing/selftests/kvm/lib/ |
| D | sparsebit.c | 1 // SPDX-License-Identifier: GPL-2.0-only
27 * sparsebit_alloc() and most also take a bit index. Frequently
30 * ---- Query Operations
37 * ---- Modifying Operations
67 * For the most part the internal implementation of sparsebit is
72 * set. It is also efficient in memory usage when most of the bits are
75 * At a high-level the state of the bit settings are maintained through
76 * the use of a binary-search tree, where each node contains at least
87 * node, while the mask member stores the setting of the first 32-bits.
99 * represent cases where most bits are set. For example, the case of all
[all …]
|
| /linux-5.10/net/wimax/ |
| D | wimax-internal.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
6 * Copyright (C) 2007 Intel Corporation <linux-wimax@intel.com>
7 * Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
32 * (wimax_dev->mutex). As well, most operations need to call this
33 * function to check if the state is the right one.
35 * An error value will be returned if the state is not the right
42 if (wimax_dev->state == __WIMAX_ST_NULL) in wimax_dev_is_ready()
43 return -EINVAL; /* Device is not even registered! */ in wimax_dev_is_ready()
44 if (wimax_dev->state == WIMAX_ST_DOWN) in wimax_dev_is_ready()
45 return -ENOMEDIUM; in wimax_dev_is_ready()
[all …]
|
| /linux-5.10/drivers/media/rc/keymaps/ |
| D | rc-kworld-plus-tv-analog.c | 1 // SPDX-License-Identifier: GPL-2.0+
2 // kworld-plus-tv-analog.h - Keytable for kworld_plus_tv_analog Remote Controller
4 // keymap imported from ir-keymaps.c
8 #include <media/rc-map.h>
17 { 0x16, KEY_CLOSECD }, /* -> ) */
26 /* Two keys have the same code: 4 and right */
45 /* Couldn't map key left/key right since those
55 Most of them conflict with digits.
|
| /linux-5.10/lib/ |
| D | btree.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * lib/btree.c - Simple In-memory B+Tree
5 * Copyright (c) 2007-2008 Joern Engel <joern@purestorage.com>
9 * see http://programming.kicks-ass.net/kernel-patches/vma_lookup/btree.patch
27 * ~98% pointers - hard to beat. Very sparse radix trees contain only ~2%
35 * values are to the right, not to the left. All used slots within a node
36 * are on the left, all unused slots contain NUL values. Most operations
97 node = mempool_alloc(head->mempool, gfp); in btree_node_alloc()
109 return -1; in longcmp()
140 for (i = geo->keylen - 1; i >= 0; i--) { in dec_key()
[all …]
|
| /linux-5.10/Documentation/driver-api/media/ |
| D | v4l2-intro.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ------------
7 hardware: most devices have multiple ICs, export multiple device nodes in
8 /dev, and create also non-V4L2 devices such as DVB, ALSA, FB, I2C and input
12 do audio/video muxing/encoding/decoding makes it more complex than most.
15 called 'sub-devices'.
22 connecting to sub-devices themselves. Some of this is quite complicated
23 to do right and many drivers never did do it correctly.
32 A good example to look at as a reference is the v4l2-pci-skeleton.c
38 -------------------------
[all …]
|
| D | rc-core.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 -------------------------
13 Also, on most hardware, keeping a key pressed for more than a few dozens of
23 infrared-based remote controllers, there's no key release event. Instead,
26 However, most of the remote controllers use infrared (IR) to transmit signals.
48 At receiver, a simple low-pass filter can be used to convert the received
64 without any receivers. Right now, all such devices work only in
78 The Kernel has support for mapping tables available on most media
86 .. kernel-doc:: include/media/rc-core.h
88 .. kernel-doc:: include/media/rc-map.h
|
| /linux-5.10/scripts/dummy-tools/ |
| D | gcc | 2 # SPDX-License-Identifier: GPL-2.0-only
13 # super-set of CONFIG options that cover any build environment. If some of the
17 # However, it is not feasible to get a full-featured compiler for every arch.
24 # $ make CROSS_COMPILE=scripts/dummy-tools/ oldconfig
26 # Most of compiler features are tested by cc-option, which simply checks the
27 # exit code of $(CC). This script does nothing and just exits with 0 in most
28 # cases. So, $(cc-option, ...) is evaluated as 'y'.
30 # This scripts caters to more checks; handle --version and pre-process __GNUC__
31 # etc. to pretend to be GCC, and also do right things to satisfy some scripts.
36 # arg_contain <word-you-are-searching-for> "$@"
[all …]
|
| /linux-5.10/Documentation/driver-api/usb/ |
| D | dma.rst | 11 The big picture is that USB drivers can continue to ignore most DMA issues,
12 though they still must provide DMA-ready buffers (see
13 :doc:`/core-api/dma-api-howto`). That's how they've worked through
14 the 2.4 (and earlier) kernels, or they can now be DMA-aware.
16 DMA-aware usb drivers:
18 - New calls enable DMA-aware drivers, letting them allocate dma buffers and
19 manage dma mappings for existing dma-ready buffers (see below).
21 - URBs have an additional "transfer_dma" field, as well as a transfer_flags
25 - "usbcore" will map this DMA address, if a DMA-aware driver didn't do
29 - There's a new "generic DMA API", parts of which are usable by USB device
[all …]
|
| /linux-5.10/Documentation/timers/ |
| D | timers-howto.rst | 2 delays - Information on the various kernel delay / sleep mechanisms
8 This question is most often faced by driver writers who have to
9 deal with hardware delays and who may not be the most intimately
14 ----------------
16 The first, and most important, question you need to ask is "Is my
30 udelay is the generally preferred API; ndelay-level
31 precision may not actually exist on many non-PC devices.
38 NON-ATOMIC CONTEXT:
41 work correctly, using the "right" sleep function will
45 -- Backed by busy-wait loop:
[all …]
|
| /linux-5.10/arch/parisc/math-emu/ |
| D | fpbits.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * Linux/PA-RISC Project (http://www.parisc-linux.org/)
5 * Floating-point emulation code
6 * Copyright (C) 2001 Hewlett-Packard (Paul Bame) <bame@debian.org>
10 PA header file -- do not include this header file for non-PA builds.
18 * and bitfield assignment (default left-to-right, unlike VAX, PDP-11)
20 * the C compiler "-D" flag (e.g., -DHOSTWDSZ=36 -DBITFLR for the DEC-20).
22 * is a 32-bit integer (right-justified on the 20) and that bit 0 is the
23 * most significant bit.
33 /*-------------------------------------------------------------------------
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/input/ |
| D | adc-joystick.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
2 # Copyright 2019-2020 Artur Rojek
4 ---
5 $id: "http://devicetree.org/schemas/input/adc-joystick.yaml#"
6 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
11 - Artur Rojek <contact@artur-rojek.eu>
19 const: adc-joystick
21 io-channels:
27 See Documentation/devicetree/bindings/iio/iio-bindings.txt for details.
29 '#address-cells':
[all …]
|
| /linux-5.10/drivers/media/i2c/ |
| D | tda7432.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * For the STS-Thompson TDA7432 audio processor chip
18 * debug - set to 1 if you'd like to see debug messages
21 * loudness - set between 0 and 15 for varying degrees of loudness effect
23 * maxvol - set maximum volume to +20db (1), default is 0db(0)
37 #include <media/v4l2-device.h>
38 #include <media/v4l2-ioctl.h>
39 #include <media/v4l2-ctrls.h>
84 return &container_of(ctrl->handler, struct tda7432, hdl)->sd; in to_sd()
87 /* The TDA7432 is made by STS-Thompson
[all …]
|
| /linux-5.10/Documentation/s390/ |
| D | vfio-ap.rst | 13 The AP adapter cards are exposed via the AP bus. The motivation for vfio-ap
16 facilities which do most of the hard work of providing direct access to AP
45 sub-directory::
75 /sys/bus/ap/ap_control_domain_mask. The bits in the mask, from most to least
76 significant bit, correspond to domains 0-255.
111 * NQAP: to enqueue an AP command-request message to a queue
112 * DQAP: to dequeue an AP command-reply message from a queue
131 to the KVM guest. Each bit in the mask, from left to right (i.e. from most
133 an APID from 0-255. If a bit is set, the corresponding adapter is valid for
137 assigned to the KVM guest. Each bit in the mask, from left to right (i.e. from
[all …]
|