Skip to content

Commit b1e50eb

Browse files
glikelyglikely
committed
Merge remote branch 'origin' into secretlab/next-spi
2 parents 0c2a2ae + 7e125f7 commit b1e50eb

File tree

6,890 files changed

+470191
-215018
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

6,890 files changed

+470191
-215018
lines changed

‎Documentation/00-INDEX

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -250,6 +250,8 @@ numastat.txt
250250
- info on how to read Numa policy hit/miss statistics in sysfs.
251251
oops-tracing.txt
252252
- how to decode those nasty internal kernel error dump messages.
253+
padata.txt
254+
- An introduction to the "padata" parallel execution API
253255
parisc/
254256
- directory with info on using Linux on PA-RISC architecture.
255257
parport.txt

‎Documentation/ABI/obsolete/sysfs-bus-usb

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
What: /sys/bus/usb/devices/.../power/level
2+
Date: March 2007
3+
KernelVersion: 2.6.21
4+
Contact: Alan Stern <[email protected]>
5+
Description:
6+
Each USB device directory will contain a file named
7+
power/level. This file holds a power-level setting for
8+
the device, either "on" or "auto".
9+
10+
"on" means that the device is not allowed to autosuspend,
11+
although normal suspends for system sleep will still
12+
be honored. "auto" means the device will autosuspend
13+
and autoresume in the usual manner, according to the
14+
capabilities of its driver.
15+
16+
During normal use, devices should be left in the "auto"
17+
level. The "on" level is meant for administrative uses.
18+
If you want to suspend a device immediately but leave it
19+
free to wake up in response to I/O requests, you should
20+
write "0" to power/autosuspend.
21+
22+
Device not capable of proper suspend and resume should be
23+
left in the "on" level. Although the USB spec requires
24+
devices to support suspend/resume, many of them do not.
25+
In fact so many don't that by default, the USB core
26+
initializes all non-hub devices in the "on" level. Some
27+
drivers may change this setting when they are bound.
28+
29+
This file is deprecated and will be removed after 2010.
30+
Use the power/control file instead; it does exactly the
31+
same thing.

‎Documentation/ABI/obsolete/sysfs-class-rfkill

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
rfkill - radio frequency (RF) connector kill switch support
2+
3+
For details to this subsystem look at Documentation/rfkill.txt.
4+
5+
What: /sys/class/rfkill/rfkill[0-9]+/state
6+
Date: 09-Jul-2007
7+
KernelVersion v2.6.22
8+
Contact: [email protected]
9+
Description: Current state of the transmitter.
10+
This file is deprecated and sheduled to be removed in 2014,
11+
because its not possible to express the 'soft and hard block'
12+
state of the rfkill driver.
13+
Values: A numeric value.
14+
0: RFKILL_STATE_SOFT_BLOCKED
15+
transmitter is turned off by software
16+
1: RFKILL_STATE_UNBLOCKED
17+
transmitter is (potentially) active
18+
2: RFKILL_STATE_HARD_BLOCKED
19+
transmitter is forced off by something outside of
20+
the driver's control.
21+
22+
What: /sys/class/rfkill/rfkill[0-9]+/claim
23+
Date: 09-Jul-2007
24+
KernelVersion v2.6.22
25+
Contact: [email protected]
26+
Description: This file is deprecated because there no longer is a way to
27+
claim just control over a single rfkill instance.
28+
This file is scheduled to be removed in 2012.
29+
Values: 0: Kernel handles events

‎Documentation/ABI/stable/sysfs-class-rfkill

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
rfkill - radio frequency (RF) connector kill switch support
2+
3+
For details to this subsystem look at Documentation/rfkill.txt.
4+
5+
For the deprecated /sys/class/rfkill/*/state and
6+
/sys/class/rfkill/*/claim knobs of this interface look in
7+
Documentation/ABI/obsolete/sysfs-class-rfkill.
8+
9+
What: /sys/class/rfkill
10+
Date: 09-Jul-2007
11+
KernelVersion: v2.6.22
12+
Contact: [email protected],
13+
Description: The rfkill class subsystem folder.
14+
Each registered rfkill driver is represented by an rfkillX
15+
subfolder (X being an integer > 0).
16+
17+
18+
What: /sys/class/rfkill/rfkill[0-9]+/name
19+
Date: 09-Jul-2007
20+
KernelVersion v2.6.22
21+
Contact: [email protected]
22+
Description: Name assigned by driver to this key (interface or driver name).
23+
Values: arbitrary string.
24+
25+
26+
What: /sys/class/rfkill/rfkill[0-9]+/type
27+
Date: 09-Jul-2007
28+
KernelVersion v2.6.22
29+
Contact: [email protected]
30+
Description: Driver type string ("wlan", "bluetooth", etc).
31+
Values: See include/linux/rfkill.h.
32+
33+
34+
What: /sys/class/rfkill/rfkill[0-9]+/persistent
35+
Date: 09-Jul-2007
36+
KernelVersion v2.6.22
37+
Contact: [email protected]
38+
Description: Whether the soft blocked state is initialised from non-volatile
39+
storage at startup.
40+
Values: A numeric value.
41+
0: false
42+
1: true
43+
44+
45+
What: /sys/class/rfkill/rfkill[0-9]+/hard
46+
Date: 12-March-2010
47+
KernelVersion v2.6.34
48+
Contact: [email protected]
49+
Description: Current hardblock state. This file is read only.
50+
Values: A numeric value.
51+
0: inactive
52+
The transmitter is (potentially) active.
53+
1: active
54+
The transmitter is forced off by something outside of
55+
the driver's control.
56+
57+
58+
What: /sys/class/rfkill/rfkill[0-9]+/soft
59+
Date: 12-March-2010
60+
KernelVersion v2.6.34
61+
Contact: [email protected]
62+
Description: Current softblock state. This file is read and write.
63+
Values: A numeric value.
64+
0: inactive
65+
The transmitter is (potentially) active.
66+
1: active
67+
The transmitter is turned off by software.

