linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Dooks <ben-linux@fluff.org>
To: Daniel Silverstone <dsilvers@simtec.co.uk>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	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: Thu, 15 Jan 2009 15:12:28 +0000	[thread overview]
Message-ID: <20090115151228.GU15238@trinity.fluff.org> (raw)
In-Reply-To: <1231954613.9219.8.camel@ataraxia>

On Wed, Jan 14, 2009 at 05:36:53PM +0000, Daniel Silverstone wrote:
> On Tue, 2009-01-13 at 21:35 -0800, Dmitry Torokhov wrote:
> > > 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.
> > Geez... you sure it wasn't just broken device/batch?
> 
> Nope, the datasheet proudly proclaims this watchdog functionality.

Would be useful to add a comment about that being the primary function
for the irq_always flag, ie:

+       /* Always service the USB devices irq not just when the input device is
+        * open. This is often for devices that have a watchdog which watches
+	 * the polling process.
+        */
 
> > > 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?
> > I just checked TSLIB and the change to recognize devices that do not
> > report pressure was applied 2 months ago so everything should work fine
> > now. I do not think that we need to implement workarounds in newly
> > added drivers just because users are not willing to upgrade their
> > TSLIB installation.
> 
> I see. I shall look into sorting out a fresh patch without fake
> pressure.

-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.


  reply	other threads:[~2009-01-15 15:40 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
2009-01-14  5:35         ` Dmitry Torokhov
2009-01-14 17:36           ` Daniel Silverstone
2009-01-15 15:12             ` Ben Dooks [this message]
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=20090115151228.GU15238@trinity.fluff.org \
    --to=ben-linux@fluff.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dsilvers@simtec.co.uk \
    --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 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).