public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Reichel <sre@kernel.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: "kernel list" <linux-kernel@vger.kernel.org>,
	"Greg KH" <greg@kroah.com>,
	dbaryshkov@gmail.com, dwmw2@infradead.org,
	linux-pm@vger.kernel.org, "Pali Rohár" <pali.rohar@gmail.com>
Subject: Re: Mess in the /sysfs: class/power_supply/bq2415x
Date: Wed, 25 Feb 2015 22:44:42 +0100	[thread overview]
Message-ID: <20150225214441.GK13695@earth> (raw)
In-Reply-To: <20150131213919.GA16133@amd>

[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]

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?

> 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
> 
> (and this is in uA)
> 
> root@n900:/sys/class/power_supply# cat bq27200-0/current_now
> 12138
> 
> (I believe uA is right, so it is bq24150a that should be fixed....?)

> 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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-02-25 21:44 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 ` Sebastian Reichel [this message]
2015-02-25 22:01   ` Mess in the /sysfs: class/power_supply/bq2415x Pali Rohár

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=20150225214441.GK13695@earth \
    --to=sre@kernel.org \
    --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=pali.rohar@gmail.com \
    --cc=pavel@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