From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Lan Tianyu <tianyu.lan@intel.com>
Cc: lenb@kernel.org, qbanin@gmail.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI/EC: Add msi quirk for Clevo W350etq
Date: Tue, 02 Sep 2014 23:52:10 +0200 [thread overview]
Message-ID: <1789359.lgutrb7SVa@vostro.rjw.lan> (raw)
In-Reply-To: <1409280608-19714-1-git-send-email-tianyu.lan@intel.com>
On Friday, August 29, 2014 10:50:08 AM Lan Tianyu wrote:
> Clevo W350etq's EC will not produce GPE interrupt some time after
> booting. The ACPI notify event won't trigger when the issue takes
> place. After debugging, adding msi quirk for the machine can fix
> the issue. This patch is to add msi quirk for the machine.
>
> Reference: https://bugzilla.kernel.org/show_bug.cgi?id=77431
> Reported-and-tested-by: qbanin@gmail.com
> Signed-off-by: Lan Tianyu <tianyu.lan@intel.com>
Queued up for 3.17-rc4, thanks!
> ---
> drivers/acpi/ec.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/acpi/ec.c b/drivers/acpi/ec.c
> index a66ab65..d8535b3 100644
> --- a/drivers/acpi/ec.c
> +++ b/drivers/acpi/ec.c
> @@ -1015,6 +1015,10 @@ static struct dmi_system_id ec_dmi_table[] __initdata = {
> DMI_MATCH(DMI_SYS_VENDOR, "Quanta"),
> DMI_MATCH(DMI_PRODUCT_NAME, "TW9/SW9"),}, NULL},
> {
> + ec_flag_msi, "Clevo W350etq", {
> + DMI_MATCH(DMI_SYS_VENDOR, "CLEVO CO."),
> + DMI_MATCH(DMI_PRODUCT_NAME, "W35_37ET"),}, NULL},
> + {
> ec_validate_ecdt, "ASUS hardware", {
> DMI_MATCH(DMI_BIOS_VENDOR, "ASUS") }, NULL},
> {
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2014-09-02 21:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 2:50 Lan Tianyu
2014-09-02 21:52 ` Rafael J. Wysocki [this message]
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=1789359.lgutrb7SVa@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qbanin@gmail.com \
--cc=tianyu.lan@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
all inboxes | Powered by JetHome®