From: Romit Dasgupta <romit@ti.com>
To: "Premi, Sanjeev" <premi@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: omap3evm: touchscreen delays on pm branch
Date: Fri, 27 Nov 2009 15:54:55 +0530 [thread overview]
Message-ID: <4B0FA8F7.30300@ti.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59301DE7B9180@dbde02.ent.ti.com>
>
> 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.
Do you see PER powerdomain entering retention?
next prev parent reply other threads:[~2009-11-27 10:24 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 [this message]
2009-11-27 10:34 ` Hemanth V
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=4B0FA8F7.30300@ti.com \
--to=romit@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=premi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox