From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 08/14] omap: Use ioremap for omap4 L4 code
Date: Mon, 19 Oct 2009 10:38:32 -0700 [thread overview]
Message-ID: <20091019173831.GS12576@atomide.com> (raw)
In-Reply-To: <A24693684029E5489D1D202277BE89444CFD9382@dlee02.ent.ti.com>
* Aguirre Rodriguez, Sergio Alberto <saaguirre@ti.com> [091019 10:21]:
> Tony,
>
> > -----Original Message-----
> > From: linux-omap-owner at vger.kernel.org
> > [mailto:linux-omap-owner at vger.kernel.org] On Behalf Of Tony Lindgren
> > Sent: Monday, October 19, 2009 12:12 PM
> > To: Shilimkar, Santosh
> > Cc: linux-arm-kernel at lists.infradead.org; linux-omap at vger.kernel.org
> > Subject: Re: [PATCH 08/14] omap: Use ioremap for omap4 L4 code
> >
> > * Shilimkar, Santosh <santosh.shilimkar@ti.com> [091019 00:27]:
> > > Tony,
> > > > -----Original Message-----
> > > > From: Tony Lindgren [mailto:tony at atomide.com]
> > > > Sent: Monday, October 19, 2009 5:54 AM
> > > > To: Shilimkar, Santosh
> > > > Cc: linux-arm-kernel at lists.infradead.org;
> > linux-omap at vger.kernel.org
> > > > Subject: Re: [PATCH 08/14] omap: Use ioremap for omap4 L4 code
> > > >
> > > > * Tony Lindgren <tony@atomide.com> [091017 09:19]:
> > > > > * Shilimkar, Santosh <santosh.shilimkar@ti.com> [091017 03:49]:
> > > > > > Thanks Tony for this ioremap series!!
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Tony Lindgren [mailto:tony at atomide.com]
> > > > > > > Sent: Saturday, October 17, 2009 5:16 AM
> > > > > > > To: linux-arm-kernel at lists.infradead.org
> > > > > > > Cc: linux-omap at vger.kernel.org; Shilimkar, Santosh
> > > > > > > Subject: Re: [PATCH 08/14] omap: Use ioremap for
> > omap4 L4 code
> > > > > > >
> > > > > > > * Tony Lindgren <tony@atomide.com> [091016 16:42]:
> > > > > > > > Use ioremap for omap4 L4 code
> > > > > > >
> > > > > > > Santosh, can you please check and ack this patch?
> > > > > > >
> > > > > > > Especially some of the ioremap sizes may be wrong.
> > Also, this one
> > > > > > > I cannot boot test, so it's just compile tested.
> > > > > >
> > > > > > I have checked the patch and it looks all right
> > except few typo. Also
> > > > the scu_base is needed bit earlier.
> > > >
> > > > <snip>
> > > >
> > > > > > Here is the patch on top of ioremap series which
> > should fix above
> > > > mentioned things. With below patch + two serial related
> > patches the kernel
> > > > boots on OMAP4430.
> > > > >
> > > > > Great, will update. Thanks for taking the time to fix it!
> > > >
> > > > Here's this one updated with Santosh's fix merged in.
> > > V2 has one typo which I think I also missed in my patch.
> > > >+ /* Static mapping, never released */
> > > >+ gic_cpu_base_addr = ioremap(OMAP44XX_GIC_CPU_BASE, SZ_512);
> > > >+ BUG_ON(!base);
> > > Should be BUG_ON(!gic_cpu_base_addr);
> >
> > OK, here's V3 of the patch.
>
> Tony,
>
> > diff --git a/arch/arm/plat-omap/include/mach/entry-macro.S b/arch/arm/plat-omap/include/mach/entry-macro.S
> > index abe0864..3bad928 100644
> > --- a/arch/arm/plat-omap/include/mach/entry-macro.S
> > +++ b/arch/arm/plat-omap/include/mach/entry-macro.S
> > @@ -104,6 +104,8 @@
> >
> > .endm
> > #else
> > +#define OMAP44XX_VA_GIC_CPU_BASE OMAP2_IO_ADDRESS(OMAP44XX_GIC_CPU_BASE)
> > +
>
> Shouldn't this define go with the ioremap aproach?
That's still needed for the get_irqnr_and_base assembly macro.
But at least it's now defined locally for the macro.
Tony
next prev parent reply other threads:[~2009-10-19 17:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 23:40 [PATCH 00/14] Use ioremap for omap, split OMAP2_IO_ADDRESS for more space Tony Lindgren
2009-10-16 23:40 ` [PATCH 01/14] omap: Change low-level serial init to use ioremap Tony Lindgren
2009-10-16 23:40 ` [PATCH 02/14] omap: Use ioremap in irq.c Tony Lindgren
2009-10-16 23:40 ` [PATCH 03/14] omap: Use ioremap in dma.c Tony Lindgren
2009-10-16 23:40 ` [PATCH 04/14] omap: Use ioremap in dmtimer.c Tony Lindgren
2009-10-16 23:41 ` [PATCH 05/14] omap: Use ioremap in gpio.c Tony Lindgren
2009-10-17 8:10 ` Russell King - ARM Linux
2009-10-17 16:13 ` Tony Lindgren
2009-10-19 0:19 ` Tony Lindgren
2009-10-16 23:41 ` [PATCH 06/14] omap: Use ioremap in omap_hwmod.c Tony Lindgren
2009-10-16 23:41 ` [PATCH 07/14] omap: Use getnstimeofday for omap_device Tony Lindgren
2009-10-16 23:41 ` [PATCH 08/14] omap: Use ioremap for omap4 L4 code Tony Lindgren
2009-10-16 23:46 ` Tony Lindgren
2009-10-17 10:48 ` Shilimkar, Santosh
2009-10-17 16:19 ` Tony Lindgren
2009-10-19 0:24 ` Tony Lindgren
2009-10-19 7:27 ` Shilimkar, Santosh
2009-10-19 17:12 ` Tony Lindgren
2009-10-19 17:21 ` Aguirre Rodriguez, Sergio Alberto
2009-10-19 17:38 ` Tony Lindgren [this message]
2009-10-19 18:07 ` Aguirre Rodriguez, Sergio Alberto
2009-10-20 6:34 ` Shilimkar, Santosh
2009-10-16 23:41 ` [PATCH 09/14] omap: Use ioremap in dispc.c Tony Lindgren
2009-10-16 23:42 ` [PATCH 10/14] omap: Split OMAP2_IO_ADDRESS to L3 and L4 Tony Lindgren
2009-10-16 23:42 ` [PATCH 11/14] omap: Remap L3, L4 to get more kernel io address space Tony Lindgren
2009-10-20 0:20 ` Tony Lindgren
2009-10-20 6:32 ` Shilimkar, Santosh
2009-10-16 23:42 ` [PATCH 12/14] omap: Move SRAM map to claim more io space Tony Lindgren
2009-10-16 23:42 ` [PATCH 13/14] omap: Fix DEBUG_LL UART io address Tony Lindgren
2009-10-16 23:42 ` [PATCH 14/14] omap: Add OMAP4 L3 and L4 peripherals 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=20091019173831.GS12576@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).