From: Marco Chiappero <marco@absence.it>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: platform-driver-x86@vger.kernel.org,
Javier Achirica <achirica@gmail.com>,
Mattia Dongili <malattia@linux.it>
Subject: Re: Commit 7751ab8e600f26e10c2ba12a92d48a4852a51da8
Date: Wed, 13 Apr 2011 18:50:34 +0200 [thread overview]
Message-ID: <4DA5D45A.9070901@absence.it> (raw)
In-Reply-To: <20110412152009.GA32032@srcf.ucam.org>
Il 12/04/2011 17:20, Matthew Garrett ha scritto:
> Hmm. How low is useful? There's no real problem with shifting everything
> by an offset.
I agree. The DSDT of any ALS equipped Vaio provides us 9 backlight
levels (that are LCD/model specific), so the first and the last ones
define our useful operating range, which is always different from 0-255
(eg. 13-255 for the Vaio S, 52-255 for the Vaio F, 7-182 for the Vaio Z,
7-213 for the Vaio TT and so on). However the code to retrieve and use
those lower and upper bounds is still lacking upstream (I, Javier
Achirica and many other people are testing a heavily modified
sony-laptop.c written by us which includes lots of features that we
might include soon, but there is no patchset yet).
Moreover it is questionable whether to expose this "wire-range"/fine
grain backlight device, which is intended to be used for an ambient
light based regulation (that requires smooth transitions and sometimes
minimal changes), while for normal backlight operations the 9 levels
already mentioned should suffice.
Regards,
Marco Chiappero
next prev parent reply other threads:[~2011-04-13 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 16:17 Commit 7751ab8e600f26e10c2ba12a92d48a4852a51da8 Marco Chiappero
2011-04-12 15:20 ` Matthew Garrett
2011-04-13 16:50 ` Marco Chiappero [this message]
2011-04-13 16:53 ` Matthew Garrett
2011-04-14 7:37 ` Marco Chiappero
2011-04-14 22:42 ` Mattia Dongili
2011-04-16 13:04 ` [PATCH] sony-laptop: limit brightness range to DSDT provided ones Mattia Dongili
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=4DA5D45A.9070901@absence.it \
--to=marco@absence.it \
--cc=achirica@gmail.com \
--cc=malattia@linux.it \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.