linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: Dave Gerlach <d-gerlach@ti.com>, Daniel Mack <zonque@gmail.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: Thu, 6 Nov 2014 14:03:31 +0530	[thread overview]
Message-ID: <545B325B.4050109@ti.com> (raw)
In-Reply-To: <545A682F.4060306@ti.com>

On Wednesday 05 November 2014 11:40 PM, Dave Gerlach wrote:
> Sekhar,
> On 11/05/2014 10:04 AM, Sekhar Nori wrote:
>> On Wednesday 05 November 2014 09:27 PM, Dave Gerlach wrote:
>>> On 08/26/2014 03:52 AM, Daniel Mack wrote:
>>>> This patch makes the edma driver resume correctly after suspend. Tested
>>>> on an AM33xx platform with cyclic audio streams and omap_hsmmc.
>>>>
>>>> All information can be reconstructed by already known runtime
>>>> information.
>>>>
>>>> As we now use some functions that were previously only used from __init
>>>> context, annotations had to be dropped.
>>>>
>>>> [nm@ti.com: added error handling for runtime + suspend_late/early_resume]
>>>> Signed-off-by: Nishanth Menon <nm@ti.com>
>>>> Signed-off-by: Daniel Mack <zonque@gmail.com>
>>>> Tested-by: Joel Fernandes <joelf@ti.com>
>>>> Acked-by: Joel Fernandes <joelf@ti.com>
>>>> ---
>>>> Changes from v8:
>>>>
>>>> 	* Drop the edma_suspend hook altogether. Even though back then
>>>> 	  when I wrote the code I was sure disabling the interrupts
>>>> 	  during suspend is necessary, tests now show it in fact isn't.
>>>> 	  My test setup still works if that code is omitted.
>>>> 	* Use SET_LATE_SYSTEM_SLEEP_PM_OPS in the dev_pm_ops
>>>> 	  declaration.
>>>>
>>>> 	Thanks to Sekhar for pointing out the above.
>>>>
>>>>  arch/arm/common/edma.c | 60 ++++++++++++++++++++++++++++++++++++++++++++++++--
>>>>  1 file changed, 58 insertions(+), 2 deletions(-)
>>>
>>> Doesn't seem to be any comments here, any chance this can be picked up? This
>>> patch always seems to get missed but will be needed for suspend/resume on both
>>> AM335x and AM437x.
>>
>> Dave, do you have a branch against mainline with suspend working on any
>> of these SoCs using which I can test this patch?
> 
> Yes, here is WIP of next version with all required patches + this one.
> https://github.com/dgerlach/linux-pm/tree/pm-ds0-v3.18-rc3-WIP
> 
> For suspend to work you need to select:
> 
> CONFIG_WKUP_M3_IPC=y
> CONFIG_WKUP_M3_RPROC=y

I get this:

arch/arm/mach-omap2/pm33xx.c:28:31: fatal error: linux/wkup_m3_ipc.h: No such file or directory
 #include <linux/wkup_m3_ipc.h>
                               ^
compilation terminated.
make[1]: *** [arch/arm/mach-omap2/pm33xx.o] Error 1

Forgot to commit wkup_m3_ipc.h?

Thanks,
Sekhar
 


  reply	other threads:[~2014-11-06  8:33 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 [this message]
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

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=545B325B.4050109@ti.com \
    --to=nsekhar@ti.com \
    --cc=d-gerlach@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=tony@atomide.com \
    --cc=zonque@gmail.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).