[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3076410.nE1Nu6ITeM@wuerfel>
Date: Fri, 26 Apr 2013 16:59:09 +0200
From: Arnd Bergmann <arnd@...db.de>
To: artem.bityutskiy@...ux.intel.com
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Hui Wang <jason77.wang@...il.com>,
Zhang Jiejing <jiejing.zhang@...escale.com>,
linux-input@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Hofemeier, Ulf" <ulf.hofemeier@...el.com>
Subject: Re: eGalax touchscreen regression
On Wednesday 24 April 2013 12:03:13 Artem Bityutskiy wrote:
> 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.
So you use a usb-to-i2c interface?
You have to figure out how the wakeup line is connected to the eGalax
device and provide an alternative implementation for egalax_wake_up_device
that can be used in your case then.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists