Skip to content

Commit

Permalink
---
Browse files Browse the repository at this point in the history 
yaml
---
r: 305062
b: refs/heads/master
c: 224b321
h: refs/heads/master
v: v3
  • Loading branch information
Przemo Firszt authored and Jiri Kosina committed Mar 28, 2012
1 parent 74c19b6 commit bac2b0d
Show file tree
Hide file tree
Showing 8,410 changed files with 178,225 additions and 329,464 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
2 changes: 1 addition & 1 deletion [refs]
View file
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
---
refs/heads/master: 44d27f7dfedd9aadc082cda31462f6600f56e4ec
refs/heads/master: 224b321b312e9c03989e1563beaa50f98f9b48e0
6 changes: 2 additions & 4 deletions trunk/Documentation/00-INDEX
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,8 @@ Please try and keep the descriptions small enough to fit on one line.

Following translations are available on the WWW:

- Japanese, maintained by the JF Project (jf@listserv.linux.or.jp), at
http://linuxjf.sourceforge.jp/
- Japanese, maintained by the JF Project (JF@linux.or.jp), at
http://www.linux.or.jp/JF/

00-INDEX
- this file.
Expand Down Expand Up @@ -104,8 +104,6 @@ cpuidle/
- info on CPU_IDLE, CPU idle state management subsystem.
cputopology.txt
- documentation on how CPU topology info is exported via sysfs.
crc32.txt
- brief tutorial on CRC computation
cris/
- directory with info about Linux on CRIS architecture.
crypto/
Expand Down
2 changes: 1 addition & 1 deletion trunk/Documentation/ABI/obsolete/sysfs-class-rfkill
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ Date: 09-Jul-2007
KernelVersion v2.6.22
Contact: linux-wireless@vger.kernel.org
Description: Current state of the transmitter.
This file is deprecated and scheduled to be removed in 2014,
This file is deprecated and sheduled to be removed in 2014,
because its not possible to express the 'soft and hard block'
state of the rfkill driver.
Values: A numeric value.
Expand Down
16 changes: 8 additions & 8 deletions trunk/Documentation/ABI/stable/sysfs-driver-usb-usbtmc
View file
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
What: /sys/bus/usb/drivers/usbtmc/*/interface_capabilities
What: /sys/bus/usb/drivers/usbtmc/*/device_capabilities
What: /sys/bus/usb/drivers/usbtmc/devices/*/interface_capabilities
What: /sys/bus/usb/drivers/usbtmc/devices/*/device_capabilities
Date: August 2008
Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Description:
Expand All @@ -12,8 +12,8 @@ Description:
The files are read only.


What: /sys/bus/usb/drivers/usbtmc/*/usb488_interface_capabilities
What: /sys/bus/usb/drivers/usbtmc/*/usb488_device_capabilities
What: /sys/bus/usb/drivers/usbtmc/devices/*/usb488_interface_capabilities
What: /sys/bus/usb/drivers/usbtmc/devices/*/usb488_device_capabilities
Date: August 2008
Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Description:
Expand All @@ -27,7 +27,7 @@ Description:
The files are read only.


What: /sys/bus/usb/drivers/usbtmc/*/TermChar
What: /sys/bus/usb/drivers/usbtmc/devices/*/TermChar
Date: August 2008
Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Description:
Expand All @@ -40,7 +40,7 @@ Description:
sent to the device or not.


What: /sys/bus/usb/drivers/usbtmc/*/TermCharEnabled
What: /sys/bus/usb/drivers/usbtmc/devices/*/TermCharEnabled
Date: August 2008
Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Description:
Expand All @@ -51,11 +51,11 @@ Description:
published by the USB-IF.


What: /sys/bus/usb/drivers/usbtmc/*/auto_abort
What: /sys/bus/usb/drivers/usbtmc/devices/*/auto_abort
Date: August 2008
Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Description:
This file determines if the transaction of the USB TMC
This file determines if the the transaction of the USB TMC
device is to be automatically aborted if there is any error.
For more details about this, please see the document,
"Universal Serial Bus Test and Measurement Class Specification
Expand Down
2 changes: 1 addition & 1 deletion trunk/Documentation/ABI/stable/sysfs-module
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Description:
The name of the module that is in the kernel. This
module name will show up either if the module is built
directly into the kernel, or if it is loaded as a
dynamic module.
dyanmic module.

/sys/module/MODULENAME/parameters
This directory contains individual files that are each
Expand Down
16 changes: 0 additions & 16 deletions trunk/Documentation/ABI/testing/debugfs-olpc
View file

This file was deleted.

25 changes: 0 additions & 25 deletions trunk/Documentation/ABI/testing/sysfs-block-dm
View file

This file was deleted.

18 changes: 0 additions & 18 deletions trunk/Documentation/ABI/testing/sysfs-block-rssd
View file

This file was deleted.

14 changes: 0 additions & 14 deletions trunk/Documentation/ABI/testing/sysfs-bus-event_source-devices-format
View file

This file was deleted.

75 changes: 0 additions & 75 deletions trunk/Documentation/ABI/testing/sysfs-bus-rpmsg
View file

This file was deleted.

8 changes: 0 additions & 8 deletions trunk/Documentation/ABI/testing/sysfs-cfq-target-latency
View file

This file was deleted.

18 changes: 0 additions & 18 deletions trunk/Documentation/ABI/testing/sysfs-devices-power
View file
Original file line number Diff line number Diff line change
Expand Up @@ -165,21 +165,3 @@ Description:

Not all drivers support this attribute. If it isn't supported,
attempts to read or write it will yield I/O errors.

