Searched +full:4 +full:- +full:way (Results 1 – 25 of 506) sorted by relevance
12345678910>>...21
| /Documentation/userspace-api/media/v4l/ |
| D | yuv-formats.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _yuv-formats:
12 *color difference* signals, this way the green component can be
16 color in a way compatible with existing receivers a new signal carrier
29 direction are possible, common factors are 1 (no subsampling), 2 and 4, with
33 - `4:4:4`: No subsampling
34 - `4:2:2`: Horizontal subsampling by 2, no vertical subsampling
35 - `4:2:0`: Horizontal subsampling by 2, vertical subsampling by 2
36 - `4:1:1`: Horizontal subsampling by 4, no vertical subsampling
37 - `4:1:0`: Horizontal subsampling by 4, vertical subsampling by 4
[all …]
|
| /Documentation/devicetree/bindings/mux/ |
| D | mux-controller.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mux/mux-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Peter Rosin <peda@axentia.se>
20 space is a simple zero-based enumeration. I.e. 0-1 for a 2-way multiplexer,
21 0-7 for an 8-way multiplexer, etc.
25 --------------------
28 specifier using the '#mux-control-cells' or '#mux-state-cells' property.
29 The value of '#mux-state-cells' will always be one greater than the value
[all …]
|
| /Documentation/networking/device_drivers/ethernet/dec/ |
| D | dmfe.rst | 1 .. SPDX-License-Identifier: GPL-2.0
26 dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
32 This way it will autodetect the device mode.This is the suggested way to load the module.Or you can…
37 insmod dmfe mode=4 # Force 10M Full Duplex
56 - Implement pci_driver::suspend() and pci_driver::resume() power management methods.
57 - Check on 64 bit boxes.
58 - Check and fix on big endian boxes.
59 - Test and make sure PCI latency is now correct for all cases.
68 - Marcelo Tosatti <marcelo@conectiva.com.br>
69 - Alan Cox <alan@lxorguk.ukuu.org.uk>
[all …]
|
| /Documentation/networking/ |
| D | nexthop-group-resilient.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Resilient Next-hop Groups
7 Resilient groups are a type of next-hop group that is aimed at minimizing
12 the legacy multipath next-hop group, which uses the hash-threshold
15 To select a next hop, hash-threshold algorithm first assigns a range of
22 +-------+-------+-------+-------+-------+
23 | 1 | 2 | 3 | 4 | 5 |
24 +-------+-+-----+---+---+-----+-+-------+
25 | 1 | 2 | 4 | 5 |
26 +---------+---------+---------+---------+
[all …]
|
| /Documentation/security/ |
| D | sak.rst | 10 is an undefeatable way of killing all programs which could be
15 providing SAK. One is the ALT-SYSRQ-K sequence. You shouldn't use
19 The proper way of generating a SAK is to define the key sequence using
28 What key sequence should you use? Well, CTRL-ALT-DEL is used to reboot
29 the machine. CTRL-ALT-BACKSPACE is magical to the X server. We'll
30 choose CTRL-ALT-PAUSE.
57 # ls -l /proc/[0-9]*/fd/* | grep console
58 l-wx------ 1 root root 64 Mar 18 00:46 /proc/579/fd/0 -> /dev/console
63 root 579 0.0 0.1 1088 436 ? S 00:43 0:00 gpm -t ps/2
83 exec 4>&1
[all …]
|
| /Documentation/process/ |
| D | development-process.rst | 8 an attempt to document how this community works in a way which is
11 there is some technical material here, this is very much a process-oriented
22 3.Early-stage
23 4.Coding
|
| /Documentation/usb/ |
| D | raw-gadget.rst | 5 USB Raw Gadget is a gadget driver that gives userspace low-level control over
33 3. Raw Gadget provides a way to select a UDC device/driver to bind to,
37 4. Raw Gadget explicitly exposes information about endpoints addresses and
38 capabilities. This allows the user to write UDC-agnostic gadgets.
40 5. Raw Gadget has an ioctl-based interface instead of a filesystem-based
46 The user can interact with Raw Gadget by opening ``/dev/raw-gadget`` and
53 1. Create a Raw Gadget instance by opening ``/dev/raw-gadget``.
56 4. In a loop issue ``USB_RAW_IOCTL_EVENT_FETCH`` to receive events from
62 Nevertheless, Raw Gadget provides a UDC-agnostic way to write USB gadgets.
71 https://github.com/xairy/raw-gadget
[all …]
|
| /Documentation/hwmon/ |
| D | adm1025.rst | 10 Addresses scanned: I2C 0x2c - 0x2e
18 Addresses scanned: I2C 0x2c - 0x2d
24 * Only two possible addresses (0x2c - 0x2d).
29 - Chen-Yuan Wu <gwu@esoft.com>,
30 - Jean Delvare <jdelvare@suse.de>
33 -----------
36 monitor for microprocessor-based systems, providing measurement and limit
39 the processor core voltage. The ADM1025 can monitor a sixth power-supply
41 remote temperature-sensing diode and an on-chip temperature sensor allows
45 different manners. It can act as the +12V power-supply voltage analog
[all …]
|
| D | pc87427.rst | 21 -----------
28 This chip also has fan controlling features (up to 4 PWM outputs),
36 --------------
38 Fan rotation speeds are reported as 14-bit values from a gated clock
47 -----------------
49 Fan speed can be controlled by PWM outputs. There are 4 possible modes:
56 ----------------------
60 connected. The integer part can be 8-bit or 9-bit, and can be signed or
61 not. I couldn't find a way to figure out the external sensor data
62 temperature format, so user-space adjustment (typically by a factor 2)
|
| D | sch5627.rst | 18 -----------
21 capabilities. They can monitor up to 5 voltages, 4 fans and 8 temperatures.
39 ---------------------
45 In which way the value of fanX_min affects the fan speed is currently unknown.
|
| D | adm1026.rst | 16 - Philip Pokorny <ppokorny@penguincomputing.com> for Penguin Computing
17 - Justin Thiessen <jthiessen@penguincomputing.com>
20 -----------------
23 List of GPIO pins (0-16) to program as inputs
26 List of GPIO pins (0-16) to program as outputs
29 List of GPIO pins (0-16) to program as inverted
32 List of GPIO pins (0-16) to program as normal/non-inverted
35 List of GPIO pins (0-7) to program as fan tachs
39 -----------
45 16 general purpose digital I/O lines, eight (8) fan speed sensors (8-bit),
[all …]
|
| /Documentation/admin-guide/ |
| D | devices.txt | 1 0 Unnamed devices (e.g. non-device mounts)
7 2 = /dev/kmem OBSOLETE - replaced by /proc/kcore
9 4 = /dev/port I/O port access
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
61 4 = /dev/fd?d360 5.25" 360K in a 360K drive(1)
[all …]
|
| /Documentation/arch/m68k/ |
| D | buddha-driver.rst | 8 ------------------------------------------------------------------------
11 Buddha-part of the Catweasel Zorro-II version
21 product number: 0 (42 for Catweasel Z-II)
23 Rom-vector: $1000
25 The card should be a Z-II board, size 64K, not for freemem
26 list, Rom-Vektor is valid, no second Autoconfig-board on the
30 as the Amiga Kickstart does: The lower nibble of the 8-Bit
31 address is written to $4a, then the whole Byte is written to
32 $48, while it doesn't matter how often you're writing to $4a
35 address just written. Make sure $4a is written before $48,
[all …]
|
| /Documentation/PCI/ |
| D | acpi-info.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 OS might use unless there's another way for the OS to find it [1, 2].
39 If the OS is expected to manage a non-discoverable device described via
50 These are all device-specific, non-architected things, so the only way a
52 the device-specific details. The host bridge registers also include ECAM
56 ("Consumer") from the bridge apertures ("Producer") [4, 5], but early
64 Consumer/Producer meant there was no way to describe bridge registers in
66 bridge registers (including ECAM space) in PNP0C02 catch-all devices [6].
67 With the exception of ECAM, the bridge register space is device-specific
76 describe bridge registers this way on those architectures.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-lefi-boardinfo | 20 Board Name : LEMOTE-LS3A4000-7A1000-1w-V01-pc
25 Version : Kunlun-A1901-V4.1.3-20200414093938
26 ROM Size : 4 KB
27 Release Date : 2020-04-14
29 By the way, using dmidecode command can get the similar info if there
|
| /Documentation/core-api/ |
| D | printk-basics.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 standard tool we have for printing messages and usually the most basic way of
12 - printk() messages can specify a log level.
14 - the format string, while largely compatible with C99, doesn't follow the
17 printk format specifiers right <printk-specifiers>`.
20 buffer exported to userspace through /dev/kmsg. The usual way to read it is
30 +----------------+--------+-----------------------------------------------+
34 +----------------+--------+-----------------------------------------------+
36 +----------------+--------+-----------------------------------------------+
38 +----------------+--------+-----------------------------------------------+
[all …]
|
| D | unaligned-memory-access.rst | 24 For example, reading 4 bytes of data from address 0x10004 is fine, but
25 reading 4 bytes of data from address 0x10005 would be an unaligned memory
32 which will compile to multiple-byte memory access instructions, namely when
48 writing code that satisfies natural alignment requirements is the easiest way
59 - Some architectures are able to perform unaligned memory accesses
61 - Some architectures raise processor exceptions when unaligned accesses
64 - Some architectures raise processor exceptions when unaligned accesses
67 - Some architectures are not capable of unaligned memory access, but will
98 by 4 (remember, we're reading a 4 byte value here).
131 structure type. This GCC-specific attribute tells the compiler never to
[all …]
|
| /Documentation/filesystems/ |
| D | inotify.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Inotify - A Powerful yet Simple File Change Notification System
11 Document updated 4 Jan 2015 by Zhang Zhen <zhenzhang.zhang@huawei.com>
13 - Deleted obsoleted interface, just refer to manpages for user interface.
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/arch/arm/ |
| D | interrupts.rst | 5 2.5.2-rmk5:
7 major architecture-specific subsystems.
9 Firstly, it contains some pretty major changes to the way we handle the
10 MMU TLB. Each MMU TLB variant is now handled completely separately -
18 The 2.5 kernels will be having major changes to the way IRQs are handled.
26 SA1100 ------------> Neponset -----------> SA1111
28 -----------> USAR
30 -----------> SMC9196
32 The way stuff currently works, all SA1111 interrupts are mutually
33 exclusive of each other - if you're processing one interrupt from the
[all …]
|
| /Documentation/virt/kvm/ |
| D | ppc-pv.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 space code in PR=1 which is user space. This way we trap all privileged
35 'hypercall-instructions'. This property contains at most 4 opcodes that make
43 r0 - volatile
47 r6 4th parameter 3rd output value
48 r7 5th parameter 4th output value
53 r12 - volatile
80 applicable to the target. For now, we always map the page to -4096. This way we
84 ld rX, -4096(0)
133 - MSR_EE
[all …]
|
| /Documentation/scheduler/ |
| D | sched-eevdf.rst | 9 of EEVDF proposed by Peter Zijlstra in 2023 [2-4]. More information
11 Documentation/scheduler/sched-design-CFS.rst.
16 whether a task has received its fair share of CPU time. In this way, a task
21 allows latency-sensitive tasks with shorter time slices to be prioritized,
29 lag to decay over VRT. Hence, long-sleeping tasks eventually have their lag
32 which further facilitates the job of latency-sensitive applications.
39 [2] https://lore.kernel.org/lkml/a79014e6-ea83-b316-1e12-2ae056bda6fa@linux.vnet.ibm.com/
43 [4] https://lwn.net/Articles/925371/
|
| /Documentation/power/ |
| D | s2ram.rst | 22 debugging - the thing that Chuck tried to disable. That's often the _only_
23 way to debug these things, and it's actually pretty powerful (but
24 time-consuming - having to insert TRACE_RESUME() markers into the device
27 Anyway, the way to debug this for people who are interested (have a
30 - enable PM_DEBUG, and PM_TRACE
32 - use a script like this::
41 - if it doesn't come back up (which is usually the problem), reboot by
45 Magic number: 4:156:725
63 that "radeonfb" simply cannot resume that device - it tries to set the
76 ordering-sensitive bugs).
[all …]
|
| /Documentation/dev-tools/kunit/api/ |
| D | functionredirection.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 stability of the rest of the system (making it less likely for test-specific
22 This coupling is often due to global state in some way: be it a global list of
32 A simpler way to intercept and replace some of the function calls is to use
39 Static stubs are a way of redirecting calls to one function (the "real"
57 .. code-block:: c
68 In the event they need to access or modify test-specific state, they can use
75 .. code-block:: c
93 .. code-block:: c
99 4. Call (perhaps indirectly) the real function.
[all …]
|
| /Documentation/driver-api/ |
| D | switchtec.rst | 23 through the Memory-mapped Remote Procedure Call (MRPC) interface.
24 Commands are submitted to the interface with a 4-byte command
26 respond with a 4-byte return code and up to 1KB of command-specific
38 * A write must consist of at least 4 bytes and no more than 1028 bytes.
39 The first 4 bytes will be interpreted as the Command ID and the
48 the 4-byte Command Return Value plus up to 1024 bytes of output
50 call -- reading less than 4 bytes will produce an error.)
57 * SWITCHTEC_IOCTL_FLASH_INFO - Retrieve firmware length and number
60 * SWITCHTEC_IOCTL_FLASH_PART_INFO - Retrieve address and lengeth for
63 * SWITCHTEC_IOCTL_EVENT_SUMMARY - Read a structure of bitmaps
[all …]
|
| /Documentation/hid/ |
| D | hidreport-parsing.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 $ hexdump -C /sys/bus/hid/devices/0003\:093A\:2510.0002/report_descriptor
20 length of the item, 2 bits for the type of the item and 4 bits for the
23 +----------+
25 +----------+
27 ---- Length of data (see HID spec 6.2.2.2)
29 ------ Type of the item (see HID spec 6.2.2.2, then jump to 6.2.2.7)
31 --------- Function of the item (see HID spec 6.2.2.7, then HUT Sec 3)
46 we have a ``Usage``. From HUT, Sec. 4, "Generic Desktop Page", we see that
49 The following numbers can be parsed in the same way.
|
12345678910>>...21