linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Alan Stern <stern@rowland.harvard.edu>,
	Paul Elder <paul.elder@ideasonboard.com>
Cc: USB list <linux-usb@vger.kernel.org>
Subject: Re: Explicit status-stage requests for USB gadgets
Date: Tue, 16 Apr 2019 11:10:04 +0300	[thread overview]
Message-ID: <87y34a8j6r.fsf@linux.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1904151439210.1575-100000@iolanthe.rowland.org>

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


Hi Alan,

Alan Stern <stern@rowland.harvard.edu> writes:
> I finally took the time to put more work into the explicit-status-stage
> project.  Now I've got patches adding support to both dummy-hcd and
> net2280.  (The two patches for net2280 I sent earlier today address
> unrelated issues that turned up while this work was under way.)  Along
> with Paul's work on musb, it seems like a good start and worth merging.

Thanks for doing all the work.

> Getting someone to do the same for dwc2 and dwc3 shouldn't be very 
> hard, but they are out of my ballpark.

I can do dwc3, no problem.

> Paul, there is one change I think we should make to your original core
> patch.  usb_gadget_control_complete() should not check request->length,
> because it has to be possible for a gadget driver to send a zero-length
> reply as the data stage for a control-IN request and still get an 
> implicit status-stage request.
>
> Aside from that, everything seems to be ready to move forward.
>
> Felipe, any comments?

I haven't had time to look at the patches yet due to some internal
projects happening at this moment. I'll try to get to them still this
week.

-- 
balbi

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2019-04-16  8:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 20:19 Explicit status-stage requests for USB gadgets Alan Stern
2019-04-16  8:10 ` Felipe Balbi [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=87y34a8j6r.fsf@linux.intel.com \
    --to=felipe.balbi@linux.intel.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=paul.elder@ideasonboard.com \
    --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;
as well as URLs for NNTP newsgroup(s).