From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] dt-bindings: Add new boards to bcm4708 DT bindings
Date: Tue, 13 Oct 2015 15:37:49 -0700 [thread overview]
Message-ID: <561D87BD.5030405@gmail.com> (raw)
In-Reply-To: <20151013214051.GN12512@broadcom.com>
On 13/10/15 14:40, Jon Mason wrote:
> On Sat, Oct 10, 2015 at 04:42:04PM +0200, Hauke Mehrtens wrote:
>> On 10/03/2015 12:22 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..bdf4c06 100644
>>> --- a/Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt
>>> +++ b/Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt
>>
>> What should be documented in this file? This is more a question to the
>> guys more familiar with arm in Linux. Currently the Linux kernel only
>> supports brcm,bcm4708 and all goes back to that one.
>
> I was under the impression that all boards should be added to these
> files. We have been doing so for Cygnus and NSP.
Tracking exactly which boards are supported by the brcm,bcm4708
compatible string might be tedious, I tend to agree with just listing
the supported SoCs, and leaving the specific board compatibles to the
individual DTS files instead.
>
> Thanks,
> Jon
>
>>
>>> @@ -5,4 +5,11 @@ Boards with the BCM4708 SoC shall have the following properties:
>>>
>>> Required root node property:
>>>
>>> +bcm94709
>>> compatible = "brcm,bcm4708";
>>> +
>>> +bcm94709
>>> +compatible = "brcm,bcm4709", "brcm,bcm4708";
>>> +
>>> +bcm953012k
>>> +compatible = "brcm,bcm5301k", "brcm,bcm4708";
>>>
>>
--
Florian
next prev parent reply other threads:[~2015-10-13 22:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 22:22 [PATCH 1/2] ARM: dts: bcm5301x: Add BCM SVK DT files Jon Mason
2015-10-02 22:22 ` [PATCH 2/2] dt-bindings: Add new boards to bcm4708 DT bindings Jon Mason
2015-10-10 14:42 ` Hauke Mehrtens
2015-10-13 16:58 ` Scott Branden
2015-10-13 21:40 ` Jon Mason
2015-10-13 22:37 ` Florian Fainelli [this message]
2015-10-14 15:34 ` Jon Mason
2015-10-14 19:44 ` Scott Branden
2015-10-10 14:39 ` [PATCH 1/2] ARM: dts: bcm5301x: Add BCM SVK DT files Hauke Mehrtens
2015-10-13 21:38 ` Jon Mason
2015-10-13 22:43 ` Ray Jui
2015-10-14 15:36 ` 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=561D87BD.5030405@gmail.com \
--to=f.fainelli@gmail.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;
as well as URLs for NNTP newsgroup(s).