[lkml]   [2007]   [Apr]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 3/7] [RFC] Battery monitoring class
    Hi Anton,

    A few comments on the ever-contentious choice of battery attributes:

    On 4/11/07, Anton Vorontsov <> wrote:
    > + * All voltages, currents, capacities and temperatures in mV, mA, mAh and
    > + * tenths of a degree unless otherwise stated. It's driver's job to convert
    > + * its raw values to which this class operates. If for some reason driver
    > + * can't afford this requirement, then it have to create its own attributes,
    > + * plus additional "XYZ_units" for each of them.
    > + */

    Many (most, I believe) laptop batteries report capacity in mWh
    (energy), not mAh (charge). You can't convert between the two without
    a detailed, up-to-date physical model of the battery. This is too
    common to relegate to a non-standardized "XYZ_units" extension.

    > +BATTERY_INT_ATTR(min_voltage);
    > +BATTERY_INT_ATTR(min_current);
    > +BATTERY_INT_ATTR(min_capacity);
    > +BATTERY_INT_ATTR(max_voltage);
    > +BATTERY_INT_ATTR(max_current);
    > +BATTERY_INT_ATTR(max_capacity);
    > +BATTERY_INT_ATTR(temp);
    > +BATTERY_INT_ATTR(voltage);
    > +BATTERY_INT_ATTR(current);
    > +BATTERY_INT_ATTR(capacity);

    I suggest adding "remaining operating time" and "remaining charging
    time". You can try deducing these from the above attributes, but in
    practice this gives very inaccurate predictions. On laptops (e.g.,
    ThinkPad) the BIOS or EC often provides much better estimates, using a
    more accurate physical model.

    I also see you omitted a host of other common attributes, like design
    capacity, cycle count, model string, and temperatures. There was an
    extensive LKML discussion of the choice and naming of attributes, in
    the context of David Woodhouse's patch; there are futher observations
    there. Also, here's the list of attributes in my tp_smapi ThinkPad

    Does "max capaxity" correspond to what's usually denoted "last full capacity".

    I understand you allow adding custom attributes, but they're of
    limited use if generic userspace tools don't know their name and
    semantics. It's important to standardize all reasonably common

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-04-12 17:03    [W:0.021 / U:19.136 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site