linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH] touchscreen: Fujitsu touchscreen driver
Date: Tue, 10 Jul 2007 16:09:23 -0700	[thread overview]
Message-ID: <20070710160923.7065b64a@localhost> (raw)
In-Reply-To: <d120d5000705220624k38728dc5kdff5ea3670bf6036@mail.gmail.com>

On Tue, 22 May 2007 09:24:20 -0400
"Dmitry Torokhov" <dmitry.torokhov@gmail.com> wrote:

> Hi Stephen,
> 
> Thank you for looking at the patch and working out quirks...
> 
> On 5/21/07, Stephen Hemminger <shemminger@linux-foundation.org> wrote:
> > +
> > +#define X_AXIS_MIN     90
> > +#define X_AXIS_MAX     4000
> > +#define Y_AXIS_MIN     185
> > +#define Y_AXIS_MAX     4000
> 
> I am not sure that we want to use data from one particular laptop
> here. Since we don't know a way to query the thouchscreen on a
> particular box I'd stick with physical protocol limits (0 - 4095) and
> have user calibrate the screen.

Went back to 0 by 4096 on followup versions

> Have you tried going through the calibration procedure with evtouch
> driver? Does it not work or works incorrectly (I have no idea since I
> don't have the hardware)?

I tried it, and it corrects for offsets.

> > +static irqreturn_t fujitsu_interrupt(struct serio *serio,
> > +                                    unsigned char data, unsigned int flags)
> > +{
> > +       struct fujitsu *fujitsu = serio_get_drvdata(serio);
> > +       struct input_dev *dev = fujitsu->dev;
> > +
> > +       if (fujitsu->idx == 0) {
> > +               /* resync skip until start of frame */
> > +               if (!(data & 0x80))
> > +                       return IRQ_HANDLED;
> 
> The data sheet that I have shows the following for the first byte:
> 
> 1 C 0 0 R S S S
> 
> Where C is 1 while in calibration mode (which we don't use) and R is 1
> when no coordinate corection was done. My original patch had the check
> "(data & 0xf8) != 80", did it give you issues with the data stream
> coming out of the touchscreen? Or the missing fujitsu->idx = 0 is all
> that is really needed?
>

The first byte is always: 0x88

Sample touch in middle is
	88 72 11 4b 0f
        89 71 11 4c 0f
	89 72 11 4b 0f
	8a 71 11 48 0f

So original code that checks for (data & 0xf8) == 0x80
wouldn't work

      reply	other threads:[~2007-07-10 23:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22  6:16 Getting touchscreen to work on Fujitsu B6210 Stephen Hemminger
2007-04-04  5:16 ` Dmitry Torokhov
2007-04-05 19:39   ` Stephen Hemminger
2007-04-05 20:51     ` Dmitry Torokhov
2007-04-05 20:36   ` Stephen Hemminger
2007-04-06  2:27     ` Dmitry Torokhov
2007-04-10 22:40       ` Richard Purdie
2007-05-01 15:49       ` Dmitry Torokhov
2007-05-01 17:39         ` Stephen Hemminger
2007-05-01 18:02           ` Dmitry Torokhov
2007-05-21 19:02             ` [PATCH] touchscreen: Fujitsu touchscreen driver Stephen Hemminger
2007-05-22 13:24               ` Dmitry Torokhov
2007-07-10 23:09                 ` Stephen Hemminger [this message]

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=20070710160923.7065b64a@localhost \
    --to=shemminger@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    /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).