‎Documentation/ABI/testing/sysfs-bus-pci

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -133,6 +133,46 @@ Description:
133133
The symbolic link points to the PCI device sysfs entry of the
134134
Physical Function this device associates with.
135135

136+
137+
What: /sys/bus/pci/slots/...
138+
Date: April 2005 (possibly older)
139+
KernelVersion: 2.6.12 (possibly older)
140+
Contact: [email protected]
141+
Description:
142+
When the appropriate driver is loaded, it will create a
143+
directory per claimed physical PCI slot in
144+
/sys/bus/pci/slots/. The names of these directories are
145+
specific to the driver, which in turn, are specific to the
146+
platform, but in general, should match the label on the
147+
machine's physical chassis.
148+
149+
The drivers that can create slot directories include the
150+
PCI hotplug drivers, and as of 2.6.27, the pci_slot driver.
151+
152+
The slot directories contain, at a minimum, a file named
153+
'address' which contains the PCI bus:device:function tuple.
154+
Other files may appear as well, but are specific to the
155+
driver.
156+
157+
What: /sys/bus/pci/slots/.../function[0-7]
158+
Date: March 2010
159+
KernelVersion: 2.6.35
160+
Contact: [email protected]
161+
Description:
162+
If PCI slot directories (as described above) are created,
163+
and the physical slot is actually populated with a device,
164+
symbolic links in the slot directory pointing to the
165+
device's PCI functions are created as well.
166+
167+
What: /sys/bus/pci/devices/.../slot
168+
Date: March 2010
169+
KernelVersion: 2.6.35
170+
Contact: [email protected]
171+
Description:
172+
If PCI slot directories (as described above) are created,
173+
a symbolic link pointing to the slot directory will be
174+
created as well.
175+
136176
What: /sys/bus/pci/slots/.../module
137177
Date: June 2009
138178
Contact: [email protected]

‎Documentation/ABI/testing/sysfs-bus-usb

Lines changed: 0 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -14,34 +14,6 @@ Description:
1414
The autosuspend delay for newly-created devices is set to
1515
the value of the usbcore.autosuspend module parameter.
1616

17-
What: /sys/bus/usb/devices/.../power/level
18-
Date: March 2007
19-
KernelVersion: 2.6.21
20-
Contact: Alan Stern <[email protected]>
21-
Description:
22-
Each USB device directory will contain a file named
23-
power/level. This file holds a power-level setting for
24-
the device, either "on" or "auto".
25-
26-
"on" means that the device is not allowed to autosuspend,
27-
although normal suspends for system sleep will still
28-
be honored. "auto" means the device will autosuspend
29-
and autoresume in the usual manner, according to the
30-
capabilities of its driver.
31-
32-
During normal use, devices should be left in the "auto"
33-
level. The "on" level is meant for administrative uses.
34-
If you want to suspend a device immediately but leave it
35-
free to wake up in response to I/O requests, you should
36-
write "0" to power/autosuspend.
37-
38-
Device not capable of proper suspend and resume should be
39-
left in the "on" level. Although the USB spec requires
40-
devices to support suspend/resume, many of them do not.
41-
In fact so many don't that by default, the USB core
42-
initializes all non-hub devices in the "on" level. Some
43-
drivers may change this setting when they are bound.
44-
4517
What: /sys/bus/usb/devices/.../power/persist
4618
Date: May 2007
4719
KernelVersion: 2.6.23

