From: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
To: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: "Kishon Vijay Abraham I" <kishon@ti.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Paul Kocialkowski" <paul.kocialkowski@bootlin.com>,
"Mylène Josserand" <mylene.josserand@bootlin.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: [PATCH 0/3] SMSC USB333x ULPI USB PHY Support
Date: Wed, 30 Jan 2019 16:50:20 +0100 [thread overview]
Message-ID: <20190130155023.4495-1-paul.kocialkowski@bootlin.com> (raw)
This series adds support for the SMSC USB333x ULPI USB PHY.
The USB333x usually does not require particular configuration as it
implements generic registers described in the ULPI specification.
However, specific use cases require tweaking some bits. In our case,
VBUS is not connected to anything so the internal EXTVBUS signal has to
be routed to assert VbusValid.
Paul Kocialkowski (3):
dt-bindings: phy: Add bindings for the SMSC USB333x ULPI USB PHY
phy: Add support for the SMSC USB333x ULPI USB PHY
MAINTAINERS: Add entry for the SMSC USB333x ULPI USB PHY
.../devicetree/bindings/phy/smsc-usb333x.txt | 50 +++
MAINTAINERS | 6 +
drivers/phy/Kconfig | 1 +
drivers/phy/Makefile | 1 +
drivers/phy/smsc/Kconfig | 11 +
drivers/phy/smsc/Makefile | 2 +
drivers/phy/smsc/phy-usb333x.c | 301 ++++++++++++++++++
7 files changed, 372 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/smsc-usb333x.txt
create mode 100644 drivers/phy/smsc/Kconfig
create mode 100644 drivers/phy/smsc/Makefile
create mode 100644 drivers/phy/smsc/phy-usb333x.c
--
2.20.1
next reply other threads:[~2019-01-30 15:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 15:50 Paul Kocialkowski [this message]
2019-01-30 15:50 ` [PATCH 1/3] dt-bindings: phy: Add bindings for the SMSC USB333x ULPI USB PHY Paul Kocialkowski
2019-02-25 16:41 ` Rob Herring
2019-03-19 12:47 ` Paul Kocialkowski
2019-01-30 15:50 ` [PATCH 2/3] phy: Add support " Paul Kocialkowski
2019-01-30 15:50 ` [PATCH 3/3] MAINTAINERS: Add entry " Paul Kocialkowski
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=20190130155023.4495-1-paul.kocialkowski@bootlin.com \
--to=paul.kocialkowski@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mylene.josserand@bootlin.com \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.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).