Merge tag 'omap-for-v3.19/fixes-for-merge-window' of... (1888d2fa) · Commits · e / devices / android_kernel_teracube_mt6765

Documentation/ABI/stable/sysfs-driver-ib_srp

+19 −6

Original line number	Diff line number	Diff line
		@@ -55,12 +55,12 @@ Description: Interface for making ib_srp connect to a new target.
		only safe with partial memory descriptor list support enabled
		(allow_ext_sg=1).
		* comp_vector, a number in the range 0..n-1 specifying the
		MSI-X completion vector. Some HCA's allocate multiple (n)
		MSI-X vectors per HCA port. If the IRQ affinity masks of
		these interrupts have been configured such that each MSI-X
		interrupt is handled by a different CPU then the comp_vector
		parameter can be used to spread the SRP completion workload
		over multiple CPU's.
		MSI-X completion vector of the first RDMA channel. Some
		HCA's allocate multiple (n) MSI-X vectors per HCA port. If
		the IRQ affinity masks of these interrupts have been
		configured such that each MSI-X interrupt is handled by a
		different CPU then the comp_vector parameter can be used to
		spread the SRP completion workload over multiple CPU's.
		* tl_retry_count, a number in the range 2..7 specifying the
		IB RC retry count.
		* queue_size, the maximum number of commands that the
		@@ -88,6 +88,13 @@ 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>/ch_count
		Date: April 1, 2015
		KernelVersion: 3.19
		Contact: linux-rdma@vger.kernel.org
		Description: Number of RDMA channels used for communication with the SRP
		target.

		What: /sys/class/scsi_host/host<n>/cmd_sg_entries
		Date: May 19, 2011
		KernelVersion: 2.6.39
		@@ -95,6 +102,12 @@ 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>/comp_vector
		Date: September 2, 2013
		KernelVersion: 3.11
		Contact: linux-rdma@vger.kernel.org
		Description: Completion vector used for the first RDMA channel.

		What: /sys/class/scsi_host/host<n>/dgid
		Date: June 17, 2006
		KernelVersion: 2.6.17

Documentation/arm/firmware.txt

+5 −23

Original line number	Diff line number	Diff line
		@@ -7,32 +7,14 @@ world, which changes the way some things have to be initialized. This makes
		a need to provide an interface for such platforms to specify available firmware
		operations and call them when needed.

		Firmware operations can be specified using struct firmware_ops

		struct firmware_ops {
		/*
		* Enters CPU idle mode
		*/
		int (*do_idle)(void);
		/*
		* Sets boot address of specified physical CPU
		*/
		int (*set_cpu_boot_addr)(int cpu, unsigned long boot_addr);
		/*
		* Boots specified physical CPU
		*/
		int (*cpu_boot)(int cpu);
		/*
		* Initializes L2 cache
		*/
		int (*l2x0_init)(void);
		};

		and then registered with register_firmware_ops function
		Firmware operations can be specified by filling in a struct firmware_ops
		with appropriate callbacks and then registering it with register_firmware_ops()
		function.

		void register_firmware_ops(const struct firmware_ops *ops)

		the ops pointer must be non-NULL.
		The ops pointer must be non-NULL. More information about struct firmware_ops
		and its members can be found in arch/arm/include/asm/firmware.h header.

		There is a default, empty set of operations provided, so there is no need to
		set anything if platform does not require firmware operations.

Documentation/arm/sunxi/README

+13 −3

Original line number	Diff line number	Diff line
		@@ -37,16 +37,26 @@ SunXi family
		http://dl.linux-sunxi.org/A20/A20%20User%20Manual%202013-03-22.pdf

		- Allwinner A23
		+ Not Supported
		+ Datasheet
		http://dl.linux-sunxi.org/A23/A23%20Datasheet%20V1.0%2020130830.pdf
		+ User Manual
		http://dl.linux-sunxi.org/A23/A23%20User%20Manual%20V1.0%2020130830.pdf

		* Quad ARM Cortex-A7 based SoCs
		- Allwinner A31 (sun6i)
		+ Datasheet
		http://dl.linux-sunxi.org/A31/A31%20Datasheet%20-%20v1.00%20(2012-12-24).pdf
		http://dl.linux-sunxi.org/A31/A3x_release_document/A31/IC/A31%20datasheet%20V1.3%2020131106.pdf
		+ User Manual
		http://dl.linux-sunxi.org/A31/A3x_release_document/A31/IC/A31%20user%20manual%20V1.1%2020130630.pdf

		- Allwinner A31s (sun6i)
		+ Not Supported
		+ Datasheet
		http://dl.linux-sunxi.org/A31/A3x_release_document/A31s/IC/A31s%20datasheet%20V1.3%2020131106.pdf
		+ User Manual
		http://dl.linux-sunxi.org/A31/A3x_release_document/A31s/IC/A31s%20User%20Manual%20%20V1.0%2020130322.pdf

		* Quad ARM Cortex-A15, Quad ARM Cortex-A7 based SoCs
		- Allwinner A80
		+ Not Supported
		No newline at end of file
		+ Datasheet
		http://dl.linux-sunxi.org/A80/A80_Datasheet_Revision_1.0_0404.pdf

Documentation/arm64/legacy_instructions.txt

0 → 100644

+45 −0

Original line number	Diff line number	Diff line
		The arm64 port of the Linux kernel provides infrastructure to support
		emulation of instructions which have been deprecated, or obsoleted in
		the architecture. The infrastructure code uses undefined instruction
		hooks to support emulation. Where available it also allows turning on
		the instruction execution in hardware.

		The emulation mode can be controlled by writing to sysctl nodes
		(/proc/sys/abi). The following explains the different execution
		behaviours and the corresponding values of the sysctl nodes -

		* Undef
		Value: 0
		Generates undefined instruction abort. Default for instructions that
		have been obsoleted in the architecture, e.g., SWP

		* Emulate
		Value: 1
		Uses software emulation. To aid migration of software, in this mode
		usage of emulated instruction is traced as well as rate limited
		warnings are issued. This is the default for deprecated
		instructions, .e.g., CP15 barriers

		* Hardware Execution
		Value: 2
		Although marked as deprecated, some implementations may support the
		enabling/disabling of hardware support for the execution of these
		instructions. Using hardware execution generally provides better
		performance, but at the loss of ability to gather runtime statistics
		about the use of the deprecated instructions.

		The default mode depends on the status of the instruction in the
		architecture. Deprecated instructions should default to emulation
		while obsolete instructions must be undefined by default.

		Supported legacy instructions
		-----------------------------
		* SWP{B}
		Node: /proc/sys/abi/swp
		Status: Obsolete
		Default: Undef (0)

		* CP15 Barriers
		Node: /proc/sys/abi/cp15_barrier
		Status: Deprecated
		Default: Emulate (1)

Documentation/block/biodoc.txt

+0 −4

Original line number	Diff line number	Diff line
		@@ -827,10 +827,6 @@ but in the event of any barrier requests in the tag queue we need to ensure
		that requests are restarted in the order they were queue. This may happen
		if the driver needs to use blk_queue_invalidate_tags().

		Tagging also defines a new request flag, REQ_QUEUED. This is set whenever
		a request is currently tagged. You should not use this flag directly,
		blk_rq_tagged(rq) is the portable way to do so.

		3.3 I/O Submission

		The routine submit_bio() is used to submit a single io. Higher level i/o