mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Giuseppe Bilotta" <bilotta78@hotpop.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Polling for battery stauts and lost keypresses (was: Touchpad problems with latest kernels)
Date: Mon, 14 Aug 2006 16:17:01 -0400	[thread overview]
Message-ID: <d120d5000608141317p50540cd5x5e8ec409dc9343ef@mail.gmail.com> (raw)
In-Reply-To: <1q38ghnxvrliv$.zzgutgu0exkm$.dlg@40tude.net>

On 8/14/06, Giuseppe Bilotta <bilotta78@hotpop.com> wrote:
> On Mon, 14 Aug 2006 12:06:06 -0400, Dmitry Torokhov wrote:
>
> > On many laptops (including mine) polling battery takes a loooong time
> > and is done in SMI mode in BIOS causing lost keypresses, jerky mouse
> > etc. It is pretty common problem. I think I have my ACPI client
> > refreshing every 3 minutes.
>
> BTW, polling battery status takes a lot on a Dell Inspiron 8200 too,
> and all keypresses and mouse movements (and I think even network
> IRQs?) are totally *dead* while polling.
>
> However, The Other OS(tm) *seems* to do it right enough to have no
> noticeable keypress losses, even when updating the battery status. Is
> it using different system calls, or what?
>

I am not sure, but there are many things that may affect it:

1. Battry attributes are divided into 2 groups - static (i think they
go into /proc/acpi/battery/<name>/info and dynamic
(/proc/acpi/batetry/state). Static attributes take really long time to
pull and they do not change so it may wery well be they are polled one
at startup. Dynamic attributes are cheaper to poll and even then OS
may cache access or limit rate.

2. Quite often there are OEM drivers that are tweaked to a specific
hardware and involve hardware-specific hacks.

-- 
Dmitry

  reply	other threads:[~2006-08-14 20:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 13:58 Touchpad problems with latest kernels Luke Sharkey
2006-08-14 14:36 ` Dmitry Torokhov
2006-08-14 15:18   ` Dave Jones
2006-08-14 14:38 ` Gene Heskett
2006-08-14 15:06   ` Ian Stirling
2006-08-14 15:19     ` Gene Heskett
2006-08-14 15:41       ` Ian Stirling
2006-08-14 15:13   ` Dmitry Torokhov
2006-08-14 15:25     ` Mattia Dongili
2006-08-14 15:34     ` Gene Heskett
2006-08-14 15:53       ` Dmitry Torokhov
2006-08-14 16:33         ` Gene Heskett
2006-08-14 16:59           ` Dmitry Torokhov
2006-08-14 15:20   ` Andreas Mohr
2006-08-14 15:41     ` Dmitry Torokhov
2006-08-14 15:54       ` Andreas Mohr
2006-08-14 16:06         ` Dmitry Torokhov
2006-08-14 20:06           ` Polling for battery stauts and lost keypresses (was: Touchpad problems with latest kernels) Giuseppe Bilotta
2006-08-14 20:17             ` Dmitry Torokhov [this message]
2006-08-16  7:31               ` Polling for battery stauts and lost keypresses Giuseppe Bilotta
2006-08-19 15:50                 ` Dmitry Torokhov
2006-08-19 16:02                   ` Arjan van de Ven
2006-08-21 11:56                     ` Giuseppe Bilotta
2006-08-21 12:34                     ` Dmitry Torokhov
2006-08-21 12:52                       ` Arjan van de Ven
2006-08-24 20:31                 ` Pavel Machek
2006-08-14 19:30       ` Touchpad problems with latest kernels Dmitry Torokhov

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=d120d5000608141317p50540cd5x5e8ec409dc9343ef@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=bilotta78@hotpop.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®