public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Fabio Giovagnini <fabio.giovagnini@aurion-tech.com>
To: linux-sh@vger.kernel.org
Subject: Re: Hi guys, does any of you have experience with touchscreen controllers?
Date: Sun, 02 May 2010 08:16:46 +0000	[thread overview]
Message-ID: <201005021016.46168.fabio.giovagnini@aurion-tech.com> (raw)
In-Reply-To: <201004222004.38724.fabio.giovagnini@aurion-tech.com>

Hi Dale,
for this application I need neccessarly to deliver ASAP, I'm using linux 
2.6.17; so I do not have al lot of stuff present into the newer ones.
I''ll migrate to state of art as soon as I deliver this application and I'll 
start teh new one.
I wrote a simple driver that works pritty much good

Thanks a lot


In data sabato 01 maggio 2010 16:45:03, Dale ha scritto:
: > Fabio Giovagnini wrote:
> > Hi Dale,
> 
> Hi Fabio,
> 
> Sorry for the delay in responding. I was at the ESC conference this week.
> 
> > maybe I need to be more clear about my condition.
> > 1) I connected the ads7843 to general I/O ports because the SPIs
> > available on sh2a7203 have been be used for other functions;
> > 2) My real problem is the following: I wrote an ADS7843 device driver as
> > a button driver of the input subsystem. I configured the ads7843 with INT
> 
> You wrote the driver? I just used the existing one in the 2.6.28.2 kernel.
> 
> > enabled; so when the touch is pressed I have a burst of IRQ. The IRQ
> > handler read the ads7843 and return to the input subsystem the abs values
> > of the touchscreen.
> 
> I seem to recall you need disable the interrupt upon #PENIRQ and allow the
> polling code to do the job of determining the pen up event.
> 
> > The user program open the file /dev/input/event0 and with the select
> > waits for data; what I see is: during all the time I have a finger on the
> > touch only IRQ handler is exeuted and no action is done in the user
> > program. I tried also opening /dev/input/event0 with O_NONBLOCK flag but
> > nothing changes.
> 
> The existing driver uses the event system. The easiest way to see what I
>  did is to unpack a 2.6.28.2 linux tarball and apply the patch I've
>  attached to this post.
> 
> Dale Larson
> Johnson Controls, Inc
> 

-- 
Fabio Giovagnini

Aurion s.r.l.
P.I e C.F.
00885711200
Tel. +39.051.594.78.24
Cell. +39.335.83.50.919

      parent reply	other threads:[~2010-05-02  8:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22 18:04 Hi guys, does any of you have experience with touchscreen controllers? Fabio Giovagnini
2010-04-24 21:46 ` Dale
2010-04-25  2:26 ` Dale
2010-04-25  2:26 ` Dale Larson
2010-04-26  6:50 ` Fabio Giovagnini
2010-04-26  7:13 ` Fabio Giovagnini
2010-04-26 10:41 ` Michael Trimarchi
2010-04-26 10:45 ` Fabio Giovagnini
2010-04-26 10:52 ` Michael Trimarchi
2010-05-01 14:45 ` Dale
2010-05-02  8:16 ` Fabio Giovagnini [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=201005021016.46168.fabio.giovagnini@aurion-tech.com \
    --to=fabio.giovagnini@aurion-tech.com \
    --cc=linux-sh@vger.kernel.org \
    /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