Merge commit 'v2.6.36-rc3' into x86/memblock (daab7fc7) · Commits · e / devices / android_kernel_teracube_2e

Documentation/00-INDEX

+2 −2

Original line number	Diff line number	Diff line
		@@ -130,8 +130,6 @@ edac.txt
		- information on EDAC - Error Detection And Correction
		eisa.txt
		- info on EISA bus support.
		exception.txt
		- how Linux v2.2 handles exceptions without verify_area etc.
		fault-injection/
		- dir with docs about the fault injection capabilities infrastructure.
		fb/
		@@ -234,6 +232,8 @@ memory.txt
		- info on typical Linux memory problems.
		mips/
		- directory with info about Linux on MIPS architecture.
		mmc/
		- directory with info about the MMC subsystem
		mono.txt
		- how to execute Mono-based .NET binaries with the help of BINFMT_MISC.
		mutex-design.txt

Documentation/ABI/testing/debugfs-ec

0 → 100644

+20 −0

Original line number	Diff line number	Diff line
		What: /sys/kernel/debug/ec/*/{gpe,use_global_lock,io}
		Date: July 2010
		Contact: Thomas Renninger <trenn@suse.de>
		Description:

		General information like which GPE is assigned to the EC and whether
		the global lock should get used.
		Knowing the EC GPE one can watch the amount of HW events related to
		the EC here (XY -> GPE number from /sys/kernel/debug/ec/*/gpe):
		/sys/firmware/acpi/interrupts/gpeXY

		The io file is binary and a userspace tool located here:
		ftp://ftp.suse.com/pub/people/trenn/sources/ec/
		should get used to read out the 256 Embedded Controller registers
		or writing to them.

		CAUTION: Do not write to the Embedded Controller if you don't know
		what you are doing! Rebooting afterwards also is a good idea.
		This can influence the way your machine is cooled and fans may
		not get switched on again after you did a wrong write.

Documentation/ABI/testing/debugfs-kmemtrace

deleted100644 → 0

+0 −71

Original line number	Diff line number	Diff line
		What: /sys/kernel/debug/kmemtrace/
		Date: July 2008
		Contact: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
		Description:

		In kmemtrace-enabled kernels, the following files are created:

		/sys/kernel/debug/kmemtrace/
		cpu<n> (0400) Per-CPU tracing data, see below. (binary)
		total_overruns (0400) Total number of bytes which were dropped from
		cpu<n> files because of full buffer condition,
		non-binary. (text)
		abi_version (0400) Kernel's kmemtrace ABI version. (text)

		Each per-CPU file should be read according to the relay interface. That is,
		the reader should set affinity to that specific CPU and, as currently done by
		the userspace application (though there are other methods), use poll() with
		an infinite timeout before every read(). Otherwise, erroneous data may be
		read. The binary data has the following _core_ format:

		Event ID (1 byte) Unsigned integer, one of:
		0 - represents an allocation (KMEMTRACE_EVENT_ALLOC)
		1 - represents a freeing of previously allocated memory
		(KMEMTRACE_EVENT_FREE)
		Type ID (1 byte) Unsigned integer, one of:
		0 - this is a kmalloc() / kfree()
		1 - this is a kmem_cache_alloc() / kmem_cache_free()
		2 - this is a __get_free_pages() et al.
		Event size (2 bytes) Unsigned integer representing the
		size of this event. Used to extend
		kmemtrace. Discard the bytes you
		don't know about.
		Sequence number (4 bytes) Signed integer used to reorder data
		logged on SMP machines. Wraparound
		must be taken into account, although
		it is unlikely.
		Caller address (8 bytes) Return address to the caller.
		Pointer to mem (8 bytes) Pointer to target memory area. Can be
		NULL, but not all such calls might be
		recorded.

		In case of KMEMTRACE_EVENT_ALLOC events, the next fields follow:

		Requested bytes (8 bytes) Total number of requested bytes,
		unsigned, must not be zero.
		Allocated bytes (8 bytes) Total number of actually allocated
		bytes, unsigned, must not be lower
		than requested bytes.
		Requested flags (4 bytes) GFP flags supplied by the caller.
		Target CPU (4 bytes) Signed integer, valid for event id 1.
		If equal to -1, target CPU is the same
		as origin CPU, but the reverse might
		not be true.

		The data is made available in the same endianness the machine has.

		Other event ids and type ids may be defined and added. Other fields may be
		added by increasing event size, but see below for details.
		Every modification to the ABI, including new id definitions, are followed
		by bumping the ABI version by one.

		Adding new data to the packet (features) is done at the end of the mandatory
		data:
		Feature size (2 byte)
		Feature ID (1 byte)
		Feature data (Feature size - 3 bytes)


		Users:
		kmemtrace-user - git://repo.or.cz/kmemtrace-user.git

Documentation/ABI/testing/sysfs-bus-i2c-devices-hm6352

0 → 100644

+21 −0

Original line number	Diff line number	Diff line
		Where: /sys/bus/i2c/devices/.../heading0_input
		Date: April 2010
		Kernel Version: 2.6.36?
		Contact: alan.cox@intel.com
		Description: Reports the current heading from the compass as a floating
		point value in degrees.

		Where: /sys/bus/i2c/devices/.../power_state
		Date: April 2010
		Kernel Version: 2.6.36?
		Contact: alan.cox@intel.com
		Description: Sets the power state of the device. 0 sets the device into
		sleep mode, 1 wakes it up.

		Where: /sys/bus/i2c/devices/.../calibration
		Date: April 2010
		Kernel Version: 2.6.36?
		Contact: alan.cox@intel.com
		Description: Sets the calibration on or off (1 = on, 0 = off). See the
		chip data sheet.

Documentation/ABI/testing/sysfs-bus-pci

+27 −0

Original line number	Diff line number	Diff line
		@@ -139,3 +139,30 @@ Contact: linux-pci@vger.kernel.org
		Description:
		This symbolic link points to the PCI hotplug controller driver
		module that manages the hotplug slot.

		What: /sys/bus/pci/devices/.../label
		Date: July 2010
		Contact: Narendra K <narendra_k@dell.com>, linux-bugs@dell.com
		Description:
		Reading this attribute will provide the firmware
		given name(SMBIOS type 41 string) of the PCI device.
		The attribute will be created only if the firmware
		has given a name to the PCI device.
		Users:
		Userspace applications interested in knowing the
		firmware assigned name of the PCI device.

		What: /sys/bus/pci/devices/.../index
		Date: July 2010
		Contact: Narendra K <narendra_k@dell.com>, linux-bugs@dell.com
		Description:
		Reading this attribute will provide the firmware
		given instance(SMBIOS type 41 device type instance)
		of the PCI device. The attribute will be created
		only if the firmware has given a device type instance
		to the PCI device.
		Users:
		Userspace applications interested in knowing the
		firmware assigned device type instance of the PCI
		device that can help in understanding the firmware
		intended order of the PCI device.