From: Alexey Starikovskiy <aystarik@gmail.com>
To: Zhao Yakui <yakui.zhao@intel.com>
Cc: linux-acpi@vger.kernel.org, lenb@kernel.org, astarikovskiy@suse.de
Subject: Re: [RFC] [PATCH] ACPI :Remove the EC space handler explicitly when failing in _REG object
Date: Wed, 26 Nov 2008 23:03:23 +0300 [thread overview]
Message-ID: <492DAB8B.30409@gmail.com> (raw)
In-Reply-To: <1227689447.4053.5.camel@yakui_zhao.sh.intel.com>
This is hardly a "fix", you just disable EC on this machine... Famous
question
"how windows runs on this machine?" is not answered...
Regards,
Alex.
Zhao Yakui wrote:
> Hi, All
>
> On some laptops as it fails in evaluating the _REG object, which brings that
> EC device can't be initialized correctly. But the EC space handler is not removed.
> In such case maybe EC internal register will still be accessed in AML code. It is
> not reasonable.
> The following patch is to fix the above issue. When it fails in evaluating the
> _REG object, the EC space handler should be removed explicitly.
> Thanks for the comments.
>
>
> On some laptops the incorrect status is returned by acpi_install_space
> _handler because of the buggy _REG object, which causes that the EC device can't
> be initialized correctly.
> In such case it will be appropriate that the EC space handler is removed
> explicitly if OS fails in evaluating _REG object.
>
> http://bugzilla.kernel.org/show_bug.cgi?id=11884
>
> Signed-off-by: Zhao Yakui <yakui.zhao@intel.com>
> cc:Alexey Starikovskiy <astarikovskiy@suse.de>
> ---
> drivers/acpi/ec.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> Index: linux-2.6/drivers/acpi/ec.c
> ===================================================================
> --- linux-2.6.orig/drivers/acpi/ec.c
> +++ linux-2.6/drivers/acpi/ec.c
> @@ -916,6 +916,17 @@ static int ec_install_handlers(struct ac
> printk(KERN_ERR "Fail in evaluating the _REG object"
> " of EC device. Broken bios is suspected.\n");
> } else {
> + /*
> + * If incorrect status is returned because of the buggy
> + * _REG object, the EC space handler should be
> + * uninstalled explicitly.
> + * Otherwise maybe the EC internal register is still
> + * accessed in AML code although EC device is not
> + * initialized correctly.
> + */
> + acpi_remove_address_space_handler(ec->handle,
> + ACPI_ADR_SPACE_EC,
> + &acpi_ec_space_handler);
> acpi_remove_gpe_handler(NULL, ec->gpe,
> &acpi_ec_gpe_handler);
> return -ENODEV;
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-11-26 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 8:50 [RFC] [PATCH] ACPI :Remove the EC space handler explicitly when failing in _REG object Zhao Yakui
2008-11-26 20:03 ` Alexey Starikovskiy [this message]
2008-11-27 1:29 ` Zhao Yakui
2008-11-27 9:42 ` Alexey Starikovskiy
2008-11-28 2:57 ` Zhao Yakui
2008-11-28 8:08 ` Alexey Starikovskiy
2008-12-01 1:53 ` Zhao Yakui
2008-12-01 2:47 ` Zhao Yakui
2008-12-01 8:12 ` the issue about the bogus ECDT table Zhao Yakui
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=492DAB8B.30409@gmail.com \
--to=aystarik@gmail.com \
--cc=astarikovskiy@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--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