public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: sundeep subbaraya <sundeep.lkml@gmail.com>
Cc: Paul Zimmerman <Paul.Zimmerman@synopsys.com>,
	"balbi@ti.com" <balbi@ti.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: query on DWC3
Date: Mon, 22 Dec 2014 10:11:23 -0600	[thread overview]
Message-ID: <20141222161123.GE12815@saruman> (raw)
In-Reply-To: <CALHRZupFbTxTn9KiUCmvcmgYxUUcNfvAoMqOq=Drq0gZ+H246w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 838 bytes --]

Hi,

(please don't top-post)

On Sun, Dec 14, 2014 at 08:39:18AM +0530, sundeep subbaraya wrote:
> Hi Paul,
> 
> As per my understanding, for BULK OUT we do queue a request with 512
> bytes length since we do not

sometimes we _do_ know the size. In case of Mass Storage, we _know_ that
the first bulk out transfer will be 31-bytes (CBW), if we were to start
a 31-byte transfer, we would't receive anything.

> know the length of the transfer Host is going to send. For Control OUT
> we know the length in wLength of
> Setup packet, hence I assumed there is no difference in programming
> model of Control IN and OUT.

there is _no_ difference. It's just that it was agreed that for anything
other than control ep, the function drivers would take care of it. See
the uses of quirk_ep_out_aligned_size.

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-12-22 16:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-13  5:13 query on DWC3 sundeep subbaraya
2014-12-13 23:51 ` Paul Zimmerman
2014-12-14  3:09   ` sundeep subbaraya
2014-12-22 16:11     ` Felipe Balbi [this message]
2014-12-22 16:12       ` Felipe Balbi
2015-01-06  7:09         ` sundeep subbaraya
2015-01-08 16:57           ` Felipe Balbi
2015-01-19  6:05             ` sundeep subbaraya

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=20141222161123.GE12815@saruman \
    --to=balbi@ti.com \
    --cc=Paul.Zimmerman@synopsys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sundeep.lkml@gmail.com \
    /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