From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Peng Wu <pengw-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>
Cc: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
"devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
"cooloney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<cooloney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH 1/2] ARM: DT: tegra: Add Tegra30 Beaver board support
Date: Fri, 08 Feb 2013 21:40:24 +0000 [thread overview]
Message-ID: <20130208214024.9467E3E2C27@localhost> (raw)
In-Reply-To: <50E478AF.2040406-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On Wed, 2 Jan 2013 10:13:03 -0800, Peng Wu <pengw-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> wrote:
> On 12/28/2012 08:43 PM, Olof Johansson wrote:
> > On Fri, Dec 28, 2012 at 3:54 PM, Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> 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.
The model string is intended to be human-friendly, where as compatible
is primarily the matching mechanism.
I don't think it is stricly necessary to document top level compatible
strings unless there is something quirky that begs to be documented.
WARNING: multiple messages have this Message-ID (diff)
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: DT: tegra: Add Tegra30 Beaver board support
Date: Fri, 08 Feb 2013 21:40:24 +0000 [thread overview]
Message-ID: <20130208214024.9467E3E2C27@localhost> (raw)
In-Reply-To: <50E478AF.2040406@nvidia.com>
On Wed, 2 Jan 2013 10:13:03 -0800, Peng Wu <pengw@nvidia.com> wrote:
> 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.
The model string is intended to be human-friendly, where as compatible
is primarily the matching mechanism.
I don't think it is stricly necessary to document top level compatible
strings unless there is something quirky that begs to be documented.
next prev parent reply other threads:[~2013-02-08 21:40 UTC|newest]
Thread overview: 18+ 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 ` Bryan Wu
[not found] ` <1356032489-27619-1-git-send-email-pengw-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-20 19:41 ` [PATCH 2/2] ARM: DT: tegra: Unify the description of Tegra20 boards Bryan Wu
2012-12-20 19:41 ` Bryan Wu
[not found] ` <1356032489-27619-2-git-send-email-pengw-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-01-02 19:33 ` Stephen Warren
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-20 19:58 ` Stephen Warren
2012-12-28 16:22 ` Rob Herring
2012-12-28 16:22 ` Rob Herring
[not found] ` <50DDC743.2080606-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-12-28 23:54 ` Stephen Warren
2012-12-28 23:54 ` Stephen Warren
[not found] ` <50DE3146.6090001-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-29 4:43 ` Olof Johansson
2012-12-29 4:43 ` Olof Johansson
[not found] ` <CAOesGMgW890K4Wo2-SFE4YFn5f8T950BTZ82rkCQfwpV+bsRyQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-02 18:13 ` Peng Wu
2013-01-02 18:13 ` Peng Wu
[not found] ` <50E478AF.2040406-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-02-08 21:40 ` Grant Likely [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=20130208214024.9467E3E2C27@localhost \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=cooloney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=pengw-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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.