From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Calvin Johnson <linux.cj@gmail.com>
Cc: AceLan Kao <acelan.kao@canonical.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH] pinctrl: intel: add blacklist list for XPS machines
Date: Wed, 5 Oct 2016 11:55:02 +0300 [thread overview]
Message-ID: <20161005085502.GY1765@lahna.fi.intel.com> (raw)
In-Reply-To: <CAEhpT-WvLqfzfxrsRB_+tifq4tESnz_HqdaFb=0VUjff2=3-mg@mail.gmail.com>
On Wed, Oct 05, 2016 at 01:27:31PM +0530, Calvin Johnson wrote:
> On Wed, Oct 5, 2016 at 11:27 AM, AceLan Kao <acelan.kao@canonical.com> wrote:
> > The touchscreen on some Dell machines stop working after
> > closing and opening the lid after this driver is introduced.
> > So, I add a dmi list to black out those machines that doesn't
> > work well with this driver.
>
> Why don't you find out what in the driver is causing this problem,
> instead of avoiding the driver loading altogether?
Exactly!
next prev parent reply other threads:[~2016-10-05 9:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 5:57 [PATCH] pinctrl: intel: add blacklist list for XPS machines AceLan Kao
2016-10-05 7:57 ` Calvin Johnson
2016-10-05 8:55 ` Mika Westerberg [this message]
2016-10-05 9:23 ` AceLan Kao
2016-10-05 9:32 ` Mika Westerberg
2016-10-05 12:47 ` AceLan Kao
2016-10-10 13:39 ` [PATCH] pinctrl: intel: Only restore pins that are used by the driver Mika Westerberg
2016-10-10 14:37 ` Mario.Limonciello
2016-10-10 14:53 ` Mika Westerberg
2016-10-11 1:31 ` AceLan Kao
2016-10-11 2:38 ` AceLan Kao
2016-10-11 9:27 ` Mika Westerberg
2016-10-12 1:35 ` AceLan Kao
2016-10-18 12:39 ` Linus Walleij
2016-10-12 16:31 ` [PATCH] pinctrl: intel: add blacklist list for XPS machines Jon Masters
2016-10-18 12:43 ` Linus Walleij
2016-10-18 12:46 ` Mika Westerberg
2016-10-20 12:01 ` Linus Walleij
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=20161005085502.GY1765@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=acelan.kao@canonical.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux.cj@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).