Re: [PATCH 2/2] usb: musb: notify USB_EVENT_ENUMERATED from musb_gadget_vbus_draw()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Sep 22, 2010 at 3:04 PM, Heikki Krogerus
<ext-heikki.krogerus@xxxxxxxxx> wrote:
>
> If I remove the 0mA condition, I'm seeing first 100mA notification
> then 0, 100 again and finally 500 from the configuration. This is a lot
> of notifications, but I guess you are correct. Let's remove all
> conditions.
>

Yes its true. I also see these notifications in this order (100,0,100,500).

It seems we get two RESET interrupts. On the first Reset
musb->g.speed is set to some value other than USB_SPEED_UNKNOWN.

When second Reset occurs due to the below code musb_g_disconnect()
gets called which is why we see that 0mA notification.

/* Code snippet from musb_g_reset() function */
 if (musb->g.speed != USB_SPEED_UNKNOWN) {
                musb_g_disconnect(musb);
 }

Regards,
Maulik
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux