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:24:47 -0800 [thread overview]
Message-ID: <20110128002446.GQ23412@atomide.com> (raw)
In-Reply-To: <20110128002115.GO23412@atomide.com>
* Tony Lindgren <tony@atomide.com> [110127 16:20]:
> * Tony Lindgren <tony@atomide.com> [110127 16:17]:
> >
> > Will also post a similar change for omap1.
>
> And here's the omap1 related change.
> --- a/arch/arm/mach-omap1/irq.c
> +++ b/arch/arm/mach-omap1/irq.c
> @@ -57,6 +57,7 @@ struct omap_irq_bank {
> unsigned long wake_enable;
> };
>
> +void __iomem *omap_irq_flags;
> static unsigned int irq_bank_count;
> static struct omap_irq_bank *irq_banks;
>
The omap_irq_flags here should not be void __iomem *, updated
patch below.
Tony
From: Tony Lindgren <tony@atomide.com>
Date: Thu, 27 Jan 2011 15:52:16 -0800
Subject: [PATCH] omap1: Simplify use of omap_irq_flags
Commit 03a9e5126147c9f92aeba4b34f62b15b625087fb
(omap1: Use asm_irq_flags for entry-macro.S) added support
for multi-omap builds with addition of the omap_irq_flags.
Commit 9f9605c2eda9679e6f63c605cbd9cbf6a9a7f3fa
(omap2+: Fix unused variable warning for omap_irq_base)
simplified omap2+ entry-macro.S by moving omap_irq_flags
out of entry-macro.S.
Simplify omap1 entry-macro.S in a similar way to keep the
code consistent. Based on a similar earlier patch for omap2+
by Russell King <rmk+kernel@arm.linux.org.uk>.
Signed-off-by: Tony Lindgren <tony@atomide.com>
--- a/arch/arm/mach-omap1/include/mach/entry-macro.S
+++ b/arch/arm/mach-omap1/include/mach/entry-macro.S
@@ -14,19 +14,6 @@
#include <mach/irqs.h>
#include <asm/hardware/gic.h>
-/*
- * We use __glue to avoid errors with multiple definitions of
- * .globl omap_irq_flags as it's included from entry-armv.S but not
- * from entry-common.S.
- */
-#ifdef __glue
- .pushsection .data
- .globl omap_irq_flags
-omap_irq_flags:
- .word 0
- .popsection
-#endif
-
.macro disable_fiq
.endm
--- a/arch/arm/mach-omap1/irq.c
+++ b/arch/arm/mach-omap1/irq.c
@@ -57,6 +57,7 @@ struct omap_irq_bank {
unsigned long wake_enable;
};
+u32 omap_irq_flags;
static unsigned int irq_bank_count;
static struct omap_irq_bank *irq_banks;
@@ -176,7 +177,6 @@ static struct irq_chip omap_irq_chip = {
void __init omap_init_irq(void)
{
- extern unsigned int omap_irq_flags;
int i, j;
#if defined(CONFIG_ARCH_OMAP730) || defined(CONFIG_ARCH_OMAP850)
next prev parent reply other threads:[~2011-01-28 0:24 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
2011-01-28 0:21 ` Tony Lindgren
2011-01-28 0:24 ` Tony Lindgren [this message]
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=20110128002446.GQ23412@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