forked from grate-driver/linux
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Sync with Linus tree to have 157550f ("mtd: add GPMI-NAND driver in the config and Makefile") as I have patch depending on that one.
- Loading branch information
Showing
10,717 changed files
with
673,332 additions
and
456,443 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
What: /sys/firmware/acpi/pm_profile | ||
Date: 03-Nov-2011 | ||
KernelVersion: v3.2 | ||
Contact: linux-acpi@vger.kernel.org | ||
Description: The ACPI pm_profile sysfs interface exports the platform | ||
power management (and performance) requirement expectations | ||
as provided by BIOS. The integer value is directly passed as | ||
retrieved from the FADT ACPI table. | ||
Values: For possible values see ACPI specification: | ||
5.2.9 Fixed ACPI Description Table (FADT) | ||
Field: Preferred_PM_Profile | ||
|
||
Currently these values are defined by spec: | ||
0 Unspecified | ||
1 Desktop | ||
2 Mobile | ||
3 Workstation | ||
4 Enterprise Server | ||
5 SOHO Server | ||
6 Appliance PC | ||
7 Performance Server | ||
>7 Reserved |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
What: /sys/kernel/debug/ideapad/cfg | ||
Date: Sep 2011 | ||
KernelVersion: 3.2 | ||
Contact: Ike Panhc <ike.pan@canonical.com> | ||
Description: | ||
|
||
cfg shows the return value of _CFG method in VPC2004 device. It tells machine | ||
capability and what graphic component within the machine. | ||
|
||
|
||
What: /sys/kernel/debug/ideapad/status | ||
Date: Sep 2011 | ||
KernelVersion: 3.2 | ||
Contact: Ike Panhc <ike.pan@canonical.com> | ||
Description: | ||
|
||
status shows infos we can read and tells its meaning and value. | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
What: /sys/bus/pci/drivers/ehci_hcd/.../companion | ||
/sys/bus/usb/devices/usbN/../companion | ||
Date: January 2007 | ||
KernelVersion: 2.6.21 | ||
Contact: Alan Stern <stern@rowland.harvard.edu> | ||
Description: | ||
PCI-based EHCI USB controllers (i.e., high-speed USB-2.0 | ||
controllers) are often implemented along with a set of | ||
"companion" full/low-speed USB-1.1 controllers. When a | ||
high-speed device is plugged in, the connection is routed | ||
to the EHCI controller; when a full- or low-speed device | ||
is plugged in, the connection is routed to the companion | ||
controller. | ||
|
||
Sometimes you want to force a high-speed device to connect | ||
at full speed, which can be accomplished by forcing the | ||
connection to be routed to the companion controller. | ||
That's what this file does. Writing a port number to the | ||
file causes connections on that port to be routed to the | ||
companion controller, and writing the negative of a port | ||
number returns the port to normal operation. | ||
|
||
For example: To force the high-speed device attached to | ||
port 4 on bus 2 to run at full speed: | ||
|
||
echo 4 >/sys/bus/usb/devices/usb2/../companion | ||
|
||
To return the port to high-speed operation: | ||
|
||
echo -4 >/sys/bus/usb/devices/usb2/../companion | ||
|
||
Reading the file gives the list of ports currently forced | ||
to the companion controller. | ||
|
||
Note: Some EHCI controllers do not have companions; they | ||
may contain an internal "transaction translator" or they | ||
may be attached directly to a "rate-matching hub". This | ||
mechanism will not work with such controllers. Also, it | ||
cannot be used to force a port on a high-speed hub to | ||
connect at full speed. | ||
|
||
Note: When this file was first added, it appeared in a | ||
different sysfs directory. The location given above is | ||
correct for 2.6.35 (and probably several earlier kernel | ||
versions as well). | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
What: /sys/class/devfreq/.../ | ||
Date: September 2011 | ||
Contact: MyungJoo Ham <myungjoo.ham@samsung.com> | ||
Description: | ||
Provide a place in sysfs for the devfreq objects. | ||
This allows accessing various devfreq specific variables. | ||
The name of devfreq object denoted as ... is same as the | ||
name of device using devfreq. | ||
|
||
What: /sys/class/devfreq/.../governor | ||
Date: September 2011 | ||
Contact: MyungJoo Ham <myungjoo.ham@samsung.com> | ||
Description: | ||
The /sys/class/devfreq/.../governor shows the name of the | ||
governor used by the corresponding devfreq object. | ||
|
||
What: /sys/class/devfreq/.../cur_freq | ||
Date: September 2011 | ||
Contact: MyungJoo Ham <myungjoo.ham@samsung.com> | ||
Description: | ||
The /sys/class/devfreq/.../cur_freq shows the current | ||
frequency of the corresponding devfreq object. | ||
|
||
What: /sys/class/devfreq/.../central_polling | ||
Date: September 2011 | ||
Contact: MyungJoo Ham <myungjoo.ham@samsung.com> | ||
Description: | ||
The /sys/class/devfreq/.../central_polling shows whether | ||
the devfreq ojbect is using devfreq-provided central | ||
polling mechanism or not. | ||
|
||
What: /sys/class/devfreq/.../polling_interval | ||
Date: September 2011 | ||
Contact: MyungJoo Ham <myungjoo.ham@samsung.com> | ||
Description: | ||
The /sys/class/devfreq/.../polling_interval shows and sets | ||
the requested polling interval of the corresponding devfreq | ||
object. The values are represented in ms. If the value is | ||
less than 1 jiffy, it is considered to be 0, which means | ||
no polling. This value is meaningless if the governor is | ||
not polling; thus. If the governor is not using | ||
devfreq-provided central polling | ||
(/sys/class/devfreq/.../central_polling is 0), this value | ||
may be useless. | ||
|
||
What: /sys/class/devfreq/.../userspace/set_freq | ||
Date: September 2011 | ||
Contact: MyungJoo Ham <myungjoo.ham@samsung.com> | ||
Description: | ||
The /sys/class/devfreq/.../userspace/set_freq shows and | ||
sets the requested frequency for the devfreq object if | ||
userspace governor is in effect. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,72 @@ | ||
What: /sys/class/hidraw/hidraw*/device/speed | ||
Date: April 2010 | ||
Kernel Version: 2.6.35 | ||
Contact: linux-bluetooth@vger.kernel.org | ||
Description: | ||
The /sys/class/hidraw/hidraw*/device/speed file controls | ||
reporting speed of Wacom bluetooth tablet. Reading from | ||
this file returns 1 if tablet reports in high speed mode | ||
or 0 otherwise. Writing to this file one of these values | ||
switches reporting speed. | ||
|
||
What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/led | ||
Date: August 2011 | ||
Contact: linux-input@vger.kernel.org | ||
Description: | ||
Attribute group for control of the status LEDs and the OLEDs. | ||
This attribute group is only available for Intuos 4 M, L, | ||
and XL (with LEDs and OLEDs) and Cintiq 21UX2 (LEDs only). | ||
Therefore its presence implicitly signifies the presence of | ||
said LEDs and OLEDs on the tablet device. | ||
|
||
What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status0_luminance | ||
Date: August 2011 | ||
Contact: linux-input@vger.kernel.org | ||
Description: | ||
Writing to this file sets the status LED luminance (1..127) | ||
when the stylus does not touch the tablet surface, and no | ||
button is pressed on the stylus. This luminance level is | ||
normally lower than the level when a button is pressed. | ||
|
||
What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status1_luminance | ||
Date: August 2011 | ||
Contact: linux-input@vger.kernel.org | ||
Description: | ||
Writing to this file sets the status LED luminance (1..127) | ||
when the stylus touches the tablet surface, or any button is | ||
pressed on the stylus. | ||
|
||
What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status_led0_select | ||
Date: August 2011 | ||
Contact: linux-input@vger.kernel.org | ||
Description: | ||
Writing to this file sets which one of the four (for Intuos 4) | ||
or of the right four (for Cintiq 21UX2) status LEDs is active (0..3). | ||
The other three LEDs on the same side are always inactive. | ||
|
||
What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status_led1_select | ||
Date: September 2011 | ||
Contact: linux-input@vger.kernel.org | ||
Description: | ||
Writing to this file sets which one of the left four (for Cintiq 21UX2) | ||
status LEDs is active (0..3). The other three LEDs on the left are always | ||
inactive. | ||
|
||
What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/buttons_luminance | ||
Date: August 2011 | ||
Contact: linux-input@vger.kernel.org | ||
Description: | ||
Writing to this file sets the overall luminance level (0..15) | ||
of all eight button OLED displays. | ||
|
||
What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/button<n>_rawimg | ||
Date: August 2011 | ||
Contact: linux-input@vger.kernel.org | ||
Description: | ||
When writing a 1024 byte raw image in Wacom Intuos 4 | ||
interleaving format to the file, the image shows up on Button N | ||
of the device. The image is a 64x32 pixel 4-bit gray image. The | ||
1024 byte binary is split up into 16x 64 byte chunks. Each 64 | ||
byte chunk encodes the image data for two consecutive lines on | ||
the display. The low nibble of each byte contains the first | ||
line, and the high nibble contains the second line. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.