Merge d83414ff on remote branch

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:

this byte for application use.

	(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) Non-zero tags are not 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 watchpoint debug exceptions, where the tag information

	    will be preserved.

Passing tagged addresses to the kernel

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

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

	    since it is likely that C compilers will not hazard two

	    virtual addresses differing only in the upper byte.

All interpretation of userspace memory addresses by the kernel assumes

an address tag of 0x00.

This includes, but is not limited to, addresses found in:

 - pointer arguments to system calls, including pointers in structures

   passed to system calls,

 - the stack pointer (sp), e.g. when interpreting it to deliver a

   signal,

 - the frame pointer (x29) and frame records, e.g. when interpreting

   them to generate a backtrace or call graph.

Using non-zero address tags in any of these locations may result in an

error code being returned, a (fatal) signal being raised, or other modes

of failure.

For these reasons, passing non-zero address tags to the kernel via

system calls is forbidden, and using a non-zero address tag for sp is

strongly discouraged.

Programs maintaining a frame pointer and frame records that use non-zero

address tags may suffer impaired or inaccurate debug and profiling

visibility.

Preserving tags

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

Non-zero tags are not 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 watchpoint debug exceptions, where the tag information will

be preserved.

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.

Other considerations

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

Special care should be taken when using tagged pointers, since it is

likely that C compilers will not hazard two virtual addresses differing

only in the upper byte.

			    "allwinner,sun6i-a31"

			    "allwinner,sun8i-a23"

			    "arm,psci"

			    "psci"

			    "brcm,brahma-b15"

			    "marvell,armada-375-smp"

			    "marvell,armada-380-smp"

ADV7481 chip driver (VIDEO_ADV7481)

VIDEO_ADV7481 is a kernel platform driver that is used for video decoder

and dual mode HDMI/MHL receiver.

The devicetree representation of the VIDEO_ADV7481 block should be:

Required properties

- compatible: "qcom,adv7481"

- reg: The i2c slave address of adv7481 device.

- qcom,cci-master: The i2c master id to be used for adv7481 driver.

- gpios: The GPIOs required to be configured for the driver. It should

	be in the order I2C data line, i2c clock line, reset line,

	interrupt 1, interrupt 2 and interrupt 3.

- cam_vdig-supply: Should contain regulator to be used for the digital

	vdd.

- cam_vio-supply: Should contain regulator to be used for the IO vdd.

- cam_vana-supply: Should contain regulator from which analog voltage

	is supplied.

- qcom,cam-vreg-name: Should specify array of regulator names required

	for the device.

- qcom,cam-vreg-min-voltage: Should specify array of minimum voltage

	level in uV for the regulators specified in the property

	"qcom,cam-vreg-name".

- qcom,cam-vreg-max-voltage: Should specify array of maximum voltage

	level in uV for the regulators specified in the property

	"qcom,cam-vreg-name".

- qcom,cam-vreg-op-mode: Should specify array of current level in uA

	for the regulators specified in the property "qcom,cam-vreg-name".

Example:

	qcom,adv7481@70 {

		compatible = "qcom,adv7481";

		reg = <0x70 0xff>;

		cam_vdig-supply = <&vph_pwr_vreg>;

		/* Cameras powered by PMIC: */

		cam_vio-supply = <&pm8994_lvs1>;

		cam_vana-supply = <&pm8994_l17>;

		/* Self-powered cameras: */

		qcom,cam-vreg-name = "cam_vdig", "cam_vio", "cam_vana";

		qcom,cam-vreg-min-voltage = <1300000 0 2500000>;

		qcom,cam-vreg-max-voltage = <1300000 0 2500000>;

		qcom,cam-vreg-op-mode = <105000 0 80000>;

		qcom,cci-master = <0>;

		qcom,slave-addr = <0x70>;

		gpios = <&tlmm 17 0>,          /* I2C SDA */

			<&tlmm 18 0>,          /* I2C SCL */

			<&pm8994_gpios 4 0>,   /* RST     */

			<&pm8994_gpios 5 0>,   /* INT1    */

			<&pm8994_gpios 6 0>,   /* INT2    */

			<&pm8994_gpios 7 0>;   /* INT3    */

	};

Android firmware

Node to specify early mount of vendor partition.

Required properties

-compatible: "android,firmware"

Child nodes:

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

fstab:

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

fstab entry to specify mount attributes of vendor partition.

Required properties:

-compatible: "android,fstab"

Child nodes:

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

vendor:

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

vendor partition specification.

Required properties:

-compatible: "android, vendor"

-dev: block device corresponding to vendor partition

-type: file system type of vendor partition

-mnt_flags: mount flags

-fsmgr_flags: fsmgr flags

Example:

	firmware: firmware {

		android {

			compatible = "android,firmware";

			fstab {

				compatible = "android,fstab";

				vendor {

					compatible = "android,vendor";

					dev = "/dev/block/platform/soc/1da4000.ufshc/by-name/vendor";

					type = "ext4";

					mnt_flags = "ro,barrier=1,discard";

					fsmgr_flags = "wait,slotselect";

					status = "ok";

				};

			};

		};

	};

			by pil. Absence of this property indicates that

			subsystem loading through pil voting is disabled for

			that subsystem.

-qcom,dynamic-wakeup-source:	Boolean property to indicate that G-Link

				transport supports dynamic wakeup source

Example:

	qcom,ipc_router_modem_xprt {