mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adam Williamson <awilliam@redhat.com>
To: "Jin, Yao" <yao.jin@linux.intel.com>
Cc: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	alan@linux.intel.com, mathias.nyman@intel.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH] pinctrl-baytrail: fix for irq descriptor conflict on ASUS T100TA
Date: Sun, 20 Apr 2014 08:28:10 -0700	[thread overview]
Message-ID: <1398007690.2674.0.camel@adam.happyassassin.net> (raw)
In-Reply-To: <5353B8A4.1080900@linux.intel.com>

On Sun, 2014-04-20 at 20:08 +0800, Jin, Yao wrote:
> For the issue that touch screen doesn't work, could you check power
> state of LPSS devices? For example:
> 
> cd /sys/bus/acpi/devices
> grep -H . */power_state
> 
> If they are D3cold, it should be the reason why touch screen doesn't
> work. That's another issue, unrelated to this gpio patch.

The touch screen worked fine with kernel 3.14, and Benjamin looked at
debug output from the attempt to load the touchscreen driver when
diagnosing the problem, he's not just guessing. I am building a kernel
without your patch to confirm that fixes it.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net


  reply	other threads:[~2014-04-20 15:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 12:05 Jin Yao
2014-04-18 20:44 ` Benjamin Tissoires
2014-04-18 21:17   ` Adam Williamson
2014-04-20 10:31   ` Jin, Yao
2014-04-20 12:08     ` Jin, Yao
2014-04-20 15:28       ` Adam Williamson [this message]
2014-04-21  6:27         ` Jin, Yao
2014-04-21 13:28           ` Jin, Yao
2014-04-21 14:30             ` Benjamin Tissoires
2014-04-21 15:51               ` Adam Williamson
2014-04-23  5:16               ` Adam Williamson
2014-04-23  8:34                 ` Mika Westerberg
2014-04-23 12:23                   ` Mika Westerberg
2014-04-23 23:18                     ` Adam Williamson
2014-04-24 13:30                     ` Jin, Yao
2014-04-24 15:58                       ` Adam Williamson
2014-04-24 21:33                       ` Adam Williamson
2014-04-25  7:27                         ` Jin, Yao
2014-04-25  9:40                           ` Mika Westerberg
2014-04-25 12:46                             ` Jin, Yao
2014-04-25  9:32                         ` Linus Walleij
2014-04-25 15:13                           ` Adam Williamson
2014-04-26  3:04                             ` Jin, Yao
2014-04-26  3:42                               ` Jin, Yao
2014-05-02 22:46                                 ` Linus Walleij
2014-04-20 12:56     ` Benjamin Tissoires
2014-04-22 11:51 ` Mika Westerberg
2014-04-22 12:46   ` Jin, Yao

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=1398007690.2674.0.camel@adam.happyassassin.net \
    --to=awilliam@redhat.com \
    --cc=alan@linux.intel.com \
    --cc=benjamin.tissoires@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=yao.jin@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 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®