Merge tag 'amlogic-dt64' of...

* Amlogic GXBB AO Clock and Reset Unit

The Amlogic GXBB AO clock controller generates and supplies clock to various

controllers within the Always-On part of the SoC.

Required Properties:

- compatible: should be "amlogic,gxbb-aoclkc"

- reg: physical base address of the clock controller and length of memory

       mapped region.

- #clock-cells: should be 1.

Each clock is assigned an identifier and client nodes can use this identifier

to specify the clock which they consume. All available clocks are defined as

preprocessor macros in the dt-bindings/clock/gxbb-aoclkc.h header and can be

used in device tree sources.

- #reset-cells: should be 1.

Each reset is assigned an identifier and client nodes can use this identifier

to specify the reset which they consume. All available resets are defined as

preprocessor macros in the dt-bindings/reset/gxbb-aoclkc.h header and can be

used in device tree sources.

Example: AO Clock controller node:

	clkc_AO: clock-controller@040 {

		compatible = "amlogic,gxbb-aoclkc";

		reg = <0x0 0x040 0x0 0x4>;

		#clock-cells = <1>;

		#reset-cells = <1>;

	};

Example: UART controller node that consumes the clock and reset generated

  by the clock controller:

	uart_AO: serial@4c0 {

		compatible = "amlogic,meson-uart";

		reg = <0x4c0 0x14>;

		interrupts = <0 90 1>;

		clocks = <&clkc_AO CLKID_AO_UART1>;

		resets = <&clkc_AO RESET_AO_UART1>;

		status = "disabled";

	};

* 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";

};