linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "G, Manjunath Kondaiah" <manjugk@ti.com>
To: Kevin Hilman <khilman@ti.com>
Cc: "G, Manjunath Kondaiah" <manjugk@ti.com>,
	linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.arm.linux.org.uk, paul@pwsan.com,
	tony@atomide.com
Subject: Re: [PATCH v2 0/4] OMAP: DMA: mstandby mode and runtime pm support
Date: Fri, 18 Mar 2011 15:30:12 +0530	[thread overview]
Message-ID: <20110318095925.GA13784@m-desktop> (raw)
In-Reply-To: <87lj0dwi4x.fsf@ti.com>

On Thu, Mar 17, 2011 at 02:29:18PM -0700, Kevin Hilman wrote:
> "G, Manjunath Kondaiah" <manjugk@ti.com> writes:
> 
> > Patch series to support mstandby mode handling and enabling runtime PM
> > support for DMA driver.
> 
> I still have the same problems as with the previous revision: 
> 
> 
> This is still not runtime-suspending when I use my DMA test in linking
> mode.
> 
> If I put a large enough period between transfers, it should autosuspend
> during transfers.  It seems to do auto-suspend and resume once, but then
> it never suspends again.
> 
> I tested with my dmatest module[1], and loaded with:
> 
>   # insmod ./dmatest.ko linking=1 forever=1 forever_period=1024
> 
> Not only does it not auto-suspend between transfers (which I expected),
> it also doesn't suspend after removing the module which stops all active
> channels.

Tested again on 2.6.38 with patches pulled from patchworks and for me,
the same test case seems to be passing. Here is the log:
http://pastebin.com/ccEmTZS5

The above test case is executed on blaze and same result is observed
with other OMAP2+ boards also.

Can you please let me know which board and code base you are using for
testing so that I can try to replicate the same.

-Manjunath
> 

  reply	other threads:[~2011-03-18 10:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 14:20 [PATCH v2 0/4] OMAP: DMA: mstandby mode and runtime pm support G, Manjunath Kondaiah
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 [this message]
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=20110318095925.GA13784@m-desktop \
    --to=manjugk@ti.com \
    --cc=khilman@ti.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).