[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4759698.elnRBldlxl@wuerfel>
Date: Mon, 02 May 2016 09:31:12 +0200
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Sanchayan Maity <maitysanchayan@...il.com>, shawnguo@...nel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
stefan@...er.ch, robh+dt@...nel.org, lee.jones@...aro.org
Subject: Re: [PATCH v2 2/5] ARM: dts: vfxxx: Add device tree node for OCOTP
On Monday 02 May 2016 12:35:01 Sanchayan Maity wrote:
> + ocotp@...a5000 {
> + compatible = "fsl,vf610-ocotp";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + reg = <0x400a5000 0xCF0>;
> + clocks = <&clks VF610_CLK_OCOTP>;
> +
> + ocotp_cfg0: cfg0@410 {
> + reg = <0x410 0x4>;
> + };
> +
> + ocotp_cfg1: cfg1@420 {
> + reg = <0x420 0x4>;
> + };
> + };
How do the registers of the child nodes relate to the registers of the
parent? If there are in the same address space, it might be good to
add a "ranges" property to describe it.
Arnd
Download attachment "forwarded message" of type "message/rfc822" (8777 bytes)
Powered by blists - more mailing lists