All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <aystarik@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Alexey Starikovskiy <astarikovskiy@suse.de>,
	Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
	linux acpi <linux-acpi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: acpi-test tree on eeepc: EC error message on second resume
Date: Sat, 11 Oct 2008 23:31:06 +0400	[thread overview]
Message-ID: <48F0FEFA.7050308@gmail.com> (raw)
In-Reply-To: <200810112130.57757.rjw@sisk.pl>

Rafael J. Wysocki wrote:
> On Saturday, 11 of October 2008, Alexey Starikovskiy wrote:
>   
>> Alan Jenkins wrote:
>>     
>>> I think I found the problem.  The "input buffer empty" wait depends on
>>> "interrupt mode" to work properly, and we don't immediately enable the
>>> interrupt on resume.  The wait should have a polling fallback anyway, to
>>> be consistent with the other transaction waits.
>>>
>>> Alan
>>>       
>> Yep, I think something like attached patch may help:
>>     
>
> [Can you please append patches instead of or apart from attaching them?
> That would make it easier to comment them.]
>
>   
Ok.
> if (!wait_event_timeout(ec->wait, ec_check_ibf0(ec),
> -                               msecs_to_jiffies(ACPI_EC_DELAY))) {
> +                               msecs_to_jiffies(ACPI_EC_DELAY)) &&
> +           !ec_check_ibf0(ec)) {
>
> Shouldn't this go under the spinlock?  Surely it can race with the GPE handler.
>
>   
No, we discussed this before -- we are outside of the transaction, thus 
no GPE
activity could interfere with ec_check_ibf0.

Regards,
Alex.

  reply	other threads:[~2008-10-11 19:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-11 16:57 acpi-test tree on eeepc: EC error message on second resume Alan Jenkins
2008-10-11 17:09 ` Rafael J. Wysocki
2008-10-11 17:12   ` Alan Jenkins
2008-10-11 17:53     ` Rafael J. Wysocki
2008-10-11 18:15       ` Alan Jenkins
2008-10-11 18:39         ` Alexey Starikovskiy
2008-10-11 19:30           ` Rafael J. Wysocki
2008-10-11 19:31             ` Alexey Starikovskiy [this message]
2008-10-11 19:40               ` Rafael J. Wysocki
2008-10-11 19:38                 ` Alexey Starikovskiy
2008-10-11 20:54                   ` Rafael J. Wysocki
2008-10-12  9:13                     ` Alan Jenkins
2008-10-12 19:23                       ` Alexey Starikovskiy
2008-10-13  5:56                         ` Zhao Yakui
2008-10-13  8:22                         ` Alan Jenkins
2008-10-13 16:39                           ` Alan Jenkins
2008-10-15 22:02                             ` [PATCH] ACPI: EC: Check for IBF=0 periodically if not in GPE mode Alexey Starikovskiy
2008-10-16 22:14                               ` Len Brown

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=48F0FEFA.7050308@gmail.com \
    --to=aystarik@gmail.com \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=astarikovskiy@suse.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.