From: "G, Manjunath Kondaiah" <manjugk@ti.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk
Cc: khilman@deeprootsystems.com, paul@pwsan.com, tony@atomide.com
Subject: [PATCH v2 0/4] OMAP: DMA: mstandby mode and runtime pm support
Date: Fri, 11 Mar 2011 19:50:11 +0530 [thread overview]
Message-ID: <1299853215-8507-1-git-send-email-manjugk@ti.com> (raw)
Patch series to support mstandby mode handling and enabling runtime PM
support for DMA driver.
Changes from v1:
- fixed runtime_status issue if channel linking feature is used.
- fixed context restore issue during off mode.
- removed sysconfig register access during DMA context/restore
The review comments and alignment can be found at:
http://thread.gmane.org/gmane.linux.ports.arm.omap/53150
Baseline:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git
Branch: omap-for-linus
commit 94a06b74e724caabcf0464c81527cfbcae0c8aff
Merge: 0dde52a 9062511
Author: Tony Lindgren <tony@atomide.com>
Note: For OMAP2420 and OMAP2430, the patch series is tested on top of
v2.6.38-rc4 since boot fails with latest mainline for the above OMAP's.
Build:
- omap1_defconfig
- omap2plus_defconfig
Boot test:
- OMAP1710 H3
- OMAP2420 H4
- OMAP2430 SDP
- OMAP3430 Zoom2
- OMAP3630 Zoom3
- OMAP4430 Blaze
DMA tests:
The following dma test code is used for testing OMAP2+ boards:
git://gitorious.org/omap-test/dmatest.git
Apart from that, offmode testing is done for OMAP3430-Zoom2 using the procedure:
echo 1 > /debug/pm_debug/sleep_while_idle
echo 1 > /debug/pm_debug/enable_off_mode
echo 5 > /sys/devices/platform/omap/omap_uart.0/sleep_timeout
echo 5 > /sys/devices/platform/omap/omap_uart.1/sleep_timeout
echo 5 > /sys/devices/platform/omap/omap_uart.2/sleep_timeout
With the above steps, core off mode count gets increasing if the the board
is idle for more than 5 seconds.
Also, DMA transfers are done with forever option using:
insmod ./dmatest.ko linking=1 forever=1 forever_period=1024 debug=1
The /sys/devices/platform/omap/omap_dma_system.0/power/runtime_status
was verified and after completion of the tests, runtime_status will be
always suspended.
(Special thanks to Kevin Hilman for identifying runtime_status count issue
with DMA linking option).
G, Manjunath Kondaiah (4):
OMAP2+: PM: omap device: API's for handling mstandby mode
OMAP2+: DMA: prevent races while setting M idle mode to nostandby
OMAP: PM: DMA: Enable runtime pm
OMAP: DMA: Fix: context restore during off mode
arch/arm/mach-omap1/dma.c | 1 +
arch/arm/mach-omap2/dma.c | 16 ++
arch/arm/mach-omap2/omap_hwmod.c | 42 ++++++
arch/arm/plat-omap/dma.c | 194 +++++++++++++++++++++----
arch/arm/plat-omap/include/plat/dma.h | 1 +
arch/arm/plat-omap/include/plat/omap_device.h | 2 +
arch/arm/plat-omap/include/plat/omap_hwmod.h | 4 +-
arch/arm/plat-omap/omap_device.c | 64 ++++++++
8 files changed, 293 insertions(+), 31 deletions(-)
next reply other threads:[~2011-03-11 14:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 14:20 G, Manjunath Kondaiah [this message]
2011-03-11 14:20 ` [PATCH v2 1/4] OMAP2+: PM: omap device: API's for handling mstandby mode G, Manjunath Kondaiah
2011-03-11 14:20 ` [PATCH v2 2/4] OMAP2+: DMA: prevent races while setting M idle mode to nostandby G, Manjunath Kondaiah
2011-03-11 14:20 ` [PATCH v2 3/4] OMAP: PM: DMA: Enable runtime pm G, Manjunath Kondaiah
2011-03-11 14:20 ` [PATCH v2 4/4] OMAP: DMA: Fix: context restore during off mode G, Manjunath Kondaiah
2011-03-17 21:08 ` Kevin Hilman
2011-03-19 3:20 ` G, Manjunath Kondaiah
2011-03-16 14:38 ` [PATCH v2 0/4] OMAP: DMA: mstandby mode and runtime pm support G, Manjunath Kondaiah
2011-03-17 21:29 ` Kevin Hilman
2011-03-18 10:00 ` G, Manjunath Kondaiah
2011-03-18 18:27 ` Kevin Hilman
2011-03-19 3:16 ` G, Manjunath Kondaiah
2011-03-23 12:12 ` G, Manjunath Kondaiah
2011-03-23 14:11 ` Kevin Hilman
2011-03-23 15:29 ` Kevin Hilman
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=1299853215-8507-1-git-send-email-manjugk@ti.com \
--to=manjugk@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).