From: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
To: David Brownell <david-b@pacbell.net>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
linux-fbdev-devel@lists.sourceforge.net,
Linux Kernel list <linux-kernel@vger.kernel.org>,
"Antonino A. Daplas" <adaplas@gmail.com>,
ARM Linux Mailing List <linux-arm-kernel@lists.arm.linux.org.uk>,
Sedji GAOUAOU <sedji.gaouaou@atmel.com>,
Patrice VILCHEZ <patrice.vilchez@atmel.com>,
Andrew Victor <linux@maxim.org.za>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] atmel_lcdfb: suspend/resume support
Date: Thu, 13 Mar 2008 21:00:12 +0100 [thread overview]
Message-ID: <20080313210012.5b9b97c5@siona.local> (raw)
In-Reply-To: <200803131219.38154.david-b@pacbell.net>
On Thu, 13 Mar 2008 11:19:37 -0800
David Brownell <david-b@pacbell.net> wrote:
> On Thursday 13 March 2008, Haavard Skinnemoen wrote:
>
> > > + sinfo->saved_lcdcon = lcdc_readl(sinfo, ATMEL_LCDC_CONTRAST_VAL);
> >
> > You're saving CONTRAST_VAL into a field called saved_lcdcon even though
> > it has nothing to do with LCDCON1 or LCDCON2...
>
> Yeah, why don't registers named LCDCONx have nothing
> to do with LCD CONtrast? Better to have named the PWM
> registers PWM ... and say they could be used for either
> contrast or backlight control.
While I admit you have a point, I think it's easier to change the name
of that field than changing the hardware documentation at this point ;)
> The saved contrast/backlight counter value CONTRAST_VAL is
> one of two PWM control registers.
I know.
> > > + lcdc_writel(sinfo, ATMEL_LCDC_CONTRAST_CTR, 0);
> >
> > ...then you're altering CONTRAST_CTR...
>
> That's forces the contrast signal low and disables the
> PWM counter, so it won't "randomly" leave the PWM output
> high when the clock is stopped (leaving at least some
> displays lit during suspend).
I'm not saying it's the wrong thing to do. I just think it's strange
that you alter a different register than the one you saved.
> It's possible that only CTR needed to be saved; all the
> backlight support in this driver still needs work.
Yes, I do think we can assume VAL stays unchanged during suspend.
> > > +}
> > > +
> > > +static int atmel_lcdfb_resume(struct platform_device *pdev)
> > > +{
> >
> > > + lcdc_writel(sinfo, ATMEL_LCDC_CONTRAST_CTR, sinfo->saved_lcdcon);
> >
> > ...and later restoring the saved value of CONTRAST_VAL into CONTRAST_CTR.
> >
> > Confused.
>
> Yeah, that looks wrong; the patch below makes more sense.
> Though it *does* behave right for some reason...
Yes, that looks better. Perhaps you used a contrast value that happened
to set the right bits when written to CTR?
I still think the name of the saved_lcdcon field is confusing though.
Haavard
prev parent reply other threads:[~2008-03-13 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 13:51 [PATCH] atmel_lcdfb: suspend/resume support Nicolas Ferre
2008-03-13 15:24 ` Haavard Skinnemoen
2008-03-13 19:19 ` David Brownell
2008-03-13 20:00 ` Haavard Skinnemoen [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=20080313210012.5b9b97c5@siona.local \
--to=haavard.skinnemoen@atmel.com \
--cc=adaplas@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=nicolas.ferre@atmel.com \
--cc=patrice.vilchez@atmel.com \
--cc=sedji.gaouaou@atmel.com \
/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).