public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Hiremath, Vaibhav" <hvaibhav@ti.com>
Cc: "Hilman, Kevin" <khilman@ti.com>, Paul Walmsley <paul@pwsan.com>,
	"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>
Subject: Re: [PATCH-V5 2/3] arm:omap:am33xx: Add AM335XEVM machine support
Date: Mon, 7 May 2012 10:32:29 -0700	[thread overview]
Message-ID: <20120507173229.GA5088@atomide.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A83EA1778E@DBDE01.ent.ti.com>

* Hiremath, Vaibhav <hvaibhav@ti.com> [120507 07:41]:
> On Sat, May 05, 2012 at 01:35:47, Tony Lindgren wrote:
> > 
> > I suggest doing some clean-up patches before adding SOC_AM33XX where
> > you just convert those to be
> > 
> > #if defined(CONFIG_ARCH_OMAP2PLUS) && !defined(CONFIG_ARCH_OMAP2)
> > 
> > or something similar depending if they already are inside mach-omap2
> > directory. This will make them future proof for adding new SoCs
> > without having to patch all over the place.

BTW, just noticied that the above won't work the right way in the
multi-omap case when all of them are compiled in..

> Cool, I also thought exactly same solution on this, but next thought came to 
> my mind was, it won't scale up, since we still have dependency on ARCH_OMAP2 
> option. However, it will be a good temporary solution for our problem, lets 
> review them first (I will submit shortly).

..so probably the best way to deal with that is with the additional
CONFIG_SOC_OMAP3PLUS and CONFIG_SOC_OMAP4PLUS options that I posted
at:

http://www.mail-archive.com/linux-omap@vger.kernel.org/msg67938.html

Can you please take a look and see how that works for am33xx?

Regards,

Tony

  reply	other threads:[~2012-05-07 17:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02  6:43 [PATCH-V5 2/3] arm:omap:am33xx: Add AM335XEVM machine support hvaibhav
2012-05-02  9:23 ` Paul Walmsley
2012-05-02  9:34   ` Hiremath, Vaibhav
2012-05-03 15:57     ` Tony Lindgren
2012-05-03 16:41       ` Hiremath, Vaibhav
2012-05-03 19:37         ` Tony Lindgren
2012-05-04  6:14           ` Hiremath, Vaibhav
2012-05-03 21:17         ` Kevin Hilman
2012-05-04  6:00           ` Hiremath, Vaibhav
2012-05-04 20:05             ` Tony Lindgren
2012-05-07 14:38               ` Hiremath, Vaibhav
2012-05-07 17:32                 ` Tony Lindgren [this message]
2012-05-07 18:55                   ` Hiremath, Vaibhav
2012-05-08 19:06                     ` Tony Lindgren
2012-05-08 19:57                       ` Hiremath, Vaibhav
2012-05-04  6:28       ` Hiremath, Vaibhav
2012-05-04 20:00         ` 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=20120507173229.GA5088@atomide.com \
    --to=tony@atomide.com \
    --cc=afzal@ti.com \
    --cc=hvaibhav@ti.com \
    --cc=khilman@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox