From: Alexey Starikovskiy <astarikovskiy@suse.de>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: Zhao Yakui <yakui.zhao@intel.com>, LenBrown <lenb@kernel.org>,
Linux-acpi@vger.kernel.org,
Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Subject: Re: [PATCH] ACPI: EC: do transaction from interrupt context
Date: Fri, 26 Sep 2008 10:01:04 +0400 [thread overview]
Message-ID: <48DC7AA0.8030204@suse.de> (raw)
In-Reply-To: <48DC763B.7080203@yahoo.com>
Hi Sitsofe,
Alan already tested my patch and it works for him.
Regards,
Alex.
Sitsofe Wheeler wrote:
> Zhao Yakui wrote:
>> I think that the problem on the asus-EEEPC can't be resolved really
>> by the Alexey's patch. IMO it is only lucky.
>
> How lucky? It really does go from excruciatingly slow to quite fast on
> that laptop. What will happen should my luck fail? What are the odds of
> my luck failing?
>
>> In fact the main problem on Asus-EEEPC is related with the broken EC.
>> Before an EC notification event is processed, another EC notification
>> event arrives again.
>> If EC driver check whether the SCI_EVT bit is set after processing
>> one EC notification event, the problem will be resolved.
>> http://bugzilla.kernel.org/show_bug.cgi?id=11089
>> Alan Jenkins already sent a patch about how to fix the issue on the
>> Asus-EEEPC.
>
> I'll cc Alan and see what he makes of this patch.
>
>> But if the above patch is merged , maybe it will break some laptops.
>
> Fair enough but can those people with such laptops test the patch too
> and report back? Can you say in what form the breakages will take? From
> what you are saying it sounds like this patch shouldn't have had any
> affect for me but it does. What happens when they try it? What happens
> when you try it?
>
next prev parent reply other threads:[~2008-09-26 6:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 17:00 [PATCH] ACPI: EC: do transaction from interrupt context Alexey Starikovskiy
2008-09-25 17:52 ` Sitsofe Wheeler
2008-09-26 1:06 ` Zhao Yakui
2008-09-26 5:42 ` Sitsofe Wheeler
2008-09-26 6:01 ` Alexey Starikovskiy [this message]
2008-09-26 9:03 ` Alan Jenkins
2008-09-26 10:42 ` Alexey Starikovskiy
2008-09-26 11:17 ` Alan Jenkins
2008-09-26 6:04 ` Zhao Yakui
2008-09-26 12:33 ` Rafael J. Wysocki
2008-09-26 13:54 ` Zhao, Yakui
2008-09-26 14:15 ` Rafael J. Wysocki
2008-09-26 14:53 ` Alexey Starikovskiy
2008-09-26 15:18 ` Rafael J. Wysocki
2008-09-26 15:21 ` Alexey Starikovskiy
2008-09-26 15:48 ` Rafael J. Wysocki
2008-09-26 15:47 ` Alexey Starikovskiy
2008-09-26 15:57 ` Rafael J. Wysocki
2008-09-26 15:10 ` Zhao Yakui
2008-09-26 15:39 ` Rafael J. Wysocki
2008-09-27 3:39 ` Zhao Yakui
2008-09-27 5:37 ` Alexey Starikovskiy
2008-09-27 5:59 ` Zhao Yakui
2008-09-27 6:44 ` Alexey Starikovskiy
2008-09-25 20:10 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2008-09-26 6:16 Sitsofe Wheeler
2008-09-25 11:24 Alexey Starikovskiy
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=48DC7AA0.8030204@suse.de \
--to=astarikovskiy@suse.de \
--cc=Linux-acpi@vger.kernel.org \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=lenb@kernel.org \
--cc=sitsofe@yahoo.com \
--cc=yakui.zhao@intel.com \
/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