Searched +full:8 +full:- +full:way (Results 1 – 25 of 355) sorted by relevance
12345678910>>...15
| /Documentation/arch/x86/ |
| D | entry_64.rst | 1 .. SPDX-License-Identifier: GPL-2.0
16 for 64-bit, arch/x86/entry/entry_32.S for 32-bit and finally
17 arch/x86/entry/entry_64_compat.S which implements the 32-bit compatibility
18 syscall entry points and thus provides for 32-bit processes the
19 ability to execute syscalls when running on 64-bit kernels.
25 - system_call: syscall instruction from 64-bit code.
27 - entry_INT80_compat: int 0x80 from 32-bit or 64-bit code; compat syscall
28 either way.
30 - entry_INT80_compat, ia32_sysenter: syscall and sysenter from 32-bit
33 - interrupt: An array of entries. Every IDT vector that doesn't
[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
11 6 = /dev/core OBSOLETE - replaced by /proc/kcore
13 8 = /dev/random Nondeterministic random number gen.
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
67 8 = /dev/fd?h1200 5.25" 1200K in a 1200K drive(1)
[all …]
|
| /Documentation/hwmon/ |
| 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
34 * gpio_fan: int array (min = 1, max = 8)
35 List of GPIO pins (0-7) to program as fan tachs
39 -----------
[all …]
|
| D | ads7828.rst | 6 * Texas Instruments/Burr-Brown ADS7828
23 - Steve Hardy <shardy@redhat.com>
24 - Vivien Didelot <vivien.didelot@savoirfairelinux.com>
25 - Guillaume Roguez <guillaume.roguez@savoirfairelinux.com>
28 -------------
49 -----------
53 The ADS7828 device is a 12-bit 8-channel A/D converter, while the ADS7830 does
54 8-bit sampling.
56 It can operate in single ended mode (8 +ve inputs) or in differential mode,
63 There is no reliable way to identify this chip, so the driver will not scan
[all …]
|
| D | pc87427.rst | 21 -----------
24 monitoring capabilities. It can monitor up to 18 voltages, 8 fans and
36 --------------
38 Fan rotation speeds are reported as 14-bit values from a gated clock
47 -----------------
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 | aht10.rst | 1 .. SPDX-License-Identifier: GPL-2.0
16 …Chinese: http://www.aosong.com/userfiles/files/media/AHT10%E4%BA%A7%E5%93%81%E6%89%8B%E5%86%8C%20A…
27 -----------
34 ----------------
40 -----------
43 way to determine if an i2c chip is or isn't an AHT10/AHT20. The device has
45 Documentation/i2c/instantiating-devices.rst for details.
48 -------------
|
| 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.
|
| /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
27 8.Conclusion
|
| /Documentation/networking/devlink/ |
| D | devlink-region.rst | 1 .. SPDX-License-Identifier: GPL-2.0
24 Regions may also be used to provide an additional way to debug complex error
25 states, but see also Documentation/networking/devlink/devlink-health.rst
44 -------------
56 pci/0000:00:05.0/cr-space: size 1048576 snapshot [1 2] max 8
57 pci/0000:00:05.0/fw-health: size 64 snapshot [1 2] max 8
60 $ devlink region del pci/0000:00:05.0/cr-space snapshot 1
63 $ devlink region new pci/0000:00:05.0/cr-space
64 pci/0000:00:05.0/cr-space: snapshot 5
67 $ devlink region dump pci/0000:00:05.0/fw-health snapshot 1
[all …]
|
| D | devlink-linecard.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 The ``devlink-linecard`` mechanism is targeted for manipulation of
29 Similar to splitter cable, where the device might have no way
31 might not have a way to detect line card type. For that devices,
36 - Device driver would instruct the ASIC to prepare all
41 being physically connected or powered-up
44 - As on the ordinary ports, user may provision a splitter
51 * Line card is not inserted or powered-down
53 - The carrier is always down
56 - The carrier is decided as for ordinary port netdevice
[all …]
|
| /Documentation/i2c/ |
| D | smbus-protocol.rst | 46 Comm (8 bits) Command byte, a data byte which often selects a register on
48 Data (8 bits) A plain data byte. DataLow and DataHigh represent the low and
50 Count (8 bits) A data byte containing the length of a block operation.
124 available for reads where the two data bytes are the other way
158 available for writes where the two data bytes are the other way
207 SMBus Block Write - Block Read Process Call
210 SMBus Block Write - Block Read Process Call was introduced in
234 This is implemented in the following way in the Linux kernel:
241 client->irq assigned to a Host Notify IRQ if no one else specified another.
243 There is currently no way to retrieve the data parameter from the client.
[all …]
|
| /Documentation/trace/ |
| D | debugging.rst | 11 - Written for: 6.12
14 ------------
21 $ sudo mount -t tracefs tracefs /sys/kernel/tracing
25 --------------------
30 written to the tracing ring buffer in a lockless way. To make it even
33 arguments will be post processed when the ring buffer is read. This way the
57 ------------------------
77 buffers is broken up into sub-buffers that are by default PAGE_SIZE. The
79 so, on a machine with 8 CPUs, that's actually 400K total.
82 -------------------------------
[all …]
|
| D | osnoise-tracer.rst | 5 In the context of high-performance computing (HPC), the Operating System
9 system. Moreover, hardware-related jobs can also cause noise, for example,
32 source of interferences, increasing a per-cpu interference counter. The
38 hardware-related noise. In this way, osnoise can account for any
44 -----
59 # _-----=> irqs-off
60 # / _----=> need-resched
61 # | / _---=> hardirq/softirq
62 # || / _--=> preempt-depth MAX
64 … |||| RUNTIME NOISE % OF CPU NOISE +-----------------------------+
[all …]
|
| /Documentation/staging/ |
| D | crc32.rst | 5 A CRC is a long-division remainder. You add the CRC to the message,
11 protocols put the end-of-frame flag after the CRC.
15 - We're working in binary, so the digits are only 0 and 1, and
16 - When dividing polynomials, there are no carries. Rather than add and
21 To produce a 32-bit CRC, the divisor is actually a 33-bit CRC polynomial.
24 familiar with the IEEE 754 floating-point format, it's the same idea.)
28 the best error-detecting properties, this should correspond to the
29 order they're actually sent. For example, standard RS-232 serial is
30 little-endian; the most significant bit (sometimes used for parity)
38 back into range. In binary, this is easy - it has to be either 0 or 1,
[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/driver-api/ |
| D | ioctl.rst | 5 ioctl() is the most common way for applications to interface
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 …]
|
| /Documentation/admin-guide/gpio/ |
| D | gpio-mockup.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
8 This module has been obsoleted by the more flexible gpio-sim.rst.
14 The GPIO Testing Driver (gpio-mockup) provides a way to create simulated GPIO
20 --------------------------------------------
22 When loading the gpio-mockup driver a number of parameters can be passed to the
28 pairs. Each pair defines the base GPIO number (non-negative integer)
30 is -1, the gpiolib will assign it automatically. while the following
33 Example: gpio_mockup_ranges=-1,8,-1,16,405,409
35 The line above creates three chips. The first one will expose 8 lines,
44 The name format is: gpio-mockup-X-Y where X is mockup chip's ID
[all …]
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | cw2015_battery.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Tobias Schramm <t.schramm@manjaro.org>
13 The driver can utilize information from a simple-battery linked via a
14 phandle in monitored-battery. If specified the driver uses the
15 charge-full-design-microamp-hours property of the battery.
18 - $ref: power-supply.yaml#
27 cellwise,battery-profile:
30 of this binary blob is kept secret by CellWise. The only way to obtain
[all …]
|
| /Documentation/devicetree/bindings/display/ |
| D | arm,pl11x.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Liviu Dudau <Liviu.Dudau@arm.com>
11 - Andre Przywara <andre.przywara@arm.com>
24 - arm,pl110
25 - arm,pl111
27 - compatible
32 - enum:
33 - arm,pl110
[all …]
|
| /Documentation/arch/arm64/ |
| D | sve.rst | 23 -----------
26 tracked per-thread.
34 instructions and registers, and the Linux-specific system interfaces
61 cpu-feature-registers.txt for details.
70 NT_ARM_SVE regset. The recommended way of detecting support for this regset
79 an endianness-invariant layout, with bits [(8 * i + 7) : (8 * i)] encoded at
84 Beware that on big-endian systems this results in a different byte order than
85 for the FPSIMD V-registers, which are stored as single host-endian 128-bit
86 values, with bits [(127 - 8 * i) : (120 - 8 * i)] of the register encoded at
91 -----------------------------
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-usb-devices-usbsevseg | 6 A value of 0 is off and a non-zero value is on.
18 for an 8 character display the values are
26 Description: Controls the way the device interprets its text buffer.
28 hex: each character is between 0-15
29 ascii: each character is between '0'-'9' and 'A'-'F'.
|
| /Documentation/input/ |
| D | gameport-programming.rst | 34 Please also consider enabling the gameport on the card in the ->open()
35 callback if the io is mapped to ISA space - this way it'll occupy the io
37 ->close() callback. You also can select the io address in the ->open()
44 When a gameport can be accessed through MMIO, this way is preferred, because
70 the driver doesn't have to measure them the old way - an ADC is built into
86 return -(mode != GAMEPORT_MODE_COOKED);
91 gameport.fuzz = 8;
96 gameports can set this to zero, most common have fuzz between 8 and 32.
97 See analog.c and input.c for handling of fuzz - the fuzz value determines
105 examples 1+2 or 1+3. Gameports can support internal calibration - see below,
[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
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.
78 PNP0C02 "motherboard" devices are basically a catch-all. There's no
[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
36 otherwise your chance is only 1:16 to find the board :-).
38 The local memory-map is even active when mapped to $e8:
41 $0-$7e Autokonfig-space, see Z-II docs.
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-devices-system-cpu | 2 Date: 13-May-2014
8 This value is not a global default: it is a way to set
9 all per-CPU defaults at the same time.
12 What: /sys/devices/system/cpu/cpu[0-9]+/dscr
13 Date: 13-May-2014
69 Description: human-readable list of CPUs within the same core.
70 The format is like 0-3, 8-11, 14,17.
80 Description: human-readable list of CPUs sharing the same physical_package_id.
81 The format is like 0-3, 8-11, 14,17.
90 Description: per-socket protected processor inventory number
[all …]
|
12345678910>>...15