From: sbranden@broadcom.com (Scott Branden)
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 13:59:31 -0700 [thread overview]
Message-ID: <562013B3.9070707@broadcom.com> (raw)
In-Reply-To: <5620120F.3060109@hauke-m.de>
On 15-10-15 01:52 PM, Hauke Mehrtens wrote:
> 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
this should be bcm4708
>
> 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?
Yes - the 9 infront indicates its some type of board. The SoC part
numbers should be listed here. The SoCs are all variants of
Northstar/Northstar plus family. Some have different io, packaging,
speed grades, etc.
>
> Hauke
>
>> compatible = "brcm,bcm4708";
>> +
>> +bcm94709
This should be bcm4709
>> +compatible = "brcm,bcm4709";
>> +
>> +bcm953012
This should be bcm53012
>> +compatible = "brcm,bcm53012";
>>
>
WARNING: multiple messages have this Message-ID (diff)
From: Scott Branden <sbranden@broadcom.com>
To: Hauke Mehrtens <hauke@hauke-m.de>,
Jon Mason <jonmason@broadcom.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH v2 1/2] dt-bindings: Add new boards to bcm4708 DT bindings
Date: Thu, 15 Oct 2015 13:59:31 -0700 [thread overview]
Message-ID: <562013B3.9070707@broadcom.com> (raw)
In-Reply-To: <5620120F.3060109@hauke-m.de>
On 15-10-15 01:52 PM, Hauke Mehrtens wrote:
> 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
this should be bcm4708
>
> 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?
Yes - the 9 infront indicates its some type of board. The SoC part
numbers should be listed here. The SoCs are all variants of
Northstar/Northstar plus family. Some have different io, packaging,
speed grades, etc.
>
> Hauke
>
>> compatible = "brcm,bcm4708";
>> +
>> +bcm94709
This should be bcm4709
>> +compatible = "brcm,bcm4709";
>> +
>> +bcm953012
This should be bcm53012
>> +compatible = "brcm,bcm53012";
>>
>
WARNING: multiple messages have this Message-ID (diff)
From: Scott Branden <sbranden@broadcom.com>
To: Hauke Mehrtens <hauke@hauke-m.de>,
Jon Mason <jonmason@broadcom.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: Add new boards to bcm4708 DT bindings
Date: Thu, 15 Oct 2015 13:59:31 -0700 [thread overview]
Message-ID: <562013B3.9070707@broadcom.com> (raw)
In-Reply-To: <5620120F.3060109@hauke-m.de>
On 15-10-15 01:52 PM, Hauke Mehrtens wrote:
> 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
this should be bcm4708
>
> 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?
Yes - the 9 infront indicates its some type of board. The SoC part
numbers should be listed here. The SoCs are all variants of
Northstar/Northstar plus family. Some have different io, packaging,
speed grades, etc.
>
> Hauke
>
>> compatible = "brcm,bcm4708";
>> +
>> +bcm94709
This should be bcm4709
>> +compatible = "brcm,bcm4709";
>> +
>> +bcm953012
This should be bcm53012
>> +compatible = "brcm,bcm53012";
>>
>
next prev parent reply other threads:[~2015-10-15 20:59 UTC|newest]
Thread overview: 31+ 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 ` Jon Mason
2015-10-14 22:14 ` Jon Mason
2015-10-14 22:14 ` [PATCH v2 1/2] dt-bindings: Add new boards to bcm4708 DT bindings Jon Mason
2015-10-14 22:14 ` Jon Mason
2015-10-14 22:14 ` Jon Mason
2015-10-15 20:52 ` Hauke Mehrtens
2015-10-15 20:52 ` Hauke Mehrtens
2015-10-15 20:52 ` Hauke Mehrtens
2015-10-15 20:59 ` Scott Branden [this message]
2015-10-15 20:59 ` Scott Branden
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-14 22:14 ` Jon Mason
2015-10-14 22:14 ` Jon Mason
2015-10-15 20:40 ` Hauke Mehrtens
2015-10-15 20:40 ` Hauke Mehrtens
2015-10-15 20:55 ` Hauke Mehrtens
2015-10-15 20:55 ` Hauke Mehrtens
2015-10-15 21:25 ` Jon Mason
2015-10-15 21:25 ` Jon Mason
2015-10-15 21:25 ` Jon Mason
2015-10-15 21:32 ` Hauke Mehrtens
2015-10-15 21:32 ` Hauke Mehrtens
2015-10-15 21:32 ` Hauke Mehrtens
2015-10-15 22:22 ` Jon Mason
2015-10-15 22:22 ` Jon Mason
2015-10-15 22:22 ` Jon Mason
2015-10-15 21:47 ` Jon Mason
2015-10-15 21:47 ` 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=562013B3.9070707@broadcom.com \
--to=sbranden@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.