[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <41840b750610281112q7790ecao774b3d1b375aca9b@mail.gmail.com>
Date: Sat, 28 Oct 2006 20:12:41 +0200
From: "Shem Multinymous" <multinymous@...il.com>
To: "David Zeuthen" <davidz@...hat.com>
Cc: "Richard Hughes" <hughsient@...il.com>,
"David Woodhouse" <dwmw2@...radead.org>,
"Dan Williams" <dcbw@...hat.com>, linux-kernel@...r.kernel.org,
devel@...top.org, sfr@...b.auug.org.au, len.brown@...el.com,
greg@...ah.com, benh@...nel.crashing.org,
"linux-thinkpad mailing list" <linux-thinkpad@...ux-thinkpad.org>,
"Pavel Machek" <pavel@...e.cz>, "Jean Delvare" <khali@...ux-fr.org>
Subject: Re: [PATCH v2] Re: Battery class driver.
Hi David,
On 10/28/06, David Zeuthen <davidz@...hat.com> wrote:
> What about just prepending the unit to the 'threshold' file? Then user
> space can expect the contents of said file to be of the form "%d %s". I
> don't think that violates the "only one value per file" sysfs mantra.
The tp_smapi battery driver did just this ("16495 mW"). But I dropped
it in a recent version when Pavel pointed out the rest of sysfs, hwmon
included, uses undecorated integers.
Consistency aside, it seems reasonable and convenient. You have to
decree that writes to the attributes (where relevant) don't include
the units, of course, so no one will expect the kernel to parse that.
There's an issue here if a drunk driver decides to specify (say)
capacity_remaining in mWh and capacity_last_full in mAa, which will
confuse anyone comparing those attributest. So don't do that.
Jean, what's your opinion on letting hwmon-ish attributes specify
units as "%d %s" where these are hardware-dependent?
Shem
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists