From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Tristian Celestin <tristiancelestin@fastmail.com>
Cc: lenb@kernel.org, andriy.shevchenko@linux.intel.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] acpi/x86: enable touchscreen on Dell Venue Pro 7139
Date: Thu, 05 Jul 2018 13:33:56 +0200 [thread overview]
Message-ID: <1929463.ctoOnHkgrM@aspire.rjw.lan> (raw)
In-Reply-To: <1528582686-18577-1-git-send-email-tristiancelestin@fastmail.com>
On Sunday, June 10, 2018 12:18:06 AM CEST Tristian Celestin wrote:
> Permanently enable the SYNA7500 touchscreen device on the Dell
> Venue Pro 7139. The DSDT hides the touchscreen ACPI device on
> the 7139 in the same fashion as the 7130, and needs to
> be enabled in the same way.
>
> Signed-off-by: Tristian Celestin <tristiancelestin@fastmail.com>
> ---
> drivers/acpi/x86/utils.c | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/acpi/x86/utils.c b/drivers/acpi/x86/utils.c
> index ec5b0f1..3a13b2a 100644
> --- a/drivers/acpi/x86/utils.c
> +++ b/drivers/acpi/x86/utils.c
> @@ -62,14 +62,20 @@ struct always_present_id {
> */
> ENTRY("INT0002", "1", ICPU(INTEL_FAM6_ATOM_AIRMONT), {}),
> /*
> - * On the Dell Venue 11 Pro 7130 the DSDT hides the touchscreen ACPI
> - * device until a certain time after _SB.PCI0.GFX0.LCD.LCD1._ON gets
> - * called has passed *and* _STA has been called at least 3 times since.
> + * On the Dell Venue 11 Pro 7130 and 7139, the DSDT hides
> + * the touchscreen ACPI device until a certain time
> + * after _SB.PCI0.GFX0.LCD.LCD1._ON gets called has passed
> + * *and* _STA has been called at least 3 times since.
> */
> ENTRY("SYNA7500", "1", ICPU(INTEL_FAM6_HASWELL_ULT), {
> DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
> DMI_MATCH(DMI_PRODUCT_NAME, "Venue 11 Pro 7130"),
> }),
> + ENTRY("SYNA7500", "1", ICPU(INTEL_FAM6_HASWELL_ULT), {
> + DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
> + DMI_MATCH(DMI_PRODUCT_NAME, "Venue 11 Pro 7139"),
> + }),
> +
> /*
> * The GPD win BIOS dated 20170221 has disabled the accelerometer, the
> * drivers sometimes cause crashes under Windows and this is how the
>
Applied, thanks!
prev parent reply other threads:[~2018-07-05 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-09 22:18 [PATCH] acpi/x86: enable touchscreen on Dell Venue Pro 7139 Tristian Celestin
2018-06-11 8:55 ` Andy Shevchenko
2018-07-05 11:33 ` 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=1929463.ctoOnHkgrM@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tristiancelestin@fastmail.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).