Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 3fa04ecd authored by Trond Myklebust's avatar Trond Myklebust
Browse files

Merge branch 'writeback-for-2.6.34' into nfs-for-2.6.34

parents 180b62a3 1cda707d
Loading
Loading
Loading
Loading
+14 −0
Original line number Diff line number Diff line
@@ -128,3 +128,17 @@ Description:
		preferred request size for workloads where sustained
		throughput is desired.  If no optimal I/O size is
		reported this file contains 0.

What:		/sys/block/<disk>/queue/nomerges
Date:		January 2010
Contact:
Description:
		Standard I/O elevator operations include attempts to
		merge contiguous I/Os. For known random I/O loads these
		attempts will always fail and result in extra cycles
		being spent in the kernel. This allows one to turn off
		this behavior on one of two ways: When set to 1, complex
		merge checks are disabled, but the simple one-shot merges
		with the previous I/O request are enabled. When set to 2,
		all merge tries are disabled. The default value is 0 -
		which enables all types of merge tries.
+11 −0
Original line number Diff line number Diff line
@@ -159,3 +159,14 @@ Description:
		device.  This is useful to ensure auto probing won't
		match the driver to the device.  For example:
		# echo "046d c315" > /sys/bus/usb/drivers/foo/remove_id

What:		/sys/bus/usb/device/.../avoid_reset
Date:		December 2009
Contact:	Oliver Neukum <oliver@neukum.org>
Description:
		Writing 1 to this file tells the kernel that this
		device will morph into another mode when it is reset.
		Drivers will not use reset for error handling for
		such devices.
Users:
		usb_modeswitch
+79 −0
Original line number Diff line number Diff line
What:		/sys/devices/.../power/
Date:		January 2009
Contact:	Rafael J. Wysocki <rjw@sisk.pl>
Description:
		The /sys/devices/.../power directory contains attributes
		allowing the user space to check and modify some power
		management related properties of given device.

What:		/sys/devices/.../power/wakeup
Date:		January 2009
Contact:	Rafael J. Wysocki <rjw@sisk.pl>
Description:
		The /sys/devices/.../power/wakeup attribute allows the user
		space to check if the device is enabled to wake up the system
		from sleep states, such as the memory sleep state (suspend to
		RAM) and hibernation (suspend to disk), and to enable or disable
		it to do that as desired.

		Some devices support "wakeup" events, which are hardware signals
		used to activate the system from a sleep state.  Such devices
		have one of the following two values for the sysfs power/wakeup
		file:

		+ "enabled\n" to issue the events;
		+ "disabled\n" not to do so;

		In that cases the user space can change the setting represented
		by the contents of this file by writing either "enabled", or
		"disabled" to it.

		For the devices that are not capable of generating system wakeup
		events this file contains "\n".  In that cases the user space
		cannot modify the contents of this file and the device cannot be
		enabled to wake up the system.

What:		/sys/devices/.../power/control
Date:		January 2009
Contact:	Rafael J. Wysocki <rjw@sisk.pl>
Description:
		The /sys/devices/.../power/control attribute allows the user
		space to control the run-time power management of the device.

		All devices have one of the following two values for the
		power/control file:

		+ "auto\n" to allow the device to be power managed at run time;
		+ "on\n" to prevent the device from being power managed;

		The default for all devices is "auto", which means that they may
		be subject to automatic power management, depending on their
		drivers.  Changing this attribute to "on" prevents the driver
		from power managing the device at run time.  Doing that while
		the device is suspended causes it to be woken up.

What:		/sys/devices/.../power/async
Date:		January 2009
Contact:	Rafael J. Wysocki <rjw@sisk.pl>
Description:
		The /sys/devices/.../async attribute allows the user space to
		enable or diasble the device's suspend and resume callbacks to
		be executed asynchronously (ie. in separate threads, in parallel
		with the main suspend/resume thread) during system-wide power
		transitions (eg. suspend to RAM, hibernation).

		All devices have one of the following two values for the
		power/async file:

		+ "enabled\n" to permit the asynchronous suspend/resume;
		+ "disabled\n" to forbid it;

		The value of this attribute may be changed by writing either
		"enabled", or "disabled" to it.

		It generally is unsafe to permit the asynchronous suspend/resume
		of a device unless it is certain that all of the PM dependencies
		of the device are known to the PM core.  However, for some
		devices this attribute is set to "enabled" by bus type code or
		device drivers and in that cases it should be safe to leave the
		default value.
