> -----Original Message-----
> From: Stuart Yoder [mailto:stuart.yo...@freescale.com]
> Sent: Friday, September 25, 2015 4:08 PM
> To: robh...@kernel.org; mark.rutl...@arm.com
> Cc: devicet...@vger.kernel.org; linux-kernel@vger.kernel.org; Rivera
> Jose-B46482; Sharma Bhupesh-B45370; katz Itai-RM05202; Yoder Stuart-
> B08248
> Subject: [PATCH 1/3] Docs: dt: fsl-mc: update binding to include msi-
> parent
> 
> The Freescale Management Complex and all associated objects use message
> interrupts, and thus an msi-parent is required.
> 
> Signed-off-by: Stuart Yoder <stuart.yo...@freescale.com>
> ---
>  Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt
> b/Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt
> index c7a26ca..6aac955 100644
> --- a/Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt
> +++ b/Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt
> @@ -30,11 +30,17 @@ Required properties:
>                          region may not be present in some scenarios,
> such
>                          as in the device tree presented to a virtual
> machine.
> 
> +    - msi-parent
> +        Value type: <phandle>
> +        Definition: Must be present and point to the MSI controller node
> +                    handling message interrupts for the MC.
> +
>  Example:
> 
>          fsl_mc: fsl-mc@80c000000 {
>                  compatible = "fsl,qoriq-mc";
>                  reg = <0x00000008 0x0c000000 0 0x40>,    /* MC portal
> base */
>                        <0x00000000 0x08340000 0 0x40000>; /* MC control
> reg */
> +                msi-parent = <&its>;
>          };
> 
> --
> 2.3.3

Acked-by: J. German Rivera <german.riv...@freescale.com>

--
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/

Reply via email to