Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1945965AbWBOPEs (ORCPT ); Wed, 15 Feb 2006 10:04:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1945964AbWBOPEs (ORCPT ); Wed, 15 Feb 2006 10:04:48 -0500 Received: from mail.suse.de ([195.135.220.2]:57748 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S1945957AbWBOPEr (ORCPT ); Wed, 15 Feb 2006 10:04:47 -0500 Message-ID: <43F3430D.1010002@suse.de> Date: Wed, 15 Feb 2006 16:04:45 +0100 From: Thomas Renninger User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050715) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthew Garrett Cc: "Rafael J. Wysocki" , Pavel Machek , Stefan Seyfried , linux-pm@lists.osdl.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH, RFC] [1/3] Generic in-kernel AC status References: <20060208125753.GA25562@srcf.ucam.org> <20060210121913.GA4974@elf.ucw.cz> <43F216FE.7050101@suse.de> <200602142117.31232.rjw@sisk.pl> <43F3206B.6090902@suse.de> <20060215124729.GA10968@srcf.ucam.org> In-Reply-To: <20060215124729.GA10968@srcf.ucam.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1576 Lines: 38 Matthew Garrett wrote: > On Wed, Feb 15, 2006 at 01:36:59PM +0100, Thomas Renninger wrote: > >> Maybe I oversaw an issue, but I really don't see a reason for connecting >> the brightness to ac in kernel space. > > The backlight class maintainer specified that /sys/../brightness should Who's that? Is there more info/spec available? > return the *current* brightness. In some cases that's impossible without > knowing the ac status. > Ok. The ac/battery status is used to guess the current brightness? Please do not set suggested values automatically, IMO this is not a nice feature... I am really looking forward to see a general /sys/../brightness. Thanks a lot for working on this! Just an idea for later: Beside min/max there probably should be a /sys/../brightness_bat and /sys/../brightness_ac. - If ac/battery brightness will not be set by kernel, userspace can write the right value to /sys/../brightness and the above two can be readonly. - If ac/battery brightness will be set by kernel the above two should even be writeable so that people can avoid the need of pressing "brightness up" button without hacking the kernel. I vote for letting userspace doing the stuff..., e.g. changing brightness behind the back of some userspace tool will result in userspace tools starting to poll. Comments? Thomas - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/