> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Tony Lindgren
> Sent: Saturday, September 25, 2010 12:40 AM
> To: Sripathy, Vishwanath
> Cc: linux-o...@vger.kernel.org; linaro-dev@lists.linaro.org; Kevin Hillman
> Subje
* Vishwanath BS [100924 03:50]:
> There is no need to keep omap3 sleep code in SRAM. This code can be run very
> well on DDR. This would help us to instrument CPUIdle latencies.
Uhh, are you sure about this? To me it sounds like you're then
relying on the code running from the cache for off-idle?
* Tony Lindgren [100924 11:53]:
> * Vishwanath BS [100924 03:50]:
> > There is no need to keep omap3 sleep code in SRAM. This code can be run very
> > well on DDR. This would help us to instrument CPUIdle latencies.
>
> Uhh, are you sure about this? To me it sounds like you're then
> relying on
I finally got to this and wrote up a summary of the contents of the ST-E BSP
that we are mirroring on the Linaro git server:
https://wiki.linaro.org/BSP/ST-Ericsson
I did not write up my recommendations of how to proceed, but it should give
an idea of the work in front of us/them.
Linus,
Vishwanath BS writes:
> This patch has done some clean up of omap3 sleep code.
> Basically all possible hardcodings are removed and code is Reorganized
> into more logical buckets for better readability and instrumentation.
>
> Tested on ZOOM3.
Again, please describe more about how it was tested
On Thu, 23 Sep 2010 15:42:34 -0300, Guilherme Salgado
wrote:
> Hi,
>
> I've recently changed l-m-c to take an hwpack, which is installed before
> the image is built. To keep that change simple I had to unpack the
> binary tarball into a tmp directory, install the hwpack, repack the
> tarball an
Vishwanath BS writes:
> There is no need to keep omap3 sleep code in SRAM.
> This code can be run very well on DDR.
/me remains skeptical
> This would help us to instrument CPUIdle latencies.
Indeed, but...
I'm afraid we will need a much more descriptive changelog here,
describing in detail
Enclosed you'll find a link to the agenda, notes and actions from the
Linaro User Platforms Weekly Status meeting dated 9/22 held in
#linaro-meeting on irc.freenode.net at 13:00 UTC.
https://wiki.linaro.org/Platform/UserPlatforms/WeeklyStatus/2010-09-22
Regards,
Tom (tgall_foo)
User Platforms Tea
the latest image so that I don't
>need to parse the HTML to get the latest build; something like
>/latest/ or /current/ would help here
> * having a constant name for the data as to be rsync friendly; that is,
>if the image is named linaro-m-headless-tar-20100923-0.tar.g
thing like
/latest/ or /current/ would help here
* having a constant name for the data as to be rsync friendly; that is,
if the image is named linaro-m-headless-tar-20100923-0.tar.gz and
linaro-m-headless-tar-20100924-0.tar.gz the next day, it's hard to
convince rsync that the dat
Hi
Notes from today's Landing Teams call; also at
https://wiki.linaro.org/LandingTeams/Meetings/2010-09-24
Cheers,
=== Attendees ===
* Loïc Minier
* Scott Bambrough
* Torez Smith
* Mounir Bsaibes
* Matt Waddel
=== Agenda ===
* Action items from last meeting.
* Achievements
This patch has done some clean up of omap3 sleep code.
Basically all possible hardcodings are removed and code is Reorganized
into more logical buckets for better readability and instrumentation.
Tested on ZOOM3.
Signed-off-by: Vishwanath BS
Cc: Kevin Hillman
Cc: linaro-dev@lists.linaro.org
--
There is no need to keep omap3 sleep code in SRAM. This code can be run very
well on DDR. This would help us to instrument CPUIdle latencies.
Tested on ZOOM3.
Signed-off-by: Vishwanath BS
Cc: Kevin Hillman
Cc: linaro-dev@lists.linaro.org
---
arch/arm/mach-omap2/pm34xx.c |9 +
1 fi
This patch series has some clean up in OMAP3 sleep code.
Patches have been rebased to latest kevin's pm branch.
Vishwanath BS (2):
OMAP3 PM: move omap3 sleep to ddr
OMAP3 PM: sleep code clean up
arch/arm/mach-omap2/pm34xx.c |9 +-
arch/arm/mach-omap2/sleep34xx.S |
14 matches
Mail list logo
