From: richard.yu@hpe.com
To: verdun@hpe.com, nick.hawkins@hpe.com, gregkh@linuxfoundation.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, richard.yu@hpe.com,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/3] Add USB driver for HPE GXP Architecture
Date: Thu, 6 Jul 2023 16:59:07 -0500 [thread overview]
Message-ID: <20230706215910.78772-1-richard.yu@hpe.com> (raw)
From: Richard Yu <richard.yu@hpe.com>
The GXP vEHCI controller presents a four port EHCI compatible PCI function
to host software. Each EHCI port is logically connected to a
corresponding set of virtual device registers.
Richard Yu (3):
dt-bindings: usb: Add HPE GXP UDCG Controller
usb: gadget: udc: gxp-udc: add HPE GXP USB support
MAINTAINERS: add USB support to GXP
.../devicetree/bindings/usb/hpe,gxp-udcg.yaml | 70 +
MAINTAINERS | 2 +
drivers/usb/gadget/udc/Kconfig | 6 +
drivers/usb/gadget/udc/Makefile | 1 +
drivers/usb/gadget/udc/gxp-udc.c | 1401 +++++++++++++++++
5 files changed, 1480 insertions(+)
create mode 100644 Documentation/devicetree/bindings/usb/hpe,gxp-udcg.yaml
create mode 100644 drivers/usb/gadget/udc/gxp-udc.c
--
2.17.1
next reply other threads:[~2023-07-06 22:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 21:59 richard.yu [this message]
2023-07-06 21:59 ` [PATCH v1 1/3] dt-bindings: usb: Add HPE GXP UDCG Controller richard.yu
2023-07-07 8:27 ` Krzysztof Kozlowski
2023-08-01 18:07 ` Yu, Richard
2023-08-05 19:08 ` Krzysztof Kozlowski
2023-08-09 15:52 ` Yu, Richard
2023-08-19 18:30 ` Krzysztof Kozlowski
2023-08-23 16:07 ` Yu, Richard
2023-08-24 6:31 ` Krzysztof Kozlowski
2023-07-06 21:59 ` [PATCH v1 2/3] usb: gadget: udc: gxp-udc: add HPE GXP USB support richard.yu
2023-07-07 2:16 ` Alan Stern
2023-08-01 18:50 ` Yu, Richard
2023-07-07 6:07 ` Greg KH
2023-07-07 8:35 ` Krzysztof Kozlowski
2023-07-07 10:11 ` Greg KH
2023-07-06 21:59 ` [PATCH v1 3/3] MAINTAINERS: add USB support to GXP richard.yu
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=20230706215910.78772-1-richard.yu@hpe.com \
--to=richard.yu@hpe.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nick.hawkins@hpe.com \
--cc=robh+dt@kernel.org \
--cc=verdun@hpe.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;
as well as URLs for NNTP newsgroup(s).