linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pengw@nvidia.com (Peng Wu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: DT: tegra: Add Tegra30 Beaver board support
Date: Wed, 2 Jan 2013 10:13:03 -0800	[thread overview]
Message-ID: <50E478AF.2040406@nvidia.com> (raw)
In-Reply-To: <CAOesGMgW890K4Wo2-SFE4YFn5f8T950BTZ82rkCQfwpV+bsRyQ@mail.gmail.com>

On 12/28/2012 08:43 PM, Olof Johansson wrote:
> On Fri, Dec 28, 2012 at 3:54 PM, Stephen Warren <swarren@nvidia.com> wrote:
>> On 12/28/2012 09:22 AM, Rob Herring wrote:
>>> On 12/20/2012 01:41 PM, Bryan Wu wrote:
>>>> This patch adds support for Tegra30 Beaver board in upstream kernel.
>>>> diff --git a/arch/arm/boot/dts/tegra30-beaver.dts b/arch/arm/boot/dts/tegra30-beaver.dts
>>>> +/ {
>>>> +    model = "NVIDIA Tegra30 Beaver evaluation board";
>>>> +    compatible = "nvidia,beaver", "nvidia,tegra30";
>>> nvidia,beaver needs to be documented.
>> Hmmm. I guess we've managed not to document /any/ of the Tegra
>> board-level compatible values. Bryan, could you make a separate patch to
>> add all the existing board compatible values to
>> Documentation/devicetree/bindings/arm/tegra.txt. The Beaver addition to
>> that file can still be part of the Beaver-specific patch though.
> Does it need to be documented? Then the "support a new platform only
> through DTS update" is no longer true. :)
>
> In the past, I don't think we've strictly documented all derivative
> platform compatible values, just some of the reference ones?
>
>
> -Olof

Actually in every Tegra board dts file, there is a model string to 
describe this machine as well as a compatible board string, just like 
the "nvidia,beaver". So do we still need put this duplicated information 
in a document file? Or if this is the requirement of DeviceTree. I will 
do that. I think we have 12 boards need to add such document currently.

Thanks and happy new year.
-Bryan

  reply	other threads:[~2013-01-02 18:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-20 19:41 [PATCH 1/2] ARM: DT: tegra: Add Tegra30 Beaver board support Bryan Wu
2012-12-20 19:41 ` [PATCH 2/2] ARM: DT: tegra: Unify the description of Tegra20 boards Bryan Wu
2013-01-02 19:33   ` Stephen Warren
2012-12-20 19:58 ` [PATCH 1/2] ARM: DT: tegra: Add Tegra30 Beaver board support Stephen Warren
2012-12-28 16:22 ` Rob Herring
2012-12-28 23:54   ` Stephen Warren
2012-12-29  4:43     ` Olof Johansson
2013-01-02 18:13       ` Peng Wu [this message]
2013-02-08 21:40         ` Grant Likely

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=50E478AF.2040406@nvidia.com \
    --to=pengw@nvidia.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).