From: Tony Lindgren <tony@atomide.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: Kevin Hilman <khilman@mvista.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH] dmtimer posting
Date: Wed, 2 Apr 2008 10:23:40 +0300 [thread overview]
Message-ID: <20080402072340.GH31913@atomide.com> (raw)
In-Reply-To: <3B6D69C3A9EBCA4BA5DA60D91302742903E22347@dlee13.ent.ti.com>
* Woodruff, Richard <r-woodruff2@ti.com> [080331 15:18]:
> > > > Attached is a rev-4 with the cpu_relax() added to while loops as
> > > > suggested by Ladislav, and CTRL register defines moved to the
> right
> > > > location.
> > >
> > > I confirm this version of the patch works on 3430 with latest
> kernel.
> >
> > I'll push the rev-4 version of the patch today. The second patch needs
> > a bit more work still.
>
> Great.
>
> I've been testing on a few systems with a functional variant of the 1st
> + 2nd patch back ported to older TI CDP kernels. So far I've only ran
> into positive side effects. No noticeable load, pass normal functional
> tests, and still able to hit all low power states.
>
> In that variant I just added a load_start() function in addition to the
> load function and converted all the in tree callers to use this as they
> all called load() then start() in order anyway. This left the API
> behavior the same but optimized all current users.
Can you send a patch against l-o tree for the load_start()? That might
be optimized enough :)
Tony
> Regards,
> Richard W.
>
> I did get my ETM adaptor board back so I have been able to verify
> directly. ETM is cool in that you can get (depending on filtering)
> almost a 60 second complete capture of instruction execution during some
> use case.
next prev parent reply other threads:[~2008-04-02 7:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ae36f8040803061301y6e0823a8pbdf0b6f0b47e5639@mail.gmail.com>
[not found] ` <3B6D69C3A9EBCA4BA5DA60D91302742903AFC880@dlee13.ent.ti.com>
[not found] ` <20080307071454.GC7635@atomide.com>
2008-03-15 0:24 ` [PATCH] [RFC] dmtimer library is very inefficient today Woodruff, Richard
2008-03-18 18:33 ` Kevin Hilman
2008-03-18 18:51 ` Woodruff, Richard
2008-03-19 2:40 ` [PATCH] dmtimer posting Woodruff, Richard
2008-03-19 14:15 ` Tony Lindgren
2008-03-19 14:47 ` Woodruff, Richard
2008-03-19 15:58 ` Tony Lindgren
2008-03-19 22:13 ` Woodruff, Richard
2008-03-20 11:57 ` Tony Lindgren
2008-03-20 12:19 ` Tony Lindgren
2008-03-21 0:13 ` Woodruff, Richard
2008-03-21 0:01 ` Woodruff, Richard
2008-03-31 10:49 ` Tony Lindgren
2008-03-31 12:18 ` Woodruff, Richard
2008-04-02 7:23 ` Tony Lindgren [this message]
2008-04-04 4:50 ` Woodruff, Richard
2008-04-04 20:03 ` [PATCH] timer optimization part 2 Woodruff, Richard
2008-04-04 20:23 ` Idle picture for those interested Woodruff, Richard
2008-04-04 20:56 ` David Brownell
2008-04-04 21:45 ` Woodruff, Richard
2008-04-04 21:56 ` Woodruff, Richard
2008-04-04 22:07 ` David Brownell
[not found] ` <49DA3A9F04A0E5498FF06EFCC343DCF90203DA56FF@dlee13.ent.ti.com>
2008-05-07 23:46 ` [PATCH] timer optimization part 2 Woodruff, Richard
2008-05-08 17:40 ` Tony Lindgren
2008-03-19 19:52 ` [PATCH] [RFC] dmtimer library is very inefficient today Ladislav Michl
2008-03-20 8:58 ` Tony Lindgren
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=20080402072340.GH31913@atomide.com \
--to=tony@atomide.com \
--cc=khilman@mvista.com \
--cc=linux-omap@vger.kernel.org \
--cc=r-woodruff2@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