From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] dt-bindings: Add documentation for Broadcom Vulcan
Date: Wed, 17 Feb 2016 17:17:01 +0000 [thread overview]
Message-ID: <20160217171700.GI32647@leverpostej> (raw)
In-Reply-To: <1455389195-31870-3-git-send-email-jchandra@broadcom.com>
On Sun, Feb 14, 2016 at 12:16:33AM +0530, Jayachandran C wrote:
> Update arm/cpus.txt to add brcm,vulcan CPU. Add documentation
> for Broadcom vulcan boards in arm/bcm/brcm,vulcan.txt
>
> Signed-off-by: Jayachandran C <jchandra@broadcom.com>
> ---
> Documentation/devicetree/bindings/arm/bcm/brcm,vulcan.txt | 9 +++++++++
> Documentation/devicetree/bindings/arm/cpus.txt | 1 +
> 2 files changed, 10 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,vulcan.txt
>
> diff --git a/Documentation/devicetree/bindings/arm/bcm/brcm,vulcan.txt b/Documentation/devicetree/bindings/arm/bcm/brcm,vulcan.txt
> new file mode 100644
> index 0000000..dac9eb5
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/bcm/brcm,vulcan.txt
> @@ -0,0 +1,9 @@
> +Broadcom Vulcan device tree bindings
> +------------------------------------
> +
> +Boards with Broadcom Vulcan shall have the following properties:
> +
> +Required root node property:
> +
> +Vulcan Evaluation Board
> +compatible = "brcm,vulcan-eval", "brcm,vulcan";
You can't use "brcm,vulcan" as both a board and CPU string.
Please come up with different strings.
Mark.
> diff --git a/Documentation/devicetree/bindings/arm/cpus.txt b/Documentation/devicetree/bindings/arm/cpus.txt
> index ae9be07..bc43ad7 100644
> --- a/Documentation/devicetree/bindings/arm/cpus.txt
> +++ b/Documentation/devicetree/bindings/arm/cpus.txt
> @@ -167,6 +167,7 @@ nodes to be present and contain the properties described below.
> "arm,cortex-r5"
> "arm,cortex-r7"
> "brcm,brahma-b15"
> + "brcm,vulcan"
> "cavium,thunder"
> "faraday,fa526"
> "intel,sa110"
> --
> 1.9.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2016-02-17 17:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 18:46 [PATCH 0/4] Support for Broadcom Vulcan ARM64 processor Jayachandran C
2016-02-13 18:46 ` [PATCH 1/4] arm64: Broadcom Vulcan support Jayachandran C
2016-02-17 1:22 ` Florian Fainelli
2016-02-17 17:16 ` Mark Rutland
2016-02-19 6:58 ` Jayachandran Chandrashekaran Nair
2016-02-18 18:15 ` [1/4] " Ray Jui
2016-02-19 19:24 ` Florian Fainelli
2016-02-13 18:46 ` [PATCH 2/4] dt-bindings: Add documentation for Broadcom Vulcan Jayachandran C
2016-02-17 17:17 ` Mark Rutland [this message]
2016-02-13 18:46 ` [PATCH 3/4] arm64: defconfig: Add Broadcom Vulcan to defconfig Jayachandran C
2016-02-13 18:46 ` [PATCH 4/4] arm64: cputype info for Broadcom Vulcan Jayachandran C
2016-02-15 10:12 ` Will Deacon
2016-02-17 1:16 ` Florian Fainelli
2016-02-17 17:26 ` Catalin Marinas
2016-02-17 7:32 ` Zi Shen Lim
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=20160217171700.GI32647@leverpostej \
--to=mark.rutland@arm.com \
--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