From: AceLan Kao <acelan.kao@canonical.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Calvin Johnson <linux.cj@gmail.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 17:23:08 +0800 [thread overview]
Message-ID: <CAFv23Qkv7EGQy+ObQukaArdyeeQhWTyUmvk=gxycwV_YD3dd2Q@mail.gmail.com> (raw)
In-Reply-To: <20161005085502.GY1765@lahna.fi.intel.com>
I have no knowledge of those pin definitions, and with 3.19 kernel,
those 2 blacklisted machines work well.
There is no pinctrl-sunrisepoint in 3.19 kernel, so I think this
driver is not critical for the machines,
that why I blacklisted the machines in the driver.
Or maybe anyone of you can give me some hints, which pin related to
the touchscreen which is connected on USB port.
I can do some test to see if I can find other solution.
The issue we encountered is that closing the lid to enter S3 and then
open the lid to wake up, the touchscreen fails to work.
By other ways to enter S3, pm-suspend, or click from GUI, the
touchscreen still works after waking up.
Thanks.
2016-10-05 16:55 GMT+08:00 Mika Westerberg <mika.westerberg@linux.intel.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:23 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
2016-10-05 9:23 ` AceLan Kao [this message]
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='CAFv23Qkv7EGQy+ObQukaArdyeeQhWTyUmvk=gxycwV_YD3dd2Q@mail.gmail.com' \
--to=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 \
--cc=mika.westerberg@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.