linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: aliguori@us.ibm.com, adaplas@gmail.com, linux-sh@vger.kernel.org,
	armbru@redhat.com, lethal@linux-sh.org,
	Magnus Damm <magnus.damm@gmail.com>,
	jayakumar.lkml@gmail.com
Subject: [PATCH 00/05] video: deferred io sys helpers V2
Date: Wed, 24 Dec 2008 17:29:46 +0900	[thread overview]
Message-ID: <20081224082946.1848.46644.sendpatchset@rx1.opensource.se> (raw)

video: deferred io sys helpers V2

[PATCH 01/05] video: deferred io sys helpers - core V2
[PATCH 02/05] video: deferred io sys helpers - sh_mobile_lcdcfb V2
[PATCH 03/05] video: deferred io sys helpers - hecuba / n411 V2
[PATCH 04/05] video: deferred io sys helpers - metronome V2
[PATCH 05/05] video: deferred io sys helpers - xen V2

This patchset extends the deferred io core code with commonly used functions.

The following functions are added to and exported from fb_defio.c:
 - fb_deferred_io_read()
 - fb_deferred_io_write()
 - fb_deferred_io_fillrect()
 - fb_deferred_io_copyarea()
 - fb_deferred_io_imageblit()

The functions above makes use the deferred io delay which so far only
has been used for mmap. This means for instance that the drivers using
these functions no longer will refresh the screen according to the soft
cursor refresh rate, instead the screen refresh rate derived from the
deferred io delay value will be used.

The deferred io core code now keeps track of a dirty area between the
calls to the functions above. Only xen is currently making use of this.

In the future we may want to extend the dirty area tracking code to
instead modify the dirty bits for the pages backing the frame buffer.

Status:
- sh_mobile_lcdcfb: compiles and works well
- hecuba / n411: compiles on superh, but untested
- metronome: compiles on superh, but untested
- xen: unknown

Signed-off-by: Magnus Damm <damm@igel.co.jp>
---

 drivers/video/Kconfig            |   35 +++---------
 drivers/video/fb_defio.c         |   77 ++++++++++++++++++++++++++
 drivers/video/hecubafb.c         |   86 +----------------------------
 drivers/video/metronomefb.c      |  109 ++++++++------------------------------
 drivers/video/sh_mobile_lcdcfb.c |   39 +------------
 drivers/video/xen-fbfront.c      |   51 +++--------------
 include/linux/fb.h               |   12 ++++
 7 files changed, 145 insertions(+), 264 deletions(-)

             reply	other threads:[~2008-12-24  8:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-24  8:29 Magnus Damm [this message]
2008-12-24  8:29 ` [PATCH 01/05] video: deferred io sys helpers - core V2 Magnus Damm
2008-12-25 19:03   ` Jaya Kumar
2008-12-24  8:30 ` [PATCH 02/05] video: deferred io sys helpers - sh_mobile_lcdcfb V2 Magnus Damm
2008-12-24  8:30 ` [PATCH 03/05] video: deferred io sys helpers - hecuba / n411 V2 Magnus Damm
2008-12-24  8:30 ` [PATCH 04/05] video: deferred io sys helpers - metronome V2 Magnus Damm
2008-12-24  8:30 ` [PATCH 05/05] video: deferred io sys helpers - xen V2 Magnus Damm

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=20081224082946.1848.46644.sendpatchset@rx1.opensource.se \
    --to=magnus.damm@gmail.com \
    --cc=adaplas@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=armbru@redhat.com \
    --cc=jayakumar.lkml@gmail.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-sh@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;
as well as URLs for NNTP newsgroup(s).