From: Alexander Clouter <alex@digriz.org.uk>
To: linux-kernel@vger.kernel.org
Cc: linux-embedded@vger.kernel.org
Subject: Re: [POWER] battery calibration parameters from sysfs
Date: Fri, 4 Dec 2009 11:34:25 +0000 [thread overview]
Message-ID: <1n8nu6-4va.ln1@chipmunk.wormnet.eu> (raw)
In-Reply-To: A6D19A13FE030A409EC4362C172E091F0E0495F6@eseldmw101.eemea.ericsson.se
Linus Walleij <linus.walleij@stericsson.com> wrote:
>
> [snipped]
>
> Is probably not very elegant. (Or is it?) Would it be permissible to
> pass in a table like:
>
> cat >/sys/.../v_vs_cap <<EOF
> x0,y0
> x1,y1
> x2,y2
> EOF
>
> And have the kernel parse x,y pairs up to EOF?
>
> Or would it be preferable to do this thing by creating some
> misc device node like /dev/battery0 and a custom ioctl()?
>
> Or is there some other way I haven't thought of?
>
Although I'm a 'nobody' I would probably go for:
----
echo x0,y0:x1,y1:....
----
Pairs are seperated by ':' whilst values with ','. I guess you could
just use comma's all the way but I personally say that reduces
readability...also means that maybe one day you want to pass only one or
three values...the format could still work.
Easy to parse, a one liner, no fixed length, fits in with the existing
use, etc etc.
Cheers
--
Alexander Clouter
.sigmonster says: You'll be sorry...
next prev parent reply other threads:[~2009-12-04 11:34 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 10:42 [POWER] battery calibration parameters from sysfs Linus Walleij
2009-12-04 10:42 ` Linus Walleij
2009-12-04 10:49 ` Mark Brown
2009-12-04 14:17 ` Mark Brown
2009-12-05 13:08 ` Linus Walleij
2009-12-05 13:08 ` Linus Walleij
2009-12-05 17:45 ` Mark Brown
2009-12-07 11:48 ` Mark Brown
2009-12-07 14:07 ` Linus Walleij
2009-12-07 14:07 ` Linus Walleij
2009-12-07 16:56 ` Mark Brown
2009-12-08 5:27 ` Brian Swetland
2009-12-08 10:28 ` Mark Brown
2009-12-13 13:24 ` Pavel Machek
2009-12-13 13:24 ` Pavel Machek
2009-12-13 13:24 ` Pavel Machek
2009-12-14 12:12 ` Mark Brown
2009-12-14 12:12 ` Mark Brown
2009-12-14 12:12 ` Mark Brown
2009-12-14 21:22 ` Pavel Machek
2009-12-14 21:22 ` Pavel Machek
2009-12-14 21:22 ` Pavel Machek
2009-12-14 23:43 ` Aras Vaichas
2009-12-14 23:43 ` Aras Vaichas
2009-12-14 23:43 ` Aras Vaichas
2009-12-15 3:02 ` Bill Gatliff
2009-12-15 3:02 ` Bill Gatliff
2009-12-15 3:02 ` Bill Gatliff
2009-12-15 22:58 ` Aras Vaichas
2009-12-15 22:58 ` Aras Vaichas
2009-12-15 22:58 ` Aras Vaichas
2009-12-15 23:32 ` Stanislav Brabec
2009-12-15 23:32 ` Stanislav Brabec
2009-12-15 23:32 ` Stanislav Brabec
2009-12-16 9:40 ` Andy Green
2009-12-16 9:40 ` Andy Green
2009-12-16 9:40 ` Andy Green
[not found] ` <4B28AAFC.5010108-/Zus8d0mwwtBDgjK7y7TUQ@public.gmane.org>
2009-12-18 8:48 ` Pavel Machek
2009-12-18 8:48 ` Pavel Machek
2009-12-18 8:48 ` Pavel Machek
[not found] ` <20091214121247.GB22388-HF5t3jzXg/6ND3a5+9QAFujbO/Zr0HzV@public.gmane.org>
2009-12-16 22:53 ` Pavel Machek
2009-12-16 22:53 ` Pavel Machek
2009-12-16 22:53 ` Pavel Machek
2009-12-13 13:19 ` Pavel Machek
2009-12-14 11:50 ` Mark Brown
2009-12-14 11:58 ` Pavel Machek
2009-12-14 12:14 ` Mark Brown
2009-12-04 11:34 ` Alexander Clouter [this message]
2009-12-06 20:52 ` Greg KH
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=1n8nu6-4va.ln1@chipmunk.wormnet.eu \
--to=alex@digriz.org.uk \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.