From: "Jaya Kumar" <jayakumar.lkml@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Paul Mundt <lethal@linux-sh.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, James Simmons <jsimmons@infradead.org>
Subject: Re: [PATCH 2.6.20 1/1] fbdev,mm: hecuba/E-Ink fbdev driver
Date: Wed, 21 Feb 2007 11:55:17 -0500 [thread overview]
Message-ID: <45a44e480702210855t344441c1xf8e081c82ece4e63@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0702200906070.2082@pademelon.sonytel.be>
On 2/20/07, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> Don't you need a way to specify the maximum deferral time? E.g. a field in
> fb_info.
>
You are right. I will need that. I could put that into struct
fb_deferred_io. So drivers would setup like:
static struct fb_deferred_io hecubafb_defio = {
.delay = HZ,
.deferred_io = hecubafb_dpy_update,
};
where that would be:
struct fb_deferred_io {
unsigned long delay; /* delay between mkwrite and deferred handler */
struct mutex lock; /* mutex that protects the page list */
struct list_head pagelist; /* list of touched pages */
struct delayed_work deferred_work;
void (*deferred_io)(struct fb_info *info, struct list_head
*pagelist); /* callback */
};
and the driver would do:
...
info->fbdefio = hecubafb_defio;
register_framebuffer...
When the driver calls register_framebuffer and unregister_framebuffer,
I can then do the init and destruction of the other members of that
struct. Does this sound okay?
Thanks,
jaya
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-02-21 16:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-17 10:42 [PATCH 2.6.20 1/1] fbdev,mm: hecuba/E-Ink fbdev driver Jaya Kumar
2007-02-17 12:34 ` Peter Zijlstra
2007-02-17 13:25 ` Jaya Kumar
2007-02-17 13:59 ` Paul Mundt
2007-02-18 11:31 ` Jaya Kumar
2007-02-18 23:57 ` Paul Mundt
2007-02-20 4:13 ` Jaya Kumar
2007-02-20 4:38 ` Paul Mundt
2007-02-20 6:11 ` Jaya Kumar
2007-02-21 16:46 ` Jaya Kumar
2007-02-20 8:07 ` Geert Uytterhoeven
2007-02-21 16:55 ` Jaya Kumar [this message]
2007-02-21 21:52 ` James Simmons
2007-02-21 23:22 ` Jaya Kumar
2007-02-28 16:50 ` [Linux-fbdev-devel] [PATCH 2.6.20 1/1] fbdev, mm: " James Simmons
2007-02-21 23:43 ` Antonino A. Daplas
2007-02-21 23:47 ` Jaya Kumar
2007-02-21 23:43 ` Antonino A. Daplas
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=45a44e480702210855t344441c1xf8e081c82ece4e63@mail.gmail.com \
--to=jayakumar.lkml@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=lethal@linux-sh.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).