From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm/dt: tegra devicetree support
Date: Wed, 20 Jul 2011 12:56:07 -0600 [thread overview]
Message-ID: <20110720185607.GJ4642@ponder.secretlab.ca> (raw)
In-Reply-To: <CAOesGMiy1t-98KZ_imFkGO-ify3S_00d_0XKc2vcLNRekxOvpw@mail.gmail.com>
On Tue, Jul 19, 2011 at 04:56:46PM -0700, Olof Johansson wrote:
> Nice!
>
>
> On Tue, Jul 19, 2011 at 4:43 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
> > Everything required to populate NVIDIA Tegra devices from the device
> > tree. ?This patch adds a new DT_MACHINE_DESC() which matches against
> > a tegra20 device tree. ?So far it only registers the on-chip devices,
> > but it will be refined in follow on patches to configure clocks and
> > pin IO from the device tree also.
> >
> > Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
>
> Acked-by: Olof Johansson <olof@lixom.net
>
>
> Minor nit:
>
> > +++ b/arch/arm/boot/dts/tegra20.dtsi
> > @@ -0,0 +1,148 @@
> > +/include/ "skeleton.dtsi"
> > +
> > +/ {
> > + ? ? ? model = "NVIDIA Tegra 250";
>
> NVIDIA Tegra2 or Tegra20 to be more in line with the recent 250->20
> conversion (and Harmony)
I'll remove the model property entirely. It doesn't make any sense
for the soc include file since "model" describes the system.
g.
next prev parent reply other threads:[~2011-07-20 18:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 23:43 [PATCH] arm/dt: tegra devicetree support Grant Likely
2011-07-19 23:56 ` Olof Johansson
2011-07-20 18:56 ` Grant Likely [this message]
2011-07-20 15:37 ` Stephen Warren
2011-07-20 16:03 ` Mark Brown
2011-07-20 18:31 ` Grant Likely
2011-07-20 18:40 ` Stephen Warren
2011-07-20 18:47 ` Grant Likely
2011-07-20 19:49 ` Mark Brown
2011-07-20 18:28 ` Grant Likely
2011-07-20 18:33 ` Stephen Warren
2011-07-20 18:45 ` Grant Likely
2011-07-20 22:49 ` Shawn Guo
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=20110720185607.GJ4642@ponder.secretlab.ca \
--to=grant.likely@secretlab.ca \
--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