From: Kevin Hilman <khilman@deeprootsystems.com>
To: "G, Manjunath Kondaiah" <manjugk@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Issue observed with pm_runtime_put_sync
Date: Mon, 18 Oct 2010 08:30:53 -0700 [thread overview]
Message-ID: <87k4lfecwi.fsf@deeprootsystems.com> (raw)
In-Reply-To: <E0D41E29EB0DAC4E9F3FF173962E9E9402DBC61359@dbde02.ent.ti.com> (Manjunath Kondaiah G.'s message of "Mon, 18 Oct 2010 13:30:30 +0530")
Manjunath,
"G, Manjunath Kondaiah" <manjugk@ti.com> writes:
> While using pm runtime API's with DMA, it was observed that, during
> omap_free_dma, pm_runtime_put_sync is called which results in warning
> dump. It looks like, when cpu idle patch is under processing, DMA
> interrupt gets fired which inturn call omap_free_dma which results
> multiple spin_locks.
>
> The DMA driver uses *_get_sync during omap_request_dma and *_put_sync during
> omap_free_dma.
>
> Environment:
> Kernel:
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git
> Branch: master
> Commit: 99cf630 Linux-omap rebuilt: Fixed omap4 kernel panic without nosmp,
> updated to -rc7
> +
> DMA hwmod patches
>
> defconfig: omap2plus_defconfig
> board: OMAP3630 Zoom3
>
> Is this a known issue or issue with pm runtime API usage in DMA driver?
It's an issue in the runtime PM usage in DMA driver.
Specifically, the _sync versions of the API cannot be used from
interrupt context because they can sleep.
Are the _sync versions really needed at that point? Without having the
code, I cannot tell, but I susupect that the async versions could be
used there instead.
If not, then the code will need to be reworked so the ISR is not doing
the actual work, but instead is scheduling work to be done later in
process context.
Kevin
next parent reply other threads:[~2010-10-18 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E0D41E29EB0DAC4E9F3FF173962E9E9402DBC61359@dbde02.ent.ti.com>
2010-10-18 15:30 ` Kevin Hilman [this message]
2010-10-18 16:00 ` Issue observed with pm_runtime_put_sync G, Manjunath Kondaiah
2010-10-18 16:11 ` Shilimkar, Santosh
2010-10-18 18:44 ` G, Manjunath Kondaiah
2010-10-18 21:42 ` Kevin Hilman
2010-10-19 5:15 ` G, Manjunath Kondaiah
2010-10-18 21:38 ` Kevin Hilman
2010-10-18 8:19 G, Manjunath Kondaiah
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=87k4lfecwi.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=manjugk@ti.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.