From: Vincent Wan <Vincent.Wan@amd.com>
To: dmitry.torokhov@gmail.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Ray.Huang@amd.com, mcuos.com@gmail.com,
Vincent Wan <Vincent.Wan@amd.com>
Subject: [PATCH] input: i8042: add quirk to implement i8042 detect for AMD
Date: Fri, 16 Oct 2015 09:27:00 -0400 [thread overview]
Message-ID: <1445002020-12672-1-git-send-email-Vincent.Wan@amd.com> (raw)
Detecting platform supports i8042 or not, AMD resorted to
BIOS's FADT i8042 flag.
Signed-off-by: Vincent Wan <Vincent.Wan@amd.com>
---
drivers/input/serio/i8042-x86ia64io.h | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/input/serio/i8042-x86ia64io.h b/drivers/input/serio/i8042-x86ia64io.h
index c115565..bf3a605 100644
--- a/drivers/input/serio/i8042-x86ia64io.h
+++ b/drivers/input/serio/i8042-x86ia64io.h
@@ -9,6 +9,7 @@
#ifdef CONFIG_X86
#include <asm/x86_init.h>
+#include <linux/acpi.h>
#endif
/*
@@ -1047,6 +1048,11 @@ static int __init i8042_platform_init(void)
/* Just return if pre-detection shows no i8042 controller exist */
if (!x86_platform.i8042_detect())
return -ENODEV;
+
+ if (boot_cpu_data.x86_vendor == X86_VENDOR_AMD) {
+ if (!(acpi_gbl_FADT.boot_flags & ACPI_FADT_8042))
+ return -ENODEV;
+ }
#endif
/*
--
1.9.1
next reply other threads:[~2015-10-16 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 13:27 Vincent Wan [this message]
2015-10-16 8:58 ` [PATCH] input: i8042: add quirk to implement i8042 detect for AMD Borislav Petkov
2015-10-16 9:06 ` Huang Rui
2015-10-16 9:35 ` Wan ZongShun
2015-10-16 10:21 ` Borislav Petkov
2015-10-17 16:38 ` Dmitry Torokhov
2015-11-19 14:40 ` Wan, Vincent
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=1445002020-12672-1-git-send-email-Vincent.Wan@amd.com \
--to=vincent.wan@amd.com \
--cc=Ray.Huang@amd.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcuos.com@gmail.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;
as well as URLs for NNTP newsgroup(s).