From: Daniel Silverstone <dsilvers@simtec.co.uk>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Ben Dooks <ben-linux@fluff.org>,
linux-input@vger.kernel.org, vince@simtec.co.uk
Subject: Re: usbtouchscreen: Add support for Zytronic capacitive touchscreen
Date: Tue, 13 Jan 2009 09:29:18 +0000 [thread overview]
Message-ID: <1231838958.30531.3.camel@petitemort> (raw)
In-Reply-To: <20090112212907.ZZRA012@mailhub.coreip.homeip.net>
On Mon, 2009-01-12 at 21:33 -0800, Dmitry Torokhov wrote:
> > > > + /* Always service the USB devices irq not just when the input device is
> > > > + * open.
> > > > + */
> > > > + int irq_always;
> > > Why is this needed?
> > Some devices (E.g. specifically this one) expect their interrupt
> > endpoints to always be serviced. In this case, the device has an
> > on-board watchdog and will reboot (disconnect and reconnecting to the
> > USB) if it is not serviced in a timely fashion.
> So what happens if driver was unloaded or there was no driver loaded at
> all? Is this device constantly connecting and reconnecting?
As I understand it; yes. (Some bits of hardware really are hideous
things) Indeed if the driver fails to load quickly enough, the device
might disconnect/reconnect before the driver can get hold of it.
> > > > + dev->touch = 1;
> > > > + dev->press = 1;
> > > Since the device does not report real pressure readings don't try to
> > > fake it, reporting touch is enough.
> > I believe that this is because some userland libraries, particularly
> > tslib, require the pressure reading in order to believe the device is
> > functioning usefully. Specifically, consider plugins/input-raw of
> > tslib's source package which uses pressure rather than touch.
> Yes, I am aware of TSLIB case and I am telling everyone who submits
> touchscreen drivers that they need to fix it. The policy is that
> kernel should not generate fake events but present as accurate state
> of hardware as possible.
Unfortunately it's often harder to get people to change their userland
than their kernel. It seems a pity to make the driver less useful during
any longer-term effort to fix TSLIB. If acceptance of this patch is
predicated on removing that then I guess we'll have to discuss it
amongst ourselves and try and work out what we'd rather do. Is removing
the fake pressure report a requirement or a would-like?
Regards,
Daniel.
--
Daniel Silverstone http://www.simtec.co.uk/
PGP mail accepted and encouraged. Key Id: 2BC8 4016 2068 7895
next prev parent reply other threads:[~2009-01-13 9:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 12:10 usbtouchscreen: Add support for Zytronic capacitive touchscreen Ben Dooks
2009-01-12 7:53 ` Dmitry Torokhov
2009-01-12 9:07 ` Daniel Silverstone
2009-01-13 5:33 ` Dmitry Torokhov
2009-01-13 9:29 ` Daniel Silverstone [this message]
2009-01-14 5:35 ` Dmitry Torokhov
2009-01-14 17:36 ` Daniel Silverstone
2009-01-15 15:12 ` Ben Dooks
2009-01-29 10:55 ` Daniel Silverstone
2009-03-31 9:52 ` Daniel Silverstone
2009-04-08 20:33 ` Dmitry Torokhov
2009-04-09 8:20 ` Daniel Silverstone
-- strict thread matches above, loose matches on Subject: below --
2009-11-23 14:39 Ben Dooks
2009-11-23 17:21 ` Dmitry Torokhov
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=1231838958.30531.3.camel@petitemort \
--to=dsilvers@simtec.co.uk \
--cc=ben-linux@fluff.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=vince@simtec.co.uk \
/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.