What: /sys/devices/.../power/pm_qos_latency_us
Date: March 2012
Contact: Rafael J. Wysocki <rjw@sisk.pl>
Description:
The /sys/devices/.../power/pm_qos_resume_latency_us attribute
contains the PM QoS resume latency limit for the given device,
which is the maximum allowed time it can take to resume the
device, after it has been suspended at run time, from a resume
request to the moment the device will be ready to process I/O,
in microseconds. If it is equal to 0, however, this means that
the PM QoS resume latency may be arbitrary.

Not all drivers support this attribute. If it isn't supported,
it is not present.

This attribute has no effect on system-wide suspend/resume and
hibernation.
18 changes: 0 additions & 18 deletions trunk/Documentation/ABI/testing/sysfs-driver-samsung-laptop
View file
Original file line number Diff line number Diff line change
Expand Up @@ -17,21 +17,3 @@ Description: Some Samsung laptops have different "performance levels"
Specifically, not all support the "overclock" option,
and it's still unknown if this value even changes
anything, other than making the user feel a bit better.

What: /sys/devices/platform/samsung/battery_life_extender
Date: December 1, 2011
KernelVersion: 3.3
Contact: Corentin Chary <corentin.chary@gmail.com>
Description: Max battery charge level can be modified, battery cycle
life can be extended by reducing the max battery charge
level.
0 means normal battery mode (100% charge)
1 means battery life extender mode (80% charge)

What: /sys/devices/platform/samsung/usb_charge
Date: December 1, 2011
KernelVersion: 3.3
Contact: Corentin Chary <corentin.chary@gmail.com>
Description: Use your USB ports to charge devices, even
when your laptop is powered off.
1 means enabled, 0 means disabled.
20 changes: 0 additions & 20 deletions trunk/Documentation/ABI/testing/sysfs-firmware-acpi
View file
Original file line number Diff line number Diff line change
@@ -1,23 +1,3 @@
What: /sys/firmware/acpi/bgrt/
Date: January 2012
Contact: Matthew Garrett <mjg@redhat.com>
Description:
The BGRT is an ACPI 5.0 feature that allows the OS
to obtain a copy of the firmware boot splash and
some associated metadata. This is intended to be used
by boot splash applications in order to interact with
the firmware boot splash in order to avoid jarring
transitions.

image: The image bitmap. Currently a 32-bit BMP.
status: 1 if the image is valid, 0 if firmware invalidated it.
type: 0 indicates image is in BMP format.
version: The version of the BGRT. Currently 1.
xoffset: The number of pixels between the left of the screen
and the left edge of the image.
yoffset: The number of pixels between the top of the screen
and the top edge of the image.

What: /sys/firmware/acpi/interrupts/
Date: February 2008
Contact: Len Brown <lenb@kernel.org>
Expand Down
11 changes: 11 additions & 0 deletions trunk/Documentation/ABI/testing/sysfs-kernel-mm-cleancache
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
What: /sys/kernel/mm/cleancache/
Date: April 2011
Contact: Dan Magenheimer <dan.magenheimer@oracle.com>
Description:
/sys/kernel/mm/cleancache/ contains a number of files which
record a count of various cleancache operations
(sum across all filesystems):
succ_gets
failed_gets
puts
flushes
29 changes: 0 additions & 29 deletions trunk/Documentation/CodingStyle
View file
Original file line number Diff line number Diff line change
Expand Up @@ -793,35 +793,6 @@ own custom mode, or may have some other magic method for making indentation
work correctly.


Chapter 19: Inline assembly

In architecture-specific code, you may need to use inline assembly to interface
with CPU or platform functionality. Don't hesitate to do so when necessary.
However, don't use inline assembly gratuitously when C can do the job. You can
and should poke hardware from C when possible.

Consider writing simple helper functions that wrap common bits of inline
assembly, rather than repeatedly writing them with slight variations. Remember
that inline assembly can use C parameters.

Large, non-trivial assembly functions should go in .S files, with corresponding
C prototypes defined in C header files. The C prototypes for assembly
functions should use "asmlinkage".

You may need to mark your asm statement as volatile, to prevent GCC from
removing it if GCC doesn't notice any side effects. You don't always need to
do so, though, and doing so unnecessarily can limit optimization.

When writing a single inline assembly statement containing multiple
instructions, put each instruction on a separate line in a separate quoted
string, and end each string except the last with \n\t to properly indent the
next instruction in the assembly output:

asm ("magic %reg1, #42\n\t"
"more_magic %reg2, %reg3"
: /* outputs */ : /* inputs */ : /* clobbers */);



Appendix I: References

Expand Down
18 changes: 0 additions & 18 deletions trunk/Documentation/DMA-attributes.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -31,21 +31,3 @@ may be weakly ordered, that is that reads and writes may pass each other.
Since it is optional for platforms to implement DMA_ATTR_WEAK_ORDERING,
those that do not will simply ignore the attribute and exhibit default
behavior.

DMA_ATTR_WRITE_COMBINE
----------------------

DMA_ATTR_WRITE_COMBINE specifies that writes to the mapping may be
buffered to improve performance.

Since it is optional for platforms to implement DMA_ATTR_WRITE_COMBINE,
those that do not will simply ignore the attribute and exhibit default
behavior.

DMA_ATTR_NON_CONSISTENT
-----------------------

DMA_ATTR_NON_CONSISTENT lets the platform to choose to return either
consistent or non-consistent memory as it sees fit. By using this API,
you are guaranteeing to the platform that you have all the correct and
necessary sync points for this memory in the driver.
Loading

0 comments on commit bac2b0d

Please sign in to comment.