public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mattia Dongili" <malattia@linux.it>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Len Brown <lenb@kernel.org>, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] sony-laptop: allow complex per-value input/output   validation
Date: Tue, 13 Feb 2007 10:29:08 +0100 (CET)	[thread overview]
Message-ID: <50157.85.47.20.193.1171358948.squirrel@picard.linux.it> (raw)
In-Reply-To: <1171357148.6028.5.camel@localhost.localdomain>

On Tue, February 13, 2007 9:59 am, Richard Purdie said:
> On Tue, 2007-02-13 at 09:47 +0100, Mattia Dongili wrote:
>> On Tue, February 13, 2007 5:55 am, Len Brown said:
>> > On Monday 12 February 2007 16:01, Mattia Dongili wrote:
>> >> allows consistency between the sony-laptop
>> >> specific 'brightness_default' and the backlight subsystem 0-based
>> >> 'brightness'.
>> >
>> > Why do we need to have "sony-laptop specific 'brightness_default'" --
>> > is that a shortcoming of the backlight subsystem?
>>
>> It depends on how do you see it :)
>> brightness_default is the value that brightness will have at the next
>> (and
>> later) reboot and it's currently handled as a platform_device attribute.
>> It would be nice anyway if one such attribute could be added to the
>> backlight subsystem (I'll provide patches - added rpurdie to the Cc
>> list)
>> in order to standardize its behavior/interface.
>
> The backlight class doesn't really have any reason to know anything
> about defaults. The current behaviour is that if you want it at a
> certain 'default' brightness, you set it to this after you register the
> device. Some devices don't want the brightness changed and want to use
> whatever it was set to originally. In the case of some other drivers,
> you can't read the brightness value.

well this is actually hardware driven, the brightness_default in
sony-laptop only exposes a DSDT method to set this value.
So it's actually one more feature, not a software trick :)
I admit the attribute could be better named 'poweron_brightness'.

> With any patches, please keep in mind the changes in
> http://git.o-hand.com/?p=linux-rpurdie-backlight;a=shortlog;h=for-mm as
> I've separated out the ops functions from the actual device specific
> data.

Yep, thanks.
-- 
mattia
:wq!



  reply	other threads:[~2007-02-13  9:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-12 21:01 [PATCH] sony-laptop: allow complex per-value input/output validation Mattia Dongili
2007-02-13  4:55 ` Len Brown
2007-02-13  8:47   ` Mattia Dongili
2007-02-13  8:59     ` Richard Purdie
2007-02-13  9:29       ` Mattia Dongili [this message]
2007-02-13 12:16         ` Henrique de Moraes Holschuh
2007-02-13 15:49           ` Mattia Dongili
2007-02-14  1:17             ` Henrique de Moraes Holschuh

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=50157.85.47.20.193.1171358948.squirrel@picard.linux.it \
    --to=malattia@linux.it \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    /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