From: "Pali Rohár" <pali.rohar@gmail.com>
To: Sebastian Reichel <sre@kernel.org>
Cc: Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>,
dbaryshkov@gmail.com, dwmw2@infradead.org,
linux-pm@vger.kernel.org
Subject: Re: Mess in the /sysfs: class/power_supply/bq2415x
Date: Wed, 25 Feb 2015 23:01:41 +0100 [thread overview]
Message-ID: <201502252301.41633@pali> (raw)
In-Reply-To: <20150225214441.GK13695@earth>
[-- Attachment #1: Type: Text/Plain, Size: 2919 bytes --]
On Wednesday 25 February 2015 22:44:42 Sebastian Reichel wrote:
> Hi Pavel,
>
> On Sat, Jan 31, 2015 at 10:39:19PM +0100, Pavel Machek wrote:
> > So we have multiple values in one sysfs file:
> >
> > root@n900:/sys/class/power_supply# cat bq24150a-0/registers
> > 0x00=0x50
> > 0x01=0xc8
> > 0x02=0x8e
> > 0x03=0x4b
> > 0x04=0x99
> >
> > (should this go to debugfs somewhere?)
>
> I guess this should be dropped in favour of debugfs. A
> standardized debugfs node will be exported automatically if
> the driver is converted to regmap.
>
> > Unobvious and undocumented entries:
> >
> > root@n900:/sys/class/power_supply# cat
> > bq24150a-0/boost_status 0
> > pavel@duo:/data/l/linux-n900$ grep -ri boost_status
> > Documentation/ pavel@duo:/data/l/linux-n900$ grep -ri
> > termination_current Documentation/
> > pavel@duo:/data/l/linux-n900$ grep -ri current_now
> > Documentation/ pavel@duo:/data/l/linux-n900$ grep -ri
> > time_to_empty_avg Documentation/
> > pavel@duo:/data/l/linux-n900$
>
> Anton seems to have missed making Pali to write a
> Documentation patch. Pali: Can you do so, please?
>
Some of properties are standard power_supply properties and those
are documented in Documentation/power/power_supply_class.txt
bq2415x specific are documented only in bq2415x_charger.c source
code. So probably we should move documentation into
Documentation/power/bq2415x_charer.txt
But I think there are other stuff with higher priority for N900
as moving comments/documentation...
> > And different units in different parts of tree:
> >
> > (these are mA)
> >
> > root@n900:/sys/class/power_supply# cat
> > bq24150a-0/current_limit 1800
> > root@n900:/sys/class/power_supply# cat
> > bq24150a-0/termination_current 100
> >
Those are non standard power-supply properties and so unit is not
defined.
> > (and this is in uA)
> >
> > root@n900:/sys/class/power_supply# cat bq27200-0/current_now
> > 12138
> >
This is power supply.
> > (I believe uA is right, so it is bq24150a that should be
> > fixed....?)
> >
Units
~~~~~
Quoting include/linux/power_supply.h:
All voltages, currents, charges, energies, time and
temperatures in µV,
µA, µAh, µWh, seconds and tenths of degree Celsius unless
otherwise
stated. It's driver's job to convert its raw values to units in
which
this class operates.
> > Ok, of course questions are: do we need to do something with
> > it? If so, what?
>
> For consistency it should be uA, but I guess this would
> introduce a regression for Maemo people. Pali?
>
> -- Sebastian
It looks like that in Maemo & CSSU we are using only:
/sys/class/power_supply/bq24150a-0/mode
/sys/class/power_supply/bq24150a-0/stat_pin_enable
But it does not mean that some other people do not use other
bq2415x sysfs nodes.
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2015-02-25 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 21:39 Mess in the /sysfs: class/power_supply Pavel Machek
2015-02-25 21:44 ` Mess in the /sysfs: class/power_supply/bq2415x Sebastian Reichel
2015-02-25 22:01 ` Pali Rohár [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=201502252301.41633@pali \
--to=pali.rohar@gmail.com \
--cc=dbaryshkov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sre@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).