From: David Brownell <david-b@pacbell.net>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: is dynamic tick working?
Date: Sun, 14 May 2006 09:19:08 -0700 [thread overview]
Message-ID: <200605140919.09540.david-b@pacbell.net> (raw)
In-Reply-To: <20060514104911.GB4715@atomide.com>
On Sunday 14 May 2006 3:49 am, Tony Lindgren wrote:
> * David Brownell <david-b@pacbell.net> [060512 19:05]:
> > In short, enabling dyntick got me 14x as many IRQs, instead of
> > shrinking the number of IRQs. Known bug?
>
> Is this with touchscreen enabled? I saw something similar last week
> where SPI was generating interrupts continuously. I think Imre has a
> patch for that already available.
It was, but I don't think I've seen such a patch yet.
I had noticed that the ads7846 code grew a glitch whereby its timer
polls for position even when the "pen" isn't down. That's oddly
similar to a glitch in omap-keyboard, where it keeps a timer active
even when no Mistral key is pressed.
> In general dyntick should work, and you should see about 4-6HZ idle
> tick rate.
Depending on drivers, it seems ... ;)
I have a patch to get rid of the OHCI root hub polling, which will
get rid of one 4Hz timer.
- Dave
next prev parent reply other threads:[~2006-05-14 16:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-13 2:05 is dynamic tick working? David Brownell
2006-05-14 10:49 ` Tony Lindgren
2006-05-14 16:19 ` David Brownell [this message]
2006-05-14 17:57 ` Imre Deak
2006-05-14 19:20 ` David Brownell
2006-05-14 20:31 ` Imre Deak
2006-05-15 9:22 ` Tony Lindgren
2006-05-15 22:11 ` David Brownell
2006-05-16 6:59 ` Tony Lindgren
2006-05-26 23:44 ` Tony Lindgren
2006-05-15 9:26 ` Tony Lindgren
2006-05-15 17:33 ` Linux On TI Omap850 Vince
2006-05-16 6:52 ` Tony Lindgren
2006-05-16 14:11 ` Brian Swetland
2006-05-16 13:32 ` is dynamic tick working? Imre Deak
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=200605140919.09540.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap-open-source@linux.omap.com \
--cc=tony@atomide.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