From: Richard Purdie <rpurdie@rpsys.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: lenz@cs.wisc.edu, Bompart Cedric <cedric.bompart@thales-is.com>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Hook collie frontlight into sysfs
Date: Fri, 31 Mar 2006 11:13:45 +0100 [thread overview]
Message-ID: <1143800026.6443.28.camel@localhost.localdomain> (raw)
In-Reply-To: <20060331082352.GF1663@elf.ucw.cz>
On Fri, 2006-03-31 at 10:23 +0200, Pavel Machek wrote:
> Hi!
>
> > During our test with Richard, we've been thinking can you implement the
> > full range of brightness intensity values? For example for the others
> > Zaurus, I think the range is between 0 and 63. So the userspace can
>
> Well, I'm not sure if other values are "legal". They could damage
> frontlight long-term or just eat too much power...
For what its worth, these back/frontlight controllers are normally PWM
driven so the LED is always at full brightness and just the percentage
of time its turned on varies. These numbers in the driver control the
duty cycle of the PWM.
The original code for corgi/spitz only had a limited number of values
and I exposed the whole range into userspace. I doubt you can damage the
hardware with the different values. There are probably optimal points
for power consumption which is perhaps why Sharp limited the values
exposed. My view is that its up to userspace to limit the values for
optimal power consumption :).
> > adjust a wider range of levels for the backlight. Another thing, I
> > didn't see anything different visually between the value 3 and 4.
>
> You are right, the code to go brightness 4 is attached. It probably
> needs to be converted to writel/readl...
This makes sense as on corgi/spitz there is also this magic bit to set
for the second level of brightness settings...
I'll have a look at these patches and perhaps combine/convert them to
the replacement backlight interface, then we can submit them to Antonino
Daplas/Andrew so all the backlight patches are in one place (currently
-mm).
Given what I've said above, would you be happy to expose the full range
of values to userspace?
Richard
next prev parent reply other threads:[~2006-03-31 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 7:29 Bompart Cedric
2006-03-31 8:23 ` Pavel Machek
2006-03-31 10:13 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-30 11:46 Pavel Machek
2006-03-30 22:59 ` Richard Purdie
2006-03-30 23:30 ` Pavel Machek
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=1143800026.6443.28.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=cedric.bompart@thales-is.com \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
Powered by JetHome