public inbox for linux-acpi@vger.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: Re: What's up with the Embedded Controller driver? [was Re: [ACPI] patched sms-cm acpi/ec.c to 2.6.11.5]
Date: Tue, 29 Mar 2005 10:09:21 -0500	[thread overview]
Message-ID: <42496FA1.90105@bartol.udel.edu> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F84041AC161@pdsmsx403>

Yu, Luming wrote:
> I'm sorry, what is  sbs-cm packag? 
> Please make sure sbs-cm package is using ec_read/write functions defined in ec.c

The sbs-cm package is a patchset for DSDT, that implements the Control
Method battery API for systems that use Smart Battery technology; see here:

http://sourceforge.net/projects/sbs-linux/

The ec_read/write functions are NOT used in sbs-cm, because all accesses
to the Embedded Controller are done from within the AML virtual machine,
using the EC OperationRegion. So in fact sbs-cm accesses the EC via the
address space handler in ec.c, NOT the read/write routines.

Note that many of the people reporting problems with ec.c (including
myself, Pedro and Francois) are using this package. So it may be that
the problem with ec.c is in the address space handler.


cheers,

Rich

> 
> Thanks
> Luming 
> 
> 
>>-----Original Message-----
>>From: Rich Townsend [mailto:rhdt-OBnUx95tOyn10jlvfTC4gA@public.gmane.org] 
>>Sent: 2005年3月29日 22:50
>>To: Yu, Luming
>>Cc: François Valenduc; ACPI devel
>>Subject: Re: [ACPI] Re: What's up with the Embedded Controller 
>>driver? [was Re: [ACPI] patched sms-cm acpi/ec.c to 2.6.11.5]
>>
>>Yu, Luming wrote:
>>
>>>You modified DSDT just remove some AML methods that related to EC.
>>>That means it just delete the problem. 
>>>I believe if you think this is the regression, just because 
>>
>>the changeset
>>
>>http://linux-acpi.bkbits.net:8080/26-latest-test/diffs/include/
>>acpi/acconfig.h@1.55?nav=index.html|src/.|src/include|src/inclu
> 
> de/acpi|hist/include/acpi/acconfig.h
> 
>>>make _those AML methods just run.
>>>So, this is NOT a regression problem.
>>>
>>>Please cat /proc/interrupts to me before accessing EC and 
>>
>>after accessing EC.(using burst mode EC patch)
>>
>>Hi Yuming --
>>
>>I'm using your ec patch, plus a DSDT modified using my sbs-cm package
>>(which accesses the Smart Battery system through the EC address space
>>handler). Here's what happens to the interrupts when I access 
>>the battery:
>>
>>rhdt@sto ~ $ cat /proc/interrupts
>>          CPU0
>> 0:  127116981          XT-PIC  timer
>> 1:     213426          XT-PIC  i8042
>> 2:          0          XT-PIC  cascade
>> 6:     171382          XT-PIC  i915@pci:0000:00:02.0, uhci_hcd,
>>uhci_hcd, uhci_hcd, eth1
>> 8:          8          XT-PIC  rtc
>> 9:    3305062          XT-PIC  acpi
>>10:    1965890          XT-PIC  Intel 82801DB-ICH4, yenta, ehci_hcd,
>>ipw2200
>>12:    4335843          XT-PIC  i8042
>>14:     466033          XT-PIC  ide0
>>15:         28          XT-PIC  ide1
>>NMI:          0
>>LOC:          0
>>ERR:          0
>>rhdt@sto ~ $ cat /proc/acpi/battery/BAT0/state
>>present:                 yes
>>capacity state:          ok
>>charging state:          charged
>>present rate:            0 mA
>>remaining capacity:      4081 mAh
>>present voltage:         16699 mV
>>rhdt@sto ~ $ cat /proc/interrupts
>>          CPU0
>> 0:  127131974          XT-PIC  timer
>> 1:     213488          XT-PIC  i8042
>> 2:          0          XT-PIC  cascade
>> 6:     171462          XT-PIC  i915@pci:0000:00:02.0, uhci_hcd,
>>uhci_hcd, uhci_hcd, eth1
>> 8:          8          XT-PIC  rtc
>> 9:    3305297          XT-PIC  acpi
>>10:    1966133          XT-PIC  Intel 82801DB-ICH4, yenta, ehci_hcd,
>>ipw2200
>>12:    4335843          XT-PIC  i8042
>>14:     466065          XT-PIC  ide0
>>15:         28          XT-PIC  ide1
>>NMI:          0
>>LOC:          0
>>ERR:          0
>>
>>Note that the battery access took over 5 seconds! And note, of course,
>>the big jump in the acpi interrupt count.
>>
>>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_ide95&alloc_id\x14396&op=click

  reply	other threads:[~2005-03-29 15:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-29 15:01 Re: What's up with the Embedded Controller driver? [was Re: [ACPI] patched sms-cm acpi/ec.c to 2.6.11.5] Yu, Luming
2005-03-29 15:09 ` Rich Townsend [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-29  2:22 Yu, Luming
2005-03-29 14:50 ` Rich Townsend
2005-03-25  1:23 Yu, Luming
     [not found] <3ACA40606221794F80A5670F0AF15F84041AC15D@pdsmsx403>
2005-03-24 19:40 ` François Valenduc
2005-03-24 16:02 Yu, Luming
2005-03-24 14:18 Yu, Luming
2005-03-24 15:37 ` François Valenduc
2005-03-28  0:01 ` 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=42496FA1.90105@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox