dt-bindings: Add snapshot for 5.4-rc2

Actions Semi platforms device tree bindings

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

S500 SoC

========

Required root node properties:

 - compatible :  must contain "actions,s500"

Modules:

Root node property compatible must contain, depending on module:

 - LeMaker Guitar: "lemaker,guitar"

Boards:

Root node property compatible must contain, depending on board:

 - Allo.com Sparky: "allo,sparky"

 - Cubietech CubieBoard6: "cubietech,cubieboard6"

 - LeMaker Guitar Base Board rev. B: "lemaker,guitar-bb-rev-b", "lemaker,guitar"

S700 SoC

========

Required root node properties:

- compatible :  must contain "actions,s700"

Boards:

Root node property compatible must contain, depending on board:

 - Cubietech CubieBoard7: "cubietech,cubieboard7"

S900 SoC

========

Required root node properties:

- compatible :  must contain "actions,s900"

Boards:

Root node property compatible must contain, depending on board:

 - uCRobotics Bubblegum-96: "ucrobotics,bubblegum-96"

Amlogic Meson Firmware registers Interface

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

The Meson SoCs have a register bank with status and data shared with the

secure firmware.

Required properties:

 - compatible: For Meson GX SoCs, must be "amlogic,meson-gx-ao-secure", "syscon"

Properties should indentify components of this register interface :

Meson GX SoC Information

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

A firmware register encodes the SoC type, package and revision information on

the Meson GX SoCs.

If present, the following property should be added :

Optional properties:

  - amlogic,has-chip-id: If present, the interface gives the current SoC version.

Example

-------

ao-secure@140 {

	compatible = "amlogic,meson-gx-ao-secure", "syscon";

	reg = <0x0 0x140 0x0 0x140>;

	amlogic,has-chip-id;

};

# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)

# Copyright 2019 BayLibre, SAS

%YAML 1.2

---

$id: "http://devicetree.org/schemas/arm/amlogic/amlogic,meson-gx-ao-secure.yaml#"

$schema: "http://devicetree.org/meta-schemas/core.yaml#"

title: Amlogic Meson Firmware registers Interface

maintainers:

  - Neil Armstrong <narmstrong@baylibre.com>

description: |

  The Meson SoCs have a register bank with status and data shared with the

  secure firmware.

# We need a select here so we don't match all nodes with 'syscon'

select:

  properties:

    compatible:

      contains:

        const: amlogic,meson-gx-ao-secure

  required:

    - compatible

properties:

  compatible:

   items:

      - const: amlogic,meson-gx-ao-secure

      - const: syscon

  reg:

    maxItems: 1

  amlogic,has-chip-id:

    description: |

      A firmware register encodes the SoC type, package and revision

      information on the Meson GX SoCs. If present, the interface gives

      the current SoC version.

    type: boolean

required:

  - compatible

  - reg

examples:

  - |

    ao-secure@140 {

          compatible = "amlogic,meson-gx-ao-secure", "syscon";

          reg = <0x140 0x140>;

          amlogic,has-chip-id;

    };

-------

The Device Tree node representing the AP806 system controller provides

a number of clocks:

The Device Tree node representing the AP806/AP807 system controller

provides a number of clocks:

 - 0: clock of CPU cluster 0

 - 1: clock of CPU cluster 1

 - 0: reference clock of CPU cluster 0

 - 1: reference clock of CPU cluster 1

 - 2: fixed PLL at 1200 Mhz

 - 3: MSS clock, derived from the fixed PLL

Required properties:

 - compatible: must be: "marvell,ap806-clock"

 - compatible: must be one of:

   * "marvell,ap806-clock"

   * "marvell,ap807-clock"

 - #clock-cells: must be set to 1

Pinctrl:

		#thermal-sensor-cells = <1>;

	};

};

Cluster clocks:

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

Device Tree Clock bindings for cluster clock of Marvell

AP806/AP807. Each cluster contain up to 2 CPUs running at the same

frequency.

Required properties:

 - compatible: must be one of:

   * "marvell,ap806-cpu-clock"

   * "marvell,ap807-cpu-clock"

- #clock-cells : should be set to 1.

- clocks : shall be the input parent clock(s) phandle for the clock

           (one per cluster)

- reg: register range associated with the cluster clocks

ap_syscon1: system-controller@6f8000 {

	compatible = "marvell,armada-ap806-syscon1", "syscon", "simple-mfd";

	reg = <0x6f8000 0x1000>;

	cpu_clk: clock-cpu@278 {

		compatible = "marvell,ap806-cpu-clock";

		clocks = <&ap_clk 0>, <&ap_clk 1>;

		#clock-cells = <1>;

		reg = <0x278 0xa30>;

	};

};

	compatible = "marvell,armada-3700-avs", "syscon";

	reg = <0x11500 0x40>;

}

CZ.NIC's Turris Mox SOHO router Device Tree Bindings

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

Required root node property:

 - compatible: must contain "cznic,turris-mox"