All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rich Townsend <rhdt-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: sbs-linux acpi-ec-nospinlock patch for 2.6.11
Date: Fri, 11 Mar 2005 11:37:26 -0500	[thread overview]
Message-ID: <4231C946.4090301@bartol.udel.edu> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8407663381@pdsmsx403>



Yu, Luming wrote:
> I don't know what is acpi-ec-nospinlock patch.
> But the patch at http://bugzilla.kernel.org/show_bug.cgi?id=3851#c52 is worthy testing, if you have EC related issue.
> Thanks,
> Luming

It was a small patch I wrote, to lock EC access using a semaphore rather 
than a spinlock. This was to stop the stuttering caused when the EC 
driver was polling for completion of a transaction.

Eventually, of course, we want to switch over to event-based EC 
management. I already tried one of the older EC/event patches on the 
page you give above, with not much success; but I'll give one of the 
newer ones a shot.

I'm currently also playing around with a patch sent to me by Dmitry 
Torokhov, which I believe was a fork from the EC/event patches. It seems 
to work (in that there is no more stuttering), but there are a lot of 
AE_TIME errors returned by the address-space handler, which screws up 
execution of many DSDT methods that use the EC.

cheers,

Rich


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-03-11 16:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11  5:48 sbs-linux acpi-ec-nospinlock patch for 2.6.11 Yu, Luming
2005-03-11 16:37 ` Rich Townsend [this message]
     [not found]   ` <4231C946.4090301-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>
2005-03-11 16:55     ` Rich Townsend
     [not found]       ` <4231CD8E.5080105-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>
2005-03-11 17:54         ` Stefan Seyfried
     [not found]           ` <20050311175452.GB21611-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2005-03-11 20:50             ` Rich Townsend
  -- strict thread matches above, loose matches on Subject: below --
2005-03-06  9:08 Hendrik Jürgens
     [not found] ` <422AC893.7070304-ULHALamj7Vx/+Jgy1241yg@public.gmane.org>
2005-03-06 18:32   ` Rich Townsend

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=4231C946.4090301@bartol.udel.edu \
    --to=rhdt-obnux95toyn10jlvftc4ga@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@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 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.