linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: ext Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: ext Tony Lindgren <tony@atomide.com>,
	Grazvydas Ignotas <notasas@gmail.com>,
	"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [RFC] Initial attempt to make ARM use LMB
Date: Tue, 18 May 2010 11:58:10 +0300	[thread overview]
Message-ID: <1274173090.2307.100.camel@tubuntu.research.nokia.com> (raw)
In-Reply-To: <20100518084013.GA13832@n2100.arm.linux.org.uk>

On Tue, 2010-05-18 at 10:40 +0200, ext Russell King - ARM Linux wrote:
> On Tue, May 18, 2010 at 10:47:57AM +0300, Tomi Valkeinen wrote:
> > Allocating without ioremapping... dma_alloc_* always ioremaps the
> > allocated area, even though it's never used (in some cases).
> 
> What do you mean by that?  Are you suggesting that something does
> phys_to_virt() on the returned DMA pointer?

No.

VRFB rotation HW uses the real memory as a backend storage, and exposes
0/90/180/270 degree views of that memory area via its own memory areas.
So we need to reserve the real memory, program it to VRFB HW, and then
map VRFB's memory areas, which are used as framebuffers. The real memory
is never used directly in this case.

And even when not using VRFB, I think it's not really required to map
the framebuffer into kernel virtual memory. The kernel doesn't
read/write from/to the framebuffer (except when using FB console), it's
the user space, SGX or DSP that does the writing, and DSS which does the
reading. However, currently the framebuffer is always mapped.

 Tomi



  reply	other threads:[~2010-05-18  8:58 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 23:32 [RFC] Initial attempt to make ARM use LMB Russell King - ARM Linux
2010-03-31  6:43 ` Jeremy Kerr
2010-04-01  9:47   ` Tony Lindgren
2010-04-09 11:13   ` Russell King - ARM Linux
2010-04-08 15:32 ` Rabin Vincent
2010-04-08 18:27   ` Russell King - ARM Linux
2010-04-09 11:11     ` Russell King - ARM Linux
2010-04-10  3:42       ` Rabin Vincent
2010-04-10  7:03         ` Russell King - ARM Linux
2010-04-10 11:56           ` Rabin Vincent
2010-04-14  7:34       ` Benjamin Herrenschmidt
2010-05-05 15:02 ` Russell King - ARM Linux
2010-05-13 17:40   ` Russell King - ARM Linux
2010-05-13 21:19     ` Tony Lindgren
2010-05-13 21:58       ` Russell King - ARM Linux
2010-05-13 22:01         ` Tony Lindgren
2010-05-13 22:12           ` Russell King - ARM Linux
2010-05-14  7:24             ` Shilimkar, Santosh
2010-05-14 10:11               ` Grazvydas Ignotas
2010-05-14 10:16                 ` Russell King - ARM Linux
2010-05-17  9:38                   ` Grazvydas Ignotas
2010-05-17  9:44                     ` Russell King - ARM Linux
2010-05-17 10:26                       ` Tomi Valkeinen
2010-05-17 17:37                         ` Tony Lindgren
2010-05-18  7:47                           ` Tomi Valkeinen
2010-05-18  8:40                             ` Russell King - ARM Linux
2010-05-18  8:58                               ` Tomi Valkeinen [this message]
2010-05-14 15:22             ` Tony Lindgren
2010-05-14 15:32               ` Shilimkar, Santosh
2010-05-14 15:43                 ` Tony Lindgren
2010-05-22 21:58 ` Russell King - ARM Linux
2010-05-26  0:44   ` Tony Lindgren
2010-05-26  7:50     ` Russell King - ARM Linux
2010-05-26 13:51       ` Tony Lindgren
2010-05-26 21:40         ` Russell King - ARM Linux
2010-05-27  8:52           ` Tomi Valkeinen
2010-05-27  9:25             ` Russell King - ARM Linux
2010-05-27  9:47               ` Tomi Valkeinen
2010-05-28 14:32     ` Russell King - ARM Linux
2010-05-31  8:04       ` 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=1274173090.2307.100.camel@tubuntu.research.nokia.com \
    --to=tomi.valkeinen@nokia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=notasas@gmail.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=tony@atomide.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 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).