From: Sekhar Nori <nsekhar@ti.com>
To: Daniel Mack <daniel@zonque.org>, d-gerlach@ti.com
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
tony@atomide.com, nm@ti.com
Subject: Re: [PATCH v9] ARM: omap: edma: add suspend resume hook
Date: Mon, 17 Nov 2014 20:33:39 +0530 [thread overview]
Message-ID: <546A0E4B.5000901@ti.com> (raw)
In-Reply-To: <546636C3.8070202@zonque.org>
On Friday 14 November 2014 10:37 PM, Daniel Mack wrote:
> Hi Sekhar,
>
> On 11/14/2014 06:03 PM, Sekhar Nori wrote:
>> I think I have asked this before, and I am still not sure why this call
>> to pm_runtime_get_sync() is needed here. From my testing today, this
>> does seem to be a a no-op and this call returns from rpm_resume()
>> because of this check:
>>
>> else if (dev->power.disable_depth == 1 && dev->power.is_suspended
>> && dev->power.runtime_status == RPM_ACTIVE)
>> retval = 1;
>
> Yes. IIRC, it was in fact not needed.
>
>> So, AFAICS, the net effect is an increment of dev->power.usage_count
>> (which is already greater than 0) and its subsequent decrement at the
>> end of the function.
>>
>> After removing this call I did not see any EDMA malfunction as well
>> (can access MMC/SD just fine after suspend/resume cycle).
>>
>> So, any objections to merging this patch with the attached hunk
>> applied?
>
> Looks good to me, we can still add it back later if it turns out to be
> needed.
Okay, thanks for the confirmation.
Regards,
Sekhar
prev parent reply other threads:[~2014-11-17 15:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 8:52 [PATCH v9] ARM: omap: edma: add suspend resume hook Daniel Mack
2014-11-05 15:57 ` Dave Gerlach
2014-11-05 16:04 ` Sekhar Nori
2014-11-05 18:10 ` Dave Gerlach
2014-11-06 8:33 ` Sekhar Nori
2014-11-06 14:36 ` Dave Gerlach
2014-11-14 17:03 ` Sekhar Nori
2014-11-14 17:07 ` Daniel Mack
2014-11-17 15:03 ` Sekhar Nori [this message]
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=546A0E4B.5000901@ti.com \
--to=nsekhar@ti.com \
--cc=d-gerlach@ti.com \
--cc=daniel@zonque.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.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).