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: Thu, 14 Apr 2011 09:37:15 +0200 [thread overview]
Message-ID: <4DA6A42B.1000002@absence.it> (raw)
In-Reply-To: <20110413165344.GA739@srcf.ucam.org>
Il 13/04/2011 18:53, Matthew Garrett ha scritto:
> Can this code be merged within the next week?
Uhm, I don't know exactly but I don't think so.
> If not I agree that it'd
> be better to drop this patch for now.
There is no hurry, such backlight device is useless as long as the ALS
code isn't included too.
> I think exposing the full range of
> (usable) brightness values makes sense, since ALS policy is likely to be
> determined in userspace - we'll need some way to expose the appropriate
> mapping, but that's something that needs to be handled generically in
> the long run.
Well, Javier Achirica and another tester already produced a working
daemon implementing the ALS driven backlight regulation (and that might
also deal with a few more Vaio specific features in the near feature).
However it's not that plain and easy, exposing a single backlight device
prevents everything from working properly because of some issues
(currently we are using a different solution, with its drawbacks as
well, but that proved to work well). If you're interested I can provide
further details.
Regards,
Marco Chiappero
next prev parent reply other threads:[~2011-04-14 7:37 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
2011-04-13 16:53 ` Matthew Garrett
2011-04-14 7:37 ` Marco Chiappero [this message]
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=4DA6A42B.1000002@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.