public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Len Brown <lenb@kernel.org>, Richard Purdie <rpurdie@rpsys.net>,
	Matthew Garrett <mjg59@srcf.ucam.org>, Greg KH <greg@kroah.com>
Subject: Re: [PATCH 0/3] Generic sysfs support for ACPI ALS and other ALS devices
Date: Fri, 21 Aug 2009 13:51:00 +0200	[thread overview]
Message-ID: <20090821115100.GA20681@elf.ucw.cz> (raw)
In-Reply-To: <1250497963.5351.33.camel@rzhang-dt>

Hi!

> > > Could you please look at the documentation about ALS sysfs class in the
> > > patch I sent out just now, and comment on that one please? thanks!
> > 
> > I did. The interface is too ugly to live.
> 
> Hi, Pavel,
> 
> I tried to convert the ALS sysfs I/F to two attributes only, i.e.
> illuminance and adjustment.
> But I found several potential problems.
> 1. the illuminance to display adjustment mappings can not be convert to
> a brightness level smoothly.
> for example,
> 	illuminance	adjustment
> 1	600		70
> 2	900		100
> 3	1500		120
> when the current illuminance is not one of the values listed in the
> mappings, e.g. 750, the ALS driver don't have enough knowledge to get
> the proper display adjustment, especially that a proper display
> adjustment would be easy to select a proper brightness level.
> We'd better leave this to user space, which is more flexible.

Well, what interpolation does ACPI specs suggest to do? Maybe it is
easier to have linear interpolation in the kernel than to have ugly
20-file interface?

> 2. I don't know if there will be laptops exporting buggy mappings that
> needs to be overridden some day, but the current sysfs I/F is easy for
> expanding.
> what do you think?

If you have buggy laptop, fix the laptop. (You can still export the
raw values... and btw if you have buggy laptop and want to work around
it, maybe the workaround is easier/better done in kernel?)

								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-08-21 11:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03  9:10 [PATCH 0/3] Generic sysfs support for ACPI ALS and other ALS devices Zhang Rui
2009-08-04  1:12 ` ykzhao
2009-08-04  7:30   ` Zhang Rui
2009-08-04 13:21 ` Pavel Machek
2009-08-04 15:10   ` Greg KH
2009-08-04 17:24     ` Valdis.Kletnieks
2009-08-04 17:36       ` Greg KH
2009-08-05  1:04         ` Zhang Rui
2009-08-05 16:10           ` Valdis.Kletnieks
2009-08-06  1:51             ` Zhang Rui
2009-08-05  0:55     ` Zhang Rui
2009-08-05  1:02   ` Zhang Rui
2009-08-05 16:19     ` Pavel Machek
2009-08-06  1:41       ` Zhang Rui
2009-08-06  7:13         ` Pavel Machek
2009-08-06  8:47           ` Zhang Rui
2009-08-06  9:52             ` Pavel Machek
2009-08-17  8:32               ` Zhang Rui
2009-08-21 11:51                 ` Pavel Machek [this message]
2009-08-25  1:13                   ` Zhang Rui

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=20090821115100.GA20681@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=greg@kroah.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=rpurdie@rpsys.net \
    --cc=rui.zhang@intel.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