summaryrefslogtreecommitdiffstats
path: root/Documentation/ABI/testing/sysfs-block-device
blob: 7ac7b19b2f7224572652bf850e51f575757fd0ee (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
What:		/sys/block/*/device/sw_activity
Date:		Jun, 2008
KernelVersion:	v2.6.27
Contact:	linux-ide@vger.kernel.org
Description:
		(RW) Used by drivers which support software controlled activity
		LEDs.

		It has the following valid values:

		==	========================================================
		0	OFF - the LED is not activated on activity
		1	BLINK_ON - the LED blinks on every 10ms when activity is
			detected.
		2	BLINK_OFF - the LED is on when idle, and blinks off
			every 10ms when activity is detected.
		==	========================================================

		Note that the user must turn sw_activity OFF it they wish to
		control the activity LED via the em_message file.


What:		/sys/block/*/device/unload_heads
Date:		Sep, 2008
KernelVersion:	v2.6.28
Contact:	linux-ide@vger.kernel.org
Description:
		(RW) Hard disk shock protection

		Writing an integer value to this file will take the heads of the
		respective drive off the platter and block all I/O operations
		for the specified number of milliseconds.

		- If the device does not support the unload heads feature,
		  access is denied with -EOPNOTSUPP.
		- The maximal value accepted for a timeout is 30000
		  milliseconds.
		- A previously set timeout can be cancelled and disk can resume
		  normal operation immediately by specifying a timeout of 0.
		- Some hard drives only comply with an earlier version of the
		  ATA standard, but support the unload feature nonetheless.
		  There is no safe way Linux can detect these devices, so this
		  is not enabled by default. If it is known that your device
		  does support the unload feature, then you can tell the kernel
		  to enable it by writing -1. It can be disabled again by
		  writing -2.
		- Values below -2 are rejected with -EINVAL

		For more information, see
		Documentation/admin-guide/laptops/disk-shock-protection.rst


What:		/sys/block/*/device/ncq_prio_enable
Date:		Oct, 2016
KernelVersion:	v4.10
Contact:	linux-ide@vger.kernel.org
Description:
		(RW) Write to the file to turn on or off the SATA NCQ (native
		command queueing) priority support. By default this feature is
		turned off. If the device does not support the SATA NCQ
		priority feature, writing "1" to this file results in an error
		(see ncq_prio_supported).


What:		/sys/block/*/device/sas_ncq_prio_enable
Date:		Oct, 2016
KernelVersion:	v4.10
Contact:	linux-ide@vger.kernel.org
Description:
		(RW) This is the equivalent of the ncq_prio_enable attribute
		file for SATA devices connected to a SAS host-bus-adapter
		(HBA) implementing support for the SATA NCQ priority feature.
		This file does not exist if the HBA driver does not implement
		support for the SATA NCQ priority feature, regardless of the
		device support for this feature (see sas_ncq_prio_supported).


What:		/sys/block/*/device/ncq_prio_supported
Date:		Aug, 2021
KernelVersion:	v5.15
Contact:	linux-ide@vger.kernel.org
Description:
		(RO) Indicates if the device supports the SATA NCQ (native
		command queueing) priority feature.


What:		/sys/block/*/device/sas_ncq_prio_supported
Date:		Aug, 2021
KernelVersion:	v5.15
Contact:	linux-ide@vger.kernel.org
Description:
		(RO) This is the equivalent of the ncq_prio_supported attribute
		file for SATA devices connected to a SAS host-bus-adapter
		(HBA) implementing support for the SATA NCQ priority feature.
		This file does not exist if the HBA driver does not implement
		support for the SATA NCQ priority feature, regardless of the
		device support for this feature.