lkml.org 
[lkml]   [2006]   [Jul]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [ltp] Re: Generic battery interface
    On 7/31/06, Michael Olbrich <michael.olbrich@gmx.net> wrote:
    > On Sun, Jul 30, 2006 at 09:37:23PM +0300, Shem Multinymous wrote:
    > >
    > > Comments?
    >
    > Hmmm, that looks good for most cases. But how would you handle
    > starting/stoping laoding/draining the battery?
    > That usually results in values jumping from/to 0. A gui would want to
    > show such a change immediately while otherwise keeping a slow update
    > rate. Maybe some kind of threshhold parameter? "send an input-ready
    > immediatelly if the value changes by more than x%".

    Changes by more than x% compared to what?

    The value at the time of the ioctl()? This might completely miss a
    change that happened between the previous read() and the ioctl().

    The value at the time of the last read()? Then the kernel
    driver+infrastructure will need to keep track of the latest readout
    done by each app. That's pretty heavy.

    So what semantics make sense?

    Shem
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-07-31 17:21    [W:0.020 / U:32.276 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site