Merge branch 'v4.8/dt64' into v4.8/dt64-2

* Amlogic Secure Monitor

In the Amlogic SoCs the Secure Monitor code is used to provide access to the

NVMEM, enable JTAG, set USB boot, etc...

Required properties for the secure monitor node:

- compatible: Should be "amlogic,meson-gxbb-sm"

Example:

	firmware {

		sm: secure-monitor {

			compatible = "amlogic,meson-gxbb-sm";

		};

	};

* Amlogic Meson IR remote control receiver

Required properties:

 - compatible	: should be "amlogic,meson6-ir"

 - compatible	: depending on the platform this should be one of:

		  - "amlogic,meson6-ir"

		  - "amlogic,meson8b-ir"

		  - "amlogic,meson-gxbb-ir"

 - reg		: physical base address and length of the device registers

 - interrupts	: a single specifier for the interrupt from the device

= Amlogic eFuse device tree bindings =

Required properties:

- compatible: should be "amlogic,meson-gxbb-efuse"

= Data cells =

Are child nodes of eFuse, bindings of which as described in

bindings/nvmem/nvmem.txt

Example:

	efuse: efuse {

		compatible = "amlogic,meson-gxbb-efuse";

		#address-cells = <1>;

		#size-cells = <1>;

		sn: sn@14 {

			reg = <0x14 0x10>;

		};

		eth_mac: eth_mac@34 {

			reg = <0x34 0x10>;

		};

		bid: bid@46 {

			reg = <0x46 0x30>;

		};

	};

= Data consumers =

Are device nodes which consume nvmem data cells.

For example:

	eth_mac {

		...

		nvmem-cells = <&eth_mac>;

		nvmem-cell-names = "eth_mac";

	};

	pinctrl-names = "default";

};

&ir {

	status = "okay";

	pinctrl-0 = <&remote_input_ao_pins>;

	pinctrl-names = "default";

};

&i2c_A {

	status = "okay";

	pinctrl-0 = <&i2c_a_pins>;

	pinctrl-names = "default";

};

	compatible = "amlogic,p200", "amlogic,meson-gxbb";

	model = "Amlogic Meson GXBB P200 Development Board";

};

&i2c_B {

	status = "okay";

	pinctrl-0 = <&i2c_b_pins>;

	pinctrl-names = "default";

};