aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/ABI
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/ABI')
-rw-r--r--Documentation/ABI/obsolete/sysfs-block-zram119
-rw-r--r--Documentation/ABI/stable/sysfs-devices10
-rw-r--r--Documentation/ABI/testing/configfs-usb-gadget-printer9
-rw-r--r--Documentation/ABI/testing/sysfs-block-zram25
-rw-r--r--Documentation/ABI/testing/sysfs-bus-iio137
-rw-r--r--Documentation/ABI/testing/sysfs-class-cxl2
-rw-r--r--Documentation/ABI/testing/sysfs-class-led-flash80
-rw-r--r--Documentation/ABI/testing/sysfs-class-net8
-rw-r--r--Documentation/ABI/testing/sysfs-class-net-queues8
-rw-r--r--Documentation/ABI/testing/sysfs-driver-hid10
-rw-r--r--Documentation/ABI/testing/sysfs-driver-hid-logitech-lg4ff45
11 files changed, 441 insertions, 12 deletions
diff --git a/Documentation/ABI/obsolete/sysfs-block-zram b/Documentation/ABI/obsolete/sysfs-block-zram
new file mode 100644
index 000000000000..720ea92cfb2e
--- /dev/null
+++ b/Documentation/ABI/obsolete/sysfs-block-zram
@@ -0,0 +1,119 @@
1What: /sys/block/zram<id>/num_reads
2Date: August 2015
3Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
4Description:
5 The num_reads file is read-only and specifies the number of
6 reads (failed or successful) done on this device.
7 Now accessible via zram<id>/stat node.
8
9What: /sys/block/zram<id>/num_writes
10Date: August 2015
11Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
12Description:
13 The num_writes file is read-only and specifies the number of
14 writes (failed or successful) done on this device.
15 Now accessible via zram<id>/stat node.
16
17What: /sys/block/zram<id>/invalid_io
18Date: August 2015
19Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
20Description:
21 The invalid_io file is read-only and specifies the number of
22 non-page-size-aligned I/O requests issued to this device.
23 Now accessible via zram<id>/io_stat node.
24
25What: /sys/block/zram<id>/failed_reads
26Date: August 2015
27Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
28Description:
29 The failed_reads file is read-only and specifies the number of
30 failed reads happened on this device.
31 Now accessible via zram<id>/io_stat node.
32
33What: /sys/block/zram<id>/failed_writes
34Date: August 2015
35Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
36Description:
37 The failed_writes file is read-only and specifies the number of
38 failed writes happened on this device.
39 Now accessible via zram<id>/io_stat node.
40
41What: /sys/block/zram<id>/notify_free
42Date: August 2015
43Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
44Description:
45 The notify_free file is read-only. Depending on device usage
46 scenario it may account a) the number of pages freed because
47 of swap slot free notifications or b) the number of pages freed
48 because of REQ_DISCARD requests sent by bio. The former ones
49 are sent to a swap block device when a swap slot is freed, which
50 implies that this disk is being used as a swap disk. The latter
51 ones are sent by filesystem mounted with discard option,
52 whenever some data blocks are getting discarded.
53 Now accessible via zram<id>/io_stat node.
54
55What: /sys/block/zram<id>/zero_pages
56Date: August 2015
57Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
58Description:
59 The zero_pages file is read-only and specifies number of zero
60 filled pages written to this disk. No memory is allocated for
61 such pages.
62 Now accessible via zram<id>/mm_stat node.
63
64What: /sys/block/zram<id>/orig_data_size
65Date: August 2015
66Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
67Description:
68 The orig_data_size file is read-only and specifies uncompressed
69 size of data stored in this disk. This excludes zero-filled
70 pages (zero_pages) since no memory is allocated for them.
71 Unit: bytes
72 Now accessible via zram<id>/mm_stat node.
73
74What: /sys/block/zram<id>/compr_data_size
75Date: August 2015
76Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
77Description:
78 The compr_data_size file is read-only and specifies compressed
79 size of data stored in this disk. So, compression ratio can be
80 calculated using orig_data_size and this statistic.
81 Unit: bytes
82 Now accessible via zram<id>/mm_stat node.
83
84What: /sys/block/zram<id>/mem_used_total
85Date: August 2015
86Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
87Description:
88 The mem_used_total file is read-only and specifies the amount
89 of memory, including allocator fragmentation and metadata
90 overhead, allocated for this disk. So, allocator space
91 efficiency can be calculated using compr_data_size and this
92 statistic.
93 Unit: bytes
94 Now accessible via zram<id>/mm_stat node.
95
96What: /sys/block/zram<id>/mem_used_max
97Date: August 2015
98Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
99Description:
100 The mem_used_max file is read/write and specifies the amount
101 of maximum memory zram have consumed to store compressed data.
102 For resetting the value, you should write "0". Otherwise,
103 you could see -EINVAL.
104 Unit: bytes
105 Downgraded to write-only node: so it's possible to set new
106 value only; its current value is stored in zram<id>/mm_stat
107 node.
108
109What: /sys/block/zram<id>/mem_limit
110Date: August 2015
111Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
112Description:
113 The mem_limit file is read/write and specifies the maximum
114 amount of memory ZRAM can use to store the compressed data.
115 The limit could be changed in run time and "0" means disable
116 the limit. No limit is the initial state. Unit: bytes
117 Downgraded to write-only node: so it's possible to set new
118 value only; its current value is stored in zram<id>/mm_stat
119 node.
diff --git a/Documentation/ABI/stable/sysfs-devices b/Documentation/ABI/stable/sysfs-devices
new file mode 100644
index 000000000000..43f78b88da28
--- /dev/null
+++ b/Documentation/ABI/stable/sysfs-devices
@@ -0,0 +1,10 @@
1# Note: This documents additional properties of any device beyond what
2# is documented in Documentation/sysfs-rules.txt
3
4What: /sys/devices/*/of_path
5Date: February 2015
6Contact: Device Tree mailing list <devicetree@vger.kernel.org>
7Description:
8 Any device associated with a device-tree node will have
9 an of_path symlink pointing to the corresponding device
10 node in /sys/firmware/devicetree/
diff --git a/Documentation/ABI/testing/configfs-usb-gadget-printer b/Documentation/ABI/testing/configfs-usb-gadget-printer
new file mode 100644
index 000000000000..6b0714e3c605
--- /dev/null
+++ b/Documentation/ABI/testing/configfs-usb-gadget-printer
@@ -0,0 +1,9 @@
1What: /config/usb-gadget/gadget/functions/printer.name
2Date: Apr 2015
3KernelVersion: 4.1
4Description:
5 The attributes:
6
7 pnp_string - Data to be passed to the host in pnp string
8 q_len - Number of requests per endpoint
9
diff --git a/Documentation/ABI/testing/sysfs-block-zram b/Documentation/ABI/testing/sysfs-block-zram
index a6148eaf91e5..2e69e83bf510 100644
--- a/Documentation/ABI/testing/sysfs-block-zram
+++ b/Documentation/ABI/testing/sysfs-block-zram
@@ -141,3 +141,28 @@ Description:
141 amount of memory ZRAM can use to store the compressed data. The 141 amount of memory ZRAM can use to store the compressed data. The
142 limit could be changed in run time and "0" means disable the 142 limit could be changed in run time and "0" means disable the
143 limit. No limit is the initial state. Unit: bytes 143 limit. No limit is the initial state. Unit: bytes
144
145What: /sys/block/zram<id>/compact
146Date: August 2015
147Contact: Minchan Kim <minchan@kernel.org>
148Description:
149 The compact file is write-only and trigger compaction for
150 allocator zrm uses. The allocator moves some objects so that
151 it could free fragment space.
152
153What: /sys/block/zram<id>/io_stat
154Date: August 2015
155Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
156Description:
157 The io_stat file is read-only and accumulates device's I/O
158 statistics not accounted by block layer. For example,
159 failed_reads, failed_writes, etc. File format is similar to
160 block layer statistics file format.
161
162What: /sys/block/zram<id>/mm_stat
163Date: August 2015
164Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
165Description:
166 The mm_stat file is read-only and represents device's mm
167 statistics (orig_data_size, compr_data_size, etc.) in a format
168 similar to block layer statistics file format.
diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio
index 9a70c31619ea..3befcb19f414 100644
--- a/Documentation/ABI/testing/sysfs-bus-iio
+++ b/Documentation/ABI/testing/sysfs-bus-iio
@@ -253,6 +253,8 @@ What: /sys/bus/iio/devices/iio:deviceX/in_temp_offset
253What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_offset 253What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_offset
254What: /sys/bus/iio/devices/iio:deviceX/in_pressure_offset 254What: /sys/bus/iio/devices/iio:deviceX/in_pressure_offset
255What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_offset 255What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_offset
256What: /sys/bus/iio/devices/iio:deviceX/in_magn_offset
257What: /sys/bus/iio/devices/iio:deviceX/in_rot_offset
256KernelVersion: 2.6.35 258KernelVersion: 2.6.35
257Contact: linux-iio@vger.kernel.org 259Contact: linux-iio@vger.kernel.org
258Description: 260Description:
@@ -296,6 +298,7 @@ What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_scale
296What: /sys/bus/iio/devices/iio:deviceX/in_pressure_scale 298What: /sys/bus/iio/devices/iio:deviceX/in_pressure_scale
297What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_scale 299What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_scale
298What: /sys/bus/iio/devices/iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_scale 300What: /sys/bus/iio/devices/iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_scale
301What: /sys/bus/iio/devices/iio:deviceX/in_illuminance_scale
299KernelVersion: 2.6.35 302KernelVersion: 2.6.35
300Contact: linux-iio@vger.kernel.org 303Contact: linux-iio@vger.kernel.org
301Description: 304Description:
@@ -336,6 +339,7 @@ what /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibscale
336what /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibscale 339what /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibscale
337What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_calibscale 340What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_calibscale
338What: /sys/bus/iio/devices/iio:deviceX/in_pressure_calibscale 341What: /sys/bus/iio/devices/iio:deviceX/in_pressure_calibscale
342What: /sys/bus/iio/devices/iio:deviceX/in_illuminance_calibscale
339KernelVersion: 2.6.35 343KernelVersion: 2.6.35
340Contact: linux-iio@vger.kernel.org 344Contact: linux-iio@vger.kernel.org
341Description: 345Description:
@@ -347,7 +351,7 @@ What: /sys/bus/iio/devices/iio:deviceX/in_activity_calibgender
347What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibgender 351What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibgender
348What: /sys/bus/iio/devices/iio:deviceX/in_distance_calibgender 352What: /sys/bus/iio/devices/iio:deviceX/in_distance_calibgender
349What: /sys/bus/iio/devices/iio:deviceX/in_velocity_calibgender 353What: /sys/bus/iio/devices/iio:deviceX/in_velocity_calibgender
350KernelVersion: 3.20 354KernelVersion: 4.0
351Contact: linux-iio@vger.kernel.org 355Contact: linux-iio@vger.kernel.org
352Description: 356Description:
353 Gender of the user (e.g.: male, female) used by some pedometers 357 Gender of the user (e.g.: male, female) used by some pedometers
@@ -358,7 +362,7 @@ What: /sys/bus/iio/devices/iio:deviceX/in_activity_calibgender_available
358What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibgender_available 362What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibgender_available
359What: /sys/bus/iio/devices/iio:deviceX/in_distance_calibgender_available 363What: /sys/bus/iio/devices/iio:deviceX/in_distance_calibgender_available
360What: /sys/bus/iio/devices/iio:deviceX/in_velocity_calibgender_available 364What: /sys/bus/iio/devices/iio:deviceX/in_velocity_calibgender_available
361KernelVersion: 3.20 365KernelVersion: 4.0
362Contact: linux-iio@vger.kernel.org 366Contact: linux-iio@vger.kernel.org
363Description: 367Description:
364 Lists all available gender values (e.g.: male, female). 368 Lists all available gender values (e.g.: male, female).
@@ -375,7 +379,7 @@ Description:
375 type. 379 type.
376 380
377What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibweight 381What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibweight
378KernelVersion: 3.20 382KernelVersion: 4.0
379Contact: linux-iio@vger.kernel.org 383Contact: linux-iio@vger.kernel.org
380Description: 384Description:
381 Weight of the user (in kg). It is needed by some pedometers 385 Weight of the user (in kg). It is needed by some pedometers
@@ -612,6 +616,8 @@ Description:
612 a given event type is enabled a future point (and not those for 616 a given event type is enabled a future point (and not those for
613 whatever event was previously enabled). 617 whatever event was previously enabled).
614 618
619What: /sys/.../events/in_accel_thresh_rising_value
620What: /sys/.../events/in_accel_thresh_falling_value
615What: /sys/.../events/in_accel_x_raw_thresh_rising_value 621What: /sys/.../events/in_accel_x_raw_thresh_rising_value
616What: /sys/.../events/in_accel_x_raw_thresh_falling_value 622What: /sys/.../events/in_accel_x_raw_thresh_falling_value
617What: /sys/.../events/in_accel_y_raw_thresh_rising_value 623What: /sys/.../events/in_accel_y_raw_thresh_rising_value
@@ -661,6 +667,24 @@ Description:
661 value is in raw device units or in processed units (as _raw 667 value is in raw device units or in processed units (as _raw
662 and _input do on sysfs direct channel read attributes). 668 and _input do on sysfs direct channel read attributes).
663 669
670What: /sys/.../events/in_accel_scale
671What: /sys/.../events/in_accel_peak_scale
672What: /sys/.../events/in_anglvel_scale
673What: /sys/.../events/in_magn_scale
674What: /sys/.../events/in_rot_from_north_magnetic_scale
675What: /sys/.../events/in_rot_from_north_true_scale
676What: /sys/.../events/in_voltage_scale
677What: /sys/.../events/in_voltage_supply_scale
678What: /sys/.../events/in_temp_scale
679What: /sys/.../events/in_illuminance_scale
680What: /sys/.../events/in_proximity_scale
681KernelVersion: 3.21
682Contact: linux-iio@vger.kernel.org
683Description:
684 Specifies the conversion factor from the standard units
685 to device specific units used to set the event trigger
686 threshold.
687
664What: /sys/.../events/in_accel_x_thresh_rising_hysteresis 688What: /sys/.../events/in_accel_x_thresh_rising_hysteresis
665What: /sys/.../events/in_accel_x_thresh_falling_hysteresis 689What: /sys/.../events/in_accel_x_thresh_falling_hysteresis
666What: /sys/.../events/in_accel_x_thresh_either_hysteresis 690What: /sys/.../events/in_accel_x_thresh_either_hysteresis
@@ -776,7 +800,7 @@ Description:
776 800
777What: /sys/.../events/in_accel_x_thresh_rising_period 801What: /sys/.../events/in_accel_x_thresh_rising_period
778What: /sys/.../events/in_accel_x_thresh_falling_period 802What: /sys/.../events/in_accel_x_thresh_falling_period
779hat: /sys/.../events/in_accel_x_roc_rising_period 803What: /sys/.../events/in_accel_x_roc_rising_period
780What: /sys/.../events/in_accel_x_roc_falling_period 804What: /sys/.../events/in_accel_x_roc_falling_period
781What: /sys/.../events/in_accel_y_thresh_rising_period 805What: /sys/.../events/in_accel_y_thresh_rising_period
782What: /sys/.../events/in_accel_y_thresh_falling_period 806What: /sys/.../events/in_accel_y_thresh_falling_period
@@ -923,7 +947,7 @@ Description:
923 this type. 947 this type.
924 948
925What: /sys/.../events/in_steps_change_en 949What: /sys/.../events/in_steps_change_en
926KernelVersion: 3.20 950KernelVersion: 4.0
927Contact: linux-iio@vger.kernel.org 951Contact: linux-iio@vger.kernel.org
928Description: 952Description:
929 Event generated when channel passes a threshold on the absolute 953 Event generated when channel passes a threshold on the absolute
@@ -932,7 +956,7 @@ Description:
932 in_steps_change_value. 956 in_steps_change_value.
933 957
934What: /sys/.../events/in_steps_change_value 958What: /sys/.../events/in_steps_change_value
935KernelVersion: 3.20 959KernelVersion: 4.0
936Contact: linux-iio@vger.kernel.org 960Contact: linux-iio@vger.kernel.org
937Description: 961Description:
938 Specifies the value of change threshold that the 962 Specifies the value of change threshold that the
@@ -997,6 +1021,7 @@ What: /sys/.../iio:deviceX/scan_elements/in_incli_y_en
997What: /sys/.../iio:deviceX/scan_elements/in_pressureY_en 1021What: /sys/.../iio:deviceX/scan_elements/in_pressureY_en
998What: /sys/.../iio:deviceX/scan_elements/in_pressure_en 1022What: /sys/.../iio:deviceX/scan_elements/in_pressure_en
999What: /sys/.../iio:deviceX/scan_elements/in_rot_quaternion_en 1023What: /sys/.../iio:deviceX/scan_elements/in_rot_quaternion_en
1024What: /sys/.../iio:deviceX/scan_elements/in_proximity_en
1000KernelVersion: 2.6.37 1025KernelVersion: 2.6.37
1001Contact: linux-iio@vger.kernel.org 1026Contact: linux-iio@vger.kernel.org
1002Description: 1027Description:
@@ -1013,6 +1038,7 @@ What: /sys/.../iio:deviceX/scan_elements/in_timestamp_type
1013What: /sys/.../iio:deviceX/scan_elements/in_pressureY_type 1038What: /sys/.../iio:deviceX/scan_elements/in_pressureY_type
1014What: /sys/.../iio:deviceX/scan_elements/in_pressure_type 1039What: /sys/.../iio:deviceX/scan_elements/in_pressure_type
1015What: /sys/.../iio:deviceX/scan_elements/in_rot_quaternion_type 1040What: /sys/.../iio:deviceX/scan_elements/in_rot_quaternion_type
1041What: /sys/.../iio:deviceX/scan_elements/in_proximity_type
1016KernelVersion: 2.6.37 1042KernelVersion: 2.6.37
1017Contact: linux-iio@vger.kernel.org 1043Contact: linux-iio@vger.kernel.org
1018Description: 1044Description:
@@ -1064,6 +1090,7 @@ What: /sys/.../iio:deviceX/scan_elements/in_timestamp_index
1064What: /sys/.../iio:deviceX/scan_elements/in_pressureY_index 1090What: /sys/.../iio:deviceX/scan_elements/in_pressureY_index
1065What: /sys/.../iio:deviceX/scan_elements/in_pressure_index 1091What: /sys/.../iio:deviceX/scan_elements/in_pressure_index
1066What: /sys/.../iio:deviceX/scan_elements/in_rot_quaternion_index 1092What: /sys/.../iio:deviceX/scan_elements/in_rot_quaternion_index
1093What: /sys/.../iio:deviceX/scan_elements/in_proximity_index
1067KernelVersion: 2.6.37 1094KernelVersion: 2.6.37
1068Contact: linux-iio@vger.kernel.org 1095Contact: linux-iio@vger.kernel.org
1069Description: 1096Description:
@@ -1104,7 +1131,7 @@ Description:
1104 1131
1105What: /sys/.../iio:deviceX/in_energy_input 1132What: /sys/.../iio:deviceX/in_energy_input
1106What: /sys/.../iio:deviceX/in_energy_raw 1133What: /sys/.../iio:deviceX/in_energy_raw
1107KernelVersion: 3.20 1134KernelVersion: 4.0
1108Contact: linux-iio@vger.kernel.org 1135Contact: linux-iio@vger.kernel.org
1109Description: 1136Description:
1110 This attribute is used to read the energy value reported by the 1137 This attribute is used to read the energy value reported by the
@@ -1113,7 +1140,7 @@ Description:
1113 1140
1114What: /sys/.../iio:deviceX/in_distance_input 1141What: /sys/.../iio:deviceX/in_distance_input
1115What: /sys/.../iio:deviceX/in_distance_raw 1142What: /sys/.../iio:deviceX/in_distance_raw
1116KernelVersion: 3.20 1143KernelVersion: 4.0
1117Contact: linux-iio@vger.kernel.org 1144Contact: linux-iio@vger.kernel.org
1118Description: 1145Description:
1119 This attribute is used to read the distance covered by the user 1146 This attribute is used to read the distance covered by the user
@@ -1143,9 +1170,13 @@ Description:
1143 values should behave in the same way as a distance, i.e. lower 1170 values should behave in the same way as a distance, i.e. lower
1144 values indicate something is closer to the sensor. 1171 values indicate something is closer to the sensor.
1145 1172
1173What: /sys/.../iio:deviceX/in_illuminance_input
1174What: /sys/.../iio:deviceX/in_illuminance_raw
1146What: /sys/.../iio:deviceX/in_illuminanceY_input 1175What: /sys/.../iio:deviceX/in_illuminanceY_input
1147What: /sys/.../iio:deviceX/in_illuminanceY_raw 1176What: /sys/.../iio:deviceX/in_illuminanceY_raw
1148What: /sys/.../iio:deviceX/in_illuminanceY_mean_raw 1177What: /sys/.../iio:deviceX/in_illuminanceY_mean_raw
1178What: /sys/.../iio:deviceX/in_illuminance_ir_raw
1179What: /sys/.../iio:deviceX/in_illuminance_clear_raw
1149KernelVersion: 3.4 1180KernelVersion: 3.4
1150Contact: linux-iio@vger.kernel.org 1181Contact: linux-iio@vger.kernel.org
1151Description: 1182Description:
@@ -1174,7 +1205,7 @@ Description:
1174 seconds. 1205 seconds.
1175 1206
1176What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_integration_time 1207What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_integration_time
1177KernelVersion: 3.20 1208KernelVersion: 4.0
1178Contact: linux-iio@vger.kernel.org 1209Contact: linux-iio@vger.kernel.org
1179Description: 1210Description:
1180 Number of seconds in which to compute speed. 1211 Number of seconds in which to compute speed.
@@ -1236,7 +1267,7 @@ Description:
1236 Units after application of scale are m/s. 1267 Units after application of scale are m/s.
1237 1268
1238What: /sys/.../iio:deviceX/in_steps_debounce_count 1269What: /sys/.../iio:deviceX/in_steps_debounce_count
1239KernelVersion: 3.20 1270KernelVersion: 4.0
1240Contact: linux-iio@vger.kernel.org 1271Contact: linux-iio@vger.kernel.org
1241Description: 1272Description:
1242 Specifies the number of steps that must occur within 1273 Specifies the number of steps that must occur within
@@ -1244,8 +1275,92 @@ Description:
1244 consumer is making steps. 1275 consumer is making steps.
1245 1276
1246What: /sys/.../iio:deviceX/in_steps_debounce_time 1277What: /sys/.../iio:deviceX/in_steps_debounce_time
1247KernelVersion: 3.20 1278KernelVersion: 4.0
1248Contact: linux-iio@vger.kernel.org 1279Contact: linux-iio@vger.kernel.org
1249Description: 1280Description:
1250 Specifies number of seconds in which we compute the steps 1281 Specifies number of seconds in which we compute the steps
1251 that occur in order to decide if the consumer is making steps. 1282 that occur in order to decide if the consumer is making steps.
1283
1284What: /sys/bus/iio/devices/iio:deviceX/buffer/watermark
1285KernelVersion: 4.2
1286Contact: linux-iio@vger.kernel.org
1287Description:
1288 A single positive integer specifying the maximum number of scan
1289 elements to wait for.
1290 Poll will block until the watermark is reached.
1291 Blocking read will wait until the minimum between the requested
1292 read amount or the low water mark is available.
1293 Non-blocking read will retrieve the available samples from the
1294 buffer even if there are less samples then watermark level. This
1295 allows the application to block on poll with a timeout and read
1296 the available samples after the timeout expires and thus have a
1297 maximum delay guarantee.
1298
1299What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_enabled
1300KernelVersion: 4.2
1301Contact: linux-iio@vger.kernel.org
1302Description:
1303 A read-only boolean value that indicates if the hardware fifo is
1304 currently enabled or disabled. If the device does not have a
1305 hardware fifo this entry is not present.
1306 The hardware fifo is enabled when the buffer is enabled if the
1307 current hardware fifo watermark level is set and other current
1308 device settings allows it (e.g. if a trigger is set that samples
1309 data differently that the hardware fifo does then hardware fifo
1310 will not enabled).
1311 If the hardware fifo is enabled and the level of the hardware
1312 fifo reaches the hardware fifo watermark level the device will
1313 flush its hardware fifo to the device buffer. Doing a non
1314 blocking read on the device when no samples are present in the
1315 device buffer will also force a flush.
1316 When the hardware fifo is enabled there is no need to use a
1317 trigger to use buffer mode since the watermark settings
1318 guarantees that the hardware fifo is flushed to the device
1319 buffer.
1320
1321What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark
1322KernelVersion: 4.2
1323Contact: linux-iio@vger.kernel.org
1324Description:
1325 Read-only entry that contains a single integer specifying the
1326 current watermark level for the hardware fifo. If the device
1327 does not have a hardware fifo this entry is not present.
1328 The watermark level for the hardware fifo is set by the driver
1329 based on the value set by the user in buffer/watermark but
1330 taking into account hardware limitations (e.g. most hardware
1331 buffers are limited to 32-64 samples, some hardware buffers
1332 watermarks are fixed or have minimum levels). A value of 0
1333 means that the hardware watermark is unset.
1334
1335What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark_min
1336KernelVersion: 4.2
1337Contact: linux-iio@vger.kernel.org
1338Description:
1339 A single positive integer specifying the minimum watermark level
1340 for the hardware fifo of this device. If the device does not
1341 have a hardware fifo this entry is not present.
1342 If the user sets buffer/watermark to a value less than this one,
1343 then the hardware watermark will remain unset.
1344
1345What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark_max
1346KernelVersion: 4.2
1347Contact: linux-iio@vger.kernel.org
1348Description:
1349 A single positive integer specifying the maximum watermark level
1350 for the hardware fifo of this device. If the device does not
1351 have a hardware fifo this entry is not present.
1352 If the user sets buffer/watermark to a value greater than this
1353 one, then the hardware watermark will be capped at this value.
1354
1355What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark_available
1356KernelVersion: 4.2
1357Contact: linux-iio@vger.kernel.org
1358Description:
1359 A list of positive integers specifying the available watermark
1360 levels for the hardware fifo. This entry is optional and if it
1361 is not present it means that all the values between
1362 hwfifo_watermark_min and hwfifo_watermark_max are supported.
1363 If the user sets buffer/watermark to a value greater than
1364 hwfifo_watermak_min but not equal to any of the values in this
1365 list, the driver will chose an appropriate value for the
1366 hardware fifo watermark level.
diff --git a/Documentation/ABI/testing/sysfs-class-cxl b/Documentation/ABI/testing/sysfs-class-cxl
index 3680364b4048..d46bba801aac 100644
--- a/Documentation/ABI/testing/sysfs-class-cxl
+++ b/Documentation/ABI/testing/sysfs-class-cxl
@@ -100,7 +100,7 @@ Description: read only
100 Hexadecimal value of the device ID found in this AFU 100 Hexadecimal value of the device ID found in this AFU
101 configuration record. 101 configuration record.
102 102
103What: /sys/class/cxl/<afu>/cr<config num>/vendor 103What: /sys/class/cxl/<afu>/cr<config num>/class
104Date: February 2015 104Date: February 2015
105Contact: linuxppc-dev@lists.ozlabs.org 105Contact: linuxppc-dev@lists.ozlabs.org
106Description: read only 106Description: read only
diff --git a/Documentation/ABI/testing/sysfs-class-led-flash b/Documentation/ABI/testing/sysfs-class-led-flash
new file mode 100644
index 000000000000..220a0270b47b
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-class-led-flash
@@ -0,0 +1,80 @@
1What: /sys/class/leds/<led>/flash_brightness
2Date: March 2015
3KernelVersion: 4.0
4Contact: Jacek Anaszewski <j.anaszewski@samsung.com>
5Description: read/write
6 Set the brightness of this LED in the flash strobe mode, in
7 microamperes. The file is created only for the flash LED devices
8 that support setting flash brightness.
9
10 The value is between 0 and
11 /sys/class/leds/<led>/max_flash_brightness.
12
13What: /sys/class/leds/<led>/max_flash_brightness
14Date: March 2015
15KernelVersion: 4.0
16Contact: Jacek Anaszewski <j.anaszewski@samsung.com>
17Description: read only
18 Maximum brightness level for this LED in the flash strobe mode,
19 in microamperes.
20
21What: /sys/class/leds/<led>/flash_timeout
22Date: March 2015
23KernelVersion: 4.0
24Contact: Jacek Anaszewski <j.anaszewski@samsung.com>
25Description: read/write
26 Hardware timeout for flash, in microseconds. The flash strobe
27 is stopped after this period of time has passed from the start
28 of the strobe. The file is created only for the flash LED
29 devices that support setting flash timeout.
30
31What: /sys/class/leds/<led>/max_flash_timeout
32Date: March 2015
33KernelVersion: 4.0
34Contact: Jacek Anaszewski <j.anaszewski@samsung.com>
35Description: read only
36 Maximum flash timeout for this LED, in microseconds.
37
38What: /sys/class/leds/<led>/flash_strobe
39Date: March 2015
40KernelVersion: 4.0
41Contact: Jacek Anaszewski <j.anaszewski@samsung.com>
42Description: read/write
43 Flash strobe state. When written with 1 it triggers flash strobe
44 and when written with 0 it turns the flash off.
45
46 On read 1 means that flash is currently strobing and 0 means
47 that flash is off.
48
49What: /sys/class/leds/<led>/flash_fault
50Date: March 2015
51KernelVersion: 4.0
52Contact: Jacek Anaszewski <j.anaszewski@samsung.com>
53Description: read only
54 Space separated list of flash faults that may have occurred.
55 Flash faults are re-read after strobing the flash. Possible
56 flash faults:
57
58 * led-over-voltage - flash controller voltage to the flash LED
59 has exceeded the limit specific to the flash controller
60 * flash-timeout-exceeded - the flash strobe was still on when
61 the timeout set by the user has expired; not all flash
62 controllers may set this in all such conditions
63 * controller-over-temperature - the flash controller has
64 overheated
65 * controller-short-circuit - the short circuit protection
66 of the flash controller has been triggered
67 * led-power-supply-over-current - current in the LED power
68 supply has exceeded the limit specific to the flash
69 controller
70 * indicator-led-fault - the flash controller has detected
71 a short or open circuit condition on the indicator LED
72 * led-under-voltage - flash controller voltage to the flash
73 LED has been below the minimum limit specific to
74 the flash
75 * controller-under-voltage - the input voltage of the flash
76 controller is below the limit under which strobing the
77 flash at full current will not be possible;
78 the condition persists until this flag is no longer set
79 * led-over-temperature - the temperature of the LED has exceeded
80 its allowed upper limit
diff --git a/Documentation/ABI/testing/sysfs-class-net b/Documentation/ABI/testing/sysfs-class-net
index beb8ec4dabbc..5ecfd72ba684 100644
--- a/Documentation/ABI/testing/sysfs-class-net
+++ b/Documentation/ABI/testing/sysfs-class-net
@@ -188,6 +188,14 @@ Description:
188 Indicates the interface unique physical port identifier within 188 Indicates the interface unique physical port identifier within
189 the NIC, as a string. 189 the NIC, as a string.
190 190
191What: /sys/class/net/<iface>/phys_port_name
192Date: March 2015
193KernelVersion: 4.0
194Contact: netdev@vger.kernel.org
195Description:
196 Indicates the interface physical port name within the NIC,
197 as a string.
198
191What: /sys/class/net/<iface>/speed 199What: /sys/class/net/<iface>/speed
192Date: October 2009 200Date: October 2009
193KernelVersion: 2.6.33 201KernelVersion: 2.6.33
diff --git a/Documentation/ABI/testing/sysfs-class-net-queues b/Documentation/ABI/testing/sysfs-class-net-queues
index 5e9aeb91d355..0c0df91b1516 100644
--- a/Documentation/ABI/testing/sysfs-class-net-queues
+++ b/Documentation/ABI/testing/sysfs-class-net-queues
@@ -24,6 +24,14 @@ Description:
24 Indicates the number of transmit timeout events seen by this 24 Indicates the number of transmit timeout events seen by this
25 network interface transmit queue. 25 network interface transmit queue.
26 26
27What: /sys/class/<iface>/queues/tx-<queue>/tx_maxrate
28Date: March 2015
29KernelVersion: 4.1
30Contact: netdev@vger.kernel.org
31Description:
32 A Mbps max-rate set for the queue, a value of zero means disabled,
33 default is disabled.
34
27What: /sys/class/<iface>/queues/tx-<queue>/xps_cpus 35What: /sys/class/<iface>/queues/tx-<queue>/xps_cpus
28Date: November 2010 36Date: November 2010
29KernelVersion: 2.6.38 37KernelVersion: 2.6.38
diff --git a/Documentation/ABI/testing/sysfs-driver-hid b/Documentation/ABI/testing/sysfs-driver-hid
index b6490e14fe83..48942cacb0bf 100644
--- a/Documentation/ABI/testing/sysfs-driver-hid
+++ b/Documentation/ABI/testing/sysfs-driver-hid
@@ -8,3 +8,13 @@ Description: When read, this file returns the device's raw binary HID
8 report descriptor. 8 report descriptor.
9 This file cannot be written. 9 This file cannot be written.
10Users: HIDAPI library (http://www.signal11.us/oss/hidapi) 10Users: HIDAPI library (http://www.signal11.us/oss/hidapi)
11
12What: For USB devices : /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/country
13 For BT devices : /sys/class/bluetooth/hci<addr>/<hid-bus>:<vendor-id>:<product-id>.<num>/country
14 Symlink : /sys/class/hidraw/hidraw<num>/device/country
15Date: February 2015
16KernelVersion: 3.19
17Contact: Olivier Gay <ogay@logitech.com>
18Description: When read, this file returns the hex integer value in ASCII
19 of the device's HID country code (e.g. 21 for US).
20 This file cannot be written.
diff --git a/Documentation/ABI/testing/sysfs-driver-hid-logitech-lg4ff b/Documentation/ABI/testing/sysfs-driver-hid-logitech-lg4ff
index 167d9032b970..b3f6a2ac5007 100644
--- a/Documentation/ABI/testing/sysfs-driver-hid-logitech-lg4ff
+++ b/Documentation/ABI/testing/sysfs-driver-hid-logitech-lg4ff
@@ -5,3 +5,48 @@ Contact: Michal Malý <madcatxster@gmail.com>
5Description: Display minimum, maximum and current range of the steering 5Description: Display minimum, maximum and current range of the steering
6 wheel. Writing a value within min and max boundaries sets the 6 wheel. Writing a value within min and max boundaries sets the
7 range of the wheel. 7 range of the wheel.
8
9What: /sys/bus/hid/drivers/logitech/<dev>/alternate_modes
10Date: Feb 2015
11KernelVersion: 4.1
12Contact: Michal Malý <madcatxster@gmail.com>
13Description: Displays a set of alternate modes supported by a wheel. Each
14 mode is listed as follows:
15 Tag: Mode Name
16 Currently active mode is marked with an asterisk. List also
17 contains an abstract item "native" which always denotes the
18 native mode of the wheel. Echoing the mode tag switches the
19 wheel into the corresponding mode. Depending on the exact model
20 of the wheel not all listed modes might always be selectable.
21 If a wheel cannot be switched into the desired mode, -EINVAL
22 is returned accompanied with an explanatory message in the
23 kernel log.
24 This entry is not created for devices that have only one mode.
25
26 Currently supported mode switches:
27 Driving Force Pro:
28 DF-EX --> DFP
29
30 G25:
31 DF-EX --> DFP --> G25
32
33 G27:
34 DF-EX <*> DFP <-> G25 <-> G27
35 DF-EX <*--------> G25 <-> G27
36 DF-EX <*----------------> G27
37
38 DFGT:
39 DF-EX <*> DFP <-> DFGT
40 DF-EX <*--------> DFGT
41
42 * hid_logitech module must be loaded with lg4ff_no_autoswitch=1
43 parameter set in order for the switch to DF-EX mode to work.
44
45What: /sys/bus/hid/drivers/logitech/<dev>/real_id
46Date: Feb 2015
47KernelVersion: 4.1
48Contact: Michal Malý <madcatxster@gmail.com>
49Description: Displays the real model of the wheel regardless of any
50 alternate mode the wheel might be switched to.
51 It is a read-only value.
52 This entry is not created for devices that have only one mode.
generated by cgit v1.2.2 (git 2.25.0) at 2025-01-20 21:45:51 -0500