On 2014-11-07 14:04, Sanchayan Maity wrote:
> This patch adds a devicetree node for the Secure
> Non-Volatile Storage (SNVS) on the VF610 platform.
> The SNVS block also has a Real Time Counter (RTC).
> 
> Signed-off-by: Sanchayan Maity <[email protected]>
> ---
>  arch/arm/boot/dts/vfxxx.dtsi |   15 +++++++++++++++
>  1 file changed, 15 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/vfxxx.dtsi b/arch/arm/boot/dts/vfxxx.dtsi
> index 4e70833..bc131b0 100644
> --- a/arch/arm/boot/dts/vfxxx.dtsi
> +++ b/arch/arm/boot/dts/vfxxx.dtsi
> @@ -338,6 +338,21 @@
>                               status = "disabled";
>                       };
>  
> +                     snvs0: snvs@400a7000 {
> +                             compatible = "fsl,sec-v4.0-mon", "simple-bus";
> +                             #address-cells = <1>;
> +                             #size-cells = <1>;
> +                             ranges = <0 0x400a7000 0x2000>;
> +
> +                             snvs-rtc-lp@34 {
> +                                     compatible = "fsl,sec-v4.0-mon-rtc-lp";
> +                                     reg = <0x34 0x58>;
> +                                     interrupts = <0 100 
> IRQ_TYPE_LEVEL_HIGH>;

With the new device tree structure, the interrupt field needs to be part
of the vf500.dtsi now. The vfxxx.dtsi will be the parent also for the
Cortex-M4 device tree, which uses a different interrupt controller.

While at it, use the GIC_SPI macro for the first cell (so this will be
blend into the other interrupt definitions).

> +                                     clocks = <&clks VF610_CLK_SNVS>;
> +                                     clock-names = "snvs-rtc";
> +                             };
> +                     };
> +
>                       uart4: serial@400a9000 {
>                               compatible = "fsl,vf610-lpuart";
>                               reg = <0x400a9000 0x1000>;

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
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