aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/ABI/testing
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/ABI/testing')
-rw-r--r--Documentation/ABI/testing/configfs-usb-gadget-uvc265
-rw-r--r--Documentation/ABI/testing/sysfs-bus-amba20
-rw-r--r--Documentation/ABI/testing/sysfs-bus-event_source-devices-events6
-rw-r--r--Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x722
-rw-r--r--Documentation/ABI/testing/sysfs-bus-iio200
-rw-r--r--Documentation/ABI/testing/sysfs-class-cxl67
-rw-r--r--Documentation/ABI/testing/sysfs-class-mei15
-rw-r--r--Documentation/ABI/testing/sysfs-class-power42
-rw-r--r--Documentation/ABI/testing/sysfs-driver-input-axp-pek11
-rw-r--r--Documentation/ABI/testing/sysfs-driver-samsung-laptop8
-rw-r--r--Documentation/ABI/testing/sysfs-driver-toshiba_acpi114
-rw-r--r--Documentation/ABI/testing/sysfs-fs-f2fs6
-rw-r--r--Documentation/ABI/testing/sysfs-kernel-livepatch44
-rw-r--r--Documentation/ABI/testing/sysfs-platform-dell-laptop60
14 files changed, 817 insertions, 63 deletions
diff --git a/Documentation/ABI/testing/configfs-usb-gadget-uvc b/Documentation/ABI/testing/configfs-usb-gadget-uvc
new file mode 100644
index 000000000000..2f4a0051b32d
--- /dev/null
+++ b/Documentation/ABI/testing/configfs-usb-gadget-uvc
@@ -0,0 +1,265 @@
1What: /config/usb-gadget/gadget/functions/uvc.name
2Date: Dec 2014
3KernelVersion: 3.20
4Description: UVC function directory
5
6 streaming_maxburst - 0..15 (ss only)
7 streaming_maxpacket - 1..1023 (fs), 1..3072 (hs/ss)
8 streaming_interval - 1..16
9
10What: /config/usb-gadget/gadget/functions/uvc.name/control
11Date: Dec 2014
12KernelVersion: 3.20
13Description: Control descriptors
14
15What: /config/usb-gadget/gadget/functions/uvc.name/control/class
16Date: Dec 2014
17KernelVersion: 3.20
18Description: Class descriptors
19
20What: /config/usb-gadget/gadget/functions/uvc.name/control/class/ss
21Date: Dec 2014
22KernelVersion: 3.20
23Description: Super speed control class descriptors
24
25What: /config/usb-gadget/gadget/functions/uvc.name/control/class/fs
26Date: Dec 2014
27KernelVersion: 3.20
28Description: Full speed control class descriptors
29
30What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal
31Date: Dec 2014
32KernelVersion: 3.20
33Description: Terminal descriptors
34
35What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/output
36Date: Dec 2014
37KernelVersion: 3.20
38Description: Output terminal descriptors
39
40What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/output/default
41Date: Dec 2014
42KernelVersion: 3.20
43Description: Default output terminal descriptors
44
45 All attributes read only:
46 iTerminal - index of string descriptor
47 bSourceID - id of the terminal to which this terminal
48 is connected
49 bAssocTerminal - id of the input terminal to which this output
50 terminal is associated
51 wTerminalType - terminal type
52 bTerminalID - a non-zero id of this terminal
53
54What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/camera
55Date: Dec 2014
56KernelVersion: 3.20
57Description: Camera terminal descriptors
58
59What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/camera/default
60Date: Dec 2014
61KernelVersion: 3.20
62Description: Default camera terminal descriptors
63
64 All attributes read only:
65 bmControls - bitmap specifying which controls are
66 supported for the video stream
67 wOcularFocalLength - the value of Locular
68 wObjectiveFocalLengthMax- the value of Lmin
69 wObjectiveFocalLengthMin- the value of Lmax
70 iTerminal - index of string descriptor
71 bAssocTerminal - id of the output terminal to which
72 this terminal is connected
73 wTerminalType - terminal type
74 bTerminalID - a non-zero id of this terminal
75
76What: /config/usb-gadget/gadget/functions/uvc.name/control/processing
77Date: Dec 2014
78KernelVersion: 3.20
79Description: Processing unit descriptors
80
81What: /config/usb-gadget/gadget/functions/uvc.name/control/processing/default
82Date: Dec 2014
83KernelVersion: 3.20
84Description: Default processing unit descriptors
85
86 All attributes read only:
87 iProcessing - index of string descriptor
88 bmControls - bitmap specifying which controls are
89 supported for the video stream
90 wMaxMultiplier - maximum digital magnification x100
91 bSourceID - id of the terminal to which this unit is
92 connected
93 bUnitID - a non-zero id of this unit
94
95What: /config/usb-gadget/gadget/functions/uvc.name/control/header
96Date: Dec 2014
97KernelVersion: 3.20
98Description: Control header descriptors
99
100What: /config/usb-gadget/gadget/functions/uvc.name/control/header/name
101Date: Dec 2014
102KernelVersion: 3.20
103Description: Specific control header descriptors
104
105dwClockFrequency
106bcdUVC
107What: /config/usb-gadget/gadget/functions/uvc.name/streaming
108Date: Dec 2014
109KernelVersion: 3.20
110Description: Streaming descriptors
111
112What: /config/usb-gadget/gadget/functions/uvc.name/streaming/class
113Date: Dec 2014
114KernelVersion: 3.20
115Description: Streaming class descriptors
116
117What: /config/usb-gadget/gadget/functions/uvc.name/streaming/class/ss
118Date: Dec 2014
119KernelVersion: 3.20
120Description: Super speed streaming class descriptors
121
122What: /config/usb-gadget/gadget/functions/uvc.name/streaming/class/hs
123Date: Dec 2014
124KernelVersion: 3.20
125Description: High speed streaming class descriptors
126
127What: /config/usb-gadget/gadget/functions/uvc.name/streaming/class/fs
128Date: Dec 2014
129KernelVersion: 3.20
130Description: Full speed streaming class descriptors
131
132What: /config/usb-gadget/gadget/functions/uvc.name/streaming/color_matching
133Date: Dec 2014
134KernelVersion: 3.20
135Description: Color matching descriptors
136
137What: /config/usb-gadget/gadget/functions/uvc.name/streaming/color_matching/default
138Date: Dec 2014
139KernelVersion: 3.20
140Description: Default color matching descriptors
141
142 All attributes read only:
143 bMatrixCoefficients - matrix used to compute luma and
144 chroma values from the color primaries
145 bTransferCharacteristics- optoelectronic transfer
146 characteristic of the source picutre,
147 also called the gamma function
148 bColorPrimaries - color primaries and the reference
149 white
150
151What: /config/usb-gadget/gadget/functions/uvc.name/streaming/mjpeg
152Date: Dec 2014
153KernelVersion: 3.20
154Description: MJPEG format descriptors
155
156What: /config/usb-gadget/gadget/functions/uvc.name/streaming/mjpeg/name
157Date: Dec 2014
158KernelVersion: 3.20
159Description: Specific MJPEG format descriptors
160
161 All attributes read only,
162 except bmaControls and bDefaultFrameIndex:
163 bmaControls - this format's data for bmaControls in
164 the streaming header
165 bmInterfaceFlags - specifies interlace information,
166 read-only
167 bAspectRatioY - the X dimension of the picture aspect
168 ratio, read-only
169 bAspectRatioX - the Y dimension of the picture aspect
170 ratio, read-only
171 bmFlags - characteristics of this format,
172 read-only
173 bDefaultFrameIndex - optimum frame index for this stream
174
175What: /config/usb-gadget/gadget/functions/uvc.name/streaming/mjpeg/name/name
176Date: Dec 2014
177KernelVersion: 3.20
178Description: Specific MJPEG frame descriptors
179
180 dwFrameInterval - indicates how frame interval can be
181 programmed; a number of values
182 separated by newline can be specified
183 dwDefaultFrameInterval - the frame interval the device would
184 like to use as default
185 dwMaxVideoFrameBufferSize- the maximum number of bytes the
186 compressor will produce for a video
187 frame or still image
188 dwMaxBitRate - the maximum bit rate at the shortest
189 frame interval in bps
190 dwMinBitRate - the minimum bit rate at the longest
191 frame interval in bps
192 wHeight - height of decoded bitmap frame in px
193 wWidth - width of decoded bitmam frame in px
194 bmCapabilities - still image support, fixed frame-rate
195 support
196
197What: /config/usb-gadget/gadget/functions/uvc.name/streaming/uncompressed
198Date: Dec 2014
199KernelVersion: 3.20
200Description: Uncompressed format descriptors
201
202What: /config/usb-gadget/gadget/functions/uvc.name/streaming/uncompressed/name
203Date: Dec 2014
204KernelVersion: 3.20
205Description: Specific uncompressed format descriptors
206
207 bmaControls - this format's data for bmaControls in
208 the streaming header
209 bmInterfaceFlags - specifies interlace information,
210 read-only
211 bAspectRatioY - the X dimension of the picture aspect
212 ratio, read-only
213 bAspectRatioX - the Y dimension of the picture aspect
214 ratio, read-only
215 bDefaultFrameIndex - optimum frame index for this stream
216 bBitsPerPixel - number of bits per pixel used to
217 specify color in the decoded video
218 frame
219 guidFormat - globally unique id used to identify
220 stream-encoding format
221
222What: /config/usb-gadget/gadget/functions/uvc.name/streaming/uncompressed/name/name
223Date: Dec 2014
224KernelVersion: 3.20
225Description: Specific uncompressed frame descriptors
226
227 dwFrameInterval - indicates how frame interval can be
228 programmed; a number of values
229 separated by newline can be specified
230 dwDefaultFrameInterval - the frame interval the device would
231 like to use as default
232 dwMaxVideoFrameBufferSize- the maximum number of bytes the
233 compressor will produce for a video
234 frame or still image
235 dwMaxBitRate - the maximum bit rate at the shortest
236 frame interval in bps
237 dwMinBitRate - the minimum bit rate at the longest
238 frame interval in bps
239 wHeight - height of decoded bitmap frame in px
240 wWidth - width of decoded bitmam frame in px
241 bmCapabilities - still image support, fixed frame-rate
242 support
243
244What: /config/usb-gadget/gadget/functions/uvc.name/streaming/header
245Date: Dec 2014
246KernelVersion: 3.20
247Description: Streaming header descriptors
248
249What: /config/usb-gadget/gadget/functions/uvc.name/streaming/header/name
250Date: Dec 2014
251KernelVersion: 3.20
252Description: Specific streaming header descriptors
253
254 All attributes read only:
255 bTriggerUsage - how the host software will respond to
256 a hardware trigger interrupt event
257 bTriggerSupport - flag specifying if hardware
258 triggering is supported
259 bStillCaptureMethod - method of still image caputre
260 supported
261 bTerminalLink - id of the output terminal to which
262 the video endpoint of this interface
263 is connected
264 bmInfo - capabilities of this video streaming
265 interface
diff --git a/Documentation/ABI/testing/sysfs-bus-amba b/Documentation/ABI/testing/sysfs-bus-amba
new file mode 100644
index 000000000000..e7b54677cfbe
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-bus-amba
@@ -0,0 +1,20 @@
1What: /sys/bus/amba/devices/.../driver_override
2Date: September 2014
3Contact: Antonios Motakis <a.motakis@virtualopensystems.com>
4Description:
5 This file allows the driver for a device to be specified which
6 will override standard OF, ACPI, ID table, and name matching.
7 When specified, only a driver with a name matching the value
8 written to driver_override will have an opportunity to bind to
9 the device. The override is specified by writing a string to the
10 driver_override file (echo vfio-amba > driver_override) and may
11 be cleared with an empty string (echo > driver_override).
12 This returns the device to standard matching rules binding.
13 Writing to driver_override does not automatically unbind the
14 device from its current driver or make any attempt to
15 automatically load the specified driver. If no driver with a
16 matching name is currently loaded in the kernel, the device will
17 not bind to any driver. This also allows devices to opt-out of
18 driver binding using a driver_override name such as "none".
19 Only a single driver may be specified in the override, there is
20 no support for parsing delimiters.
diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-events b/Documentation/ABI/testing/sysfs-bus-event_source-devices-events
index 20979f8b3edb..505f080d20a1 100644
--- a/Documentation/ABI/testing/sysfs-bus-event_source-devices-events
+++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-events
@@ -52,12 +52,18 @@ Description: Per-pmu performance monitoring events specific to the running syste
52 event=0x2abc 52 event=0x2abc
53 event=0x423,inv,cmask=0x3 53 event=0x423,inv,cmask=0x3
54 domain=0x1,offset=0x8,starting_index=0xffff 54 domain=0x1,offset=0x8,starting_index=0xffff
55 domain=0x1,offset=0x8,core=?
55 56
56 Each of the assignments indicates a value to be assigned to a 57 Each of the assignments indicates a value to be assigned to a
57 particular set of bits (as defined by the format file 58 particular set of bits (as defined by the format file
58 corresponding to the <term>) in the perf_event structure passed 59 corresponding to the <term>) in the perf_event structure passed
59 to the perf_open syscall. 60 to the perf_open syscall.
60 61
62 In the case of the last example, a value replacing "?" would
63 need to be provided by the user selecting the particular event.
64 This is referred to as "event parameterization". Event
65 parameters have the format 'param=?'.
66
61What: /sys/bus/event_source/devices/<pmu>/events/<event>.unit 67What: /sys/bus/event_source/devices/<pmu>/events/<event>.unit
62Date: 2014/02/24 68Date: 2014/02/24
63Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org> 69Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7 b/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7
index 32f3f5f8bba2..f893337570c1 100644
--- a/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7
+++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7
@@ -21,3 +21,25 @@ Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
21Description: 21Description:
22 Exposes the "version" field of the 24x7 catalog. This is also 22 Exposes the "version" field of the 24x7 catalog. This is also
23 extractable from the provided binary "catalog" sysfs entry. 23 extractable from the provided binary "catalog" sysfs entry.
24
25What: /sys/bus/event_source/devices/hv_24x7/event_descs/<event-name>
26Date: February 2014
27Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
28Description:
29 Provides the description of a particular event as provided by
30 the firmware. If firmware does not provide a description, no
31 file will be created.
32
33 Note that the event-name lacks the domain suffix appended for
34 events in the events/ dir.
35
36What: /sys/bus/event_source/devices/hv_24x7/event_long_descs/<event-name>
37Date: February 2014
38Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
39Description:
40 Provides the "long" description of a particular event as
41 provided by the firmware. If firmware does not provide a
42 description, no file will be created.
43
44 Note that the event-name lacks the domain suffix appended for
45 events in the events/ dir.
diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio
index 117521dbf2b3..9a70c31619ea 100644
--- a/Documentation/ABI/testing/sysfs-bus-iio
+++ b/Documentation/ABI/testing/sysfs-bus-iio
@@ -92,6 +92,18 @@ Description:
92 is required is a consistent labeling. Units after application 92 is required is a consistent labeling. Units after application
93 of scale and offset are millivolts. 93 of scale and offset are millivolts.
94 94
95What: /sys/bus/iio/devices/iio:deviceX/in_currentY_raw
96What: /sys/bus/iio/devices/iio:deviceX/in_currentY_supply_raw
97KernelVersion: 3.17
98Contact: linux-iio@vger.kernel.org
99Description:
100 Raw (unscaled no bias removal etc.) current measurement from
101 channel Y. In special cases where the channel does not
102 correspond to externally available input one of the named
103 versions may be used. The number must always be specified and
104 unique to allow association with event codes. Units after
105 application of scale and offset are milliamps.
106
95What: /sys/bus/iio/devices/iio:deviceX/in_capacitanceY_raw 107What: /sys/bus/iio/devices/iio:deviceX/in_capacitanceY_raw
96KernelVersion: 3.2 108KernelVersion: 3.2
97Contact: linux-iio@vger.kernel.org 109Contact: linux-iio@vger.kernel.org
@@ -234,6 +246,8 @@ What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_offset
234What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_offset 246What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_offset
235What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_offset 247What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_offset
236What: /sys/bus/iio/devices/iio:deviceX/in_voltage_offset 248What: /sys/bus/iio/devices/iio:deviceX/in_voltage_offset
249What: /sys/bus/iio/devices/iio:deviceX/in_currentY_offset
250What: /sys/bus/iio/devices/iio:deviceX/in_current_offset
237What: /sys/bus/iio/devices/iio:deviceX/in_tempY_offset 251What: /sys/bus/iio/devices/iio:deviceX/in_tempY_offset
238What: /sys/bus/iio/devices/iio:deviceX/in_temp_offset 252What: /sys/bus/iio/devices/iio:deviceX/in_temp_offset
239What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_offset 253What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_offset
@@ -262,9 +276,14 @@ What: /sys/bus/iio/devices/iio:deviceX/in_voltage_scale
262What: /sys/bus/iio/devices/iio:deviceX/in_voltage-voltage_scale 276What: /sys/bus/iio/devices/iio:deviceX/in_voltage-voltage_scale
263What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_scale 277What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_scale
264What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_scale 278What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_scale
279What: /sys/bus/iio/devices/iio:deviceX/in_currentY_scale
280What: /sys/bus/iio/devices/iio:deviceX/in_currentY_supply_scale
281What: /sys/bus/iio/devices/iio:deviceX/in_current_scale
265What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale 282What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale
266What: /sys/bus/iio/devices/iio:deviceX/in_accel_peak_scale 283What: /sys/bus/iio/devices/iio:deviceX/in_accel_peak_scale
267What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_scale 284What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_scale
285What: /sys/bus/iio/devices/iio:deviceX/in_energy_scale
286What: /sys/bus/iio/devices/iio:deviceX/in_distance_scale
268What: /sys/bus/iio/devices/iio:deviceX/in_magn_scale 287What: /sys/bus/iio/devices/iio:deviceX/in_magn_scale
269What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_scale 288What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_scale
270What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_scale 289What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_scale
@@ -276,6 +295,7 @@ What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_true_tilt_comp_scale
276What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_scale 295What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_scale
277What: /sys/bus/iio/devices/iio:deviceX/in_pressure_scale 296What: /sys/bus/iio/devices/iio:deviceX/in_pressure_scale
278What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_scale 297What: /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
279KernelVersion: 2.6.35 299KernelVersion: 2.6.35
280Contact: linux-iio@vger.kernel.org 300Contact: linux-iio@vger.kernel.org
281Description: 301Description:
@@ -323,6 +343,44 @@ Description:
323 production inaccuracies). If shared across all channels, 343 production inaccuracies). If shared across all channels,
324 <type>_calibscale is used. 344 <type>_calibscale is used.
325 345
346What: /sys/bus/iio/devices/iio:deviceX/in_activity_calibgender
347What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibgender
348What: /sys/bus/iio/devices/iio:deviceX/in_distance_calibgender
349What: /sys/bus/iio/devices/iio:deviceX/in_velocity_calibgender
350KernelVersion: 3.20
351Contact: linux-iio@vger.kernel.org
352Description:
353 Gender of the user (e.g.: male, female) used by some pedometers
354 to compute the stride length, distance, speed and activity
355 type.
356
357What: /sys/bus/iio/devices/iio:deviceX/in_activity_calibgender_available
358What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibgender_available
359What: /sys/bus/iio/devices/iio:deviceX/in_distance_calibgender_available
360What: /sys/bus/iio/devices/iio:deviceX/in_velocity_calibgender_available
361KernelVersion: 3.20
362Contact: linux-iio@vger.kernel.org
363Description:
364 Lists all available gender values (e.g.: male, female).
365
366What: /sys/bus/iio/devices/iio:deviceX/in_activity_calibheight
367What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibheight
368What: /sys/bus/iio/devices/iio:deviceX/in_distance_calibheight
369What: /sys/bus/iio/devices/iio:deviceX/in_velocity_calibheight
370KernelVersion: 3.19
371Contact: linux-iio@vger.kernel.org
372Description:
373 Height of the user (in meters) used by some pedometers
374 to compute the stride length, distance, speed and activity
375 type.
376
377What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibweight
378KernelVersion: 3.20
379Contact: linux-iio@vger.kernel.org
380Description:
381 Weight of the user (in kg). It is needed by some pedometers
382 to compute the calories burnt by the user.
383
326What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale_available 384What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale_available
327What: /sys/.../iio:deviceX/in_voltageX_scale_available 385What: /sys/.../iio:deviceX/in_voltageX_scale_available
328What: /sys/.../iio:deviceX/in_voltage-voltage_scale_available 386What: /sys/.../iio:deviceX/in_voltage-voltage_scale_available
@@ -783,6 +841,14 @@ What: /sys/.../events/in_tempY_roc_falling_period
783What: /sys/.../events/in_accel_x&y&z_mag_falling_period 841What: /sys/.../events/in_accel_x&y&z_mag_falling_period
784What: /sys/.../events/in_intensity0_thresh_period 842What: /sys/.../events/in_intensity0_thresh_period
785What: /sys/.../events/in_proximity0_thresh_period 843What: /sys/.../events/in_proximity0_thresh_period
844What: /sys/.../events/in_activity_still_thresh_rising_period
845What: /sys/.../events/in_activity_still_thresh_falling_period
846What: /sys/.../events/in_activity_walking_thresh_rising_period
847What: /sys/.../events/in_activity_walking_thresh_falling_period
848What: /sys/.../events/in_activity_jogging_thresh_rising_period
849What: /sys/.../events/in_activity_jogging_thresh_falling_period
850What: /sys/.../events/in_activity_running_thresh_rising_period
851What: /sys/.../events/in_activity_running_thresh_falling_period
786KernelVersion: 2.6.37 852KernelVersion: 2.6.37
787Contact: linux-iio@vger.kernel.org 853Contact: linux-iio@vger.kernel.org
788Description: 854Description:
@@ -790,6 +856,40 @@ Description:
790 met before an event is generated. If direction is not 856 met before an event is generated. If direction is not
791 specified then this period applies to both directions. 857 specified then this period applies to both directions.
792 858
859What: /sys/.../events/in_activity_still_thresh_rising_en
860What: /sys/.../events/in_activity_still_thresh_falling_en
861What: /sys/.../events/in_activity_walking_thresh_rising_en
862What: /sys/.../events/in_activity_walking_thresh_falling_en
863What: /sys/.../events/in_activity_jogging_thresh_rising_en
864What: /sys/.../events/in_activity_jogging_thresh_falling_en
865What: /sys/.../events/in_activity_running_thresh_rising_en
866What: /sys/.../events/in_activity_running_thresh_falling_en
867KernelVersion: 3.19
868Contact: linux-iio@vger.kernel.org
869Description:
870 Enables or disables activitity events. Depending on direction
871 an event is generated when sensor ENTERS or LEAVES a given state.
872
873What: /sys/.../events/in_activity_still_thresh_rising_value
874What: /sys/.../events/in_activity_still_thresh_falling_value
875What: /sys/.../events/in_activity_walking_thresh_rising_value
876What: /sys/.../events/in_activity_walking_thresh_falling_value
877What: /sys/.../events/in_activity_jogging_thresh_rising_value
878What: /sys/.../events/in_activity_jogging_thresh_falling_value
879What: /sys/.../events/in_activity_running_thresh_rising_value
880What: /sys/.../events/in_activity_running_thresh_falling_value
881KernelVersion: 3.19
882Contact: linux-iio@vger.kernel.org
883Description:
884 Confidence value (in units as percentage) to be used
885 for deciding when an event should be generated. E.g for
886 running: If the confidence value reported by the sensor
887 is greater than in_activity_running_thresh_rising_value
888 then the sensor ENTERS running state. Conversely, if the
889 confidence value reported by the sensor is lower than
890 in_activity_running_thresh_falling_value then the sensor
891 is LEAVING running state.
892
793What: /sys/.../iio:deviceX/events/in_accel_mag_en 893What: /sys/.../iio:deviceX/events/in_accel_mag_en
794What: /sys/.../iio:deviceX/events/in_accel_mag_rising_en 894What: /sys/.../iio:deviceX/events/in_accel_mag_rising_en
795What: /sys/.../iio:deviceX/events/in_accel_mag_falling_en 895What: /sys/.../iio:deviceX/events/in_accel_mag_falling_en
@@ -822,6 +922,25 @@ Description:
822 number or direction is not specified, applies to all channels of 922 number or direction is not specified, applies to all channels of
823 this type. 923 this type.
824 924
925What: /sys/.../events/in_steps_change_en
926KernelVersion: 3.20
927Contact: linux-iio@vger.kernel.org
928Description:
929 Event generated when channel passes a threshold on the absolute
930 change in value. E.g. for steps: a step change event is
931 generated each time the user takes N steps, where N is set using
932 in_steps_change_value.
933
934What: /sys/.../events/in_steps_change_value
935KernelVersion: 3.20
936Contact: linux-iio@vger.kernel.org
937Description:
938 Specifies the value of change threshold that the
939 device is comparing against for the events enabled by
940 <type>[Y][_name]_roc[_rising|falling|]_en. E.g. for steps:
941 if set to 3, a step change event will be generated every 3
942 steps.
943
825What: /sys/bus/iio/devices/iio:deviceX/trigger/current_trigger 944What: /sys/bus/iio/devices/iio:deviceX/trigger/current_trigger
826KernelVersion: 2.6.35 945KernelVersion: 2.6.35
827Contact: linux-iio@vger.kernel.org 946Contact: linux-iio@vger.kernel.org
@@ -956,6 +1075,16 @@ Description:
956 and the relevant _type attributes to establish the data storage 1075 and the relevant _type attributes to establish the data storage
957 format. 1076 format.
958 1077
1078What: /sys/.../iio:deviceX/in_activity_still_input
1079What: /sys/.../iio:deviceX/in_activity_walking_input
1080What: /sys/.../iio:deviceX/in_activity_jogging_input
1081What: /sys/.../iio:deviceX/in_activity_running_input
1082KernelVersion: 3.19
1083Contact: linux-iio@vger.kernel.org
1084Description:
1085 This attribute is used to read the confidence for an activity
1086 expressed in units as percentage.
1087
959What: /sys/.../iio:deviceX/in_anglvel_z_quadrature_correction_raw 1088What: /sys/.../iio:deviceX/in_anglvel_z_quadrature_correction_raw
960KernelVersion: 2.6.38 1089KernelVersion: 2.6.38
961Contact: linux-iio@vger.kernel.org 1090Contact: linux-iio@vger.kernel.org
@@ -973,6 +1102,24 @@ Description:
973 For a list of available output power modes read 1102 For a list of available output power modes read
974 in_accel_power_mode_available. 1103 in_accel_power_mode_available.
975 1104
1105What: /sys/.../iio:deviceX/in_energy_input
1106What: /sys/.../iio:deviceX/in_energy_raw
1107KernelVersion: 3.20
1108Contact: linux-iio@vger.kernel.org
1109Description:
1110 This attribute is used to read the energy value reported by the
1111 device (e.g.: human activity sensors report energy burnt by the
1112 user). Units after application of scale are Joules.
1113
1114What: /sys/.../iio:deviceX/in_distance_input
1115What: /sys/.../iio:deviceX/in_distance_raw
1116KernelVersion: 3.20
1117Contact: linux-iio@vger.kernel.org
1118Description:
1119 This attribute is used to read the distance covered by the user
1120 since the last reboot while activated. Units after application
1121 of scale are meters.
1122
976What: /sys/bus/iio/devices/iio:deviceX/store_eeprom 1123What: /sys/bus/iio/devices/iio:deviceX/store_eeprom
977KernelVersion: 3.4.0 1124KernelVersion: 3.4.0
978Contact: linux-iio@vger.kernel.org 1125Contact: linux-iio@vger.kernel.org
@@ -992,7 +1139,9 @@ Description:
992 reflectivity of infrared or ultrasound emitted. 1139 reflectivity of infrared or ultrasound emitted.
993 Often these sensors are unit less and as such conversion 1140 Often these sensors are unit less and as such conversion
994 to SI units is not possible. Where it is, the units should 1141 to SI units is not possible. Where it is, the units should
995 be meters. 1142 be meters. If such a conversion is not possible, the reported
1143 values should behave in the same way as a distance, i.e. lower
1144 values indicate something is closer to the sensor.
996 1145
997What: /sys/.../iio:deviceX/in_illuminanceY_input 1146What: /sys/.../iio:deviceX/in_illuminanceY_input
998What: /sys/.../iio:deviceX/in_illuminanceY_raw 1147What: /sys/.../iio:deviceX/in_illuminanceY_raw
@@ -1024,6 +1173,12 @@ Description:
1024 This attribute is used to get/set the integration time in 1173 This attribute is used to get/set the integration time in
1025 seconds. 1174 seconds.
1026 1175
1176What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_integration_time
1177KernelVersion: 3.20
1178Contact: linux-iio@vger.kernel.org
1179Description:
1180 Number of seconds in which to compute speed.
1181
1027What: /sys/bus/iio/devices/iio:deviceX/in_rot_quaternion_raw 1182What: /sys/bus/iio/devices/iio:deviceX/in_rot_quaternion_raw
1028KernelVersion: 3.15 1183KernelVersion: 3.15
1029Contact: linux-iio@vger.kernel.org 1184Contact: linux-iio@vger.kernel.org
@@ -1051,3 +1206,46 @@ Description:
1051 after application of scale and offset. If no offset or scale is 1206 after application of scale and offset. If no offset or scale is
1052 present, output should be considered as processed with the 1207 present, output should be considered as processed with the
1053 unit in milliamps. 1208 unit in milliamps.
1209
1210What: /sys/.../iio:deviceX/in_energy_en
1211What: /sys/.../iio:deviceX/in_distance_en
1212What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_en
1213What: /sys/.../iio:deviceX/in_steps_en
1214KernelVersion: 3.19
1215Contact: linux-iio@vger.kernel.org
1216Description:
1217 Activates a device feature that runs in firmware/hardware.
1218 E.g. for steps: the pedometer saves power while not used;
1219 when activated, it will count the steps taken by the user in
1220 firmware and export them through in_steps_input.
1221
1222What: /sys/.../iio:deviceX/in_steps_input
1223KernelVersion: 3.19
1224Contact: linux-iio@vger.kernel.org
1225Description:
1226 This attribute is used to read the number of steps taken by the user
1227 since the last reboot while activated.
1228
1229What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_input
1230What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_raw
1231KernelVersion: 3.19
1232Contact: linux-iio@vger.kernel.org
1233Description:
1234 This attribute is used to read the current speed value of the
1235 user (which is the norm or magnitude of the velocity vector).
1236 Units after application of scale are m/s.
1237
1238What: /sys/.../iio:deviceX/in_steps_debounce_count
1239KernelVersion: 3.20
1240Contact: linux-iio@vger.kernel.org
1241Description:
1242 Specifies the number of steps that must occur within
1243 in_steps_filter_debounce_time for the pedometer to decide the
1244 consumer is making steps.
1245
1246What: /sys/.../iio:deviceX/in_steps_debounce_time
1247KernelVersion: 3.20
1248Contact: linux-iio@vger.kernel.org
1249Description:
1250 Specifies number of seconds in which we compute the steps
1251 that occur in order to decide if the consumer is making steps.
diff --git a/Documentation/ABI/testing/sysfs-class-cxl b/Documentation/ABI/testing/sysfs-class-cxl
index 554405ec1955..3680364b4048 100644
--- a/Documentation/ABI/testing/sysfs-class-cxl
+++ b/Documentation/ABI/testing/sysfs-class-cxl
@@ -1,3 +1,9 @@
1Note: Attributes that are shared between devices are stored in the directory
2pointed to by the symlink device/.
3Example: The real path of the attribute /sys/class/cxl/afu0.0s/irqs_max is
4/sys/class/cxl/afu0.0s/device/irqs_max, i.e. /sys/class/cxl/afu0.0/irqs_max.
5
6
1Slave contexts (eg. /sys/class/cxl/afu0.0s): 7Slave contexts (eg. /sys/class/cxl/afu0.0s):
2 8
3What: /sys/class/cxl/<afu>/irqs_max 9What: /sys/class/cxl/<afu>/irqs_max
@@ -67,7 +73,7 @@ Contact: linuxppc-dev@lists.ozlabs.org
67Description: read only 73Description: read only
68 Decimal value of the current version of the kernel/user API. 74 Decimal value of the current version of the kernel/user API.
69 75
70What: /sys/class/cxl/<afu>/api_version_com 76What: /sys/class/cxl/<afu>/api_version_compatible
71Date: September 2014 77Date: September 2014
72Contact: linuxppc-dev@lists.ozlabs.org 78Contact: linuxppc-dev@lists.ozlabs.org
73Description: read only 79Description: read only
@@ -75,6 +81,42 @@ Description: read only
75 this this kernel supports. 81 this this kernel supports.
76 82
77 83
84AFU configuration records (eg. /sys/class/cxl/afu0.0/cr0):
85
86An AFU may optionally export one or more PCIe like configuration records, known
87as AFU configuration records, which will show up here (if present).
88
89What: /sys/class/cxl/<afu>/cr<config num>/vendor
90Date: February 2015
91Contact: linuxppc-dev@lists.ozlabs.org
92Description: read only
93 Hexadecimal value of the vendor ID found in this AFU
94 configuration record.
95
96What: /sys/class/cxl/<afu>/cr<config num>/device
97Date: February 2015
98Contact: linuxppc-dev@lists.ozlabs.org
99Description: read only
100 Hexadecimal value of the device ID found in this AFU
101 configuration record.
102
103What: /sys/class/cxl/<afu>/cr<config num>/vendor
104Date: February 2015
105Contact: linuxppc-dev@lists.ozlabs.org
106Description: read only
107 Hexadecimal value of the class code found in this AFU
108 configuration record.
109
110What: /sys/class/cxl/<afu>/cr<config num>/config
111Date: February 2015
112Contact: linuxppc-dev@lists.ozlabs.org
113Description: read only
114 This binary file provides raw access to the AFU configuration
115 record. The format is expected to match the either the standard
116 or extended configuration space defined by the PCIe
117 specification.
118
119
78 120
79Master contexts (eg. /sys/class/cxl/afu0.0m) 121Master contexts (eg. /sys/class/cxl/afu0.0m)
80 122
@@ -106,7 +148,7 @@ Contact: linuxppc-dev@lists.ozlabs.org
106Description: read only 148Description: read only
107 Identifies the CAIA Version the card implements. 149 Identifies the CAIA Version the card implements.
108 150
109What: /sys/class/cxl/<card>/psl_version 151What: /sys/class/cxl/<card>/psl_revision
110Date: September 2014 152Date: September 2014
111Contact: linuxppc-dev@lists.ozlabs.org 153Contact: linuxppc-dev@lists.ozlabs.org
112Description: read only 154Description: read only
@@ -127,3 +169,24 @@ Contact: linuxppc-dev@lists.ozlabs.org
127Description: read only 169Description: read only
128 Will return "user" or "factory" depending on the image loaded 170 Will return "user" or "factory" depending on the image loaded
129 onto the card. 171 onto the card.
172
173What: /sys/class/cxl/<card>/load_image_on_perst
174Date: December 2014
175Contact: linuxppc-dev@lists.ozlabs.org
176Description: read/write
177 Valid entries are "none", "user", and "factory".
178 "none" means PERST will not cause image to be loaded to the
179 card. A power cycle is required to load the image.
180 "none" could be useful for debugging because the trace arrays
181 are preserved.
182 "user" and "factory" means PERST will cause either the user or
183 user or factory image to be loaded.
184 Default is to reload on PERST whichever image the card has
185 loaded.
186
187What: /sys/class/cxl/<card>/reset
188Date: October 2014
189Contact: linuxppc-dev@lists.ozlabs.org
190Description: write only
191 Writing 1 will issue a PERST to card which may cause the card
192 to reload the FPGA depending on load_image_on_perst.
diff --git a/Documentation/ABI/testing/sysfs-class-mei b/Documentation/ABI/testing/sysfs-class-mei
index 0ec8b8178c41..80d9888a8ece 100644
--- a/Documentation/ABI/testing/sysfs-class-mei
+++ b/Documentation/ABI/testing/sysfs-class-mei
@@ -14,3 +14,18 @@ Description:
14 The /sys/class/mei/meiN directory is created for 14 The /sys/class/mei/meiN directory is created for
15 each probed mei device 15 each probed mei device
16 16
17What: /sys/class/mei/meiN/fw_status
18Date: Nov 2014
19KernelVersion: 3.19
20Contact: Tomas Winkler <tomas.winkler@intel.com>
21Description: Display fw status registers content
22
23 The ME FW writes its status information into fw status
24 registers for BIOS and OS to monitor fw health.
25
26 The register contains running state, power management
27 state, error codes, and others. The way the registers
28 are decoded depends on PCH or SoC generation.
29 Also number of registers varies between 1 and 6
30 depending on generation.
31
diff --git a/Documentation/ABI/testing/sysfs-class-power b/Documentation/ABI/testing/sysfs-class-power
index 909e7602c717..369d2a2d7d3e 100644
--- a/Documentation/ABI/testing/sysfs-class-power
+++ b/Documentation/ABI/testing/sysfs-class-power
@@ -32,3 +32,45 @@ Description:
32 Valid values: 32 Valid values:
33 - 5, 6 or 7 (hours), 33 - 5, 6 or 7 (hours),
34 - 0: disabled. 34 - 0: disabled.
35
36What: /sys/class/power_supply/max77693-charger/device/fast_charge_timer
37Date: January 2015
38KernelVersion: 3.19.0
39Contact: Krzysztof Kozlowski <k.kozlowski@samsung.com>
40Description:
41 This entry shows and sets the maximum time the max77693
42 charger operates in fast-charge mode. When the timer expires
43 the device will terminate fast-charge mode (charging current
44 will drop to 0 A) and will trigger interrupt.
45
46 Valid values:
47 - 4 - 16 (hours), step by 2 (rounded down)
48 - 0: disabled.
49
50What: /sys/class/power_supply/max77693-charger/device/top_off_threshold_current
51Date: January 2015
52KernelVersion: 3.19.0
53Contact: Krzysztof Kozlowski <k.kozlowski@samsung.com>
54Description:
55 This entry shows and sets the charging current threshold for
56 entering top-off charging mode. When charging current in fast
57 charge mode drops below this value, the charger will trigger
58 interrupt and start top-off charging mode.
59
60 Valid values:
61 - 100000 - 200000 (microamps), step by 25000 (rounded down)
62 - 200000 - 350000 (microamps), step by 50000 (rounded down)
63 - 0: disabled.
64
65What: /sys/class/power_supply/max77693-charger/device/top_off_timer
66Date: January 2015
67KernelVersion: 3.19.0
68Contact: Krzysztof Kozlowski <k.kozlowski@samsung.com>
69Description:
70 This entry shows and sets the maximum time the max77693
71 charger operates in top-off charge mode. When the timer expires
72 the device will terminate top-off charge mode (charging current
73 will drop to 0 A) and will trigger interrupt.
74
75 Valid values:
76 - 0 - 70 (minutes), step by 10 (rounded down)
diff --git a/Documentation/ABI/testing/sysfs-driver-input-axp-pek b/Documentation/ABI/testing/sysfs-driver-input-axp-pek
new file mode 100644
index 000000000000..a5e671b9fa79
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-driver-input-axp-pek
@@ -0,0 +1,11 @@
1What: /sys/class/input/input(x)/device/startup
2Date: March 2014
3Contact: Carlo Caione <carlo@caione.org>
4Description: Startup time in us. Board is powered on if the button is pressed
5 for more than <startup_time>
6
7What: /sys/class/input/input(x)/device/shutdown
8Date: March 2014
9Contact: Carlo Caione <carlo@caione.org>
10Description: Shutdown time in us. Board is powered off if the button is pressed
11 for more than <shutdown_time>
diff --git a/Documentation/ABI/testing/sysfs-driver-samsung-laptop b/Documentation/ABI/testing/sysfs-driver-samsung-laptop
index 678819a3f8bf..63c1ad0212fc 100644
--- a/Documentation/ABI/testing/sysfs-driver-samsung-laptop
+++ b/Documentation/ABI/testing/sysfs-driver-samsung-laptop
@@ -35,3 +35,11 @@ Contact: Corentin Chary <corentin.chary@gmail.com>
35Description: Use your USB ports to charge devices, even 35Description: Use your USB ports to charge devices, even
36 when your laptop is powered off. 36 when your laptop is powered off.
37 1 means enabled, 0 means disabled. 37 1 means enabled, 0 means disabled.
38
39What: /sys/devices/platform/samsung/lid_handling
40Date: December 11, 2014
41KernelVersion: 3.19
42Contact: Julijonas Kikutis <julijonas.kikutis@gmail.com>
43Description: Some Samsung laptops handle lid closing quicker and
44 only handle lid opening with this mode enabled.
45 1 means enabled, 0 means disabled.
diff --git a/Documentation/ABI/testing/sysfs-driver-toshiba_acpi b/Documentation/ABI/testing/sysfs-driver-toshiba_acpi
new file mode 100644
index 000000000000..ca9c71a531c5
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-driver-toshiba_acpi
@@ -0,0 +1,114 @@
1What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_backlight_mode
2Date: June 8, 2014
3KernelVersion: 3.15
4Contact: Azael Avalos <coproscefalo@gmail.com>
5Description: This file controls the keyboard backlight operation mode, valid
6 values are:
7 * 0x1 -> FN-Z
8 * 0x2 -> AUTO (also called TIMER)
9 * 0x8 -> ON
10 * 0x10 -> OFF
11 Note that the kernel 3.16 onwards this file accepts all listed
12 parameters, kernel 3.15 only accepts the first two (FN-Z and
13 AUTO).
14Users: KToshiba
15
16What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_backlight_timeout
17Date: June 8, 2014
18KernelVersion: 3.15
19Contact: Azael Avalos <coproscefalo@gmail.com>
20Description: This file controls the timeout of the keyboard backlight
21 whenever the operation mode is set to AUTO (or TIMER),
22 valid values range from 0-60.
23 Note that the kernel 3.15 only had support for the first
24 keyboard type, the kernel 3.16 added support for the second
25 type and the range accepted for type 2 is 1-60.
26 See the entry named "kbd_type"
27Users: KToshiba
28
29What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/position
30Date: June 8, 2014
31KernelVersion: 3.15
32Contact: Azael Avalos <coproscefalo@gmail.com>
33Description: This file shows the absolute position of the built-in
34 accelereometer.
35
36What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/touchpad
37Date: June 8, 2014
38KernelVersion: 3.15
39Contact: Azael Avalos <coproscefalo@gmail.com>
40Description: This files controls the status of the touchpad and pointing
41 stick (if available), valid values are:
42 * 0 -> OFF
43 * 1 -> ON
44Users: KToshiba
45
46What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/available_kbd_modes
47Date: August 3, 2014
48KernelVersion: 3.16
49Contact: Azael Avalos <coproscefalo@gmail.com>
50Description: This file shows the supported keyboard backlight modes
51 the system supports, which can be:
52 * 0x1 -> FN-Z
53 * 0x2 -> AUTO (also called TIMER)
54 * 0x8 -> ON
55 * 0x10 -> OFF
56 Note that not all keyboard types support the listed modes.
57 See the entry named "available_kbd_modes"
58Users: KToshiba
59
60What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_type
61Date: August 3, 2014
62KernelVersion: 3.16
63Contact: Azael Avalos <coproscefalo@gmail.com>
64Description: This file shows the current keyboard backlight type,
65 which can be:
66 * 1 -> Type 1, supporting modes FN-Z and AUTO
67 * 2 -> Type 2, supporting modes TIMER, ON and OFF
68Users: KToshiba
69
70What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/version
71Date: February, 2015
72KernelVersion: 3.20
73Contact: Azael Avalos <coproscefalo@gmail.com>
74Description: This file shows the current version of the driver
75
76What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/fan
77Date: February, 2015
78KernelVersion: 3.20
79Contact: Azael Avalos <coproscefalo@gmail.com>
80Description: This file controls the state of the internal fan, valid
81 values are:
82 * 0 -> OFF
83 * 1 -> ON
84
85What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_function_keys
86Date: February, 2015
87KernelVersion: 3.20
88Contact: Azael Avalos <coproscefalo@gmail.com>
89Description: This file controls the Special Functions (hotkeys) operation
90 mode, valid values are:
91 * 0 -> Normal Operation
92 * 1 -> Special Functions
93 In the "Normal Operation" mode, the F{1-12} keys are as usual
94 and the hotkeys are accessed via FN-F{1-12}.
95 In the "Special Functions" mode, the F{1-12} keys trigger the
96 hotkey and the F{1-12} keys are accessed via FN-F{1-12}.
97
98What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/panel_power_on
99Date: February, 2015
100KernelVersion: 3.20
101Contact: Azael Avalos <coproscefalo@gmail.com>
102Description: This file controls whether the laptop should turn ON whenever
103 the LID is opened, valid values are:
104 * 0 -> Disabled
105 * 1 -> Enabled
106
107What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_three
108Date: February, 2015
109KernelVersion: 3.20
110Contact: Azael Avalos <coproscefalo@gmail.com>
111Description: This file controls whether the USB 3 functionality, valid
112 values are:
113 * 0 -> Disabled (Acts as a regular USB 2)
114 * 1 -> Enabled (Full USB 3 functionality)
diff --git a/Documentation/ABI/testing/sysfs-fs-f2fs b/Documentation/ABI/testing/sysfs-fs-f2fs
index 6f9157f16725..2c4cc42006e8 100644
--- a/Documentation/ABI/testing/sysfs-fs-f2fs
+++ b/Documentation/ABI/testing/sysfs-fs-f2fs
@@ -74,3 +74,9 @@ Date: March 2014
74Contact: "Jaegeuk Kim" <jaegeuk.kim@samsung.com> 74Contact: "Jaegeuk Kim" <jaegeuk.kim@samsung.com>
75Description: 75Description:
76 Controls the memory footprint used by f2fs. 76 Controls the memory footprint used by f2fs.
77
78What: /sys/fs/f2fs/<disk>/trim_sections
79Date: February 2015
80Contact: "Jaegeuk Kim" <jaegeuk@kernel.org>
81Description:
82 Controls the trimming rate in batch mode.
diff --git a/Documentation/ABI/testing/sysfs-kernel-livepatch b/Documentation/ABI/testing/sysfs-kernel-livepatch
new file mode 100644
index 000000000000..5bf42a840b22
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-kernel-livepatch
@@ -0,0 +1,44 @@
1What: /sys/kernel/livepatch
2Date: Nov 2014
3KernelVersion: 3.19.0
4Contact: live-patching@vger.kernel.org
5Description:
6 Interface for kernel live patching
7
8 The /sys/kernel/livepatch directory contains subdirectories for
9 each loaded live patch module.
10
11What: /sys/kernel/livepatch/<patch>
12Date: Nov 2014
13KernelVersion: 3.19.0
14Contact: live-patching@vger.kernel.org
15Description:
16 The patch directory contains subdirectories for each kernel
17 object (vmlinux or a module) in which it patched functions.
18
19What: /sys/kernel/livepatch/<patch>/enabled
20Date: Nov 2014
21KernelVersion: 3.19.0
22Contact: live-patching@vger.kernel.org
23Description:
24 A writable attribute that indicates whether the patched
25 code is currently applied. Writing 0 will disable the patch
26 while writing 1 will re-enable the patch.
27
28What: /sys/kernel/livepatch/<patch>/<object>
29Date: Nov 2014
30KernelVersion: 3.19.0
31Contact: live-patching@vger.kernel.org
32Description:
33 The object directory contains subdirectories for each function
34 that is patched within the object.
35
36What: /sys/kernel/livepatch/<patch>/<object>/<function>
37Date: Nov 2014
38KernelVersion: 3.19.0
39Contact: live-patching@vger.kernel.org
40Description:
41 The function directory contains attributes regarding the
42 properties and state of the patched function.
43
44 There are currently no such attributes.
diff --git a/Documentation/ABI/testing/sysfs-platform-dell-laptop b/Documentation/ABI/testing/sysfs-platform-dell-laptop
deleted file mode 100644
index 7969443ef0ef..000000000000
--- a/Documentation/ABI/testing/sysfs-platform-dell-laptop
+++ /dev/null
@@ -1,60 +0,0 @@
1What: /sys/class/leds/dell::kbd_backlight/als_setting
2Date: December 2014
3KernelVersion: 3.19
4Contact: Gabriele Mazzotta <gabriele.mzt@gmail.com>,
5 Pali Rohár <pali.rohar@gmail.com>
6Description:
7 This file allows to control the automatic keyboard
8 illumination mode on some systems that have an ambient
9 light sensor. Write 1 to this file to enable the auto
10 mode, 0 to disable it.
11
12What: /sys/class/leds/dell::kbd_backlight/start_triggers
13Date: December 2014
14KernelVersion: 3.19
15Contact: Gabriele Mazzotta <gabriele.mzt@gmail.com>,
16 Pali Rohár <pali.rohar@gmail.com>
17Description:
18 This file allows to control the input triggers that
19 turn on the keyboard backlight illumination that is
20 disabled because of inactivity.
21 Read the file to see the triggers available. The ones
22 enabled are preceded by '+', those disabled by '-'.
23
24 To enable a trigger, write its name preceded by '+' to
25 this file. To disable a trigger, write its name preceded
26 by '-' instead.
27
28 For example, to enable the keyboard as trigger run:
29 echo +keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers
30 To disable it:
31 echo -keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers
32
33 Note that not all the available triggers can be configured.
34
35What: /sys/class/leds/dell::kbd_backlight/stop_timeout
36Date: December 2014
37KernelVersion: 3.19
38Contact: Gabriele Mazzotta <gabriele.mzt@gmail.com>,
39 Pali Rohár <pali.rohar@gmail.com>
40Description:
41 This file allows to specify the interval after which the
42 keyboard illumination is disabled because of inactivity.
43 The timeouts are expressed in seconds, minutes, hours and
44 days, for which the symbols are 's', 'm', 'h' and 'd'
45 respectively.
46
47 To configure the timeout, write to this file a value along
48 with any the above units. If no unit is specified, the value
49 is assumed to be expressed in seconds.
50
51 For example, to set the timeout to 10 minutes run:
52 echo 10m > /sys/class/leds/dell::kbd_backlight/stop_timeout
53
54 Note that when this file is read, the returned value might be
55 expressed in a different unit than the one used when the timeout
56 was set.
57
58 Also note that only some timeouts are supported and that
59 some systems might fall back to a specific timeout in case
60 an invalid timeout is written to this file.
generated by cgit v1.2.2 (git 2.25.0) at 2024-11-27 04:29:52 -0500