---

yaml --- r: 198207 b: refs/heads/master c: 54a4ec4 h: refs/heads/master i: 198205: 6d87b4b 198203: 3fdad18 198199: b56d885 198191: df4849d 198175: a4a30a1 198143: 5c45800 v: v3
git-mirror · Apr 15, 2010 · 8996e92 · 8996e92
1 parent 4d4fe37
commit 8996e92
Show file tree

Hide file tree

Showing 10,111 changed files with 249,895 additions and 533,740 deletions.
diff --git a/[refs] b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: 064e297c324fff9b62226aae5dc468ebb272433c
+refs/heads/master: 54a4ec469dd6067f0b604bef8ca01a2b1fdb4dcd
diff --git a/trunk/Documentation/00-INDEX b/trunk/Documentation/00-INDEX
@@ -250,8 +250,6 @@ numastat.txt
 	- info on how to read Numa policy hit/miss statistics in sysfs.
 oops-tracing.txt
 	- how to decode those nasty internal kernel error dump messages.
-padata.txt
-	- An introduction to the "padata" parallel execution API
 parisc/
 	- directory with info on using Linux on PA-RISC architecture.
 parport.txt

diff --git a/trunk/Documentation/ABI/obsolete/sysfs-bus-usb b/trunk/Documentation/ABI/obsolete/sysfs-bus-usb
diff --git a/trunk/Documentation/ABI/obsolete/sysfs-class-rfkill b/trunk/Documentation/ABI/obsolete/sysfs-class-rfkill
diff --git a/trunk/Documentation/ABI/stable/sysfs-class-rfkill b/trunk/Documentation/ABI/stable/sysfs-class-rfkill
diff --git a/trunk/Documentation/ABI/testing/sysfs-bus-pci b/trunk/Documentation/ABI/testing/sysfs-bus-pci
@@ -133,46 +133,6 @@ Description:
 		The symbolic link points to the PCI device sysfs entry of the
 		Physical Function this device associates with.
 
-
-What:		/sys/bus/pci/slots/...
-Date:		April 2005 (possibly older)
-KernelVersion:	2.6.12 (possibly older)
-Contact:	linux-pci@vger.kernel.org
-Description:
-		When the appropriate driver is loaded, it will create a
-		directory per claimed physical PCI slot in
-		/sys/bus/pci/slots/.  The names of these directories are
-		specific to the driver, which in turn, are specific to the
-		platform, but in general, should match the label on the
-		machine's physical chassis.
-
-		The drivers that can create slot directories include the
-		PCI hotplug drivers, and as of 2.6.27, the pci_slot driver.
-
-		The slot directories contain, at a minimum, a file named
-		'address' which contains the PCI bus:device:function tuple.
-		Other files may appear as well, but are specific to the
-		driver.
-
-What:		/sys/bus/pci/slots/.../function[0-7]
-Date:		March 2010
-KernelVersion:	2.6.35
-Contact:	linux-pci@vger.kernel.org
-Description:
-		If PCI slot directories (as described above) are created,
-		and the physical slot is actually populated with a device,
-		symbolic links in the slot directory pointing to the
-		device's PCI functions are created as well.
-
-What:		/sys/bus/pci/devices/.../slot
-Date:		March 2010
-KernelVersion:	2.6.35
-Contact:	linux-pci@vger.kernel.org
-Description:
-		If PCI slot directories (as described above) are created,
-		a symbolic link pointing to the slot directory will be
-		created as well.
-
 What:		/sys/bus/pci/slots/.../module
 Date:		June 2009
 Contact:	linux-pci@vger.kernel.org

diff --git a/trunk/Documentation/ABI/testing/sysfs-bus-usb b/trunk/Documentation/ABI/testing/sysfs-bus-usb
@@ -14,6 +14,34 @@ Description:
 		The autosuspend delay for newly-created devices is set to
 		the value of the usbcore.autosuspend module parameter.
 
+What:		/sys/bus/usb/devices/.../power/level
+Date:		March 2007
+KernelVersion:	2.6.21
+Contact:	Alan Stern <stern@rowland.harvard.edu>
+Description:
+		Each USB device directory will contain a file named
+		power/level.  This file holds a power-level setting for
+		the device, either "on" or "auto".
+
+		"on" means that the device is not allowed to autosuspend,
+		although normal suspends for system sleep will still
+		be honored.  "auto" means the device will autosuspend
+		and autoresume in the usual manner, according to the
+		capabilities of its driver.
+
+		During normal use, devices should be left in the "auto"
+		level.  The "on" level is meant for administrative uses.
+		If you want to suspend a device immediately but leave it
+		free to wake up in response to I/O requests, you should
+		write "0" to power/autosuspend.
+
+		Device not capable of proper suspend and resume should be
+		left in the "on" level.  Although the USB spec requires
+		devices to support suspend/resume, many of them do not.
+		In fact so many don't that by default, the USB core
+		initializes all non-hub devices in the "on" level.  Some
+		drivers may change this setting when they are bound.
+
 What:		/sys/bus/usb/devices/.../power/persist
 Date:		May 2007
 KernelVersion:	2.6.23

diff --git a/trunk/Documentation/ABI/testing/sysfs-class-power b/trunk/Documentation/ABI/testing/sysfs-class-power
diff --git a/trunk/Documentation/ABI/testing/sysfs-devices-memory b/trunk/Documentation/ABI/testing/sysfs-devices-memory
@@ -43,7 +43,7 @@ Date:		September 2008
 Contact:	Badari Pulavarty <pbadari@us.ibm.com>
 Description:
 		The file /sys/devices/system/memory/memoryX/state
-		is read-write.  When read, its contents show the
+		is read-write.  When read, it's contents show the
 		online/offline state of the memory section.  When written,
 		root can toggle the the online/offline state of a removable
 		memory section (see removable file description above)

diff --git a/trunk/Documentation/ABI/testing/sysfs-devices-platform-_UDC_-gadget b/trunk/Documentation/ABI/testing/sysfs-devices-platform-_UDC_-gadget
diff --git a/trunk/Documentation/ABI/testing/sysfs-driver-hid-picolcd b/trunk/Documentation/ABI/testing/sysfs-driver-hid-picolcd
diff --git a/trunk/Documentation/ABI/testing/sysfs-driver-hid-prodikeys b/trunk/Documentation/ABI/testing/sysfs-driver-hid-prodikeys