All of lore.kernel.org
 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>,
	"Mohammed, Afzal" <afzal@ti.com>,
	"Cousson, Benoit" <b-cousson@ti.com>,
	Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH] ARM: OMAP2+: am33xx: Add AM335XEVM machine support
Date: Tue, 5 Jun 2012 00:53:44 -0700	[thread overview]
Message-ID: <20120605075344.GH12766@atomide.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A83EA3923D@DBDE01.ent.ti.com>

* Hiremath, Vaibhav <hvaibhav@ti.com> [120528 23:17]:
> On Fri, May 11, 2012 at 00:38:49, Hiremath, Vaibhav wrote:
> > From: Afzal Mohammed <afzal@ti.com>
> > 
> > This patch adds minimal support for AM335X machine init.
> > 
> > During last merge window, two separate patches supporting am33xx
> > machine init had been submitted,
> > 
> > 1. Link to earlier Baseport patch submission (Legacy):
> > http://www.mail-archive.com/linux-omap@vger.kernel.org/msg59325.html
> > 2. Link to earlier DT based machine init support patch submission:
> > http://www.mail-archive.com/linux-omap@vger.kernel.org/msg61398.html
> > 
> > And both had got accepted at that time, but got missed during
> > merge window.
> > 
> > But now, since we have taken decision to make am33xx as a separate
> > class and not to follow omap3 family, these patches needs to changes
> > accordingly (only changes),
> > 
> >  - Combine both the patches, since early init and timer init
> >    used in board-generic.c file requires them.
> >  - Remove dependency on AM3517EVM, and only use DT approach
> >    for machine init.
> >  - Change the config option (as changed recently)
> >    CONFIG_SOC_OMAPAM33XX --> CONFIG_SOC_AM33XX
> > 
> > Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
> > Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
> > Cc: Tony Lindgren <tony@atomide.com>
> > Cc: Benoit Cousson <b-cousson@ti.com>
> > Cc: Paul Walmsley <paul@pwsan.com>
> > ---
> >  arch/arm/mach-omap2/board-generic.c |   18 ++++++++++++++++++
> >  arch/arm/mach-omap2/common.h        |    2 ++
> >  arch/arm/mach-omap2/io.c            |   10 ++++++++++
> >  arch/arm/mach-omap2/irq.c           |    2 +-
> >  arch/arm/mach-omap2/timer.c         |    5 +++++
> >  5 files changed, 36 insertions(+), 1 deletions(-)
> > 
> 
> Tony,
> 
> Can this be merged now???

Adding this too to devel-am33xx branch.

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: am33xx: Add AM335XEVM machine support
Date: Tue, 5 Jun 2012 00:53:44 -0700	[thread overview]
Message-ID: <20120605075344.GH12766@atomide.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A83EA3923D@DBDE01.ent.ti.com>

* Hiremath, Vaibhav <hvaibhav@ti.com> [120528 23:17]:
> On Fri, May 11, 2012 at 00:38:49, Hiremath, Vaibhav wrote:
> > From: Afzal Mohammed <afzal@ti.com>
> > 
> > This patch adds minimal support for AM335X machine init.
> > 
> > During last merge window, two separate patches supporting am33xx
> > machine init had been submitted,
> > 
> > 1. Link to earlier Baseport patch submission (Legacy):
> > http://www.mail-archive.com/linux-omap at vger.kernel.org/msg59325.html
> > 2. Link to earlier DT based machine init support patch submission:
> > http://www.mail-archive.com/linux-omap at vger.kernel.org/msg61398.html
> > 
> > And both had got accepted at that time, but got missed during
> > merge window.
> > 
> > But now, since we have taken decision to make am33xx as a separate
> > class and not to follow omap3 family, these patches needs to changes
> > accordingly (only changes),
> > 
> >  - Combine both the patches, since early init and timer init
> >    used in board-generic.c file requires them.
> >  - Remove dependency on AM3517EVM, and only use DT approach
> >    for machine init.
> >  - Change the config option (as changed recently)
> >    CONFIG_SOC_OMAPAM33XX --> CONFIG_SOC_AM33XX
> > 
> > Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
> > Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
> > Cc: Tony Lindgren <tony@atomide.com>
> > Cc: Benoit Cousson <b-cousson@ti.com>
> > Cc: Paul Walmsley <paul@pwsan.com>
> > ---
> >  arch/arm/mach-omap2/board-generic.c |   18 ++++++++++++++++++
> >  arch/arm/mach-omap2/common.h        |    2 ++
> >  arch/arm/mach-omap2/io.c            |   10 ++++++++++
> >  arch/arm/mach-omap2/irq.c           |    2 +-
> >  arch/arm/mach-omap2/timer.c         |    5 +++++
> >  5 files changed, 36 insertions(+), 1 deletions(-)
> > 
> 
> Tony,
> 
> Can this be merged now???

Adding this too to devel-am33xx branch.

Tony

  reply	other threads:[~2012-06-05  7:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 19:08 [PATCH] ARM: OMAP2+: am33xx: Add AM335XEVM machine support Vaibhav Hiremath
2012-05-10 19:08 ` Vaibhav Hiremath
2012-05-29  6:12 ` Hiremath, Vaibhav
2012-05-29  6:12   ` Hiremath, Vaibhav
2012-06-05  7:53   ` Tony Lindgren [this message]
2012-06-05  7:53     ` Tony Lindgren
2012-06-05  8:00     ` Hiremath, Vaibhav
2012-06-05  8:00       ` Hiremath, Vaibhav
2012-06-05  8:02       ` Tony Lindgren
2012-06-05  8:02         ` Tony Lindgren

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=20120605075344.GH12766@atomide.com \
    --to=tony@atomide.com \
    --cc=afzal@ti.com \
    --cc=b-cousson@ti.com \
    --cc=hvaibhav@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    /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.