dt-bindings: sram: Merge Amlogic SRAM bindings into generic

Amlogic Meson8 and Meson8b SRAM for smp bringup:

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

Amlogic's SMP-capable SoCs use part of the sram for the bringup of the cores.

Once the core gets powered up it executes the code that is residing at a

specific location.

Therefore a reserved section sub-node has to be added to the mmio-sram

declaration.

Required sub-node properties:

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

		"amlogic,meson8-smp-sram"

		"amlogic,meson8b-smp-sram"

The rest of the properties should follow the generic mmio-sram discription

found in ../../misc/sram.txt

Example:

	sram: sram@d9000000 {

		compatible = "mmio-sram";

		reg = <0xd9000000 0x20000>;

		#address-cells = <1>;

		#size-cells = <1>;

		ranges = <0 0xd9000000 0x20000>;

		smp-sram@1ff80 {

			compatible = "amlogic,meson8b-smp-sram";

			reg = <0x1ff80 0x8>;

		};

	};

          Should contain a vendor specific string in the form

          <vendor>,[<device>-]<usage>

        enum:

          - amlogic,meson8-smp-sram

          - amlogic,meson8b-smp-sram

          - samsung,exynos4210-sysram

          - samsung,exynos4210-sysram-ns

            reg = <0x53000 0x1000>;

        };

    };

  - |

    // Amlogic's SMP-capable SoCs use part of the sram for the bringup of the cores.

    // Once the core gets powered up it executes the code that is residing at a

    // specific location.

    //

    // Therefore a reserved section sub-node has to be added to the mmio-sram

    // declaration.

    sram@d9000000 {

        compatible = "mmio-sram";

        reg = <0xd9000000 0x20000>;

        #address-cells = <1>;

        #size-cells = <1>;

        ranges = <0 0xd9000000 0x20000>;

        smp-sram@1ff80 {

            compatible = "amlogic,meson8b-smp-sram";

            reg = <0x1ff80 0x8>;

        };

    };