public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Pavel Machek <pavel@suse.cz>
Cc: Stefan Seyfried <seife@suse.de>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	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
Date: Tue, 14 Feb 2006 18:44:30 +0100	[thread overview]
Message-ID: <43F216FE.7050101@suse.de> (raw)
In-Reply-To: <20060210121913.GA4974@elf.ucw.cz>

Pavel Machek wrote:
> On Pá 10-02-06 09:06:43, Stefan Seyfried wrote:
>> On Wed, Feb 08, 2006 at 12:57:53PM +0000, Matthew Garrett wrote:
>>> The included patch adds support for power management methods to register 
>>> callbacks in order to allow drivers to check if the system is on AC or 
>>> not. Following patches add support to ACPI and APM. Feedback welcome.
>> Ok. Maybe i am not seeing the point. But why do we need this in the kernel?
>> Can't we handles this easily in userspace?
> 
> Some kernel parts need to now: for example powernow-k8: some
> frequencies are not allowed when you are running off battery. [Just
> now it is solved by not allowing those frequencies at all unless ACPI
> is available; quite an ugly solution.]
> 
Allowed CPUfreqs are exported via _PPC.
This is why a lot hardware sends an ac_adapter and a processor event
when (un)plugging ac adapter.
Limiting cpufreq already works nice that way.

AMD64 laptops are booting with lower freqs per default until they are
pushed up, so there shouldn't be anything critical?

For the brightness part, I don't see any "laptop is going to explode"
issue.
I always hated the brightness going down when I unplugged ac on M$
and had to push ten times the brightness "up button" before I could
go on working...

Shouldn't it be:

               
ac Event   ---> userspace <--- user config
                   |
                   | 
brightness <-------|

Whether the ac brightness will be set when going to ac, or
whatever brightness, should be configurable in userspace IMO.
This is a one liner in the acpid config?

However, I also like the general /sys/../brightness file very much!


     Thomas

  parent reply	other threads:[~2006-02-14 17:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08 12:57 [PATCH, RFC] [1/3] Generic in-kernel AC status Matthew Garrett
2006-02-08 13:03 ` [PATCH, RFC] [2/3] ACPI support for generic " Matthew Garrett
2006-02-08 13:04 ` [PATCH, RFC] [1/3] Generic " Matthew Garrett
2006-02-08 13:05   ` [PATCH, RFC] [3/3] APM support for generic " Matthew Garrett
2006-02-08 16:58   ` [linux-pm] Re: [PATCH, RFC] [1/3] Generic " Greg KH
2006-02-08 17:08     ` Matthew Garrett
2006-02-08 17:16       ` Greg KH
2006-02-08 17:49         ` Matthew Garrett
2006-02-09  5:46           ` Greg KH
2006-02-09  8:53       ` Gabor Gombas
2006-02-10 12:21         ` Pavel Machek
2006-02-10 13:13           ` Gabor Gombas
2006-02-10 13:19             ` Matthew Garrett
2006-02-10 13:54             ` Pavel Machek
2006-02-10 13:56               ` Gabor Gombas
2006-02-08 22:25   ` Philipp Matthias Hahn
2006-02-10 12:21     ` Pavel Machek
2006-02-10  8:06 ` Stefan Seyfried
2006-02-10 12:19   ` Pavel Machek
2006-02-10 12:32     ` Stefan Seyfried
2006-02-10 13:46       ` Pavel Machek
2006-02-12 10:17         ` Jan Engelhardt
2006-02-12 11:27           ` Kyle Moffett
2006-02-14 17:44     ` Thomas Renninger [this message]
2006-02-14 20:17       ` Rafael J. Wysocki
2006-02-15 12:36         ` Thomas Renninger
2006-02-15 12:47           ` Matthew Garrett
2006-02-15 15:04             ` Thomas Renninger
2006-02-16 22:44           ` Pavel Machek
2006-02-16 22:39         ` Pavel Machek

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=43F216FE.7050101@suse.de \
    --to=trenn@suse.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=pavel@suse.cz \
    --cc=seife@suse.de \
    /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