Searched +full:3 +full:a (Results 1 – 25 of 1144) sorted by relevance
12345678910>>...46
| /Documentation/networking/device_drivers/ethernet/3com/ |
| D | vortex.rst | 4 3Com Vortex device driver
12 This document describes the usage and errata of the 3Com "Vortex" device
13 driver for Linux, 3c59x.c.
29 3c575-series Cardbus cards which used to be handled by 3c575_cb.c.
33 - 3c590 Vortex 10Mbps
34 - 3c592 EISA 10Mbps Demon/Vortex
35 - 3c597 EISA Fast Demon/Vortex
36 - 3c595 Vortex 100baseTx
37 - 3c595 Vortex 100baseT4
38 - 3c595 Vortex 100base-MII
[all …]
|
| D | 3c509.rst | 4 Linux and the 3Com EtherLink III Series Ethercards (driver v1.18c and higher)
8 of the 3c509 driver. You should not use the driver without reading this file.
20 The following are notes and information on using the 3Com EtherLink III series
22 card's 3Com model number, 3c509. They are all 10mb/s ISA-bus cards and shouldn't
23 be (but sometimes are) confused with the similarly-numbered PCI-bus "3c905"
24 (aka "Vortex" or "Boomerang") series. Kernel support for the 3c509 family is
25 provided by the module 3c509.c, which has code to support all of the following
28 - 3c509 (original ISA card)
29 - 3c509B (later revision of the ISA card; supports full-duplex)
30 - 3c589 (PCMCIA)
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-rgb.rst | 9 These formats encode each pixel as a triplet of RGB values. They are packed
12 bits required to store a pixel is not aligned to a byte boundary, the data is
20 or a permutation thereof, collectively referred to as alpha formats) depend on
24 a meaningful value. Otherwise, when the device doesn't capture an alpha channel
25 but can set the alpha bit to a user-configurable value, the
28 the value specified by that control. Otherwise a corresponding format without
34 filled with meaningful values by applications. Otherwise a corresponding format
38 Formats that contain padding bits are named XRGB (or a permutation thereof).
44 - In all the tables that follow, bit 7 is the most significant bit in a byte.
46 respectively. 'a' denotes bits of the alpha component (if supported by the
[all …]
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | devices.rst | 8 Implement a cgroup to track and enforce open and mknod restrictions
9 on device files. A device cgroup associates a device access
10 whitelist with each cgroup. A whitelist entry has 4 fields.
11 'type' is a (all), c (char), or b (block). 'all' means it applies
13 either an integer or * for all. Access is a composition of r
16 The root device cgroup starts with rwm to 'all'. A child device
17 cgroup gets a copy of the parent. Administrators can then remove
18 devices from the whitelist or add new entries. A child cgroup can
19 never receive a device access which is denied by its parent.
27 echo 'c 1:3 mr' > /sys/fs/cgroup/1/devices.allow
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-class-tpm | 5 Description: The device/ directory under a specific TPM instance exposes
13 Description: The "active" property prints a '1' if the TPM chip is accepting
16 visible to the OS, but will only accept a restricted set of
41 Manufacturer is a hex dump of the 4 byte manufacturer info
42 space in a TPM. TCG version shows the TCG TPM spec level that
50 Description: The "durations" property shows the 3 vendor-specific values
51 used to wait for a short, medium and long TPM command. All
54 any longer than necessary before starting to poll for a
64 Durations can be modified in the case where a buggy chip
73 Description: The "enabled" property prints a '1' if the TPM chip is enabled,
[all …]
|
| /Documentation/admin-guide/thermal/ |
| D | intel_powerclamp.rst | 34 Consider the situation where a system’s power consumption must be
70 If the kernel can also inject idle time to the system, then a
72 level C-state. The intel_powerclamp driver is conceived as such a
73 control system, where the target set point is a user-selected idle
84 of jiffies, so accumulated errors can be prevented to avoid a jittery
92 values. This effect can be better visualized using a Perf timechart.
95 for a given "duration", then relinquishes the CPU to other tasks,
100 have a dramatic impact on the effectiveness of the powerclamp driver
121 this document. The controlling CPU is elected at runtime, with a
122 policy that favors BSP, taking into account the possibility of a CPU
[all …]
|
| /Documentation/usb/ |
| D | iuu_phoenix.rst | 8 This module provide a serial interface to use your
10 bring a ttyUSB[0-x] interface. This driver must be
15 I never had any problem with it, but I'm not a real
26 A few parameters can be used at load time
34 modprobe iuu_phoenix clockmode=3
39 1=3Mhz579,2=3Mhz680,3=6Mhz (int)
44 0=none, 1=CD, 2=!CD, 3=DSR, 4=!DSR, 5=CTS, 6=!CTS, 7=RING, 8=!RING (int)
50 - clockmode will provide 3 different base settings commonly adopted by
53 1. 3Mhz579
54 2. 3Mhz680
[all …]
|
| /Documentation/input/devices/ |
| D | elantech.rst | 17 3. Differentiating hardware versions
27 5.2.3 Two finger touch
28 6. Hardware version 3
38 7.2.3 Motion packet
39 8. Trackpoint (for Hardware version 3 and 4)
50 hardware versions unimaginatively called version 1,version 2, version 3
54 and width of the touch. Hardware version 3 uses 6 bytes per packet (and
56 of up to 3 fingers. Hardware version 4 uses 6 bytes per packet, and can
57 combine a status packet with multiple head or motion packets. Hardware version
60 Some Hardware version 3 and version 4 also have a trackpoint which uses a
[all …]
|
| D | alps.rst | 8 ALPS touchpads, called versions 1, 2, 3, 4, 5, 6, 7 and 8.
11 integrated into a variety of laptops and netbooks. These new touchpads
23 (Compatibility ID) definition as a way to uniquely identify the
24 different ALPS variants but there did not appear to be a 1:1 mapping.
32 E8-E6-E6-E6-E9. An ALPS touchpad should respond with either 00-00-0A or
40 For older touchpads supporting protocol versions 3 and 4, the E7 report
45 The new ALPS touchpads have an E7 signature of 73-03-50 or 73-03-0A but
51 Protocol versions 3 and 4 have a command mode that is used to read and write
52 one-byte device registers in a 16-bit address space. The command sequence
54 with 88-07 followed by a third byte. This third byte can be used to determine
[all …]
|
| /Documentation/admin-guide/media/ |
| D | dvb_intro.rst | 17 video) is an analogue encoding of a sequence of image frames (25 frames
20 Analogue TV card for a PC has the following purpose:
22 * Tune the receiver to receive a broadcast signal
29 some countries employ a digital audio signal
37 circuitry on the card and is often presented uncompressed. For a PAL TV
38 signal encoded at a resolution of 768x576 24-bit color pixels over 25
39 frames per second - a fair amount of data is generated and must be
46 The purpose of a simple budget digital TV card (DVB-T,C or S) is to
49 * Tune the received to receive a broadcast signal. * Extract the encoded
55 digital TV card spits out a compressed encoded digital datastream. As
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | fsl,imx6q-pinctrl.txt | 8 - fsl,pins: two integers array, represents a group of pins mux and config
9 setting. The format is fsl,pins = <PIN_FUNC_ID CONFIG>, PIN_FUNC_ID is a
10 pin working on a specific function, CONFIG is the pad setting value like
19 PAD_CTL_PUS_22K_UP (3 << 14)
25 PAD_CTL_SPEED_HIGH (3 << 6)
26 PAD_CTL_DSE_DISABLE (0 << 3)
27 PAD_CTL_DSE_240ohm (1 << 3)
28 PAD_CTL_DSE_120ohm (2 << 3)
29 PAD_CTL_DSE_80ohm (3 << 3)
30 PAD_CTL_DSE_60ohm (4 << 3)
[all …]
|
| D | fsl,imx6dl-pinctrl.txt | 8 - fsl,pins: two integers array, represents a group of pins mux and config
9 setting. The format is fsl,pins = <PIN_FUNC_ID CONFIG>, PIN_FUNC_ID is a
10 pin working on a specific function, CONFIG is the pad setting value like
19 PAD_CTL_PUS_22K_UP (3 << 14)
25 PAD_CTL_SPEED_HIGH (3 << 6)
26 PAD_CTL_DSE_DISABLE (0 << 3)
27 PAD_CTL_DSE_240ohm (1 << 3)
28 PAD_CTL_DSE_120ohm (2 << 3)
29 PAD_CTL_DSE_80ohm (3 << 3)
30 PAD_CTL_DSE_60ohm (4 << 3)
[all …]
|
| D | fsl,imx6sl-pinctrl.txt | 8 - fsl,pins: two integers array, represents a group of pins mux and config
9 setting. The format is fsl,pins = <PIN_FUNC_ID CONFIG>, PIN_FUNC_ID is a
10 pin working on a specific function, CONFIG is the pad setting value like
20 PAD_CTL_PUS_22K_UP (3 << 14)
26 PAD_CTL_SPEED_HIGH (3 << 6)
27 PAD_CTL_DSE_DISABLE (0 << 3)
28 PAD_CTL_DSE_240ohm (1 << 3)
29 PAD_CTL_DSE_120ohm (2 << 3)
30 PAD_CTL_DSE_80ohm (3 << 3)
31 PAD_CTL_DSE_60ohm (4 << 3)
[all …]
|
| /Documentation/driver-api/usb/ |
| D | usb3-debug-port.rst | 11 This is a HOWTO for using the USB3 debug port on x86 systems.
19 3) have a USB 3.0 super-speed A-to-A debugging cable.
28 When DbC is initialized and enabled, it will present a debug
31 the USB framework and provides the equivalent of a very high
33 (the system under debugging) and a debug host.
41 Other uses include simpler, lockless logging instead of a full-
44 On the debug target system, you need to customize a debugging
51 append a host controller index to this kernel parameter. This
61 port to a USB port (root port or port of any external hub) on
63 should be a USB 3.0 super-speed A-to-A debugging cable.
[all …]
|
| /Documentation/trace/ |
| D | ftrace.rst | 27 is really a framework of several assorted tracing utilities.
29 disabled and enabled, as well as for preemption and from a time
30 a task is woken to the task is actually scheduled in.
62 For quicker access to that directory you may want to make a soft link to
90 of ftrace. Here is a list of some of the key files:
127 This file holds the output of the trace in a human
130 Note, this file is not a consumer. If tracing is off
141 retrieved. Unlike the "trace" file, this file is a
145 will not be read again with a sequential read. The
154 files. Options also exist to modify how a tracer
[all …]
|
| /Documentation/driver-api/cxl/ |
| D | maturity-map.rst | 14 <https://lore.kernel.org/linux-cxl/?q=s%3APULL+s%3ACXL+tc%3Atorvalds+NOT+s%3ARe>`_,
15 those do not always convey progress relative to a starting point and a
18 What follows is a coarse breakdown of the subsystem's major
19 responsibilities along with a maturity score. The expectation is that
25 - [3] Mature: Work in this area is complete and no changes on the horizon.
30 mature, but known corner cases are still a work in progress.
36 - [0] Known gap: Feature is on a medium to long term horizon to
37 implement. If the specification has a feature that does not even have
38 a '0' score in this document, there is a good chance that no one in
68 * [3] Endpoint CDAT
[all …]
|
| /Documentation/staging/ |
| D | lzo.rst | 8 This is not a specification. No specification seems to be publicly available
20 The stream is composed of a series of instructions, operands, and data. The
21 instructions consist in a few bits representing an opcode, and bits forming
26 - a distance when copying data from the dictionary (past output buffer)
27 - a length (number of bytes to copy from dictionary)
29 as a piece of information for next instructions.
32 extra data can be a complement for the operand (eg: a length or a distance
33 encoded on larger values), or a literal to be copied to the output buffer.
35 The first byte of the block follows a different encoding from other bytes, it
39 Lengths are always encoded on a variable size starting with a small number
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | mdio-mux-gpio.yaml | 13 This is a special case of a MDIO bus multiplexer. One or more GPIO
38 An NXP sn74cbtlv3253 dual 1-of-4 switch controlled by a
39 pair of GPIO lines. Child busses 2 and 3 populated with 4
44 gpios = <&gpio1 3 0>, <&gpio1 4 0>;
56 marvell,reg-init = <3 0x10 0 0x5777>,
57 <3 0x11 0 0x00aa>,
58 <3 0x12 0 0x4105>,
59 <3 0x13 0 0x0a60>;
65 marvell,reg-init = <3 0x10 0 0x5777>,
66 <3 0x11 0 0x00aa>,
[all …]
|
| /Documentation/core-api/ |
| D | packing.rst | 10 One can memory-map a pointer to a carefully crafted struct over the hardware
20 A more robust alternative to struct field definitions would be to extract the
34 - Packing a CPU-usable number into a memory buffer (with hardware
36 - Unpacking a memory buffer (which has hardware constraints/quirks)
37 into a CPU-usable number.
47 The following examples cover the memory layout of a packed u64 field.
57 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
58 3 2 1 0
73 24 25 26 27 28 29 30 31 16 17 18 19 20 21 22 23 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7
74 3 2 1 0
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | brcm,iproc-clocks.yaml | 19 ASIU clocks are a special case. These clocks are derived directly from the
60 most iProc PLLs, this is an onboard crystal with a fixed rate.
109 crystal N/A N/A N/A
111 armpll crystal N/A N/A
120 ihost_sys genpll 3 BCM_CYGNUS_GENPLL_IHOST_SYS_CLK
128 sdio lcpll0 3 BCM_CYGNUS_LCPLL0_SDIO_CLK
136 ch2_v3d mipipll 3 BCM_CYGNUS_MIPIPLL_CH2_V3D
144 ch2_audio audiopll 3 BCM_CYGNUS_AUDIOPLL_CH2
159 crystal N/A N/A N/A
161 armpll crystal N/A N/A
[all …]
|
| /Documentation/devicetree/bindings/pci/ |
| D | intel,ixp4xx-pci.yaml | 74 #address-cells = <3>;
88 <0x0800 0 0 1 &gpio0 11 3>, /* INT A on slot 1 is irq 11 */
89 <0x0800 0 0 2 &gpio0 10 3>, /* INT B on slot 1 is irq 10 */
90 <0x0800 0 0 3 &gpio0 9 3>, /* INT C on slot 1 is irq 9 */
91 <0x0800 0 0 4 &gpio0 8 3>, /* INT D on slot 1 is irq 8 */
92 <0x1000 0 0 1 &gpio0 10 3>, /* INT A on slot 2 is irq 10 */
93 <0x1000 0 0 2 &gpio0 9 3>, /* INT B on slot 2 is irq 9 */
94 <0x1000 0 0 3 &gpio0 8 3>, /* INT C on slot 2 is irq 8 */
95 <0x1000 0 0 4 &gpio0 11 3>, /* INT D on slot 2 is irq 11 */
96 <0x1800 0 0 1 &gpio0 9 3>, /* INT A on slot 3 is irq 9 */
[all …]
|
| /Documentation/hwmon/ |
| D | lt7182s.rst | 22 LT7182S is a Dual Channel 6A, 20V PolyPhase Step-Down Silent Switcher with
32 Example: the following commands will load the driver for a LT7182S
50 curr[3-4]_label "iout[1-2]"
51 curr[3-4]_input Measured output current
52 curr[3-4]_highest Highest measured output current
53 curr[3-4]_max Maximum output current
54 curr[3-4]_max_alarm Output current high alarm
67 in[3-5]_label "vmon[1-3]"
68 in[3-5]_input Measured voltage on ITH1/ITH2/EXTVCC pins
72 in[3-4|6-7]_label "vout[1-2]"
[all …]
|
| D | dme1737.rst | 63 and SCH5127 Super-I/O chips. These chips feature monitoring of 3 temp sensors
64 temp[1-3] (2 remote diodes and 1 internal), 8 voltages in[0-7] (7 external and
66 up to 5 PWM outputs pwm[1-3,5-6] for controlling fan speeds both manually and
70 Fan[3-6] and pwm[3,5-6] are optional features and their availability depends on
74 For the SCH311x and SCH5127, fan[1-3] and pwm[1-3] are always present and
80 if it detects a DME1737, A8000, or SCH5027 and as a platform driver if it
81 detects a SCH311x or SCH5127 chip.
95 in1: Vccp (processor core) 0V - 3V
115 in1: Vccp (processor core) 0V - 3V
125 in1: Vccp (processor core) 0V - 3V
[all …]
|
| /Documentation/arch/powerpc/ |
| D | vcpudispatch_stats.rst | 7 For Shared Processor LPARs, the POWER Hypervisor maintains a relatively
11 scenarios, vcpus may be dispatched on a different processor chip (away
17 By default, the DTLB log for each vcpu is processed 50 times a second so
23 a vcpu as represented by the first field, followed by 8 numbers.
33 3. number of times this vcpu was dispatched on a different processor core
35 4. number of times this vcpu was dispatched on a different chip
36 5. number of times this vcpu was dispatches on a different socket/drawer
39 The final 3 numbers represent statistics in relation to the home node of
43 7. number of times this vcpu was dispatched in a different node
44 8. number of times this vcpu was dispatched in a node further away (numa
[all …]
|
| /Documentation/devicetree/bindings/ |
| D | numa.txt | 9 Systems employing a Non Uniform Memory Access (NUMA) architecture contain
11 that comprise what is commonly known as a NUMA node.
21 For the purpose of identification, each NUMA node is associated with a unique
22 token known as a node id. For the purpose of this binding
23 a node id is a 32-bit integer.
25 A device node is associated with a NUMA node by the presence of a
36 3 - distance-map
45 This property defines a matrix to describe the relative distances
47 It is represented as a list of node pairs and their relative distance.
52 2. The distance from a node to self (local distance) is represented
[all …]
|
12345678910>>...46