Re: [PATCH 3/3] dma: cppi41: move -EAGAIN in tear_down

[Sebastian Andrzej Siewior <bigeasy@linutronix.de>]

On 10/02/2013 11:19 AM, Daniel Mack wrote:
> Hi Sebastian,

Hi Daniel,

> On 02.10.2013 10:29, Sebastian Andrzej Siewior wrote:
>> * Daniel Mack | 2013-10-01 15:31:11 [+0200]:
> 
> Thanks a lot for having a look! As I'm going to be off for a couple of
> days now, and only be able to read my mails sporadically, maybe you can
> also try the musb suspend functions on your hardware. I'll give you a
> quick wrap-up of how my test setup looks like.
> 
> On an AM33xx board, I have a host-only (type A) connector with a USB
> memory stick plugged in. The relevant config settings are:
> 
> CONFIG_USB_MUSB_HDRC=m
> # CONFIG_USB_MUSB_HOST is not set
> # CONFIG_USB_MUSB_GADGET is not set
> CONFIG_USB_MUSB_DUAL_ROLE=y
> # CONFIG_USB_MUSB_TUSB6010 is not set
> # CONFIG_USB_MUSB_OMAP2PLUS is not set
> # CONFIG_USB_MUSB_AM35X is not set
> CONFIG_USB_MUSB_DSPS=m
> # CONFIG_USB_MUSB_UX500 is not set
> CONFIG_USB_MUSB_AM335X_CHILD=m
> # CONFIG_MUSB_PIO_ONLY is not set
> CONFIG_USB_TI_CPPI41_DMA=y
> CONFIG_TI_CPPI41=y
> 
> Once the system is booted up and the USB media is detected, I send the
> system to sleep mode with "cat mem >/sys/power/state". After wakeup, I
> access the media by mounting and unmounting it once, then send the
> system back to sleep.

Okay. Going to sleep is probably easy, I need to figure out how to
wakeup…

> Repeating the above cycle multiple times will sooner or later make the
> warning kick in without the discussed patch. Sometimes it happened on
> first try, sometimes it took me up to ~20 cycles to make it happen.

Ah. Okay.

> I'd be curious whether you see the same behavior on your board as well,
> and whether the fix work for you, too.
> 
> For reference, I just pushed my current working tree here:
> 
>   https://github.com/zonque/linux/tree/am33xx-3.12

Thanks.

> 
> 
> Thanks,
> Daniel
> 
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html