Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: Kevin Cernekee <cernekee@gmail.com>
Cc: balbi@ti.com, ralf@linux-mips.org, sebastian@breakpoint.cc,
	stern@rowland.harvard.edu, linux-mips@linux-mips.org,
	linux-usb@vger.kernel.org
Subject: Re: [PATCH V3] usb: gadget: bcm63xx UDC driver
Date: Wed, 22 Aug 2012 09:48:15 +0200	[thread overview]
Message-ID: <20120822074815.GB3563@breakpoint.cc> (raw)
In-Reply-To: <5ff8f23aae05690ba89476c4924b9387@localhost>

On Tue, Aug 21, 2012 at 06:22:35PM -0700, Kevin Cernekee wrote:

Just one thing that bit while I was sleeping:
The HW acks SetConfig on its own. Once you notice this, you set
->ep0_req_set_cfg and set state in bcm63xx_ep0_do_idle() to
EP0_IN_FAKE_STATUS_PHASE. This is I guess the workaround for mass_storage's
hold with DELAYED_STATUS and continues with a zero packet.
Now two questions:
- If a gadget descides not NAK / stall the SetConfig requests. What happens
  here?
- What happens if the host is faster than the UDC. SetConfig returns in
  usb-storage with "DELAYED_STATUS". HW Acks this. Could the Host send another
  request before the gadget queues the ep0 request?

Sebastian

  reply	other threads:[~2012-08-22  7:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22  1:22 [PATCH V3] usb: gadget: bcm63xx UDC driver Kevin Cernekee
2012-08-22  7:48 ` Sebastian Andrzej Siewior [this message]
2012-08-25 19:44   ` Kevin Cernekee
2012-08-25 20:48     ` Alan Stern
2012-08-25 20:48       ` Alan Stern
2012-08-26 19:30     ` Sebastian Andrzej Siewior

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=20120822074815.GB3563@breakpoint.cc \
    --to=sebastian@breakpoint.cc \
    --cc=balbi@ti.com \
    --cc=cernekee@gmail.com \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=stern@rowland.harvard.edu \
    /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