On Thursday 06 March 2008, Liam Girdwood wrote:Versus Documentation/hwmon/sysfs-interface which uses millivolts and milliamperes respectively. Why not adopt the same convention? (This applies to many attributes, not just these two.) Also, I'm kind of curious what you've thought about power budgeting. Example, a power supply ("regulator") may be able to supply a voltage within a given range, but only up to a maximum of 200 mA worth. The model visible through these sysfs attributes seems to be an either/or thing ... either regulating voltage, or current, but not addressing the corresponding constraints on the other one. How about just "undefined" for all those min/max values? Ditto re "milli" vs "micro". Also, "requested" seems a bit opaque. As a sum, maybe "total_mi{lli,cro}amps" would be more explanatory. - Dave --
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Linus Torvalds | Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series.. |
| Paul Jackson | Re: cpuset-remove-sched-domain-hooks-from-cpusets |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Linus Torvalds | Re: [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [klibc] [patch] import socket defines |
