Searched +full:left +full:- +full:most (Results 1 – 25 of 172) sorted by relevance
1234567
| /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
47 to the left.
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.
[all …]
|
| /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>
18 - $ref: input.yaml#
22 const: adc-joystick
24 io-channels:
31 https://github.com/devicetree-org/dt-schema/blob/master/schemas/iio/iio-consumer.yaml
[all …]
|
| /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:
45 -- Backed by busy-wait loop:
49 -- Backed by hrtimers:
[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/devicetree/bindings/interrupt-controller/ |
| D | brcm,bcm7038-l1-intc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interrupt-controller/brcm,bcm7038-l1-intc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Broadcom BCM7038-style Level 1 interrupt controller
11 directly to one of the HW INT lines on each CPU. Every BCM7xxx set-top chip
16 - 64, 96, 128, or 160 incoming level IRQ lines
18 - Most onchip peripherals are wired directly to an L1 input
20 - A separate instance of the register set for each CPU, allowing individual
23 - Atomic mask/unmask operations
[all …]
|
| /Documentation/driver-api/ |
| D | sm501.rst | 15 ----
29 The core re-uses the platform device system as the platform device
31 need to create a new bus-type and the associated code to go with it.
35 ---------
43 as this is by-far the most resource-sensitive of the on-chip functions.
53 of it. Any memory left over in the middle is used for the acceleration
59 -------------
69 There is an errata (AB-5) affecting the selection of the
|
| /Documentation/userspace-api/media/v4l/ |
| D | selection-api-examples.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
14 .. code-block:: c
22 exit(-1);
26 exit(-1);
28 Setting a composing area on output of size of *at most* half of limit
34 .. code-block:: c
44 exit(-1);
48 r.left = sel.r.width / 4;
55 exit(-1);
63 .. code-block:: c
[all …]
|
| /Documentation/sound/hd-audio/ |
| D | realtek-pc-beep.rst | 20 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
24 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
33 Amplify 1Ah loopback, left (L): 1 bit
34 Amplify the left channel of 1Ah before mixing it into outputs as specified
58 +--DIV--+--!DIV--+ {1Ah boost control}
60 +--(b == 0)--+--(b != 0)--+
70 +-----!h-----+-----S-----+
79 All Realtek HDA codecs have a vendor-defined widget with node ID 20h which
87 Realtek, is of note: unlike most registers, which seem to control detailed
111 Linux, it seems, has gone through most of them. For one, the register resets
[all …]
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux-reg.txt | 1 Register-based I2C Bus Mux
7 - compatible: i2c-mux-reg
8 - i2c-parent: The phandle of the I2C bus that this multiplexer's master-side
10 * Standard I2C mux properties. See i2c-mux.yaml in this directory.
11 * I2C child bus nodes. See i2c-mux.yaml in this directory.
14 - reg: this pair of <offset size> specifies the register to control the mux.
15 The <offset size> depends on its parent node. It can be any memory-mapped
18 - little-endian: The existence indicates the register is in little endian.
19 - big-endian: The existence indicates the register is in big endian.
20 If both little-endian and big-endian are omitted, the endianness of the
[all …]
|
| D | i2c-mux-pinctrl.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/i2c/i2c-mux-pinctrl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Pinctrl-based I2C Bus Mux
10 - Wolfram Sang <wsa@kernel.org>
17 +-----+ +-----+
19 +------------------------+ +-----+ +-----+
21 | /----|------+--------+
22 | +---+ +------+ | child bus A, on first set of pins
[all …]
|
| D | i2c-mux-gpio.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/i2c/i2c-mux-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: GPIO-based I2C Bus Mux
10 - Wolfram Sang <wsa@kernel.org>
15 +-----+ +-----+
17 +------------+ +-----+ +-----+
19 | | /--------+--------+
20 | +------+ | +------+ child bus A, on GPIO value set to 0
[all …]
|
| /Documentation/devicetree/bindings/opp/ |
| D | opp-v2-base.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/opp/opp-v2-base.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Viresh Kumar <viresh.kumar@linaro.org>
13 Devices work at voltage-current-frequency combinations and some implementations
25 pattern: '^opp-table(-[a-z0-9]+)?$'
27 opp-shared:
36 '^opp(-?[0-9]+)*$':
39 One or more OPP nodes describing voltage-current-frequency combinations.
[all …]
|
| /Documentation/hwmon/ |
| D | lm63.rst | 45 -----------
53 - No low limit for local temperature.
54 - No critical limit for local temperature.
55 - Critical limit for remote temperature can be changed only once. We
56 will consider that the critical limit is read-only.
66 The fan speed is measured using a tachometer. Contrary to most chips which
67 store the value in an 8-bit register and have a selectable clock divider
68 to make sure that the result will fit in the register, the LM63 uses 16-bit
75 is left to the BIOS, and the driver will blindly trust it. Only the original
|
| /Documentation/locking/ |
| D | robust-futexes.rst | 8 ----------
15 A futex is in essence a user-space address, e.g. a 32-bit lock variable
21 waiter with the waker - without them having to know about each other.
26 state, and there's no in-kernel state associated with it. The kernel
33 pthread_mutex_t, or yum is kill -9-ed), then waiters for that lock need
39 prematurely - and the new owner can decide whether the data protected by
45 (and in most cases there is none, futexes being fast lightweight locks)
47 Userspace has no chance to clean up after the lock either - userspace is
48 the one that crashes, so it has no opportunity to clean up. Catch-22.
50 In practice, when e.g. yum is kill -9-ed (or segfaults), a system reboot
[all …]
|
| /Documentation/fb/ |
| D | framebuffer.rst | 9 ---------------
13 software to access the graphics hardware through a well-defined interface, so
14 the software doesn't need to know anything about the low-level (hardware
22 --------------------------
39 /dev/fb0current -> fb0
40 /dev/fb1current -> fb1
50 graphics card in addition to the built-in hardware. The corresponding frame
69 --------------------------------
82 - You can request unchangeable information about the hardware, like name,
86 - You can request and change variable information about the hardware, like
[all …]
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | panel-common.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/display/panel/panel-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
24 width-mm:
29 height-mm:
43 non-descriptive information. For instance an LCD panel in a system that
55 panel-timing:
[all …]
|
| /Documentation/filesystems/iomap/ |
| D | porting.rst | 1 .. SPDX-License-Identifier: GPL-2.0
27 This worked well enough for direct/indirect-mapped filesystems such
28 as ext2, but is very inefficient for extent-based filesystems such
34 3. Direct access to storage on memory-like devices (fsdax) is only
40 No ->write_begin(), ->write_end() or direct_IO
49 Build the kernel, run fstests with the ``-g all`` option across a wide
53 The recommended approach is first to implement ``->iomap_begin`` (and
54 ``->iomap_end`` if necessary) to allow iomap to obtain a read-only
56 In most cases, this is a relatively trivial conversion of the existing
57 ``get_block()`` function for read-only mappings.
[all …]
|
| /Documentation/input/devices/ |
| D | joystick-parport.rst | 3 .. _joystick-parport:
9 :Copyright: |copy| 1998-2000 Vojtech Pavlik <vojtech@ucw.cz>
10 :Copyright: |copy| 1998 Andree Borrmann <a.borrmann@tu-bs.de>
18 Any information in this file is provided as-is, without any guarantee that
30 both output and input bits is the most suitable port on the PC for
36 Many console and 8-bit computer gamepads and joysticks are supported. The
40 ------------
59 for your pads, use either keyboard or joystick port, and make a pass-through
64 some data pin. For most gamepad and parport implementations only one pin is
69 (pin 9) -----> Power
[all …]
|
| D | yealink.rst | 2 Driver documentation for yealink usb-p1k phones
10 - keyboard full support, yealink.ko / input event API
11 - LCD full support, yealink.ko / sysfs API
12 - LED full support, yealink.ko / sysfs API
13 - dialtone full support, yealink.ko / sysfs API
14 - ringtone full support, yealink.ko / sysfs API
15 - audio playback full support, snd_usb_audio.ko / alsa API
16 - audio record full support, snd_usb_audio.ko / alsa API
27 Physical USB-P1K button layout input events
31 IN OUT left, right
[all …]
|
| /Documentation/maintainer/ |
| D | feature-and-driver-maintainers.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 Unlike most of the chapter, this section is meant for the latter (more
15 Drivers and alike most often do not have their own mailing lists and
36 may range from two working days for fast-paced subsystems (e.g. networking)
40 --------------------------
43 Maintainers must be subscribed and follow the appropriate subsystem-wide
46 `lei <https://people.kernel.org/monsieuricon/lore-lei-part-1-getting-started>`_.
52 -------
56 multiple drivers - whether to provide a review is left to the maintainer.
58 When there are multiple maintainers for a piece of code an ``Acked-by``
[all …]
|
| /Documentation/driver-api/thermal/ |
| D | cpu-cooling-api.rst | 15 to the caller. The binding of the cooling devices to the trip point is left for
22 --------------------------------------------
30 "thermal-cpufreq-%x". This api can support multiple instances of cpufreq
42 the name "thermal-cpufreq-%x" linking it with a device tree node, in
54 This interface function unregisters the "thermal-cpufreq-%x" cooling device.
63 supported currently). This power model requires that the operating-points of
73 - The time the processor spends running, consuming dynamic power, as
76 - The voltage and frequency levels as a result of DVFS. The DVFS
78 - In running time the 'execution' behaviour (instruction types, memory
79 access patterns and so forth) causes, in most cases, a second order
[all …]
|
| /Documentation/core-api/ |
| D | rbtree.rst | 2 Red-black Trees (rbtree) in Linux
9 What are red-black trees, and what are they for?
10 ------------------------------------------------
12 Red-black trees are a type of self-balancing binary search tree, used for
19 Red-black trees are similar to AVL trees, but provide faster real-time bounded
20 worst case performance for insertion and deletion (at most two rotations and
26 There are a number of red-black trees in use in the kernel.
29 The high-resolution timer code uses an rbtree to organize outstanding
31 red-black tree. Virtual memory areas (VMAs) are tracked with red-black
38 Linux Weekly News article on red-black trees
[all …]
|
| /Documentation/power/ |
| D | power_supply_class.rst | 8 properties to user-space.
60 +--------------------------------------------------------------------------+
61 | **Charge/Energy/Capacity - how to not confuse** |
62 +--------------------------------------------------------------------------+
66 | - `CHARGE_*` |
68 | - `ENERGY_*` |
70 | - `CAPACITY` |
72 +--------------------------------------------------------------------------+
142 relative, time-based measurements.
210 seconds left for battery to be considered empty
[all …]
|
| /Documentation/networking/ |
| D | net_dim.rst | 2 Net DIM - Generic Network Dynamic Interrupt Moderation
43 #. Makes a decision - suggests interrupt moderation configuration fields.
52 compared in a similar fashion - increase == "better" and decrease == "worse".
63 the algorithm: is it going left (reducing moderation), right (increasing
67 "parking" on one of the most left or most right decisions, the algorithm may
105 interrupt. Since Net DIM has a built-in moderation and it might decide to skip
129 .. code-block:: c
143 dim->state = DIM_START_MEASURE;
154 dim_update_sample(my_entity->events,
155 my_entity->packets,
[all …]
|
1234567