From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Hui Wang <jason77.wang@gmail.com>,
Zhang Jiejing <jiejing.zhang@freescale.com>,
linux-input@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Hofemeier, Ulf" <ulf.hofemeier@intel.com>
Subject: Re: eGalax touchscreen regression
Date: Wed, 24 Apr 2013 12:03:13 +0300 [thread overview]
Message-ID: <1366794193.21369.11.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20130423154007.GB4104@core.coreip.homeip.net>
On Tue, 2013-04-23 at 08:40 -0700, Dmitry Torokhov wrote:
> > the eGalax driver now requires OF. For us this is a regression because
> > we do not have OF: https://bugs.tizen.org/jira/browse/TIVI-740
>
> I see. In this case we need to come up with a platform data to pass
> wakeup gpio in case platform does not support OF. irq_to_gpio() is not
> supported on many platforms, causing compilation errors.
>
> Is the platform that you are trying to use the touchscreen upstream?
OK, so this is about just a monitor with a touchscreen (Giantec high-res
capacitive 11.6” LCD monitor). The touchscreen is connected to a
commodity hardware via USB.
So yes, the platform _is_ upstream :-) Namely, we use just a SandyBridge
PC.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2013-04-24 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 9:08 eGalax touchscreen regression Artem Bityutskiy
2013-04-23 11:09 ` [PATCH] input: egalax_ts: remove bogus OF dependency Artem Bityutskiy
2013-04-23 15:37 ` Dmitry Torokhov
2013-04-24 5:58 ` Artem Bityutskiy
2013-04-23 15:40 ` eGalax touchscreen regression Dmitry Torokhov
2013-04-24 6:06 ` Artem Bityutskiy
2013-04-24 9:03 ` Artem Bityutskiy [this message]
2013-04-26 14:59 ` Arnd Bergmann
2013-04-26 15:09 ` Artem Bityutskiy
2013-04-26 15:39 ` Dmitry Torokhov
2013-04-26 16:03 ` Artem Bityutskiy
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=1366794193.21369.11.camel@sauron.fi.intel.com \
--to=artem.bityutskiy@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jason77.wang@gmail.com \
--cc=jiejing.zhang@freescale.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ulf.hofemeier@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;
as well as URLs for NNTP newsgroup(s).