From: Tony Lindgren <tony@atomide.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: is dynamic tick working?
Date: Mon, 15 May 2006 23:59:46 -0700 [thread overview]
Message-ID: <20060516065945.GF3413@atomide.com> (raw)
In-Reply-To: <200605151511.11836.david-b@pacbell.net>
* David Brownell <david-b@pacbell.net> [060515 15:11]:
> On Monday 15 May 2006 2:22 am, Tony Lindgren wrote:
> >
> > OK, I've pushed Imre's patches. Can you check that everything got
> > patched OK?
>
> I attach three patches:
>
> - To make Mistral work better needs new callback), which worked for
> me (modulo writing the "disable" file wedging, gotta retest that);
I'll push this patch today.
> - A quickie bitbang SPI adapter for the 1510-Innovator FPGA hookup to ads7846,
> untested beyond compiling (no Innovator here!);
>
> - Removing the old OMAP-specific Mistral and Innovator touchscreen drivers;
> this may be a trifle premature given the lack of Innovator testing
Let's try these patches out before pushing. Can somebody with an
Innovator test these patches?
> Anyway, with the first of these patches I saw tick rates of about 27 Hz;
> the issue seems to be the omap_ts driver keeping a timer active (among
> other misbehaviors).
>
> In short: yes, it's better now.
AFAIK omap_ts should only need a timer when pen is down.
Tony
next prev parent reply other threads:[~2006-05-16 6:59 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
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 [this message]
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=20060516065945.GF3413@atomide.com \
--to=tony@atomide.com \
--cc=david-b@pacbell.net \
--cc=linux-omap-open-source@linux.omap.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