linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jassisinghbrar@gmail.com
To: balbi@kernel.org, gregkh@linuxfoundation.org, robh+dt@kernel.org,
	mark.rutland@arm.com
Cc: devicetree@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Jassi Brar <jaswinder.singh@linaro.org>
Subject: [PATCH v2 0/2] Max3420 udc driver
Date: Sun,  5 Jan 2020 16:55:09 -0600	[thread overview]
Message-ID: <20200105225509.21590-1-jassisinghbrar@gmail.com> (raw)

From: Jassi Brar <jaswinder.singh@linaro.org>

Changes since v1:
 # No functional changes, just cosmetic changes as suggested in review.
   o prepend everything with MAX3420_
   o avoid CaMeLcAsE
   o use GENMASK some more
   o reorder struct max3420_ep and struct max3420_udc members
   o added some comments
   o changed license in dt-bindings
   o changed interrupt property to names

Jassi Brar (2):
  dt-bindings: max3421-udc: add dt bindings for MAX3420 UDC
  usb: gadget: add udc driver for max3420

 .../bindings/usb/maxim,max3420-udc.yaml       |   69 +
 drivers/usb/gadget/udc/Kconfig                |   10 +
 drivers/usb/gadget/udc/Makefile               |    1 +
 drivers/usb/gadget/udc/max3420_udc.c          | 1333 +++++++++++++++++
 4 files changed, 1413 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/usb/maxim,max3420-udc.yaml
 create mode 100644 drivers/usb/gadget/udc/max3420_udc.c

-- 
2.20.1


             reply	other threads:[~2020-01-05 22:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-05 22:55 jassisinghbrar [this message]
2020-01-05 22:55 ` [PATCH v2 1/2] dt-bindings: max3421-udc: add dt bindings for MAX3420 UDC jassisinghbrar
2020-01-06 22:18   ` Rob Herring
2020-01-05 22:55 ` [PATCH v2 2/2] usb: gadget: add udc driver for max3420 jassisinghbrar
2020-01-08 16:41   ` Greg KH
2020-01-08 21:13     ` Jassi Brar

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=20200105225509.21590-1-jassisinghbrar@gmail.com \
    --to=jassisinghbrar@gmail.com \
    --cc=balbi@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jaswinder.singh@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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).