Merge "Merge branch '8916-dev-phase2' into msm-3.10."

Requirement: MANDATORY

The decompressed kernel image contains a 32-byte header as follows:

The decompressed kernel image contains a 64-byte header as follows:

  u32 magic	= 0x14000008;	/* branch to stext, little-endian */

  u32 res0	= 0;		/* reserved */

  u32 code0;			/* Executable code */

  u32 code1;			/* Executable code */

  u64 text_offset;		/* Image load offset */

  u64 res0	= 0;		/* reserved */

  u64 res1	= 0;		/* reserved */

  u64 res2	= 0;		/* reserved */

  u64 res3	= 0;		/* reserved */

  u64 res4	= 0;		/* reserved */

  u32 magic	= 0x644d5241;	/* Magic number, little endian, "ARM\x64" */

  u32 res5 = 0;      		/* reserved */

Header notes:

- code0/code1 are responsible for branching to stext.

The image must be placed at the specified offset (currently 0x80000)

from the start of the system RAM and called there. The start of the

TTBR0.

AArch64 Linux memory layout:

AArch64 Linux memory layout with 4KB pages:

Start			End			Size		Use

-----------------------------------------------------------------------

ffffffc000000000	ffffffffffffffff	 256GB		kernel logical memory map

AArch64 Linux memory layout with 64KB pages:

Start			End			Size		Use

-----------------------------------------------------------------------

0000000000000000	000003ffffffffff	   4TB		user

fffffc0000000000	fffffdfbfffeffff	  ~2TB		vmalloc

fffffdfbffff0000	fffffdfbffffffff	  64KB		[guard page]

fffffdfc00000000	fffffdfdffffffff	   8GB		vmemmap

fffffdfe00000000	fffffdfffbbfffff	  ~8GB		[guard, future vmmemap]

fffffdfffbc00000	fffffdfffbdfffff	   2MB		earlyprintk device

fffffdfffbe00000	fffffdfffbe0ffff	  64KB		PCI I/O space

fffffdfffbe10000	fffffdfffbffffff	  ~2MB		[guard]

fffffdfffc000000	fffffdffffffffff	  64MB		modules

fffffe0000000000	ffffffffffffffff	   2TB		kernel logical memory map

Translation table lookup with 4KB pages:

+--------+--------+--------+--------+--------+--------+--------+--------+

		Tagged virtual addresses in AArch64 Linux

		=========================================

Author: Will Deacon <will.deacon@arm.com>

Date  : 12 June 2013

This document briefly describes the provision of tagged virtual

addresses in the AArch64 translation system and their potential uses

in AArch64 Linux.

The kernel configures the translation tables so that translations made

via TTBR0 (i.e. userspace mappings) have the top byte (bits 63:56) of

the virtual address ignored by the translation hardware. This frees up

this byte for application use, with the following caveats:

	(1) The kernel requires that all user addresses passed to EL1

	    are tagged with tag 0x00. This means that any syscall

	    parameters containing user virtual addresses *must* have

	    their top byte cleared before trapping to the kernel.

	(2) Tags are not guaranteed to be preserved when delivering

	    signals. This means that signal handlers in applications

	    making use of tags cannot rely on the tag information for

	    user virtual addresses being maintained for fields inside

	    siginfo_t. One exception to this rule is for signals raised

	    in response to debug exceptions, where the tag information

	    will be preserved.

	(3) Special care should be taken when using tagged pointers,

	    since it is likely that C compilers will not hazard two

	    addresses differing only in the upper bits.

The architecture prevents the use of a tagged PC, so the upper byte will

be set to a sign-extension of bit 55 on exception return.

			phandle_of_regulator is defined by reuglator device tree.

Optional child nodes

- qcom,pmic-opt-curr-temp: Threshold temperature for requesting optimum current (request

			dual phase) for rails with PMIC, in degC. If this property exists,

			then the properties, qcom,pmic-opt-curr-temp-hysteresis and

			qcom,pmic-opt-curr-regs should also be defined to enable this

			feature.

- qcom,pmic-opt-curr-temp-hysteresis: Degree below the threshold to disable the optimum

			current request for a rail, in degC. If this property exists,

			then the properties, qcom,pmic-opt-curr-temp and

			qcom,pmic-opt-curr-regs should also be defined to enable

			this feature.

- qcom,pmic-opt-curr-regs: Name of the rails for which the optimum current should be

			requested. If this property exists, then the properties,

			qcom,pmic-opt-curr-temp and qcom,pmic-opt-curr-temp-hysteresis

			should also be defined to enable this feature.

- qcom,pmic-opt-curr-sensor-id: Sensor, which needs to be monitored for requesting OCR

			when qcom,pmic-opt-curr-temp threshold is reached.

			It is an optional property, if it is configured, msm_thermal will

			monitor only this sensor, otherwise it will monitor all TSENS for

			this feature. If this property exists, then the properties,

			qcom,pmic-opt-curr-temp, qcom,pmic-opt-curr-temp-hysteresis and

			qcom,pmic-opt-curr-regs should also be defined to enable this feature.

- qcom,<vdd restriction child node name>: Define the name of the child node.

			If this property exisits, qcom,vdd-rstr-reg, qcom,levels

			need to exist. qcom,min-level is optional if qcom,freq-req

config HAVE_DMA_CONTIGUOUS

	bool

config USE_GENERIC_SMP_HELPERS

	bool

config GENERIC_SMP_IDLE_THREAD

       bool