‎Documentation/ABI/testing/sysfs-class-power

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
What: /sys/class/power/ds2760-battery.*/charge_now
2+
Date: May 2010
3+
KernelVersion: 2.6.35
4+
Contact: Daniel Mack <[email protected]>
5+
Description:
6+
This file is writeable and can be used to set the current
7+
coloumb counter value inside the battery monitor chip. This
8+
is needed for unavoidable corrections of aging batteries.
9+
A userspace daemon can monitor the battery charging logic
10+
and once the counter drops out of considerable bounds, take
11+
appropriate action.
12+
13+
What: /sys/class/power/ds2760-battery.*/charge_full
14+
Date: May 2010
15+
KernelVersion: 2.6.35
16+
Contact: Daniel Mack <[email protected]>
17+
Description:
18+
This file is writeable and can be used to set the assumed
19+
battery 'full level'. As batteries age, this value has to be
20+
amended over time.

‎Documentation/ABI/testing/sysfs-devices-memory

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Date: September 2008
4343
Contact: Badari Pulavarty <[email protected]>
4444
Description:
4545
The file /sys/devices/system/memory/memoryX/state
46-
is read-write. When read, it's contents show the
46+
is read-write. When read, its contents show the
4747
online/offline state of the memory section. When written,
4848
root can toggle the the online/offline state of a removable
4949
memory section (see removable file description above)

‎Documentation/ABI/testing/sysfs-devices-platform-_UDC_-gadget

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
What: /sys/devices/platform/_UDC_/gadget/suspended
2+
Date: April 2010
3+
Contact: Fabien Chouteau <[email protected]>
4+
Description:
5+
Show the suspend state of an USB composite gadget.
6+
1 -> suspended
7+
0 -> resumed
8+
9+
(_UDC_ is the name of the USB Device Controller driver)

‎Documentation/ABI/testing/sysfs-driver-hid-picolcd

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/operation_mode
2+
Date: March 2010
3+
Contact: Bruno Prémont <[email protected]>
4+
Description: Make it possible to switch the PicoLCD device between LCD
5+
(firmware) and bootloader (flasher) operation modes.
6+
7+
Reading: returns list of available modes, the active mode being
8+
enclosed in brackets ('[' and ']')
9+
10+
Writing: causes operation mode switch. Permitted values are
11+
the non-active mode names listed when read.
12+
13+
Note: when switching mode the current PicoLCD HID device gets
14+
disconnected and reconnects after above delay (see attribute
15+
operation_mode_delay for its value).
16+
17+
18+
What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/operation_mode_delay
19+
Date: April 2010
20+
Contact: Bruno Prémont <[email protected]>
21+
Description: Delay PicoLCD waits before restarting in new mode when
22+
operation_mode has changed.
23+
24+
Reading/Writing: It is expressed in ms and permitted range is
25+
0..30000ms.
26+
27+
28+
What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/fb_update_rate
29+
Date: March 2010
30+
Contact: Bruno Prémont <[email protected]>
31+
Description: Make it possible to adjust defio refresh rate.
32+
33+
Reading: returns list of available refresh rates (expressed in Hz),
34+
the active refresh rate being enclosed in brackets ('[' and ']')
35+
36+
Writing: accepts new refresh rate expressed in integer Hz
37+
within permitted rates.
38+
39+
Note: As device can barely do 2 complete refreshes a second
40+
it only makes sense to adjust this value if only one or two
41+
tiles get changed and it's not appropriate to expect the application
42+
to flush it's tiny changes explicitely at higher than default rate.
43+

‎Documentation/ABI/testing/sysfs-driver-hid-prodikeys

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
What: /sys/bus/hid/drivers/prodikeys/.../channel
2+
Date: April 2010
3+
KernelVersion: 2.6.34
4+
Contact: Don Prince <[email protected]>
5+
Description:
6+
Allows control (via software) the midi channel to which
7+
that the pc-midi keyboard will output.midi data.
8+
Range: 0..15
9+
Type: Read/write
10+
What: /sys/bus/hid/drivers/prodikeys/.../sustain
11+
Date: April 2010
12+
KernelVersion: 2.6.34
13+
Contact: Don Prince <[email protected]>
14+
Description:
15+
Allows control (via software) the sustain duration of a
16+
note held by the pc-midi driver.
17+
0 means sustain mode is disabled.
18+
Range: 0..5000 (milliseconds)
19+
Type: Read/write
20+
What: /sys/bus/hid/drivers/prodikeys/.../octave
21+
Date: April 2010
22+
KernelVersion: 2.6.34
23+
Contact: Don Prince <[email protected]>
24+
Description:
25+
Controls the octave shift modifier in the pc-midi driver.
26+
The octave can be shifted via software up/down 2 octaves.
27+
0 means the no ocatve shift.
28+
Range: -2..2 (minus 2 to plus 2)
29+
Type: Read/Write

0 commit comments

Comments
 (0)