From: hauke@hauke-m.de (Hauke Mehrtens)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] dt-bindings: Add new boards to bcm4708 DT bindings
Date: Thu, 15 Oct 2015 22:52:31 +0200 [thread overview]
Message-ID: <5620120F.3060109@hauke-m.de> (raw)
In-Reply-To: <1444860890-28649-2-git-send-email-jonmason@broadcom.com>
On 10/15/2015 12:14 AM, Jon Mason wrote:
> Add the 4708, 4709, and 953012k SVKs to the the documentation for the
> Broadcom Northstar device tree bindings.
>
> Signed-off-by: Jon Mason <jonmason@broadcom.com>
> ---
> Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt b/Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt
> index 6b0f49f..b9cc308 100644
> --- a/Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt
> +++ b/Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt
> @@ -5,4 +5,11 @@ Boards with the BCM4708 SoC shall have the following properties:
>
> Required root node property:
>
> +bcm94708
I thought we wanted to add the SoC names here, isn't bcm94708 a board
the bcm4708, the SoC ion this board? I do not really care about this
file, has anyone found the documentation what should be listed here?
Hauke
> compatible = "brcm,bcm4708";
> +
> +bcm94709
> +compatible = "brcm,bcm4709";
> +
> +bcm953012
> +compatible = "brcm,bcm53012";
>
next prev parent reply other threads:[~2015-10-15 20:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 22:14 [PATCH v2 0/2] ARM: dts: bcm5301x: Add BCM SVK DT files Jon Mason
2015-10-14 22:14 ` [PATCH v2 1/2] dt-bindings: Add new boards to bcm4708 DT bindings Jon Mason
2015-10-15 20:52 ` Hauke Mehrtens [this message]
2015-10-15 20:59 ` Scott Branden
2015-10-14 22:14 ` [PATCH v2 2/2] ARM: dts: bcm5301x: Add BCM SVK DT files Jon Mason
2015-10-15 20:40 ` Hauke Mehrtens
2015-10-15 20:55 ` Hauke Mehrtens
2015-10-15 21:25 ` Jon Mason
2015-10-15 21:32 ` Hauke Mehrtens
2015-10-15 22:22 ` Jon Mason
2015-10-15 21:47 ` Jon Mason
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=5620120F.3060109@hauke-m.de \
--to=hauke@hauke-m.de \
--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;
as well as URLs for NNTP newsgroup(s).