All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] include/asm-arm/arch-omap/omap24xx.h
Date: Mon, 05 Nov 2007 20:34:09 +0100	[thread overview]
Message-ID: <472F7031.3000308@googlemail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711050052050.7016@utopia.booyaka.com>

Paul Walmsley wrote:
> On Thu, 1 Nov 2007, Tony Lindgren wrote:
> 
> 
>>* Tony Lindgren <tony@atomide.com> [071031 08:22]:
>>
>>>* Paul Walmsley <paul@pwsan.com> [071025 09:01]:
>>>
>>>
>>>>Hello Dirk,
>>>>
>>>>On Thu, 25 Oct 2007, Dirk Behme wrote:
>>>>
>>>>
>>>>>Mmh, I like to fix it in include/asm-arm/arch-omap/omap24xx.h, so I prefer 
>>>>>[1].
>>>>>
>>>>>With [1] we
>>>>>
>>>>>- fix it where it was introduced
>>>>>- have an additional #ifdef only in a header file instead of 
>>>>>plat-omap/devices.c, which is IMHO better
>>>>>- fix it for everybody now and in the future who directly or indirectly 
>>>>>includes omap24xx.h.
>>>>
>>>>Hopefully this is just a workaround until we can get rid of these 
>>>>conditional defines for multiboot kernels.  Generally speaking, would you 
>>>>propose doing the same thing for the other conditional defines in 
>>>>include/asm-arm/arch-omap/omap24xx.h, such as OMAP2_32KSYNCT_BASE, 
>>>>OMAP2_SDRC_BASE, etc.?
>>>
>>>Sounds like the real fix is to set these addresses in the init code
>>>somewhere based on the omap type.
>  
> Yeah, agreed.

Me too.

>>I'll push a temporary fix based on Luis' patch, see below.
> 
> 
> OMAP3430 builds now generate redefinition warnings for OMAP2_CTRL_BASE; 
> patch to work around is below.
...
> From: Paul Walmsley <paul@pwsan.com>
> Subject: Work around OMAP2_CTRL_BASE warnings in 3430 build
> 
> Work around OMAP2_CTRL_BASE redefinition warnings for OMAP3430 builds. 
> 
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
> 
> ---
>  include/asm/arch/omap24xx.h |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Index: linux-omap/include/asm/arch/omap24xx.h
> ===================================================================
> --- linux-omap.orig/include/asm/arch/omap24xx.h	2007-11-04 20:55:00.000000000 -0700
> +++ linux-omap/include/asm/arch/omap24xx.h	2007-11-04 21:32:31.000000000 -0700
> @@ -101,7 +101,7 @@
>  #define OMAP2_VA_IC_BASE	IO_ADDRESS(OMAP24XX_IC_BASE)
>  #define OMAP2_CTRL_BASE		OMAP243X_CTRL_BASE
>  
> -#else
> +#elif !defined(CONFIG_ARCH_OMAP34XX)
>  /* FIXME: These will go away soon */
>  #define OMAP2_CTRL_BASE		L4_24XX_BASE
>  #endif

Until we have real fix like above: Instead of now trying to cover all 
situations where OMAP2_CTRL_BASE is undefined or redefinded (maybe 
there are some more?), I wonder why not simply make it self-dependent?

#if !defined(OMAP2_CTRL_BASE)
/* FIXME: These will go away soon */
#define OMAP2_CTRL_BASE		L4_24XX_BASE
#endif

Regards

Dirk

http://linux.omap.com/pipermail/linux-omap-open-source/2007-September/011393.html

  reply	other threads:[~2007-11-05 19:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 16:58 [PATCH] include/asm-arm/arch-omap/omap24xx.h Luís Cargnini
2007-10-24 17:53 ` Dirk Behme
2007-10-25  5:31   ` Paul Walmsley
2007-10-25  5:31     ` fix undeclared OMAP2_CTRL_BASE for OMAP MMC driver in OMAP1 compiles Paul Walmsley
2007-10-25  5:54     ` [PATCH] include/asm-arm/arch-omap/omap24xx.h Luís Cargnini
2007-10-25 15:28     ` Dirk Behme
2007-10-25 16:00       ` Paul Walmsley
2007-10-31 15:22         ` Tony Lindgren
2007-11-01  8:29           ` Tony Lindgren
2007-11-05  7:57             ` Paul Walmsley
2007-11-05 19:34               ` Dirk Behme [this message]
2007-11-06 10:23                 ` Paul Walmsley
2007-11-06 12:58                   ` Tony Lindgren
2007-11-07  4:21                     ` Luís Cargnini
  -- strict thread matches above, loose matches on Subject: below --
2007-11-07  4:27 [PATCH]include/asm-arm/arch-omap/omap24xx.h Luís Cargnini
2007-11-15 21:24 ` [PATCH]include/asm-arm/arch-omap/omap24xx.h 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=472F7031.3000308@googlemail.com \
    --to=dirk.behme@googlemail.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --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.