From: Daniel Mack <daniel@zonque.org>
To: Sekhar Nori <nsekhar@ti.com>, Dave Gerlach <d-gerlach@ti.com>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Cc: Tony Lindgren <tony@atomide.com>, Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH v7 RESEND] ARM: omap: edma: add suspend suspend/resume hooks
Date: Tue, 26 Aug 2014 10:46:56 +0200 [thread overview]
Message-ID: <53FC4980.1070606@zonque.org> (raw)
In-Reply-To: <53FC2AD4.4070400@ti.com>
Hi,
On 08/26/2014 08:36 AM, Sekhar Nori wrote:
> On Friday 22 August 2014 01:16 PM, Dave Gerlach wrote:
Thanks for pushing that forward!
>> +static int edma_pm_suspend(struct device *dev)
>> +{
>> + int j, r;
>> +
>> + r = pm_runtime_get_sync(dev);
>> + if (r < 0) {
>> + dev_err(dev, "%s: get_sync returned %d\n", __func__, r);
>> + return r;
>> + }
>
> The driver currently does a pm_runtime_get_sync() once during probe. And
> does not do a put(). So this should actually be not required. In fact
> looks like this additional get() call will prevent the clock from
> getting disabled which is probably not what you intend.
Well, the pm runtime is put again ...
>> +
>> + for (j = 0; j < arch_num_cc; j++) {
>> + struct edma *ecc = edma_cc[j];
>> +
>> + disable_irq(ecc->irq_res_start);
>> + disable_irq(ecc->irq_res_end);
>
> Do we really need to disable these irqs?
>
>> + }
>> +
>> + pm_runtime_put_sync(dev);
... here, so it's in sync and should be fine.
I was also sure than when I wrote the code, disabling the interrupts
during suspend was necessary, and even the only thing that has to be
done at suspend time. Now that I address this again, my tests show that
in can in fact be omitted.
So I'll send a v9 now that has no edma_pm_suspend() at all anymore.
>> +static const struct dev_pm_ops edma_pm_ops = {
>> + .suspend_late = edma_pm_suspend,
>> + .resume_early = edma_pm_resume,
>> +};
>
> You can use SET_LATE_SYSTEM_SLEEP_PM_OPS() as some other DMA drivers are
> doing too.
Sure, why not.
Thanks,
Daniel
WARNING: multiple messages have this Message-ID (diff)
From: daniel@zonque.org (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 RESEND] ARM: omap: edma: add suspend suspend/resume hooks
Date: Tue, 26 Aug 2014 10:46:56 +0200 [thread overview]
Message-ID: <53FC4980.1070606@zonque.org> (raw)
In-Reply-To: <53FC2AD4.4070400@ti.com>
Hi,
On 08/26/2014 08:36 AM, Sekhar Nori wrote:
> On Friday 22 August 2014 01:16 PM, Dave Gerlach wrote:
Thanks for pushing that forward!
>> +static int edma_pm_suspend(struct device *dev)
>> +{
>> + int j, r;
>> +
>> + r = pm_runtime_get_sync(dev);
>> + if (r < 0) {
>> + dev_err(dev, "%s: get_sync returned %d\n", __func__, r);
>> + return r;
>> + }
>
> The driver currently does a pm_runtime_get_sync() once during probe. And
> does not do a put(). So this should actually be not required. In fact
> looks like this additional get() call will prevent the clock from
> getting disabled which is probably not what you intend.
Well, the pm runtime is put again ...
>> +
>> + for (j = 0; j < arch_num_cc; j++) {
>> + struct edma *ecc = edma_cc[j];
>> +
>> + disable_irq(ecc->irq_res_start);
>> + disable_irq(ecc->irq_res_end);
>
> Do we really need to disable these irqs?
>
>> + }
>> +
>> + pm_runtime_put_sync(dev);
... here, so it's in sync and should be fine.
I was also sure than when I wrote the code, disabling the interrupts
during suspend was necessary, and even the only thing that has to be
done at suspend time. Now that I address this again, my tests show that
in can in fact be omitted.
So I'll send a v9 now that has no edma_pm_suspend() at all anymore.
>> +static const struct dev_pm_ops edma_pm_ops = {
>> + .suspend_late = edma_pm_suspend,
>> + .resume_early = edma_pm_resume,
>> +};
>
> You can use SET_LATE_SYSTEM_SLEEP_PM_OPS() as some other DMA drivers are
> doing too.
Sure, why not.
Thanks,
Daniel
next prev parent reply other threads:[~2014-08-26 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 7:46 [PATCH v7 RESEND] ARM: omap: edma: add suspend suspend/resume hooks Dave Gerlach
2014-08-22 7:46 ` Dave Gerlach
2014-08-26 6:36 ` Sekhar Nori
2014-08-26 6:36 ` Sekhar Nori
2014-08-26 8:46 ` Daniel Mack [this message]
2014-08-26 8:46 ` Daniel Mack
2014-08-26 9:02 ` Sekhar Nori
2014-08-26 9:02 ` Sekhar Nori
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=53FC4980.1070606@zonque.org \
--to=daniel@zonque.org \
--cc=d-gerlach@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=nsekhar@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 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.