public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Backlund <tmb@mandriva.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Luca Tettamanti <kronos.it@gmail.com>,
	lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org,
	Jean Delvare <khali@linux-fr.org>
Subject: Re: [PATCH] asus_atk0110: add support for Asus P7P55D
Date: Tue, 29 Sep 2009 17:49:31 +0300	[thread overview]
Message-ID: <4AC21E7B.70000@mandriva.org> (raw)
In-Reply-To: <51f3faa70909290740l4f4df186w114bf48e1db3a948@mail.gmail.com>

Robert Hancock skrev:
> On Tue, Sep 29, 2009 at 8:07 AM, Luca Tettamanti <kronos.it@gmail.com> wrote:
>>>>> Hi Robert,
>>>>> I have a new patch for you :)
>>>>> It contains the previous changes to handle the bigger ASBF buffer plus a new
>>>>> method to enable the EC as suggested by Asus. Be sure to compile with
>>>>> HWMON_DEBUG_CHIP enabled.
>>>> Excellent.. seems to work now and give actually updating sensor readings :-)
>>> Have seen a couple of these though, looks like about once an hour:
>>>
>>> ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl]
>>> (20090903/evregion-424)
>>> ACPI Error (psparse-0537): Method parse/execution failed
>>> [\_SB_.PCI0.SBRG.ASOC.GIT6] (Node ffff88013ba778c0), AE_TIME
>>> ACPI Error (psparse-0537): Method parse/execution failed
>>> [\_SB_.PCI0.SBRG.ASOC.GITM] (Node ffff88013ba6ea40), AE_TIME
>>> ATK0110 ATK0110:00: atk_read_value_new: ACPI exception: AE_TIME
>>>
>>> Maybe sometimes the embedded controller takes longer than the timeout
>>> to process, or something?
>> Is there a message like "input buffer is not empty" before that?
> 
> Nope, that's all I'm getting each time it happens. Suggestions/debug
> patches welcome..
> 

Try this one:
http://marc.info/?l=linux-kernel&m=125421276407283&w=2

--
Thomas

  reply	other threads:[~2009-09-29 14:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23 19:12 [PATCH] asus_atk0110: add support for Asus P7P55D Luca Tettamanti
2009-09-24  3:18 ` Robert Hancock
2009-09-24  8:53   ` Luca Tettamanti
2009-09-28 13:17   ` Luca Tettamanti
2009-09-28 13:22     ` Jean Delvare
2009-09-28 13:40       ` Luca Tettamanti
2009-09-29  2:20     ` Robert Hancock
2009-09-29  4:34       ` Robert Hancock
2009-09-29 14:07         ` Luca Tettamanti
2009-09-29 14:40           ` Robert Hancock
2009-09-29 14:49             ` Thomas Backlund [this message]
2009-09-30  2:08               ` Robert Hancock
2009-09-30 23:38               ` Robert Hancock
2009-10-01  6:50                 ` Jean Delvare
2009-10-01 14:40                   ` Robert Hancock
2009-10-01 14:49                     ` Luca Tettamanti
2009-10-01 16:21                       ` Thomas Backlund
2009-10-01 19:05                         ` Luca Tettamanti
2009-10-02 12:26                           ` Luca Tettamanti
2009-10-02 20:43                             ` Thomas Backlund
2009-10-02 20:45                               ` Thomas Backlund
2009-10-05 15:27                               ` Luca Tettamanti
2009-10-05 17:26                                 ` Thomas Backlund
2009-10-06  1:44                                   ` Robert Hancock
2009-10-01 15:02                 ` Thomas Backlund
2009-09-29 14:54             ` Luca Tettamanti

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=4AC21E7B.70000@mandriva.org \
    --to=tmb@mandriva.org \
    --cc=hancockrwd@gmail.com \
    --cc=khali@linux-fr.org \
    --cc=kronos.it@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.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