-
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.
Merge commit 'c104f1fa1ecf4ee0fc06e31b1f77630b2551be81' into stable/f…
…or-linus-3.4 * commit 'c104f1fa1ecf4ee0fc06e31b1f77630b2551be81': (14566 commits) cpufreq: OMAP: fix build errors: depends on ARCH_OMAP2PLUS sparc64: Eliminate obsolete __handle_softirq() function sparc64: Fix bootup crash on sun4v. kconfig: delete last traces of __enabled_ from autoconf.h Revert "kconfig: fix __enabled_ macros definition for invisible and un-selected symbols" kconfig: fix IS_ENABLED to not require all options to be defined irq_domain: fix type mismatch in debugfs output format staging: android: fix mem leaks in __persistent_ram_init() staging: vt6656: Don't leak memory in drivers/staging/vt6656/ioctl.c::private_ioctl() staging: iio: hmc5843: Fix crash in probe function. panic: fix stack dump print on direct call to panic() drivers/rtc/rtc-pl031.c: enable clock on all ST variants Revert "mm: vmscan: fix misused nr_reclaimed in shrink_mem_cgroup_zone()" hugetlb: fix race condition in hugetlb_fault() drivers/rtc/rtc-twl.c: use static register while reading time drivers/rtc/rtc-s3c.c: add placeholder for driver private data drivers/rtc/rtc-s3c.c: fix compilation error MAINTAINERS: add PCDP console maintainer memcg: do not open code accesses to res_counter members drivers/rtc/rtc-efi.c: fix section mismatch warning ...
- Loading branch information
Showing
13,248 changed files
with
688,252 additions
and
437,105 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
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
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,16 @@ | ||
| What: /sys/kernel/debug/olpc-ec/cmd | ||
| Date: Dec 2011 | ||
| KernelVersion: 3.4 | ||
| Contact: devel@lists.laptop.org | ||
| Description: | ||
|
|
||
| A generic interface for executing OLPC Embedded Controller commands and | ||
| reading their responses. | ||
|
|
||
| To execute a command, write data with the format: CC:N A A A A | ||
| CC is the (hex) command, N is the count of expected reply bytes, and A A A A | ||
| are optional (hex) arguments. | ||
|
|
||
| To read the response (if any), read from the generic node after executing | ||
| a command. Hex reply bytes will be returned, *whether or not* they came from | ||
| the immediately previous command. |
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,25 @@ | ||
| What: /sys/block/dm-<num>/dm/name | ||
| Date: January 2009 | ||
| KernelVersion: 2.6.29 | ||
| Contact: dm-devel@redhat.com | ||
| Description: Device-mapper device name. | ||
| Read-only string containing mapped device name. | ||
| Users: util-linux, device-mapper udev rules | ||
|
|
||
| What: /sys/block/dm-<num>/dm/uuid | ||
| Date: January 2009 | ||
| KernelVersion: 2.6.29 | ||
| Contact: dm-devel@redhat.com | ||
| Description: Device-mapper device UUID. | ||
| Read-only string containing DM-UUID or empty string | ||
| if DM-UUID is not set. | ||
| Users: util-linux, device-mapper udev rules | ||
|
|
||
| What: /sys/block/dm-<num>/dm/suspended | ||
| Date: June 2009 | ||
| KernelVersion: 2.6.31 | ||
| Contact: dm-devel@redhat.com | ||
| Description: Device-mapper device suspend state. | ||
| Contains the value 1 while the device is suspended. | ||
| Otherwise it contains 0. Read-only attribute. | ||
| Users: util-linux, device-mapper udev rules |
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,18 @@ | ||
| What: /sys/block/rssd*/registers | ||
| Date: March 2012 | ||
| KernelVersion: 3.3 | ||
| Contact: Asai Thambi S P <asamymuthupa@micron.com> | ||
| Description: This is a read-only file. Dumps below driver information and | ||
| hardware registers. | ||
| - S ACTive | ||
| - Command Issue | ||
| - Allocated | ||
| - Completed | ||
| - PORT IRQ STAT | ||
| - HOST IRQ STAT | ||
|
|
||
| What: /sys/block/rssd*/status | ||
| Date: April 2012 | ||
| KernelVersion: 3.4 | ||
| Contact: Asai Thambi S P <asamymuthupa@micron.com> | ||
| Description: This is a read-only file. Indicates the status of the device. |
14 changes: 14 additions & 0 deletions
14
Documentation/ABI/testing/sysfs-bus-event_source-devices-format
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,14 @@ | ||
| Where: /sys/bus/event_source/devices/<dev>/format | ||
| Date: January 2012 | ||
| Kernel Version: 3.3 | ||
| Contact: Jiri Olsa <jolsa@redhat.com> | ||
| Description: | ||
| Attribute group to describe the magic bits that go into | ||
| perf_event_attr::config[012] for a particular pmu. | ||
| Each attribute of this group defines the 'hardware' bitmask | ||
| we want to export, so that userspace can deal with sane | ||
| name/value pairs. | ||
|
|
||
| Example: 'config1:1,6-10,44' | ||
| Defines contents of attribute that occupies bits 1,6-10,44 of | ||
| perf_event_attr::config1. |
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,75 @@ | ||
| What: /sys/bus/rpmsg/devices/.../name | ||
| Date: June 2011 | ||
| KernelVersion: 3.3 | ||
| Contact: Ohad Ben-Cohen <ohad@wizery.com> | ||
| Description: | ||
| Every rpmsg device is a communication channel with a remote | ||
| processor. Channels are identified with a (textual) name, | ||
| which is maximum 32 bytes long (defined as RPMSG_NAME_SIZE in | ||
| rpmsg.h). | ||
|
|
||
| This sysfs entry contains the name of this channel. | ||
|
|
||
| What: /sys/bus/rpmsg/devices/.../src | ||
| Date: June 2011 | ||
| KernelVersion: 3.3 | ||
| Contact: Ohad Ben-Cohen <ohad@wizery.com> | ||
| Description: | ||
| Every rpmsg device is a communication channel with a remote | ||
| processor. Channels have a local ("source") rpmsg address, | ||
| and remote ("destination") rpmsg address. When an entity | ||
| starts listening on one end of a channel, it assigns it with | ||
| a unique rpmsg address (a 32 bits integer). This way when | ||
| inbound messages arrive to this address, the rpmsg core | ||
| dispatches them to the listening entity (a kernel driver). | ||
|
|
||
| This sysfs entry contains the src (local) rpmsg address | ||
| of this channel. If it contains 0xffffffff, then an address | ||
| wasn't assigned (can happen if no driver exists for this | ||
| channel). | ||
|
|
||
| What: /sys/bus/rpmsg/devices/.../dst | ||
| Date: June 2011 | ||
| KernelVersion: 3.3 | ||
| Contact: Ohad Ben-Cohen <ohad@wizery.com> | ||
| Description: | ||
| Every rpmsg device is a communication channel with a remote | ||
| processor. Channels have a local ("source") rpmsg address, | ||
| and remote ("destination") rpmsg address. When an entity | ||
| starts listening on one end of a channel, it assigns it with | ||
| a unique rpmsg address (a 32 bits integer). This way when | ||
| inbound messages arrive to this address, the rpmsg core | ||
| dispatches them to the listening entity. | ||
|
|
||
| This sysfs entry contains the dst (remote) rpmsg address | ||
| of this channel. If it contains 0xffffffff, then an address | ||
| wasn't assigned (can happen if the kernel driver that | ||
| is attached to this channel is exposing a service to the | ||
| remote processor. This make it a local rpmsg server, | ||
| and it is listening for inbound messages that may be sent | ||
| from any remote rpmsg client; it is not bound to a single | ||
| remote entity). | ||
|
|
||
| What: /sys/bus/rpmsg/devices/.../announce | ||
| Date: June 2011 | ||
| KernelVersion: 3.3 | ||
| Contact: Ohad Ben-Cohen <ohad@wizery.com> | ||
| Description: | ||
| Every rpmsg device is a communication channel with a remote | ||
| processor. Channels are identified by a textual name (see | ||
| /sys/bus/rpmsg/devices/.../name above) and have a local | ||
| ("source") rpmsg address, and remote ("destination") rpmsg | ||
| address. | ||
|
|
||
| A channel is first created when an entity, whether local | ||
| or remote, starts listening on it for messages (and is thus | ||
| called an rpmsg server). | ||
|
|
||
| When that happens, a "name service" announcement is sent | ||
| to the other processor, in order to let it know about the | ||
| creation of the channel (this way remote clients know they | ||
| can start sending messages). | ||
|
|
||
| This sysfs entry tells us whether the channel is a local | ||
| server channel that is announced (values are either | ||
| true or false). |
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,8 @@ | ||
| What: /sys/block/<device>/iosched/target_latency | ||
| Date: March 2012 | ||
| contact: Tao Ma <boyu.mt@taobao.com> | ||
| Description: | ||
| The /sys/block/<device>/iosched/target_latency only exists | ||
| when the user sets cfq to /sys/block/<device>/scheduler. | ||
| It contains an estimated latency time for the cfq. cfq will | ||
| use it to calculate the time slice used for every task. |
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
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.