All of lore.kernel.org
 help / color / mirror / Atom feed
From: sr@denx.de (Stefan Roese)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: omap2: fix musb usage for n8x0
Date: Thu, 18 Jul 2013 14:38:09 +0200	[thread overview]
Message-ID: <51E7E1B1.4070407@denx.de> (raw)
In-Reply-To: <51E7D950.60900@gmail.com>

On 07/18/2013 02:02 PM, Daniel Mack wrote:
> On 18.07.2013 11:40, Stefan Roese wrote:
>> On 07/18/2013 11:18 AM, Kishon Vijay Abraham I wrote:
>>>> I'm testing musb as OTG on beagleboard (old one, not Beagle-xm). And
>>>> using the latest kernel.org version with this patch applied I see the
>>>> following messages while booting (repeatedly):
>>>>
>>>> [    4.998168] usb usb1: bus auto-suspend, wakeup 1
>>>> [    5.003112] musb_bus_suspend 2457: trying to suspend as b_idle while active
>>>> [    5.010498] usb usb1: bus suspend fail, err -16
>>>> [    5.015289] hub 1-0:1.0: hub_resume
>>>> [    5.019073] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
>>>> [    5.024963] hub 1-0:1.0: hub_suspend
>>>> [    5.028778] usb usb1: bus auto-suspend, wakeup 1
>>>> ...
>>>>
>>>> This is without a cable connected to the OTG port.
>>>>
>>>> Any ideas what might be missing here?
>>>
>>> Even I observed these prints when I have dual mode enabled. When kept as gadget
>>> only mode I dint see these prints.
>>
>> Yes. With gadget-only I don't see those messages. Thanks for the hint.
> 
> So in which mode does your port operate then? Gadget or dual-role?

Its the original Beagleboard (revision C2), so I suppose its dual-role.
Or am I mistaken here?

> And I
> take it this does not happen with 3.10?

I just checked v3.10 as again. No, I'm not seeing these messages here.

Thanks,
Stefan

      reply	other threads:[~2013-07-18 12:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16 18:52 [PATCH] ARM: omap2: fix musb usage for n8x0 Daniel Mack
2013-07-16 20:03 ` Felipe Balbi
2013-07-18  9:14 ` Stefan Roese
2013-07-18  9:18   ` Kishon Vijay Abraham I
2013-07-18  9:40     ` Stefan Roese
2013-07-18 12:02       ` Daniel Mack
2013-07-18 12:38         ` Stefan Roese [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=51E7E1B1.4070407@denx.de \
    --to=sr@denx.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.