From: Gary Thomas <gary@mlbassoc.com>
To: Kevin Hilman <khilman@ti.com>
Cc: Grazvydas Ignotas <notasas@gmail.com>,
linux-omap@vger.kernel.org, Paul Walmsley <paul@pwsan.com>,
Felipe Balbi <balbi@ti.com>
Subject: Re: PM related performance degradation on OMAP3
Date: Thu, 12 Apr 2012 11:10:05 -0600 [thread overview]
Message-ID: <4F870C6D.3030203@mlbassoc.com> (raw)
In-Reply-To: <87aa2ganwj.fsf@ti.com>
On 2012-04-12 10:57, Kevin Hilman wrote:
> +Felipe for EHCI question
>
> Gary Thomas<gary@mlbassoc.com> writes:
>
> [...]
>
>> This worked a treat, thanks. My network performance is better
>> now, but still not what it was. The same TFTP transfer now takes
>> 71 seconds, so about 50% slower than on the 3.0 kernel. Applying the
>> second [unnamed] patch (arch/arm/mach-omap2/cpuidle34xx.c) made no difference.
>
> And does a CONFIG_PM=n kernel get you back to your v3.0 performance?
Correct.
>
>> I am interested in having PM working as I'm designing a battery powered
>> portable unit, so I need to keep pursuing this.
>
> So do I. :)
>
>> Note: I noticed that when I built with CONFIG_PM off and no other
>> changes, my EHCI USB didn't work properly. Should this be the case?
>
> Probably not, but haven't tested EHCI USB. I've Cc'd Felipe to see if
> he has any ideas why EHCI wouldn't work with CONFIG_PM=n.
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2012-04-12 17:10 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 22:50 PM related performance degradation on OMAP3 Grazvydas Ignotas
2012-04-09 19:03 ` Kevin Hilman
2012-04-11 0:29 ` Grazvydas Ignotas
2012-04-12 0:19 ` Kevin Hilman
2012-04-13 17:32 ` Grazvydas Ignotas
2012-04-13 19:32 ` Grazvydas Ignotas
2012-04-17 14:30 ` Kevin Hilman
2012-04-17 21:50 ` Grazvydas Ignotas
2012-04-18 0:36 ` Kevin Hilman
2012-04-24 9:50 ` Jean Pihet
2012-04-24 10:38 ` Santosh Shilimkar
2012-04-24 12:21 ` Tero Kristo
2012-04-24 12:50 ` Jean Pihet
2012-04-24 13:04 ` Tero Kristo
2012-04-24 14:29 ` Kevin Hilman
2012-05-01 14:10 ` Jean Pihet
2012-05-01 17:27 ` Kevin Hilman
2012-05-02 5:59 ` Paul Walmsley
2012-05-02 19:46 ` Jean Pihet
2012-05-07 17:31 ` Kevin Hilman
2012-05-09 11:00 ` Jean Pihet
2012-04-12 23:02 ` Woodruff, Richard
2012-04-11 14:59 ` Gary Thomas
2012-04-11 17:23 ` Grazvydas Ignotas
2012-04-11 18:20 ` Gary Thomas
2012-04-11 19:17 ` Kevin Hilman
2012-04-12 10:44 ` Gary Thomas
2012-04-12 14:14 ` Kevin Hilman
2012-04-12 15:28 ` Gary Thomas
2012-04-12 16:57 ` Kevin Hilman
2012-04-12 17:10 ` Gary Thomas [this message]
2012-04-12 18:08 ` Kevin Hilman
2012-04-12 19:05 ` Gary Thomas
2012-04-12 22:03 ` Kevin Hilman
2012-04-13 0:39 ` Gary Thomas
2012-04-13 9:13 ` Felipe Balbi
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=4F870C6D.3030203@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=balbi@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=notasas@gmail.com \
--cc=paul@pwsan.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.