Merge branches 'for-3.8/upstream-fixes', 'for-3.9/hid-sensor',... (539cf54b) · Commits · e / devices / android_kernel_xiaomi_markw

.gitignore

+0 −1

Original line number	Diff line number	Diff line
		@@ -60,7 +60,6 @@ modules.builtin
		# Generated include files
		#
		include/config
		include/linux/version.h
		include/generated
		arch/*/include/generated

Documentation/00-INDEX

+0 −2

Original line number	Diff line number	Diff line
		@@ -136,8 +136,6 @@ fault-injection/
		- dir with docs about the fault injection capabilities infrastructure.
		fb/
		- directory with info on the frame buffer graphics abstraction layer.
		feature-removal-schedule.txt
		- list of files and features that are going to be removed.
		filesystems/
		- info on the vfs and the various filesystems that Linux supports.
		firmware_class/

Documentation/ABI/README

+0 −3

Original line number	Diff line number	Diff line
		@@ -36,9 +36,6 @@ The different levels of stability are:
		the kernel, but are marked to be removed at some later point in
		time. The description of the interface will document the reason
		why it is obsolete and when it can be expected to be removed.
		The file Documentation/feature-removal-schedule.txt may describe
		some of these interfaces, giving a schedule for when they will
		be removed.

		removed/
		This directory contains a list of the old interfaces that have

Documentation/ABI/stable/sysfs-devices-node

+95 −1

Original line number	Diff line number	Diff line
		What: /sys/devices/system/node/possible
		Date: October 2002
		Contact: Linux Memory Management list <linux-mm@kvack.org>
		Description:
		Nodes that could be possibly become online at some point.

		What: /sys/devices/system/node/online
		Date: October 2002
		Contact: Linux Memory Management list <linux-mm@kvack.org>
		Description:
		Nodes that are online.

		What: /sys/devices/system/node/has_normal_memory
		Date: October 2002
		Contact: Linux Memory Management list <linux-mm@kvack.org>
		Description:
		Nodes that have regular memory.

		What: /sys/devices/system/node/has_cpu
		Date: October 2002
		Contact: Linux Memory Management list <linux-mm@kvack.org>
		Description:
		Nodes that have one or more CPUs.

		What: /sys/devices/system/node/has_high_memory
		Date: October 2002
		Contact: Linux Memory Management list <linux-mm@kvack.org>
		Description:
		Nodes that have regular or high memory.
		Depends on CONFIG_HIGHMEM.

		What: /sys/devices/system/node/nodeX
		Date: October 2002
		Contact: Linux Memory Management list <linux-mm@kvack.org>
		Description:
		When CONFIG_NUMA is enabled, this is a directory containing
		information on node X such as what CPUs are local to the
		node.
		node. Each file is detailed next.

		What: /sys/devices/system/node/nodeX/cpumap
		Date: October 2002
		Contact: Linux Memory Management list <linux-mm@kvack.org>
		Description:
		The node's cpumap.

		What: /sys/devices/system/node/nodeX/cpulist
		Date: October 2002
		Contact: Linux Memory Management list <linux-mm@kvack.org>
		Description:
		The CPUs associated to the node.

		What: /sys/devices/system/node/nodeX/meminfo
		Date: October 2002
		Contact: Linux Memory Management list <linux-mm@kvack.org>
		Description:
		Provides information about the node's distribution and memory
		utilization. Similar to /proc/meminfo, see Documentation/filesystems/proc.txt

		What: /sys/devices/system/node/nodeX/numastat
		Date: October 2002
		Contact: Linux Memory Management list <linux-mm@kvack.org>
		Description:
		The node's hit/miss statistics, in units of pages.
		See Documentation/numastat.txt

		What: /sys/devices/system/node/nodeX/distance
		Date: October 2002
		Contact: Linux Memory Management list <linux-mm@kvack.org>
		Description:
		Distance between the node and all the other nodes
		in the system.

		What: /sys/devices/system/node/nodeX/vmstat
		Date: October 2002
		Contact: Linux Memory Management list <linux-mm@kvack.org>
		Description:
		The node's zoned virtual memory statistics.
		This is a superset of numastat.

		What: /sys/devices/system/node/nodeX/compact
		Date: February 2010
		Contact: Mel Gorman <mel@csn.ul.ie>
		Description:
		When this file is written to, all memory within that node
		will be compacted. When it completes, memory will be freed
		into blocks which have as many contiguous pages as possible

		What: /sys/devices/system/node/nodeX/scan_unevictable_pages
		Date: October 2008
		Contact: Lee Schermerhorn <lee.schermerhorn@hp.com>
		Description:
		When set, it triggers scanning the node's unevictable lists
		and move any pages that have become evictable onto the respective
		zone's inactive list. See mm/vmscan.c

		What: /sys/devices/system/node/nodeX/hugepages/hugepages-<size>/
		Date: December 2009
		Contact: Lee Schermerhorn <lee.schermerhorn@hp.com>
		Description:
		The node's huge page size control/query attributes.
		See Documentation/vm/hugetlbpage.txt
		No newline at end of file

Documentation/ABI/stable/sysfs-driver-ib_srp

0 → 100644

+156 −0

Original line number	Diff line number	Diff line
		What: /sys/class/infiniband_srp/srp-<hca>-<port_number>/add_target
		Date: January 2, 2006
		KernelVersion: 2.6.15
		Contact: linux-rdma@vger.kernel.org
		Description: Interface for making ib_srp connect to a new target.
		One can request ib_srp to connect to a new target by writing
		a comma-separated list of login parameters to this sysfs
		attribute. The supported parameters are:
		* id_ext, a 16-digit hexadecimal number specifying the eight
		byte identifier extension in the 16-byte SRP target port
		identifier. The target port identifier is sent by ib_srp
		to the target in the SRP_LOGIN_REQ request.
		* ioc_guid, a 16-digit hexadecimal number specifying the eight
		byte I/O controller GUID portion of the 16-byte target port
		identifier.
		* dgid, a 32-digit hexadecimal number specifying the
		destination GID.
		* pkey, a four-digit hexadecimal number specifying the
		InfiniBand partition key.
		* service_id, a 16-digit hexadecimal number specifying the
		InfiniBand service ID used to establish communication with
		the SRP target. How to find out the value of the service ID
		is specified in the documentation of the SRP target.
		* max_sect, a decimal number specifying the maximum number of
		512-byte sectors to be transferred via a single SCSI command.
		* max_cmd_per_lun, a decimal number specifying the maximum
		number of outstanding commands for a single LUN.
		* io_class, a hexadecimal number specifying the SRP I/O class.
		Must be either 0xff00 (rev 10) or 0x0100 (rev 16a). The I/O
		class defines the format of the SRP initiator and target
		port identifiers.
		* initiator_ext, a 16-digit hexadecimal number specifying the
		identifier extension portion of the SRP initiator port
		identifier. This data is sent by the initiator to the target
		in the SRP_LOGIN_REQ request.
		* cmd_sg_entries, a number in the range 1..255 that specifies
		the maximum number of data buffer descriptors stored in the
		SRP_CMD information unit itself. With allow_ext_sg=0 the
		parameter cmd_sg_entries defines the maximum S/G list length
		for a single SRP_CMD, and commands whose S/G list length
		exceeds this limit after S/G list collapsing will fail.
		* allow_ext_sg, whether ib_srp is allowed to include a partial
		memory descriptor list in an SRP_CMD instead of the entire
		list. If a partial memory descriptor list has been included
		in an SRP_CMD the remaining memory descriptors are
		communicated from initiator to target via an additional RDMA
		transfer. Setting allow_ext_sg to 1 increases the maximum
		amount of data that can be transferred between initiator and
		target via a single SCSI command. Since not all SRP target
		implementations support partial memory descriptor lists the
		default value for this option is 0.
		* sg_tablesize, a number in the range 1..2048 specifying the
		maximum S/G list length the SCSI layer is allowed to pass to
		ib_srp. Specifying a value that exceeds cmd_sg_entries is
		only safe with partial memory descriptor list support enabled
		(allow_ext_sg=1).

		What: /sys/class/infiniband_srp/srp-<hca>-<port_number>/ibdev
		Date: January 2, 2006
		KernelVersion: 2.6.15
		Contact: linux-rdma@vger.kernel.org
		Description: HCA name (<hca>).

		What: /sys/class/infiniband_srp/srp-<hca>-<port_number>/port
		Date: January 2, 2006
		KernelVersion: 2.6.15
		Contact: linux-rdma@vger.kernel.org
		Description: HCA port number (<port_number>).

		What: /sys/class/scsi_host/host<n>/allow_ext_sg
		Date: May 19, 2011
		KernelVersion: 2.6.39
		Contact: linux-rdma@vger.kernel.org
		Description: Whether ib_srp is allowed to include a partial memory
		descriptor list in an SRP_CMD when communicating with an SRP
		target.

		What: /sys/class/scsi_host/host<n>/cmd_sg_entries
		Date: May 19, 2011
		KernelVersion: 2.6.39
		Contact: linux-rdma@vger.kernel.org
		Description: Maximum number of data buffer descriptors that may be sent to
		the target in a single SRP_CMD request.

		What: /sys/class/scsi_host/host<n>/dgid
		Date: June 17, 2006
		KernelVersion: 2.6.17
		Contact: linux-rdma@vger.kernel.org
		Description: InfiniBand destination GID used for communication with the SRP
		target. Differs from orig_dgid if port redirection has happened.

		What: /sys/class/scsi_host/host<n>/id_ext
		Date: June 17, 2006
		KernelVersion: 2.6.17
		Contact: linux-rdma@vger.kernel.org
		Description: Eight-byte identifier extension portion of the 16-byte target
		port identifier.

		What: /sys/class/scsi_host/host<n>/ioc_guid
		Date: June 17, 2006
		KernelVersion: 2.6.17
		Contact: linux-rdma@vger.kernel.org
		Description: Eight-byte I/O controller GUID portion of the 16-byte target
		port identifier.

		What: /sys/class/scsi_host/host<n>/local_ib_device
		Date: November 29, 2006
		KernelVersion: 2.6.19
		Contact: linux-rdma@vger.kernel.org
		Description: Name of the InfiniBand HCA used for communicating with the
		SRP target.

		What: /sys/class/scsi_host/host<n>/local_ib_port
		Date: November 29, 2006
		KernelVersion: 2.6.19
		Contact: linux-rdma@vger.kernel.org
		Description: Number of the HCA port used for communicating with the
		SRP target.

		What: /sys/class/scsi_host/host<n>/orig_dgid
		Date: June 17, 2006
		KernelVersion: 2.6.17
		Contact: linux-rdma@vger.kernel.org
		Description: InfiniBand destination GID specified in the parameters
		written to the add_target sysfs attribute.

		What: /sys/class/scsi_host/host<n>/pkey
		Date: June 17, 2006
		KernelVersion: 2.6.17
		Contact: linux-rdma@vger.kernel.org
		Description: A 16-bit number representing the InfiniBand partition key used
		for communication with the SRP target.

		What: /sys/class/scsi_host/host<n>/req_lim
		Date: October 20, 2010
		KernelVersion: 2.6.36
		Contact: linux-rdma@vger.kernel.org
		Description: Number of requests ib_srp can send to the target before it has
		to wait for more credits. For more information see also the
		SRP credit algorithm in the SRP specification.

		What: /sys/class/scsi_host/host<n>/service_id
		Date: June 17, 2006
		KernelVersion: 2.6.17
		Contact: linux-rdma@vger.kernel.org
		Description: InfiniBand service ID used for establishing communication with
		the SRP target.

		What: /sys/class/scsi_host/host<n>/zero_req_lim
		Date: September 20, 2006
		KernelVersion: 2.6.18
		Contact: linux-rdma@vger.kernel.org
		Description: Number of times the initiator had to wait before sending a
		request to the target because it ran out of credits. For more
		information see also the SRP credit algorithm in the SRP
		specification.