From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 5/5] vf610-soc: Add Vybrid SoC device tree binding documentation
Date: Tue, 3 May 2016 21:30:26 -0500 [thread overview]
Message-ID: <20160504023026.GB5382@rob-hp-laptop> (raw)
In-Reply-To: <65f3a7bd7a9faf1b390644d7c599c69683c753c4.1462171990.git.maitysanchayan@gmail.com>
On Mon, May 02, 2016 at 12:35:04PM +0530, Sanchayan Maity wrote:
> Add device tree binding documentation for Vybrid SoC.
>
> Signed-off-by: Sanchayan Maity <maitysanchayan@gmail.com>
> ---
> .../bindings/arm/freescale/fsl,vf610-soc.txt | 35 ++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,vf610-soc.txt
>
> diff --git a/Documentation/devicetree/bindings/arm/freescale/fsl,vf610-soc.txt b/Documentation/devicetree/bindings/arm/freescale/fsl,vf610-soc.txt
> new file mode 100644
> index 0000000..bdd95e8
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/freescale/fsl,vf610-soc.txt
> @@ -0,0 +1,35 @@
> +Vybrid System-on-Chip
> +---------------------
> +
> +Required properties:
> +
> +- #address-cells: must be 1
> +- #size-cells: must be 1
> +- compatible: "fsl,vf610-soc-bus", "simple-bus"
If this is a bus, put the file in bindings/bus/...
> +- interrupt-parent: phandle to the MSCM interrupt router node
> +- ranges
> +- fsl,rom-revision: phandle to the on-chip ROM node and address of rom
> + revision register
Why is this needed here? Can't you search the tree for the ROM node and
get this info.
> +- fsl,cpu-count: phandle to the MSCM CPU configuration node and address of
> + CPU count register
> +- fsl,l2-size: phandle to the MSCM CPU configuration node and address of
> + L2 cache size register
> +- nvmem-cells: phandles to two OCOTP child nodes ocotp_cfg0 and ocotp_cfg1
> +- nvmem-cell-names: should contain string names "cfg0" and "cfg1"
How are all these properties used?
> +
> +Example:
> +
> + soc {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + compatible = "fsl,vf610-soc-bus", "simple-bus";
> + interrupt-parent = <&mscm_ir>;
> + ranges;
> + fsl,rom-revision = <&ocrom 0x80>;
> + fsl,cpu-count = <&mscm_cpucfg 0x2C>;
> + fsl,l2-size = <&mscm_cpucfg 0x14>;
> + nvmem-cells = <&ocotp_cfg0>, <&ocotp_cfg1>;
> + nvmem-cell-names = "cfg0", "cfg1";
> +
> + ...
> + };
> --
> 2.8.2
>
next prev parent reply other threads:[~2016-05-04 2:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 7:04 [PATCH v2 0/5] Implement SoC bus driver for Vybrid Sanchayan Maity
2016-05-02 7:05 ` [PATCH v2 1/5] mfd: syscon: Introduce syscon_regmap_read_from_offset Sanchayan Maity
2016-05-02 7:05 ` [PATCH v2 2/5] ARM: dts: vfxxx: Add device tree node for OCOTP Sanchayan Maity
2016-05-02 7:31 ` Arnd Bergmann
2016-05-02 8:12 ` maitysanchayan at gmail.com
2016-05-02 7:05 ` [PATCH v2 3/5] ARM: dts: vfxxx: Add OCROM and phandle entries for Vybrid SoC bus driver Sanchayan Maity
2016-05-02 7:05 ` [PATCH v2 4/5] soc: Add SoC bus driver for Freescale Vybrid Platform Sanchayan Maity
2016-05-02 7:05 ` [PATCH v2 5/5] vf610-soc: Add Vybrid SoC device tree binding documentation Sanchayan Maity
2016-05-04 2:30 ` Rob Herring [this message]
2016-05-05 8:27 ` maitysanchayan at gmail.com
2016-05-09 17:14 ` Rob Herring
2016-05-09 18:25 ` Stefan Agner
2016-05-09 22:58 ` Rob Herring
2016-05-10 1:13 ` Stefan Agner
2016-05-11 3:24 ` Rob Herring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160504023026.GB5382@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox