linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org
Subject: [GIT PULL] USB fixes for v5.7-rc2
Date: Sun, 19 Apr 2020 10:51:24 +0300	[thread overview]
Message-ID: <87eesjdibn.fsf@kernel.org> (raw)

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


Hi Greg,

here's the first pull request for the current -rc cycle. Patches have
been in next for a few days without any new reports.

Let me know if you want anything to be changed.

Cheers

The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:

  Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git tags/fixes-for-v5.7-rc2

for you to fetch changes up to a7b778357ca48df71bbaad6612beaca30bd96e54:

  usb: raw-gadget: Fix copy_to/from_user() checks (2020-04-17 12:26:26 +0300)

----------------------------------------------------------------
USB: fixes for v5.7-rc2

DWC3 learns how to properly set maxpacket limit and got a fix for a
request completion bug. The raw gadget got a fix for
copy_to/from_user() checks. Atmel got an improvement on vbus
disconnect handling.

We're also adding support for another SoC to the Renesas DRD driver.

----------------------------------------------------------------
Andrey Konovalov (1):
      usb: raw-gadget: fix raw_event_queue_fetch locking

Cristian Birsan (1):
      usb: gadget: udc: atmel: Fix vbus disconnect handling

Dan Carpenter (1):
      usb: raw-gadget: Fix copy_to/from_user() checks

Mauro Carvalho Chehab (1):
      docs: dt: qcom,dwc3.txt: fix cross-reference for a converted file

Nathan Chancellor (1):
      usb: gadget: udc: bdc: Remove unnecessary NULL checks in bdc_req_complete

Thinh Nguyen (4):
      usb: dwc3: Fix GTXFIFOSIZ.TXFDEP macro name
      usb: dwc3: gadget: Properly set maxpacket limit
      usb: dwc3: gadget: Do link recovery for SS and SSP
      usb: dwc3: gadget: Fix request completion check

Yoshihiro Shimoda (3):
      dt-bindings: usb: usb-xhci: add r8a77961 support
      dt-bindings: usb: renesas,usbhs: add r8a77961 support
      dt-bindings: usb: renesas,usb3-peri: add r8a77961 support

 .../devicetree/bindings/usb/qcom,dwc3.txt          |  4 +-
 .../devicetree/bindings/usb/renesas,usb3-peri.yaml |  1 +
 .../devicetree/bindings/usb/renesas,usbhs.yaml     |  1 +
 Documentation/devicetree/bindings/usb/usb-xhci.txt |  3 +-
 drivers/usb/dwc3/core.h                            |  8 ++-
 drivers/usb/dwc3/gadget.c                          | 76 +++++++++++++---------
 drivers/usb/gadget/legacy/raw_gadget.c             | 71 +++++++++++---------
 drivers/usb/gadget/udc/atmel_usba_udc.c            |  4 +-
 drivers/usb/gadget/udc/bdc/bdc_ep.c                |  2 +-
 9 files changed, 104 insertions(+), 66 deletions(-)

-- 
balbi

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

             reply	other threads:[~2020-04-19  7:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19  7:51 Felipe Balbi [this message]
2020-04-20 11:30 ` [GIT PULL] USB fixes for v5.7-rc2 Greg Kroah-Hartman

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=87eesjdibn.fsf@kernel.org \
    --to=balbi@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    /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).