From: Tony Lindgren <tony@atomide.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.arm.linux.org.uk"
<linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Re: Reclaim address space on omaps, Tony on vacation in July
Date: Fri, 26 Jun 2009 11:46:33 +0300 [thread overview]
Message-ID: <20090626084633.GD7352@atomide.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02B53AB55D@dbde02.ent.ti.com>
* Shilimkar, Santosh <santosh.shilimkar@ti.com> [090626 10:45]:
> > -----Original Message-----
> > From: linux-omap-owner@vger.kernel.org
> > [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Tony Lindgren
> > Sent: Friday, June 26, 2009 11:56 AM
> > To: linux-omap@vger.kernel.org
> > Cc: linux-arm-kernel@lists.arm.linux.org.uk
> > Subject: RFC: Reclaim address space on omaps, Tony on vacation in July
> >
> > Hi all,
> >
> > Last week I posted some more omap io.h clean-up patches to
> > the linux-omap
> > list [1], and started looking at what it would take to
> > reclaim lost address
> > space on top of the io.h clean-up patches.
> >
> > Looks like we should be able to reclaim about 454MB of the 640MB
> > of the lost IO address space by doing the following:
> >
> > 1. Start converting drivers using omap_read/write to use ioremap +
> > __raw_read/write
> >
> > 2. Remove OMAP2_IO_ADDRESS macro, and replace it with with
> > finer grained
> > OMAP_L3_ADDRESS, OMAP_L4_ADDRESS, OMAP_SDRC_ADDRESS and so
> > on macros
>
> > 3. Remap the the IO addresses in smaller sections in io.h so
> > the virtual
> > address for the blocks stays the same, and is counted down from the
> > ARM reserved DMA address.
> >
> > After these steps, omap io.h would look like this:
> >
> > #define ARM_RESERVED_FUTURE_DMA 0xff000000 /*
> > Documentation/arm/memory.txt */
> > #define OMAP23_L4_PHYS 0x48000000
> > #define OMAP24_L3_PHYS 0x68000000
> > #define OMAP4_L3_PHYS 0x44000000
> > #define OMAP4_L4_PHYS 0x4a000000
> >
> > /* These virtual addresses are the same for all omaps */
> > #define OMAP_L3_SIZE SZ_1M
> > #define OMAP_L3_VIRT (ARM_RESERVED_FUTURE_DMA - OMAP_L3_SIZE)
> > #define OMAP_L4_SIZE (SZ_16M + SZ_1M)
> > #define OMAP_L4_VIRT (OMAP_L3_VIRT - OMAP_L4_SIZE)
> > #define OMAP_SDRC_SIZE SZ_1M
> > #define OMAP_SDRC_BASE (OMAP_L4_VIRT - OMAP_SDRC_SIZE)
> > ...
> >
> >
> > #define OMAP_L3_ADDRESS(pa) (((pa) & ~0xff000000) + OMAP_L3_VIRT)
> > #define OMAP_L4_ADDRESS(pa) (((pa) & ~0xff000000) + OMAP_L4_VIRT)
> > #define OMAP_SDRC_ADDRESS(pa) (((pa) & ~0xff000000) + OMAP_SDRC_VIRT)
> We surely need this going forward since there is also demand to fit higher
> RAMS(256MB,512MB,1GB)in the system.
>
> Just to confirm, any further patches on this topic should be on top of this:
> Tony Lindgren (3):
> OMAP: Remove ifdefs for io.h
> OMAP: Rename OMAP_MPUIO_BASE to OMAP1_MPUIO_BASE
> OMAP: Remove OMAP_IO_ADDRESS, use OMAP1_IO_ADDRESS and OMAP2_IO_ADDRESS instead
>
> Is that correct Tony ?
Yes it makes it easier as the patches above remove all the ifdefs for io.h.
Tony
next prev parent reply other threads:[~2009-06-26 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 6:25 RFC: Reclaim address space on omaps, Tony on vacation in July Tony Lindgren
2009-06-26 7:45 ` Shilimkar, Santosh
2009-06-26 8:46 ` Tony Lindgren [this message]
2009-06-26 18:14 ` Woodruff, Richard
2009-06-26 21:21 ` Kevin Hilman
2009-06-26 8:37 ` RFC: " Ben Dooks
2009-06-26 8:57 ` Tony Lindgren
2009-06-26 9:02 ` 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=20090626084633.GD7352@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.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.