public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Ben Dooks <ben-linux@fluff.org>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: RFC: Reclaim address space on omaps, Tony on vacation in July
Date: Fri, 26 Jun 2009 12:02:54 +0300	[thread overview]
Message-ID: <20090626090254.GF7352@atomide.com> (raw)
In-Reply-To: <20090626085752.GE7352@atomide.com>

* Tony Lindgren <tony@atomide.com> [090626 11:58]:
> * Ben Dooks <ben-linux@fluff.org> [090626 11:37]:
> > On Fri, Jun 26, 2009 at 09:25:40AM +0300, Tony Lindgren wrote:
> > > 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
> > 
> > ioremap implies readl/writel, the __raw stuff is for items that have been
> > mapped by iodesc (iirc).
> 
> Thanks, will take a look at the iodesc.

Hmm, OK so we should just use readl/writel. No need to map everything
statically with struct map_desc.

Tony

      reply	other threads:[~2009-06-26  9:03 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
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 [this message]

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=20090626090254.GF7352@atomide.com \
    --to=tony@atomide.com \
    --cc=ben-linux@fluff.org \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-omap@vger.kernel.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