public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: Fedor Karpelevitch <fedor-ugkMPi23kyXAHCkTjeiZhQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: double power button events on presario 900 - apparently a timing issue?
Date: Thu, 25 Sep 2003 09:37:14 -0700 (PDT)	[thread overview]
Message-ID: <20030925093512.H59477@root.org> (raw)
In-Reply-To: <200309250859.46970.fedor-ugkMPi23kyXAHCkTjeiZhQ@public.gmane.org>

On Thu, 25 Sep 2003, Fedor Karpelevitch wrote:
> Fedor Karpelevitch wrote:
> > Nate Lawson wrote:
> > > On Wed, 24 Sep 2003, Fedor Karpelevitch wrote:
> > > > as I previously mentioned I am seeing an annoying problem on my
> > > > presario 900 - when power button (works as FF here) is pressed
> > > > it generates two events every time. I was experimentin with
> > > > debugging output and noticed an interesting thing - if I do
> > > > echo 0xffffffff > /proc/acpi/debug_level
> > > > to get verbose debug output the problem goes away - I only get
> > > > one event every time button is pressed. Looks like the problem
> > > > is caused by some kind timing issue which goes away when
> > > > debugging slows it down. Does this sound like a reasonable
> > > > guess? Would anyone suggest how this can be debugged further?
> > >
> > > It means you need to debounce the event.
> >
> > do you mean debouncing on the receiving end? or would that be some
> > way to avoid that in the kernel code?
> >
> by the way, I found that it is sufficient to do
>
> echo 0x0800000f > /proc/acpi/debug_level and problem disappears. That
> bit is ACPI_DB_INTERRUPTS which is only referenced it two places...

The kernel should debounce the button events after receiving them from
ACPICA.  Your debugging level change merely increases the latency between
handling events so that the second event is missed.

-Nate


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

      parent reply	other threads:[~2003-09-25 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-24 14:23 double power button events on presario 900 - apparently a timing issue? Fedor Karpelevitch
     [not found] ` <200309240723.28526.fedor-ugkMPi23kyXAHCkTjeiZhQ@public.gmane.org>
2003-09-24 18:11   ` Nate Lawson
     [not found]     ` <20030924111121.F53806-Y6VGUYTwhu0@public.gmane.org>
2003-09-24 23:21       ` Fedor Karpelevitch
     [not found]         ` <200309241621.11993.fedor-ugkMPi23kyXAHCkTjeiZhQ@public.gmane.org>
2003-09-25 15:59           ` Fedor Karpelevitch
     [not found]             ` <200309250859.46970.fedor-ugkMPi23kyXAHCkTjeiZhQ@public.gmane.org>
2003-09-25 16:37               ` Nate Lawson [this message]

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=20030925093512.H59477@root.org \
    --to=nate-y6vguytwhu0@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=fedor-ugkMPi23kyXAHCkTjeiZhQ@public.gmane.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