From: Al Cooper <alcooperx@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: "Al Cooper" <alcooperx@gmail.com>,
"Alan Stern" <stern@rowland.harvard.edu>,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
linux-usb@vger.kernel.org,
"Mathias Nyman" <mathias.nyman@intel.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v3 0/4] Add XHCI, EHCI and OHCI support for Broadcom STB SoS's
Date: Wed, 8 Apr 2020 14:14:02 -0400 [thread overview]
Message-ID: <20200408181406.40389-1-alcooperx@gmail.com> (raw)
v3 - Addressed all of Andy Shevchenko's review comments for
ehci-brcm.c.
- Fixed the brcm,bcm7445-ehci.yaml dt-bindings document,
dt_binding_check now passes.
- Added the XHCI functionality to xhci-plat.c instead of creating
new brcmstb files, as suggested by Mathias Nyman.
v2 - Addressed Andy Shevchenko's review comments.
- Fixed dt_binding_check error pointed out by Rob Herring.
- Removed pr_info message in ehci_brcm_init as suggested by
Greg Kroah-Hartman.
This adds support for the XHCI, EHCI and OHCI host controllers found
in Broadcom STB SoC's. These drivers depend on getting access to the
new Broadcom STB USB PHY driver through a device-tree phandle and
will fail if the driver is not available.
Al Cooper (4):
dt-bindings: Add Broadcom STB USB support
usb: xhci: xhci-plat: Add support for Broadcom STB SoC's
usb: ehci: Add new EHCI driver for Broadcom STB SoC's
usb: host: Add ability to build new Broadcom STB USB drivers
.../bindings/usb/brcm,bcm7445-ehci.yaml | 60 ++++
.../devicetree/bindings/usb/usb-xhci.txt | 1 +
MAINTAINERS | 8 +
drivers/usb/host/Kconfig | 16 +
drivers/usb/host/Makefile | 16 +-
drivers/usb/host/ehci-brcm.c | 286 ++++++++++++++++++
drivers/usb/host/xhci-plat.c | 10 +
7 files changed, 391 insertions(+), 6 deletions(-)
create mode 100644 Documentation/devicetree/bindings/usb/brcm,bcm7445-ehci.yaml
create mode 100644 drivers/usb/host/ehci-brcm.c
--
2.17.1
next reply other threads:[~2020-04-08 18:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 18:14 Al Cooper [this message]
2020-04-08 18:14 ` [PATCH v3 1/4] dt-bindings: Add Broadcom STB USB support Al Cooper
2020-04-14 13:50 ` Rob Herring
2020-04-08 18:14 ` [PATCH v3 2/4] usb: xhci: xhci-plat: Add support for Broadcom STB SoC's Al Cooper
2020-04-09 7:25 ` Mathias Nyman
2020-04-08 18:14 ` [PATCH v3 3/4] usb: ehci: Add new EHCI driver " Al Cooper
2020-04-08 18:14 ` [PATCH v3 4/4] usb: host: Add ability to build new Broadcom STB USB drivers Al Cooper
2020-04-09 9:08 ` Andy Shevchenko
2020-04-09 11:49 ` Alan Cooper
2020-04-09 12:30 ` Andy Shevchenko
2020-04-09 18:15 ` Alan Cooper
2020-04-09 18:47 ` Andy Shevchenko
2020-04-08 18:25 ` [PATCH v3 0/4] Add XHCI, EHCI and OHCI support for Broadcom STB SoS's Andy Shevchenko
2020-04-08 19:00 ` Alan Cooper
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=20200408181406.40389-1-alcooperx@gmail.com \
--to=alcooperx@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=j.neuschaefer@gmx.net \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=robh+dt@kernel.org \
--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).