Searched full:hard (Results 1 – 25 of 271) sorted by relevance
1234567891011
| /Documentation/driver-api/ |
| D | rfkill.rst | 21 The rfkill subsystem has a concept of "hard" and "soft" block, which
25 - hard block
56 When the device is hard-blocked (either by a call to rfkill_set_hw_state()
62 keeps track of soft and hard block separately.
89 rfkill drivers that control devices that can be hard-blocked unless they also
109 soft and hard block are properly separated (unlike sysfs, see below) and
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | keystone-reset.txt | 10 Additionally soft or hard reset can be configured.
27 By default hard reset is used.
38 WDT0 is triggered it issues hard reset for SoC.
|
| /Documentation/admin-guide/laptops/ |
| D | disk-shock-protection.rst | 2 Hard disk shock protection
26 the internal hard drive and park its heads on the ramp when critical
97 the same port as the hard drive, it generally *should* recover just
108 Finally, there are some hard drives that only comply with an earlier
114 laptop or the hard drive itself told you so), then you can tell the
140 See this page for information about Linux support of the hard disk
|
| D | laptop-mode.rst | 14 Laptop mode is used to minimize the time that the hard disk needs to be spun up,
59 * Most desktop hard drives have a very limited lifetime measured in spindown
85 have caused the hard disk to spin up) causes Linux to flush all dirty blocks. The
114 Maximum time, in seconds, of hard drive spindown time that you are
125 The idle timeout that should be set on your hard drive when laptop mode
229 # Maximum time, in seconds, of hard drive spindown time that you are
292 # Idle timeout for your hard drive (man hdparm for valid values, -S option)
301 # Set the spindown timeout on a hard drive?
343 # Maximum time, in seconds, of hard drive spindown time that you are
357 # Shall we adjust the idle timeout on a hard drive?
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-class-rfkill | 52 longer. Despite it being marked as stable, the newer "hard" and
54 to express the 'soft and hard block' state of the rfkill driver
68 What: /sys/class/rfkill/rfkill[0-9]+/hard
|
| /Documentation/ABI/testing/ |
| D | sysfs-memory-page-offline | 28 Hard-offline the memory page containing the physical
31 kernel will then attempt to hard-offline the page, by
|
| D | sysfs-kernel-reboot | 13 Description: Reboot mode. Valid values are: cold warm hard soft gpio
|
| D | sysfs-driver-habanalabs | 82 Description: Interface to trigger a hard-reset operation for the device.
83 Hard-reset will reset ALL internal components of the device
90 Description: Displays how many times the device have undergone a hard-reset
222 * "needs reset" - Device is not usable until a hard reset
|
| /Documentation/devicetree/bindings/iio/resolver/ |
| D | adi,ad2s1210.yaml | 44 Note on SPI connections: The CS line on the AD2S1210 should hard-wired to
105 RES0 and RES1 pins are hard-wired to match the assigned-resolution-bits
120 This is used to indicate the selected mode if A0 and A1 are hard-wired
130 RES1 are hard-wired to match this value.
|
| /Documentation/devicetree/bindings/display/msm/ |
| D | mdss-common.yaml | 59 - description: Phandle to apps_smmu node with SID mask for Hard-Fail port0
60 - description: Phandle to apps_smmu node with SID mask for Hard-Fail port1
|
| /Documentation/networking/ |
| D | smc-sysctl.rst | 48 The minimum value is 16KiB and there is no hard limit for max value, but
56 The minimum value is 16KiB and there is no hard limit for max value, but
|
| D | xfrm_sysctl.rst | 11 default 30 - hard timeout in seconds for acquire requests
|
| /Documentation/devicetree/bindings/clock/ |
| D | arm,syscon-icst.yaml | 25 connects the low 8 bits of the VDW (missing one bit), hard-wires RDW to
26 different values and sometimes also hard-wires the output divider. They
|
| /Documentation/filesystems/ |
| D | cramfs.rst | 15 compact also makes it _very_ hard to update on-the-fly), so you have to
31 Hard links are supported, but hard linked files
|
| D | romfs.rst | 98 4 | spec.info | Info for directories/hard links/devices
124 0 hard link link destination [file header]
134 Note that hard links are specifically marked in this filesystem, but
136 Note also that it is your responsibility to not create hard link
|
| /Documentation/driver-api/early-userspace/ |
| D | buffer-format.rst | 48 not ignored; see "handling of hard links" below.
91 Handling of hard links
96 the tuple buffer and the entry is created as usual; if found, a hard
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | adi,ad7944.yaml | 111 line is hard-wired and the state is determined by the adi,always-turbo
118 When present, this property indicates that the TURBO line is hard-wired
120 present, the TURBO line is assumed to be hard-wired and the state is
|
| /Documentation/admin-guide/ |
| D | devices.txt | 115 3 block First MFM, RLL and IDE hard disk/CD-ROM interface
504 21 block Acorn MFM hard drive interface
516 22 block Second IDE hard disk/CD-ROM interface
712 33 block Third IDE hard disk/CD-ROM interface
730 34 block Fourth IDE hard disk/CD-ROM interface
762 36 block OBSOLETE (was MCA ESDI hard disk)
1030 56 block Fifth IDE hard disk/CD-ROM interface
1042 57 block Sixth IDE hard disk/CD-ROM interface
1392 80 block I2O hard disk
1393 0 = /dev/i2o/hda First I2O hard disk, whole disk
[all …]
|
| D | lockup-watchdogs.rst | 5 The Linux kernel can act as a watchdog to detect both soft and hard
36 The soft and hard lockup detectors are built on top of the hrtimer and
|
| D | ufs.rst | 14 some implementations are undocumented, so its hard to recognize
|
| /Documentation/arch/x86/ |
| D | buslock.rst | 84 time systems. These systems run hard real time code on some cores and run
85 "untrusted" user processes on other cores. The hard real time cannot afford
89 generating split lock and bus lock to block the hard real time code to
|
| /Documentation/filesystems/ext4/ |
| D | overview.rst | 8 very hard to keep each file's blocks within the same group, thereby
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-arb-gpio-challenge.yaml | 24 * Having two masters on a bus in general makes it relatively hard to debug
25 problems (hard to tell if i2c issues were caused by one master, another,
|
| /Documentation/devicetree/bindings/usb/ |
| D | usb-hcd.yaml | 34 description: The hard wired USB devices
|
| /Documentation/devicetree/bindings/soc/intel/ |
| D | intel,hps-copy-engine.yaml | 14 The Intel Hard Processor System (HPS) Copy Engine is an IP block used to copy
|
1234567891011