From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Daniel Nicoletti <dantti12@gmail.com>
Cc: Anton Vorontsov <cbouatmailru@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Richard Hughes <hughsient@gmail.com>,
linux-input@vger.kernel.org, Jiri Kosina <jkosina@suse.cz>,
vojtech@ucw.cz, Przemo Firszt <przemo@firszt.eu>,
Richard Hughes <richard@hughsie.com>
Subject: Re: [GIT PULL] power_supply: add power supply scope
Date: Fri, 09 Dec 2011 12:36:23 -0800 [thread overview]
Message-ID: <4EE27147.4030001@goop.org> (raw)
In-Reply-To: <CACo8zOfek64X8ouGgUz6JSiQDz62OFkUJyQDSj=YdMsq8hjwoQ@mail.gmail.com>
On 12/09/2011 12:00 PM, Daniel Nicoletti wrote:
>>>> diff --git a/drivers/power/power_supply_sysfs.c b/drivers/power/power_supply_sysfs.c
>>>> index e15d4c9..21178eb 100644
>>>> --- a/drivers/power/power_supply_sysfs.c
>>>> +++ b/drivers/power/power_supply_sysfs.c
>>>> @@ -63,6 +63,9 @@ static ssize_t power_supply_show_property(struct device *dev,
>>>> static char *capacity_level_text[] = {
>>>> "Unknown", "Critical", "Low", "Normal", "High", "Full"
>>>> };
>>>> + static char *scope_text[] = {
>>>> + "Unknown", "System", "Device"
>>>> + };
>>>> ssize_t ret = 0;
>>>> struct power_supply *psy = dev_get_drvdata(dev);
>>>> const ptrdiff_t off = attr - power_supply_attrs;
>>>> @@ -95,6 +98,8 @@ static ssize_t power_supply_show_property(struct device *dev,
>>>> return sprintf(buf, "%s\n", capacity_level_text[value.intval]);
>>>> else if (off == POWER_SUPPLY_PROP_TYPE)
>>>> return sprintf(buf, "%s\n", type_text[value.intval]);
>>>> + else if (off == POWER_SUPPLY_PROP_SCOPE)
>>>> + return sprintf(buf, "%s\n", scope_text[value.intval]);
>>> Should we really handle the PROP_SCOPE as a dynamic property?
>>> Maybe do it similar to PROP_TYPE, so that drivers will only need to
>>> specity the scope during registration, and not bother w/ handling
>>> it in theirs get_property() callbacks?
>> I don't really know. I guess its possible in theory that a device could
>> change scope on the fly if its power was re-routed. But then, the type
>> can change too (if, for example, a UPS switched between AC and battery
>> power, or a HID device switching between corded USB power or cordless
>> battery power), so I'm not really sure what the rationale is either
>> way. (I guess you model power supplies switching type as having
>> multiple power supplies which turn themselves on and offline?)
> But isn't the scope about powering or not the system? If so even if
> the device is now using AC it will not be powering the computer.
>
Sure. I was just commenting on the similarity between scope and type
with respect to whether they're immutable properties of a power supply
or things that can change over time.
J
prev parent reply other threads:[~2011-12-09 20:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EC75224.7070207@goop.org>
[not found] ` <alpine.LNX.2.00.1111191212140.15187@pobox.suse.cz>
[not found] ` <4EC820F8.4070900@goop.org>
[not found] ` <alpine.LNX.2.00.1111201110480.15187@pobox.suse.cz>
[not found] ` <4ECA7E7D.80207@goop.org>
[not found] ` <alpine.LNX.2.00.1111220028130.28728@pobox.suse.cz>
[not found] ` <4ECAE019.4000409@goop.org>
[not found] ` <alpine.LNX.2.00.1111220049470.28728@pobox.suse.cz>
[not found] ` <4ECCB38A.8000503@goop.org>
[not found] ` <alpine.LNX.2.00.1111281111510.15446@pobox.suse.cz>
[not found] ` <CACo8zOd45i3EnCVMyJoDPP4bx2AnD9mEjDiC=bJKvmX=TWfXGg@mail.gmail.com>
[not found] ` <4ED90E6D.8090402@goop.org>
[not found] ` <CACo8zOcvKwr0wDkytvJfqyx4kV0ceYyCt+qnDqiSgxNywpzeHg@mail.gmail.com>
[not found] ` <4ED9BDF8.3010600@goop.org>
[not found] ` <CAD2FfiE-rg-1bMmVpYzBhnQcBMKKKO4WPnu0bvx+pvdFnpARrQ@mail.gmail.com>
[not found] ` <4EDE4C7A.1010802@goop.org>
[not found] ` <CAD2FfiHWuEmVTa54YqfJDk5zHpSQuM_nwPT=mR6NoWpajpydpg@mail.gmail.com>
[not found] ` <4EDFA192.7000602@goop.org>
[not found] ` <CAD2FfiF+fVoLPWpPyGGKdnoGhx1f=Loh2Ju-vdU58Y=2kf6C3g@mail.gmail.com>
2011-12-08 1:41 ` [GIT PULL] power_supply: add power supply scope Jeremy Fitzhardinge
2011-12-08 10:02 ` Anton Vorontsov
2011-12-08 10:05 ` Richard Hughes
2011-12-08 10:42 ` Anton Vorontsov
2011-12-08 10:41 ` Anton Vorontsov
2011-12-08 16:53 ` Jeremy Fitzhardinge
2011-12-08 23:36 ` Anton Vorontsov
2011-12-09 8:18 ` Jeremy Fitzhardinge
2011-12-09 9:59 ` Anton Vorontsov
2011-12-09 16:58 ` Jeremy Fitzhardinge
2011-12-09 10:17 ` Anton Vorontsov
2011-12-09 17:49 ` Jeremy Fitzhardinge
2011-12-09 20:00 ` Daniel Nicoletti
2011-12-09 20:36 ` Jeremy Fitzhardinge [this message]
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=4EE27147.4030001@goop.org \
--to=jeremy@goop.org \
--cc=cbouatmailru@gmail.com \
--cc=dantti12@gmail.com \
--cc=dwmw2@infradead.org \
--cc=hughsient@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=przemo@firszt.eu \
--cc=richard@hughsie.com \
--cc=vojtech@ucw.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