From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-omap@vger.kernel.org
Subject: Re: Latest regressions
Date: Thu, 27 Jan 2011 16:18:30 -0800 [thread overview]
Message-ID: <20110128001829.GN23412@atomide.com> (raw)
In-Reply-To: <20110127122245.GB26418@n2100.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [110127 04:21]:
> On Wed, Jan 26, 2011 at 10:12:16AM -0800, Tony Lindgren wrote:
> > * Russell King - ARM Linux <linux@arm.linux.org.uk> [110126 00:57]:
> > > On Fri, Jan 07, 2011 at 08:56:26AM -0800, Tony Lindgren wrote:
> > > > > diff --git a/arch/arm/mach-omap2/io.c b/arch/arm/mach-omap2/io.c
> > > > > index e66687b..c203204 100644
> > > > > --- a/arch/arm/mach-omap2/io.c
> > > > > +++ b/arch/arm/mach-omap2/io.c
> > > > > @@ -314,14 +314,13 @@ static int _set_hwmod_postsetup_state(struct omap_hwmod *oh, void *data)
> > > > > return omap_hwmod_set_postsetup_state(oh, *(u8 *)data);
> > > > > }
> > > > >
> > > > > +void __iomem *omap_irq_base;
> > > > > +
> > > > > /*
> > > > > * Initialize asm_irq_base for entry-macro.S
> > > > > */
> > > > > static inline void omap_irq_base_init(void)
> > > > > {
> > > > > - extern void __iomem *omap_irq_base;
> > > > > -
> > > > > -#ifdef MULTI_OMAP2
> > > > > if (cpu_is_omap24xx())
> > > > > omap_irq_base = OMAP2_L4_IO_ADDRESS(OMAP24XX_IC_BASE);
> > > > > else if (cpu_is_omap34xx())
> > > > > @@ -330,7 +329,6 @@ static inline void omap_irq_base_init(void)
> > > > > omap_irq_base = OMAP2_L4_IO_ADDRESS(OMAP44XX_GIC_CPU_BASE);
> > > > > else
> > > > > pr_err("Could not initialize omap_irq_base\n");
> > > > > -#endif
> > > > > }
> > > > >
> > > > > void __init omap2_init_common_infrastructure(void)
> > > >
> > > > This looks good to me.
> > >
> > > I notice this one is still there.
> >
> > Sorry I thought you'll queue this one.
> >
> > BTW this fixes regression from patch 5d190c40100793a6dfc37bf325677c10f3c80edf
> > (omap2+: Initialize omap_irq_base for entry-macro.S from platform code).
> > So it should be OK for the -rc cycle:
> >
> > Acked-by: Tony Lindgren <tony@atomide.com>
> >
> > Let me know if you want me to take it, in that case I think it's still
> > missing your Signed-off-by.
>
> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
>
> > Let me know if you want me to queue it.
>
> Yes please.
OK here's I've queued. I updated the comments a bit.
Will also post a similar change for omap1.
Tony
From: Russell King <rmk+kernel@arm.linux.org.uk>
Date: Fri, 7 Jan 2011 11:57:44 +0000
Subject: [PATCH] omap2+: Fix unused variable warning for omap_irq_base
Commit 5d190c40100793a6dfc37bf325677c10f3c80edf
(omap2+: Initialize omap_irq_base for entry-macro.S from
platform code) simplified the handling of omap_irq_base
for multi-omap builds. However, this patch also introduced
a build warning for !MULTI_OMAP2 builds:
arch/arm/mach-omap2/io.c: In function 'omap_irq_base_init':
arch/arm/mach-omap2/io.c:322: warning: unused variable 'omap_irq_base'
Fix this by removing the ifdef. Also simplify things further
by moving omap_irq_base out of entry-macro.S.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[tony@atomide.com: updated comments]
Signed-off-by: Tony Lindgren <tony@atomide.com>
--- a/arch/arm/mach-omap2/include/mach/entry-macro.S
+++ b/arch/arm/mach-omap2/include/mach/entry-macro.S
@@ -38,20 +38,6 @@
*/
#ifdef MULTI_OMAP2
-
-/*
- * We use __glue to avoid errors with multiple definitions of
- * .globl omap_irq_base as it's included from entry-armv.S but not
- * from entry-common.S.
- */
-#ifdef __glue
- .pushsection .data
- .globl omap_irq_base
-omap_irq_base:
- .word 0
- .popsection
-#endif
-
/*
* Configure the interrupt base on the first interrupt.
* See also omap_irq_base_init for setting omap_irq_base.
--- a/arch/arm/mach-omap2/io.c
+++ b/arch/arm/mach-omap2/io.c
@@ -314,14 +314,13 @@ static int _set_hwmod_postsetup_state(struct omap_hwmod *oh, void *data)
return omap_hwmod_set_postsetup_state(oh, *(u8 *)data);
}
+void __iomem *omap_irq_base;
+
/*
* Initialize asm_irq_base for entry-macro.S
*/
static inline void omap_irq_base_init(void)
{
- extern void __iomem *omap_irq_base;
-
-#ifdef MULTI_OMAP2
if (cpu_is_omap24xx())
omap_irq_base = OMAP2_L4_IO_ADDRESS(OMAP24XX_IC_BASE);
else if (cpu_is_omap34xx())
@@ -330,7 +329,6 @@ static inline void omap_irq_base_init(void)
omap_irq_base = OMAP2_L4_IO_ADDRESS(OMAP44XX_GIC_CPU_BASE);
else
pr_err("Could not initialize omap_irq_base\n");
-#endif
}
void __init omap2_init_common_infrastructure(void)
next prev parent reply other threads:[~2011-01-28 0:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 11:57 Latest regressions Russell King - ARM Linux
2011-01-07 12:58 ` Nishanth Menon
2011-01-07 14:41 ` Russell King - ARM Linux
2011-01-07 14:54 ` Santosh Shilimkar
2011-01-07 14:57 ` Russell King - ARM Linux
2011-01-07 17:12 ` Tony Lindgren
2011-01-07 16:56 ` Tony Lindgren
2011-01-07 21:56 ` Kevin Hilman
2011-01-26 8:58 ` Russell King - ARM Linux
2011-01-26 18:12 ` Tony Lindgren
2011-01-27 12:22 ` Russell King - ARM Linux
2011-01-28 0:18 ` Tony Lindgren [this message]
2011-01-28 0:21 ` Tony Lindgren
2011-01-28 0:24 ` Tony Lindgren
2011-01-26 9:01 ` Russell King - ARM Linux
2011-01-26 18:15 ` Tony Lindgren
2011-01-27 12:22 ` Russell King - ARM Linux
2011-01-28 0:22 ` 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=20110128001829.GN23412@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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