Tony,
[snip]
So after the cleanup patch introducing CONFIG_SOC_OMAP4PLUS
it can be changed as
#ifdef (CONFIG_SOC_OMAP4PLUS) !(defined(CONFIG_ARCH_OMAP2) ||
defined(CONFIG_ARCH_OMAP3))
So this will avoid patching this for the future socs. ?
Well it seems that we've come to a conclusion
Hi,
On 05/03/2012 10:26 AM, R Sricharan wrote:
OMAP5430 is Texas Instrument's SOC based on ARM Cortex-A15 SMP
architecture. It's a dual core SOC with GIC used for interrupt
handling and with an integrated L2 cache controller.
OMAP5432 is another variant of OMAP5430, with a
memory
Tony,
[snip]
-#if defined(CONFIG_ARCH_OMAP4) !(defined(CONFIG_ARCH_OMAP2) || \
- defined(CONFIG_ARCH_OMAP3))
+#if (defined(CONFIG_ARCH_OMAP5) || defined(CONFIG_ARCH_OMAP4)) \
+ !(defined(CONFIG_ARCH_OMAP2) || defined(CONFIG_ARCH_OMAP3))
* R, Sricharan r.sricha...@ti.com [120509 02:09]:
Tony,
[snip]
-#if defined(CONFIG_ARCH_OMAP4) !(defined(CONFIG_ARCH_OMAP2) || \
- defined(CONFIG_ARCH_OMAP3))
+#if (defined(CONFIG_ARCH_OMAP5) || defined(CONFIG_ARCH_OMAP4)) \
+
* Paul Walmsley p...@pwsan.com [120507 22:35]:
On Mon, 7 May 2012, Tony Lindgren wrote:
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg67938.html
I see. Yeah, the problem is that it's hard to figure out which SoCs
should go into SOC_OMAP3PLUS. AM33xx? TI81xx? etc. Some
* Hiremath, Vaibhav hvaib...@ti.com [120507 22:52]:
On Tue, May 08, 2012 at 01:05:01, Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [120507 12:22]:
* Paul Walmsley p...@pwsan.com [120507 12:11]:
Hi,
On Fri, 4 May 2012, Tony Lindgren wrote:
How about we add
On Tue, May 08, 2012 at 21:18:29, Tony Lindgren wrote:
* Hiremath, Vaibhav hvaib...@ti.com [120507 22:52]:
On Tue, May 08, 2012 at 01:05:01, Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [120507 12:22]:
* Paul Walmsley p...@pwsan.com [120507 12:11]:
Hi,
On Fri, 4
* Hiremath, Vaibhav hvaib...@ti.com [120508 10:04]:
On Tue, May 08, 2012 at 21:18:29, Tony Lindgren wrote:
* Hiremath, Vaibhav hvaib...@ti.com [120507 22:52]:
On Tue, May 08, 2012 at 01:05:01, Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [120507 12:22]:
* Paul Walmsley
* R, Sricharan r.sricha...@ti.com [120506 00:40]:
Also, please change the whole series to use CONFIG_SOC_OMAP5 instead
of CONFIG_ARCH_OMAP5. CONFIG_ARCH_OMAP stuff will go away except
for CONFIG_ARCH_OMAP2PLUS. Sorry forgot to mention that earlier.
ok. sure. will change this.
Hi,
On Fri, 4 May 2012, Tony Lindgren wrote:
How about we add CONFIG_SOC_OMAP3PLUS in the clean-up series?
Then this becomes just:
#ifdef CONFIG_SOC_OMAP3PLUS
We might want to consider having separate CONFIG_SOC_* values for each
SoC. So rather than CONFIG_SOC_OMAP3PLUS, we'd have
* Paul Walmsley p...@pwsan.com [120507 12:11]:
Hi,
On Fri, 4 May 2012, Tony Lindgren wrote:
How about we add CONFIG_SOC_OMAP3PLUS in the clean-up series?
Then this becomes just:
#ifdef CONFIG_SOC_OMAP3PLUS
We might want to consider having separate CONFIG_SOC_* values for each
* Tony Lindgren t...@atomide.com [120507 12:22]:
* Paul Walmsley p...@pwsan.com [120507 12:11]:
Hi,
On Fri, 4 May 2012, Tony Lindgren wrote:
How about we add CONFIG_SOC_OMAP3PLUS in the clean-up series?
Then this becomes just:
#ifdef CONFIG_SOC_OMAP3PLUS
We might want
On Mon, 7 May 2012, Tony Lindgren wrote:
* Paul Walmsley p...@pwsan.com [120507 12:11]:
On Fri, 4 May 2012, Tony Lindgren wrote:
How about we add CONFIG_SOC_OMAP3PLUS in the clean-up series?
Then this becomes just:
#ifdef CONFIG_SOC_OMAP3PLUS
We might want to consider
On Mon, 7 May 2012, Tony Lindgren wrote:
Of course we could make this finer grained based on features
like SOC_HAS_XYZ or SOC_HAS_OMAP3PLUS_PRMXYZBITS if you have some
grouping like that in mind.
Yep, I like that idea.
- Paul
--
To unsubscribe from this list: send the line unsubscribe
On Tue, May 08, 2012 at 01:05:01, Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [120507 12:22]:
* Paul Walmsley p...@pwsan.com [120507 12:11]:
Hi,
On Fri, 4 May 2012, Tony Lindgren wrote:
How about we add CONFIG_SOC_OMAP3PLUS in the clean-up series?
Then this
Hi Tony,
[snip]
OK this seems to be based on Santosh' Makefile cleanup.
yes..
-#if defined(CONFIG_ARCH_OMAP3) || defined(CONFIG_ARCH_OMAP4)
+#if defined(CONFIG_ARCH_OMAP3) || defined(CONFIG_ARCH_OMAP4) || \
+ defined(CONFIG_ARCH_OMAP5)
How about we add
* R Sricharan r.sricha...@ti.com [120503 00:30]:
--- a/arch/arm/mach-omap2/Makefile
+++ b/arch/arm/mach-omap2/Makefile
@@ -16,6 +16,7 @@ secure-common = omap-smc.o
omap-secure.o
obj-$(CONFIG_ARCH_OMAP2) += $(omap-2-3-common) $(hwmod-common)
* Tony Lindgren t...@atomide.com [120504 15:43]:
--- a/arch/arm/mach-omap2/clock.c
+++ b/arch/arm/mach-omap2/clock.c
@@ -400,7 +400,8 @@ int omap2_clk_set_parent(struct clk *clk, struct clk
*new_parent)
/* OMAP3/4 non-CORE DPLL clkops */
-#if defined(CONFIG_ARCH_OMAP3) ||
18 matches
Mail list logo
