From: Pavel Machek <pavel@suse.cz>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: dtor_core@ameritech.net, Matthew Garrett <mjg59@srcf.ucam.org>,
Dominik Brodowski <linux@dominikbrodowski.net>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
vojtech@suse.cz
Subject: Re: [RFC] [PATCH] Make ACPI button driver an input device
Date: Mon, 24 Apr 2006 23:29:26 +0200 [thread overview]
Message-ID: <20060424212926.GO3386@elf.ucw.cz> (raw)
In-Reply-To: <1145912371.7155.220.camel@localhost.localdomain>
Hi!
> >(Another interesting question is: is AC status 0/1 or is it number of
> > milivolts?)
>
> I'd say millivolts except for the problem of what you do on systems that
> don't support voltage readings. Use a very high value I guess. For a lot
> of devices millivolts also means in kernel conversion tables. Do such
> things belong in kernel or user space?
We should probably return 0/-1 in such case (-1 = on, but voltage unknown).
> > > to detect when its plugged in) ;). The battery class would export some
> > > information but not all of it and I don't know where the leftover
> > > information should go. If I knew that, I'd write the class.
> >
> > Leftover information?
>
> Where to put AC status and AC voltage readings amongst other things.
> Another sysfs class? Also, how do you control suspend/resume
> notifications to userspace if not using APM/ACPI?
I'd say that AC status should go to separate class, I'm
afraid. Potentially AC has more parameters (like current, current
frequency, difference between phase of current and voltage, ...?) and
UPSs even measure that.
Does userspace need to be notified of suspend/resume? [I keep
insisting that they do not, and I'm probably wrong, but... :-)]
Pavel
--
Thanks for all the (sleeping) penguins.
next prev parent reply other threads:[~2006-04-24 21:30 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 19:53 [RFC] [PATCH] Make ACPI button driver an input device Matthew Garrett
2006-04-19 20:04 ` Dominik Brodowski
2006-04-19 20:24 ` Matthew Garrett
2006-04-24 14:45 ` Dmitry Torokhov
2006-04-24 15:10 ` Matthew Garrett
2006-04-24 16:05 ` Richard Purdie
2006-04-24 16:26 ` Dmitry Torokhov
2006-04-24 17:05 ` Richard Purdie
2006-04-24 20:34 ` Pavel Machek
2006-04-24 20:59 ` Richard Purdie
2006-04-24 21:29 ` Pavel Machek [this message]
2006-04-24 20:20 ` Pavel Machek
2006-04-20 21:56 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-04-20 5:45 Yu, Luming
2006-04-20 7:37 ` Matthew Garrett
2006-04-20 15:35 ` Alexey Starikovskiy
2006-04-20 15:38 ` Matthew Garrett
2006-04-20 15:57 ` Alexey Starikovskiy
2006-04-20 16:11 ` Xavier Bestel
2006-04-20 16:33 ` Alexey Starikovskiy
2006-04-20 16:44 ` Matthew Garrett
2006-04-20 16:47 ` Alexey Starikovskiy
2006-04-20 16:55 ` Matthew Garrett
2006-04-20 17:06 ` Alexey Starikovskiy
2006-04-20 22:03 ` Pavel Machek
2006-04-20 19:30 ` Dmitry Torokhov
2006-04-20 20:07 ` Xavier Bestel
2006-04-21 8:52 ` Alexey Starikovskiy
2006-04-20 22:04 ` Pavel Machek
2006-04-21 12:56 ` Dmitry Torokhov
2006-04-20 22:01 ` Pavel Machek
2006-04-22 20:59 ` David Weinehall
2006-04-20 16:15 ` Matthew Garrett
2006-04-20 16:28 ` Alexey Starikovskiy
2006-04-20 16:32 ` Matthew Garrett
2006-04-20 16:35 ` Alexey Starikovskiy
2006-04-20 16:45 ` Matthew Garrett
2006-04-20 22:10 ` Pavel Machek
2006-04-20 16:58 ` Martin Mares
2006-04-20 17:08 ` Alexey Starikovskiy
2006-04-20 22:07 ` Pavel Machek
2006-04-24 6:54 ` Alexey Starikovskiy
2006-04-24 8:31 ` Pavel Machek
2006-04-24 14:39 ` Alexey Starikovskiy
2006-04-24 15:09 ` Matthew Garrett
2006-04-28 17:43 ` Stefan Seyfried
2006-04-21 7:27 Yu, Luming
2006-04-20 21:55 ` Pavel Machek
2006-04-24 14:51 ` Dmitry Torokhov
2006-04-21 11:37 ` Martin Mares
2006-04-21 12:21 ` Dmitry Torokhov
2006-04-25 14:17 Yu, Luming
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=20060424212926.GO3386@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=dtor_core@ameritech.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mjg59@srcf.ucam.org \
--cc=rpurdie@rpsys.net \
--cc=vojtech@suse.cz \
/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