Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1392034
| From | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2 2/5] ARM: dts: vfxxx: Add device tree node for OCOTP |
| Date | 2016-05-02 09:40 +0200 |
| Message-ID | <rugCu-7Ih-1@gated-at.bofh.it> (permalink) |
| References | <rugj7-7xc-5@gated-at.bofh.it> <rugj8-7xc-27@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Monday 02 May 2016 12:35:01 Sanchayan Maity wrote:
> + ocotp@400a5000 {
> + 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
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v2 0/5] Implement SoC bus driver for Vybrid Sanchayan Maity <maitysanchayan@gmail.com> - 2016-05-02 09:20 +0200
[PATCH v2 1/5] mfd: syscon: Introduce syscon_regmap_read_from_offset Sanchayan Maity <maitysanchayan@gmail.com> - 2016-05-02 09:20 +0200
[PATCH v2 2/5] ARM: dts: vfxxx: Add device tree node for OCOTP Sanchayan Maity <maitysanchayan@gmail.com> - 2016-05-02 09:20 +0200
Re: [PATCH v2 2/5] ARM: dts: vfxxx: Add device tree node for OCOTP Arnd Bergmann <arnd@arndb.de> - 2016-05-02 09:40 +0200
Re: [PATCH v2 2/5] ARM: dts: vfxxx: Add device tree node for OCOTP maitysanchayan@gmail.com - 2016-05-02 10:20 +0200
csiph-web