From: Al Cooper <alcooperx@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Al Cooper <alcooperx@gmail.com>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Florian Fainelli <f.fainelli@gmail.com>,
bcm-kernel-feedback-list@broadcom.com,
Kishon Vijay Abraham I <kishon@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] Add Broadcom STB USB phy driver
Date: Tue, 27 Jun 2017 10:59:09 -0400 [thread overview]
Message-ID: <1498575553-19311-1-git-send-email-alcooperx@gmail.com> (raw)
Add a new USB Phy driver for Broadcom STB SoCs. This driver
supports Broadcom STB ARM and MIPS SoCs. This driver in
combination with the Broadcom STB ohci, ehci and xhci
drivers will enable USB1.1, USB2.0 and USB3.0 support.
This Phy driver also supports the Broadcom UDC gadget
driver.
Changes since v2:
- Fix kbuild errors by changing Kconfig so the driver
only builds for ARCH_BRCMSTB || BMIPS_GENERIC systems
Changes since v1:
- Rebased to next
- Add Kconfig entry to build the driver
- Commented all delays
- Split out sysfs functionality in separate patch
- Removed parsing of old obselete device tree properties
- Changed device property "device" to "dr_mode" using
standard values "host" and "peripheral" along with new
values "drd" and "typec-pd"
- Add ability to handle the standard PHY_TYPE_USB2 and
PHY_TYPE_USB3 arguments passed in by phy consumers.
- Moved phy_provider_register() to end of probe routine
Al Cooper (4):
soc: brcmstb: Add Product ID and Family ID helper functions
dt-bindings: Add Broadcom STB USB PHY binding document
phy: usb: phy-brcm-usb: Add Broadcom STB USB phy driver
phy: usb: phy-brcm-usb: Add ability to force DRD mode to host or
device
.../bindings/phy/brcm,brcmstb-usb-phy.txt | 42 +
MAINTAINERS | 7 +
drivers/phy/broadcom/Kconfig | 12 +
drivers/phy/broadcom/Makefile | 3 +
drivers/phy/broadcom/phy-brcm-usb-init.c | 1125 ++++++++++++++++++++
drivers/phy/broadcom/phy-brcm-usb-init.h | 95 ++
drivers/phy/broadcom/phy-brcm-usb.c | 444 ++++++++
drivers/soc/bcm/brcmstb/common.c | 12 +
include/linux/soc/brcmstb/brcmstb.h | 10 +
9 files changed, 1750 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/brcm,brcmstb-usb-phy.txt
create mode 100644 drivers/phy/broadcom/phy-brcm-usb-init.c
create mode 100644 drivers/phy/broadcom/phy-brcm-usb-init.h
create mode 100644 drivers/phy/broadcom/phy-brcm-usb.c
--
1.9.0.138.g2de3478
next reply other threads:[~2017-06-27 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 14:59 Al Cooper [this message]
2017-06-27 14:59 ` [PATCH v3 1/4] soc: brcmstb: Add Product ID and Family ID helper functions Al Cooper
2017-06-27 18:54 ` Florian Fainelli
2017-06-27 14:59 ` [PATCH v3 2/4] dt-bindings: Add Broadcom STB USB PHY binding document Al Cooper
2017-06-27 14:59 ` [PATCH v3 3/4] phy: usb: phy-brcm-usb: Add Broadcom STB USB phy driver Al Cooper
2017-07-11 9:41 ` Kishon Vijay Abraham I
2017-07-11 22:12 ` Al Cooper
2017-06-27 14:59 ` [PATCH v3 4/4] phy: usb: phy-brcm-usb: Add ability to force DRD mode to host or device Al 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=1498575553-19311-1-git-send-email-alcooperx@gmail.com \
--to=alcooperx@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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).