From: Kalle Jokiniemi <kalle.jokiniemi@digia.com>
To: "khilman@deeprootsystems.com" <khilman@deeprootsystems.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 0/3] PM: Misc latency fixes
Date: Thu, 29 Oct 2009 12:15:56 +0200 [thread overview]
Message-ID: <1256811356.31764.72.camel@ubuntu> (raw)
In-Reply-To: <1256125881-12441-1-git-send-email-kalle.jokiniemi@digia.com>
Hi Kevin,
On Wed, 2009-10-21 at 14:51 +0300, Kalle Jokiniemi wrote:
> Hello,
> Here are some fruits from digging out the latency sources
> of our idle loop. The main latency source was powerdomain
> state counter updating at beginning and end of the idle
> loop. Also PER previous state reading strangely seemed to
> cause some latency with significance. Could not find any
> TRM or errata comment to why this is, though.
>
> The I2C mpu wakeup latency constraint patch has been updated
> to calculate latencies at boot from clkrate and fifo size.
> This was included in this set, since it benefits from the
> reduced latency of the other patches.
>
> Patches tested on linux-omap/pm and rx-51.
>
> Kalle Jokiniemi (3):
> OMAP3: Only update pm-counters when needed
> PM: Skip PER previous state register read
How about those latency optimization patches? Are you are you going to
take them in? I'd like to know if there is something to fix in those, so
I can finish it this week. Starting next week I'll be moving to other
responsibilities and might not be able to do additional changes for the
patches.
> OMAP: I2C: Add mpu wake up latency constraint in i2c
This i2c patch can be pushed separately, in case you're waiting for that
thread to finish.
- Kalle
>
> arch/arm/mach-omap2/pm-debug.c | 51 ++++++++++++++++++++++++++++++++++++-
> arch/arm/mach-omap2/pm.h | 2 +
> arch/arm/mach-omap2/pm34xx.c | 31 ++++++++++++++--------
> arch/arm/plat-omap/i2c.c | 54 +++++++++++++++++++++++++++++++---------
> drivers/i2c/busses/i2c-omap.c | 25 +++++++++++++++---
> include/linux/i2c-omap.h | 9 ++++++
> 6 files changed, 143 insertions(+), 29 deletions(-)
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-10-29 10:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 11:51 [PATCH 0/3] PM: Misc latency fixes Kalle Jokiniemi
2009-10-21 11:51 ` [PATCH 1/3] OMAP3: Only update pm-counters when needed Kalle Jokiniemi
2009-10-21 11:51 ` [PATCH 2/3] PM: Skip PER previous state register read Kalle Jokiniemi
2009-10-21 11:51 ` [PATCH V4 3/3] OMAP: I2C: Add mpu wake up latency constraint in i2c Kalle Jokiniemi
2009-10-23 15:53 ` Sonasath, Moiz
2009-10-29 8:55 ` Kalle Jokiniemi
2009-11-20 8:35 ` kalle.jokiniemi
2009-11-20 16:28 ` Kevin Hilman
2009-11-23 7:35 ` kalle.jokiniemi
[not found] ` <1256644921.6751.61.camel@ubuntu>
2009-11-23 16:10 ` Sonasath, Moiz
2009-11-24 15:19 ` kalle.jokiniemi
2009-11-24 15:54 ` Kevin Hilman
2009-10-30 16:31 ` [PATCH 2/3] PM: Skip PER previous state register read Kevin Hilman
2009-11-06 7:52 ` kalle.jokiniemi
2009-10-29 23:07 ` [PATCH 1/3] OMAP3: Only update pm-counters when needed Kevin Hilman
2009-10-30 9:06 ` Kalle Jokiniemi
2009-10-29 10:15 ` Kalle Jokiniemi [this message]
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=1256811356.31764.72.camel@ubuntu \
--to=kalle.jokiniemi@digia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
/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