| /Documentation/hwmon/ |
| D | drivetemp.rst | 27 the current drive temperature and, if available, temperature limits
30 the drive temperature.
36 Reading the drive temperature may reset the spin down timer on some drives.
39 tools are used to access the drive.
40 With the WD120EFAX drive, reading the drive temperature using the drivetemp
42 reading the drive temperature in this mode will not cause the drive to
43 change its mode (meaning the drive will not spin up). It is unknown if other
46 A known workaround for WD120EFAX drives is to read the drive temperature at
55 available only if reported by the drive. All temperatures are reported in
59 temp1_input Current drive temperature
|
| /Documentation/userspace-api/ioctl/ |
| D | cdrom.rst | 23 CDROMSTOP Stop the cdrom drive
24 CDROMSTART Start the cdrom drive
40 CDROMRESET hard-reset the drive
41 CDROMVOLREAD Get the drive's volume setting
67 CDROM_SEND_PACKET send a packet to the drive
114 - ENOSYS cd drive not audio-capable.
135 - ENOSYS cd drive not audio-capable.
159 - ENOSYS cd drive not audio-capable.
190 - ENOSYS cd drive not audio-capable.
219 - ENOSYS cd drive not audio-capable.
[all …]
|
| D | hdio.rst | 38 HDIO_DRIVE_TASK execute task and special drive command
39 HDIO_DRIVE_CMD execute a special drive command
117 if the device is not a disk drive or floppy drive,
125 drive geometry is an abstraction which is actually subject
127 are the "bios" values -- presumably the values the drive had
157 The value of the drive's current unmask setting
209 controls how many sectors the drive will transfer per
226 sectors the drive will transfer per interrupt.
238 - EIO Drive did not accept new block mode.
273 returns the first 142 bytes of drive identity information.
[all …]
|
| /Documentation/cdrom/ |
| D | ide-cd.rst | 15 interface. If your drive uses one of those proprietary interfaces,
18 attach to the parallel port. In addition, there is at least one drive
72 3. The CDROM drive should be connected to the host on an IDE
77 where each device can be a hard drive, a CDROM drive, a floppy drive,
78 or a tape drive. The two devices on an interface are called `master`
79 and `slave`; this is usually selectable via a jumper on the drive.
87 If you want your CDROM drive to be found automatically by the
90 the CDROM drive is the only device on the IDE interface, it should
97 4. Boot the system. If the drive is recognized, you should see a
100 hdb: NEC CD-ROM DRIVE:260, ATAPI CDROM drive
[all …]
|
| D | cdrom-standard.rst | 30 devices; the way a particular drive reacts to a `standard` *ioctl()*
44 When the CD-ROM was developed, the interface between the CD-ROM drive
52 most of the `NoName` manufacturers). In cases where a new drive really
65 capabilities of a particular drive, in an *ad hoc* manner. More
86 layer that sits on top of the low-level device drivers for each CD-ROM drive.
105 more than one CD-ROM drive, possibly of mixed types. It is important
108 drive. In the months that I was busy writing a Linux driver for it,
112 16 speed CD-ROM drive, and 24 speed drives are common.
127 CD-ROM drive behavior, and to provide a common set of services to the various
186 This structure contains information about a particular CD-ROM drive,
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | tlv320adcx140.yaml | 111 ti,asi-tx-drive:
115 data cycles. Default is to drive the output low on unused ASI cycles.
123 configuration type and the second value is for the output drive type.
134 GPO output drive configuration for the GPO pins can be one of the following:
137 1d - Drive active low and active high
138 2d - Drive active low and weak high
139 3d - Drive active low and Hi-Z
140 4d - Drive weak low and active high
141 5d - Drive Hi-Z and active high
145 Defines the configuration and output drive for the General Purpose
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-pci-devices-cciss | 5 Description: Displays the SCSI INQUIRY page 0 model for logical drive
13 drive Y of controller X.
20 drive Y of controller X.
26 Description: Displays the SCSI INQUIRY page 0 vendor for logical drive
40 drive topology changes.
47 drive Y of controller X.
53 Description: Displays the RAID level of logical drive Y of
60 Description: Displays the usage count (number of opens) of logical drive Y
|
| D | sysfs-class-scsi_tape | 17 to and from the tape drive to complete. This includes all
19 drive. An example of other SCSI commands would be tape
33 The number of I/O requests issued to the tape drive other
43 Shows the total number of bytes requested from the tape drive.
55 drive.
74 Shows the total number of bytes written to the tape drive.
86 drive.
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | atmel,at91-pio4-pinctrl.txt | 39 bias-pull-down, bias-pull-up, drive-open-drain, input-schmitt-enable,
41 - atmel,drive-strength: 0 or 1 for low drive, 2 for medium drive and 3 for
42 high drive. The default value is low drive.
73 atmel,drive-strength = <ATMEL_PIO_DRVSTR_ME>;
|
| D | pincfg-node.yaml | 54 drive-push-pull:
56 description: drive actively high and low
58 drive-open-drain:
60 description: drive with open drain
62 drive-open-source:
64 description: drive with open source
66 drive-strength:
70 drive-strength-microamp:
|
| D | qcom,ipq8064-pinctrl.txt | 30 parameters, such as pull-up, drive strength, etc.
45 pins, function, bias-disable, bias-pull-down, bias-pull-up, drive-strength,
52 Supports mux, bias, and drive-strength
55 Supports bias and drive-strength
91 drive-strength = <4>;
97 drive-strength = <2>;
|
| D | nvidia,tegra194-pinmux.txt | 17 parameters, such as pull-up, tristate, drive strength, etc.
33 0: drive, 1: tristate.
50 - nvidia,drive-type: Integer. Valid range 0...3.
51 - nvidia,pull-down-strength: Integer. Controls drive strength. 0 is weakest.
54 - nvidia,pull-up-strength: Integer. Controls drive strength. 0 is weakest.
69 Drive groups:
|
| D | qcom,msm8974-pinctrl.txt | 30 parameters, such as pull-up, drive strength, etc.
44 pins, function, bias-disable, bias-pull-down, bias-pull-up, drive-strength.
52 Supports mux, bias and drive-strength
55 Supports bias and drive-strength
111 drive-strength = <4>;
117 drive-strength = <2>;
|
| D | pinctrl-mt8183.txt | 31 configuration, pullups, drive strength, input enable/disable and input schmitt.
47 and drive-strength are valid.
62 When config drive-strength, it can support some arguments, such as
74 We can add "mediatek,drive-strength-adv = <XXX>;" to describe the specific
82 So the valid arguments of "mediatek,drive-strength-adv" are from 0 to 7.
118 mediatek,drive-strength-adv = <7>;
127 mediatek,drive-strength-adv = <4>;
|
| D | qcom,msm8998-pinctrl.txt | 62 parameters, such as pull-up, drive strength, etc.
88 Supports mux, bias and drive-strength
91 Supports bias and drive-strength
94 Supports bias and drive-strength
171 - drive-strength:
174 Definition: Selects the drive strength for the specified pins, in mA.
198 drive-strength = <2>;
|
| D | pinctrl-sx150x.txt | 47 - drive-push-pull: drive actively high and low
48 …- drive-open-drain: drive with open drain only for sx1507q, sx1508q and sx1509q and except the OSC…
|
| D | qcom,sdm845-pinctrl.txt | 54 parameters, such as pull-up, drive strength, etc.
80 Supports mux, bias and drive-strength
83 Supports bias and drive-strength
147 - drive-strength:
150 Definition: Selects the drive strength for the specified pins, in mA.
172 drive-strength = <2>;
|
| /Documentation/admin-guide/laptops/ |
| D | disk-shock-protection.rst | 22 Issuing this command should cause the drive to switch to idle mode and
26 the internal hard drive and park its heads on the ramp when critical
44 of the respective drive off the platter and block all I/O operations
62 For example, do the following in order to park the heads of drive
97 the same port as the hard drive, it generally *should* recover just
101 instead of /dev/sda), then parking the heads of one drive (drive X)
102 will generally not affect the mode of operation of another drive
103 (drive Y) on the same port as described above. It is only when a port
104 reset is required to recover from an exception on drive Y that further
105 I/O operations on that drive (and the reset itself) will be delayed
[all …]
|
| /Documentation/scsi/ |
| D | st.rst | 18 to any specific tape drive. The tape parameters can be specified with
30 new tape is loaded into the drive or if writing begins at the
32 drive performs auto-detection of the tape format well (like some
36 for the first time). The first method is applicable if the drive
38 "sensible" mode for the device. An example is a DAT drive that is
76 of the physical block on tape. When reading, the drive reads the next
80 In fixed block mode, the data transfer between the drive and the
96 as a synchronization point, i.e., all remaining data form the drive buffers is
100 write the filemarks without flushing the drive buffer. Writing filemark at
101 close() is always flushing the drive buffers. However, if the previous
[all …]
|
| /Documentation/ide/ |
| D | ChangeLog.ide-floppy.1996-2002 | 3 * ALPHA patches to this driver on an EASYSTOR LS-120 ATAPI floppy drive.
24 * bit. My LS-120 drive barfs on
39 * If drive does not support format progress indication
44 * Ver 0.91 Dec 11 99 Added IOMEGA Clik! drive support by
48 * Ver 0.93 Oct 24 00 Fixed bugs for Clik! drive
59 * drive before the drive was actually ready.
|
| D | ide.rst | 2 Information regarding the Enhanced IDE drive
22 drive for which the "prefetch" mode of the CMD640 is turned on.
26 For the CMD640, linux disables "32bit I/O" (hdparm -c1) on any drive
100 If the auto-probing during boot time confuses a drive (ie. the drive works
102 for each drive for which you'd like the drive to skip the hardware
115 for both units, though success is more likely when the drive is jumpered
122 If for some reason your cdrom drive is *not* found at boot time, you can force
132 For example, a GW2000 system might have a hard drive on the primary
133 interface (/dev/hda) and an IDE cdrom drive on the secondary interface
134 (/dev/hdc). To mount a CD in the cdrom drive, one would use something like::
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | silabs,si5351.txt | 48 - silabs,drive-strength: output drive strength in mA, shall be one of {2,4,6,8}.
87 * - 8mA output drive strength
95 silabs,drive-strength = <8>;
104 * - 4mA output drive strength
111 silabs,drive-strength = <4>;
|
| /Documentation/devicetree/bindings/phy/ |
| D | rockchip-emmc-phy.txt | 16 - drive-impedance-ohm: Specifies the drive impedance in Ohm.
35 drive-impedance-ohm = <50>;
|
| /Documentation/devicetree/bindings/mmc/ |
| D | nvidia,tegra20-sdhci.txt | 63 nvidia,pad-autocal-pull-down-offset-3v3 : Specify drive strength
66 nvidia,pad-autocal-pull-down-offset-1v8 : Specify drive strength
69 nvidia,pad-autocal-pull-down-offset-3v3-timeout : Specify drive
73 nvidia,pad-autocal-pull-down-offset-1v8-timeout : Specify drive
77 nvidia,pad-autocal-pull-down-offset-sdr104 : Specify drive strength
80 nvidia,pad-autocal-pull-down-offset-hs400 : Specify drive strength
89 - The property values are drive codes which are programmed into the
92 - A higher value corresponds to higher drive strength. Please refer
|
| /Documentation/devicetree/bindings/ata/ |
| D | pata-common.yaml | 37 DT nodes for ports connected on the PATA host. The master drive will have
38 ID number 0 and the slave drive will have ID number 1. The PATA port
47 The ID number of the drive port, 0 for the master port and 1 for the
|