devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Hiremath, Vaibhav" <hvaibhav@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
	"Cousson, Benoit" <b-cousson@ti.com>
Subject: Re: [PATCH-V1] arm/dts: Add support for TI OMAP3 EVM board
Date: Wed, 29 Feb 2012 14:31:14 -0800	[thread overview]
Message-ID: <20120229223114.GS18901@atomide.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A80719AC@DBDE01.ent.ti.com>

* Hiremath, Vaibhav <hvaibhav@ti.com> [120105 02:46]:
> > -----Original Message-----
> > From: Hiremath, Vaibhav
> > Sent: Friday, December 16, 2011 12:36 PM
> > To: linux-omap@vger.kernel.org
> > Cc: tony@atomide.com; linux-arm-kernel@lists.infradead.org; devicetree-
> > discuss@lists.ozlabs.org; grant.likely@secretlab.ca; Cousson, Benoit;
> > Hiremath, Vaibhav
> > Subject: [PATCH-V1] arm/dts: Add support for TI OMAP3 EVM board
> > 
> > Add OMAP3 EVM (OMAP3530, AM/DM37x) DTS file to use the omap3.dtsi SoC file,
> > along with memory node information.
> > 
> > Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
> > ---
> > Boot tested it on AM/DM37x EVM, kernel parses the info correctly.
> > 
> >  arch/arm/boot/dts/omap3-evm.dts |   20 ++++++++++++++++++++
> >  1 files changed, 20 insertions(+), 0 deletions(-)
> >  create mode 100644 arch/arm/boot/dts/omap3-evm.dts
> > 
> > diff --git a/arch/arm/boot/dts/omap3-evm.dts b/arch/arm/boot/dts/omap3-
> > evm.dts
> > new file mode 100644
> > index 0000000..2eee16e
> > --- /dev/null
> > +++ b/arch/arm/boot/dts/omap3-evm.dts
> > @@ -0,0 +1,20 @@
> > +/*
> > + * Copyright (C) 2011 Texas Instruments Incorporated - http://www.ti.com/
> > + *
> > + * This program is free software; you can redistribute it and/or modify
> > + * it under the terms of the GNU General Public License version 2 as
> > + * published by the Free Software Foundation.
> > + */
> > +/dts-v1/;
> > +
> > +/include/ "omap3.dtsi"
> > +
> > +/ {
> > +	model = "TI OMAP3 EVM (OMAP3530, AM/DM37x)";
> > +	compatible = "ti,omap3-evm", "ti,omap3";
> > +
> > +	memory {
> > +		device_type = "memory";
> > +		reg = <0x80000000 0x10000000>; /* 256 MB */
> > +	};
> > +};
> Can this merged? OR anybody has any comments here?

For reference, looks like this one is queued up as
commit f0e15e2b0c6b3e89daade25a1e9a2d80136c14c3.

Tony

  parent reply	other threads:[~2012-02-29 22:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16  7:05 [PATCH-V1] arm/dts: Add support for TI OMAP3 EVM board Vaibhav Hiremath
2012-01-05 11:18 ` Hiremath, Vaibhav
2012-01-05 13:54   ` Cousson, Benoit
2012-01-05 18:09     ` Grant Likely
2012-02-29 22:31   ` Tony Lindgren [this message]
2012-02-29 22:39     ` Cousson, Benoit
2012-03-01  6:19       ` Hiremath, Vaibhav

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=20120229223114.GS18901@atomide.com \
    --to=tony@atomide.com \
    --cc=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=hvaibhav@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.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).