On Thu, Jan 15, 2015 at 08:04:05AM +0000, Stefan Agner wrote:
> Add binding documentation for Miscellaneous System Control Module
> found in Freescale Vybrid SoC's.
>
> Signed-off-by: Stefan Agner <ste...@agner.ch>
> ---
> .../bindings/arm/freescale/fsl,vf610-mscm.txt | 19
> +++++++++++++++++++
> 1 file changed, 19 insertions(+)
> create mode 100644
> Documentation/devicetree/bindings/arm/freescale/fsl,vf610-mscm.txt
>
> diff --git
> a/Documentation/devicetree/bindings/arm/freescale/fsl,vf610-mscm.txt
> b/Documentation/devicetree/bindings/arm/freescale/fsl,vf610-mscm.txt
> new file mode 100644
> index 0000000..e051b88
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/freescale/fsl,vf610-mscm.txt
> @@ -0,0 +1,19 @@
> +Freescale Vybrid Miscellaneous System Control Module
> +
> +The MSCM IP contains Access Control and TrustZone Security hardware,
> +CPU Configuration registers and Interrupt Router control.
> +
> +Required properties:
> +- compatible : "fsl,vf610-mscm", "syscon"
I'm a little concerned by this also being a syscon. What other devices
need to refer to this block as a syscon?
> +- interrupt-controller : Identifies the node as an interrupt controller
> +- #interrupt-cells : Two cells, interrupt number and flags (IRQ type)
What numbers and flags are valid?
Mark.
> +- reg : the register range of the MSCM module
> +
> +Example:
> + mscm: mscm@40001000 {
> + compatible = "fsl,vf610-mscm", "syscon";
> + interrupt-controller;
> + #interrupt-cells = <2>;
> + interrupt-parent = <&intc>;
> + reg = <0x40001000 0x1000>;
> + }
> --
> 2.2.1
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
