linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
Cc: linux-fbdev <Linux-fbdev-devel@lists.sourceforge.net>,
	Linux-sh <linux-sh@vger.kernel.org>
Subject: Re: [PATCH v3] video: sh7760fb: SH7760/SH7763 LCDC framebuffer driver
Date: Tue, 1 Jul 2008 17:00:06 +0900	[thread overview]
Message-ID: <20080701080006.GB4726@linux-sh.org> (raw)
In-Reply-To: <4869DC13.30604@renesas.com>

On Tue, Jul 01, 2008 at 04:26:11PM +0900, Nobuhiro Iwamatsu wrote:
> +====================== cut here ======================================
> +
> +#include <linux/fb.h>
> +#include <asm/sh7760fb.h>
> +
> +/*
> + * NEC NL6440bc26-01 640x480 TFT
> + * dotclock 25175 kHz
> + * Xres		640	Yres		480
> + * Htotal	800	Vtotal		525
> + * HsynStart	656	VsynStart	490
> + * HsynLenn	30	VsynLenn	2
> + *
> + * The linux framebuffer layer does not use the syncstart/synclen
> + * values but right/left/upper/lower margin values. The comments
> + * for the x_margin explain how to calculate those from given
> + * panel sync timings.
> + */
> +static struct fb_videomode nl6448bc26 = {
> +/*	.name		= "NL6448BC26",*/
> +/*	.refresh	= 60,	*/
> +	.xres		= 640,
> +	.yres		= 480,
Why are .name and .refresh commented out?

> +static void sh7760fb_wait_vsync(struct fb_info *info)
> +{
> +	struct sh7760fb_par *par = info->par;
> +
> +	if (par->pd->novsync)
> +		return;
> +}
> +
This doesn't do anything, and you never use ->novsync for anything
anywhere else either. I'd suggest killing both of them off until such a
time that you plan to do something with it.

> +	/* poll for access grant */
> +	tmo = 100;
> +	while (!(ioread16(par->base + LDPALCR) & (1 << 4)) && (--tmo))
> +		msleep(0);
> +
Err.. you are sleeping for 0ms? Just use cpu_relax() here instead if you
don't have an explicit timing requirement.

> +	if (((ldmtr & 0x003f) >= LDMTR_DSTN_MONO_8) &&
> +	    ((ldmtr & 0x003f) <= LDMTR_DSTN_COLOR_16)) {
> +
> +		pr_debug(" ***** DSTN untested! *****\n");
> +
This should still use dev_dbg() for consistency.

Looks good to me otherwise, fix those up and feel free to add a:

Reviewed-by: Paul Mundt <lethal@linux-sh.org>

to the next version.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php

  reply	other threads:[~2008-07-01  8:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01  7:26 [PATCH v3] video: sh7760fb: SH7760/SH7763 LCDC framebuffer driver Nobuhiro Iwamatsu
2008-07-01  8:00 ` Paul Mundt [this message]
2008-07-01  8:17   ` Manuel Lauss
2008-07-02  2:12   ` Nobuhiro Iwamatsu

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=20080701080006.GB4726@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=Linux-fbdev-devel@lists.sourceforge.net \
    --cc=iwamatsu.nobuhiro@renesas.com \
    --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).