+6 −6
Original line number Diff line number Diff line
What:		/sys/devices/platform/asus-laptop/display
What:		/sys/devices/platform/asus_laptop/display
Date:		January 2007
KernelVersion:	2.6.20
Contact:	"Corentin Chary" <corentincj@iksaif.net>
@@ -13,7 +13,7 @@ Description:
		Ex: - 0 (0000b) means no display
		    - 3 (0011b) CRT+LCD.

What:		/sys/devices/platform/asus-laptop/gps
What:		/sys/devices/platform/asus_laptop/gps
Date:		January 2007
KernelVersion:	2.6.20
Contact:	"Corentin Chary" <corentincj@iksaif.net>
@@ -21,7 +21,7 @@ Description:
		Control the gps device. 1 means on, 0 means off.
Users:		Lapsus

What:		/sys/devices/platform/asus-laptop/ledd
What:		/sys/devices/platform/asus_laptop/ledd
Date:		January 2007
KernelVersion:	2.6.20
Contact:	"Corentin Chary" <corentincj@iksaif.net>
@@ -29,11 +29,11 @@ Description:
		Some models like the W1N have a LED display that can be
		used to display several informations.
		To control the LED display, use the following :
		    echo 0x0T000DDD > /sys/devices/platform/asus-laptop/
		    echo 0x0T000DDD > /sys/devices/platform/asus_laptop/
		where T control the 3 letters display, and DDD the 3 digits display.
		The DDD table can be found in Documentation/laptops/asus-laptop.txt

What:		/sys/devices/platform/asus-laptop/bluetooth
What:		/sys/devices/platform/asus_laptop/bluetooth
Date:		January 2007
KernelVersion:	2.6.20
Contact:	"Corentin Chary" <corentincj@iksaif.net>
@@ -42,7 +42,7 @@ Description:
		This may control the led, the device or both.
Users:		Lapsus

What:		/sys/devices/platform/asus-laptop/wlan
What:		/sys/devices/platform/asus_laptop/wlan
Date:		January 2007
KernelVersion:	2.6.20
Contact:	"Corentin Chary" <corentincj@iksaif.net>
+5 −5
Original line number Diff line number Diff line
What:		/sys/devices/platform/eeepc-laptop/disp
What:		/sys/devices/platform/eeepc/disp
Date:		May 2008
KernelVersion:	2.6.26
Contact:	"Corentin Chary" <corentincj@iksaif.net>
@@ -9,21 +9,21 @@ Description:
		- 3 = LCD+CRT
		If you run X11, you should use xrandr instead.

What:		/sys/devices/platform/eeepc-laptop/camera
What:		/sys/devices/platform/eeepc/camera
Date:		May 2008
KernelVersion:	2.6.26
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Description:
		Control the camera. 1 means on, 0 means off.

What:		/sys/devices/platform/eeepc-laptop/cardr
What:		/sys/devices/platform/eeepc/cardr
Date:		May 2008
KernelVersion:	2.6.26
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Description:
		Control the card reader. 1 means on, 0 means off.

What:		/sys/devices/platform/eeepc-laptop/cpufv
What:		/sys/devices/platform/eeepc/cpufv
Date:		Jun 2009
KernelVersion:	2.6.31
Contact:	"Corentin Chary" <corentincj@iksaif.net>
@@ -42,7 +42,7 @@ Description:
		    `------------ Availables modes
		For example, 0x301 means: mode 1 selected, 3 available modes.

What:		/sys/devices/platform/eeepc-laptop/available_cpufv
What:		/sys/devices/platform/eeepc/available_cpufv
Date:		Jun 2009
KernelVersion:	2.6.31
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Loading