public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Dahlmann <dahlmann.thomas@arcor.de>
To: Vadim Lobanov <vlobanov@speakeasy.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: amd5536udc interrupts bug
Date: Mon, 19 Jan 2009 13:23:40 +0100	[thread overview]
Message-ID: <497470CC.6070202@arcor.de> (raw)
In-Reply-To: <200901161617.18351.vlobanov@speakeasy.net>


>> Unfortunately this bit is not the complete solution for your problem.
>> When setting PUE then connect and disconnect events cannot be
>> detected by UDC. If you disconnect and connect again you
>> probably will notice that there will be no new enumeration as
>> expected.
> 
> Interestingly enough, when running in this configuration, unplugging and 
> replugging the cable does cause a re-enumeration. Hmmmm.
> 
> -- Vadim Lobanov
> 

Ah, I see. So PUE would be OK so far. I assume this worked as host
recognizes a disconnect/connect and performs a USB reset. USB reset
has almost the same effect as disconnect/connect on device side.

Thomas


  reply	other threads:[~2009-01-19 12:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49661E83.2070703@arcor.de>
2009-01-08 16:40 ` amd5536udc interrupts bug Thomas Dahlmann
2009-01-08 18:27   ` Vadim Lobanov
2009-01-09  2:02   ` Vadim Lobanov
2009-01-09 11:41     ` Thomas Dahlmann
2009-01-09 22:40       ` Vadim Lobanov
2009-01-10 20:28         ` Thomas Dahlmann
2009-01-12 19:02           ` Vadim Lobanov
2009-01-13 19:19           ` Vadim Lobanov
2009-01-14 12:43             ` Thomas Dahlmann
2009-01-14 22:49               ` Vadim Lobanov
2009-01-15  9:26                 ` Thomas Dahlmann
2009-01-17  0:17                   ` Vadim Lobanov
2009-01-19 12:23                     ` Thomas Dahlmann [this message]
2009-01-07 23:10 Vadim Lobanov
2009-01-08  2:32 ` Robert Hancock
2009-01-08  3:30   ` Vadim Lobanov

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=497470CC.6070202@arcor.de \
    --to=dahlmann.thomas@arcor.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vlobanov@speakeasy.net \
    /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