From: Manuel Lauss <mano@roarinelk.homelinux.net>
To: Paul Mundt <lethal@linux-sh.org>,
Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>,
linux-fbdev <Linux-fbdev-devel@lists.sourceforge.net>,
Linux-sh <linux-sh@vger.kernel.org>Nobuh
Subject: Re: [PATCH v3] video: sh7760fb: SH7760/SH7763 LCDC framebuffer driver
Date: Tue, 1 Jul 2008 10:17:49 +0200 [thread overview]
Message-ID: <20080701081748.GA5499@roarinelk.homelinux.net> (raw)
In-Reply-To: <20080701080006.GB4726@linux-sh.org>
Hello Paul, Iwamatsu-san,
On Tue, Jul 01, 2008 at 05:00:06PM +0900, Paul Mundt wrote:
> On Tue, Jul 01, 2008 at 04:26:11PM +0900, Nobuhiro Iwamatsu wrote:
> > +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.
I'm working on reimplementing it. I'll submit a patch when it's ready.
> > + /* 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.
I put the msleep here to prevent gcc from removing the loop.
Best regards,
Manuel Lauss
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2008-07-01 8:17 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
2008-07-01 8:17 ` Manuel Lauss [this message]
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=20080701081748.GA5499@roarinelk.homelinux.net \
--to=mano@roarinelk.homelinux.net \
--cc=Linux-fbdev-devel@lists.sourceforge.net \
--cc=iwamatsu.nobuhiro@renesas.com \
--cc=lethal@linux-sh.org \
--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).