From: "Hemanth V" <hemanthv@ti.com>
To: "Premi, Sanjeev" <premi@ti.com>, "Dasgupta, Romit" <romit@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: omap3evm: touchscreen delays on pm branch
Date: Fri, 27 Nov 2009 16:04:38 +0530 [thread overview]
Message-ID: <040b01ca6f4d$38ac95c0$LocalHost@wipultra793> (raw)
In-Reply-To: B85A65D85D7EB246BE421B3FB0FBB59301DE7B9180@dbde02.ent.ti.com
----- Original Message -----
From: "Premi, Sanjeev" <premi@ti.com>
To: "Dasgupta, Romit" <romit@ti.com>
Cc: <linux-omap@vger.kernel.org>
Sent: Friday, November 27, 2009 3:20 PM
Subject: RE: omap3evm: touchscreen delays on pm branch
>> -----Original Message-----
>> From: Dasgupta, Romit
>> Sent: Friday, November 27, 2009 2:38 PM
>> To: Premi, Sanjeev
>> Cc: linux-omap@vger.kernel.org
>> Subject: RE: omap3evm: touchscreen delays on pm branch
>>
>> On Fri, 2009-11-27 at 14:11 +0530, Premi, Sanjeev wrote:
>> > > -----Original Message-----
>> > > From: Dasgupta, Romit
>> > > Sent: Friday, November 27, 2009 2:10 PM
>> > > To: Premi, Sanjeev
>> > > Cc: linux-omap@vger.kernel.org
>> > > Subject: Re: omap3evm: touchscreen delays on pm branch
>> > >
>> > > Premi, Sanjeev wrote:
>> > > > Hi,
>> > > >
>> > > > I am finding the response of touchscreen on the
>> omap3evm very slow.
>> > > >
>> > > > Here is my test:
>> > > > On console, I run : watch -n2 "cat /proc/interrupts"
>> > > > Then, I tap the touchscreen approximately once per
>> second. However,
>> > > > (usually) no interrupts are registered. As I increase
>> the frequency
>> > > > of 'taps' more and more interrupts are registered. But still not
>> > > > matching exact taps.
>> > > >
>> > > > However, when I keep the cpu busy with "cat /dev/zero >
>> /dev/null &"
>> > > > each tap is recognized.
>> > > >
>> > > Do you see this even if we don't enable OFF?
>> > >
>> > Yes. Sleep_while_idle=0; enable_off_mode=0
>> > ~sanjeev
>>
>> Hopefully you have the same TSC driver. Nevertheless, can you
>> please try
>> this (just to see if clock domain idling is causing any
>> problem or not):
>
> It is the same driver at SDP3430. I had earlier tried removing
> cpuidle altogether and did not see this issue. I too believe that
> issue is caused by clocks being going to (auto)idle.
>
> But then, Hemanth should be seeing the same behavior.
Zoom2/Zoom3 use a different touchscreen driver compared to SDP.
Its uses Synaptic Touchscreen over I2C.
next prev parent reply other threads:[~2009-11-27 10:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 17:02 omap3evm: touchscreen delays on pm branch Premi, Sanjeev
2009-11-27 6:05 ` Hemanth V
2009-11-27 8:39 ` Romit Dasgupta
2009-11-27 8:41 ` Premi, Sanjeev
2009-11-27 9:07 ` Romit Dasgupta
2009-11-27 9:50 ` Premi, Sanjeev
2009-11-27 10:24 ` Romit Dasgupta
2009-11-27 10:34 ` Hemanth V [this message]
2009-12-01 10:06 ` Sriram V
2009-12-01 16:05 ` Premi, Sanjeev
2009-12-02 5:11 ` Romit Dasgupta
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='040b01ca6f4d$38ac95c0$LocalHost@wipultra793' \
--to=hemanthv@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=premi@ti.com \
--cc=romit@ti.com \
/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.