From: Pete Popov <ppopov@embeddedalley.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net,
Andrew Morton <akpm@osdl.org>, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH] Au1200fb driver.
Date: Mon, 17 Oct 2005 20:10:19 -0700 [thread overview]
Message-ID: <1129605019.18165.4.camel@localhost.localdomain> (raw)
In-Reply-To: <435450C5.3040800@gmail.com>
Thanks Tony. I'll fix it up and resubmit.
Pete
On Tue, 2005-10-18 at 09:32 +0800, Antonino A. Daplas wrote:
> Ralf Baechle wrote:
> > Au1200 fb driver. Updated db1200 defconfig to include driver by default.
>
> Besides coding style issues, here are a few comments:
>
> > +struct window_settings
> > +{
> > + unsigned char name[64];
> > + uint32 mode_backcolor;
> > + uint32 mode_colorkey;
> > + uint32 mode_colorkeymsk;
>
> Any problems using u32 and family instead of uint32?
>
> > +
> > +/* AU1200 framebuffer driver */
> > +
> > +int au1200fb_fb_open(struct fb_info *fbi, int user)
> > +{
> > + return 0;
> > +}
> > +
> > +int au1200fb_fb_release(struct fb_info *fbi, int user)
> > +{
> > + return 0;
> > +}
> > +
>
> You can just remove the fb_release and fb_open methods if they're not
> doing anything.
>
> > +
> > +/* fb_blank
> > + * Blank the screen. Depending on the mode, the screen will be
> > + * activated with the backlight color, or desactivated
> > + */
> > +int au1200fb_fb_blank(int blank_mode, struct fb_info *fbi)
> > +{
> > + /* Short-circuit screen blanking */
> > + if (noblanking)
> > + return 0;
> > +
> > + switch (blank_mode) {
> > +
> > + case VESA_NO_BLANKING:
> > + /* printk("turn on panel\n"); */
> > + au1200_setpanel(panel);
> > + break;
> > +
> > + case VESA_VSYNC_SUSPEND:
> > + case VESA_HSYNC_SUSPEND:
> > + case VESA_POWERDOWN:
> > + /* printk("turn off panel\n"); */
> > + au1200_setpanel(NULL);
> > + break;
>
> Better to use the FB_BLANK_* constants defined in include/linux/fb.h instead
> of the VESA_* constants. There's also one constant, FB_BLANK_NORMAL, which
> usually means blank the display but keep monitor syncs on. But if you just
> have 2 blank states, might as well do an if (blank_mode)/else.
>
> Tony
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
prev parent reply other threads:[~2005-10-18 3:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 2:10 [PATCH] Au1200fb driver Ralf Baechle
2005-10-18 1:32 ` Antonino A. Daplas
2005-10-18 3:10 ` Pete Popov [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=1129605019.18165.4.camel@localhost.localdomain \
--to=ppopov@embeddedalley.com \
--cc=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=ralf@linux-mips.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