From: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
To: jorge.ramirez-ortiz@linaro.org, gregkh@linuxfoundation.org,
mark.rutland@arm.com, kishon@ti.com, jackp@codeaurora.org,
andy.gross@linaro.org, swboyd@chromium.org
Cc: shawn.guo@linaro.org, vkoul@kernel.org,
bjorn.andersson@linaro.org, khasim.mohammed@linaro.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] USB SS PHY for Qualcomm's QCS404
Date: Tue, 29 Jan 2019 12:35:13 +0100 [thread overview]
Message-ID: <1548761715-4004-1-git-send-email-jorge.ramirez-ortiz@linaro.org> (raw)
This set adds USB SS PHY support to Qualcomm's QCS404 SoC
The PHY is implemented using Synopsys SS PHY 1.0.0 IP
The code is losely based on Sriharsha Allenki's
<sallenki@codeaurora.org> original implementation.
v2:
enable OTG mode detection
move vdd voltage levels to driver
use bulk_ control interfaces
ss-phy-bindings [1]
[1] ss-phy-binding discussion:
- qcom,dwc3-ss-usb-phy exist for a generic usb2/usb3 phy driver that
was never merged. Rather than trying to re-use these bindings (or
delete them) I propose that we go ahead with the new separate
bindings for HS and SS: if not now - investigation in progress- in
the future it might be possible to have again a common phy driver
for which these old bindings would be the binding agreement.
Jorge Ramirez-Ortiz (2):
dt-bindings: Add Qualcomm USB Super-Speed PHY bindings
phy: qualcomm: usb: Add Super-Speed PHY driver
.../devicetree/bindings/usb/qcom,usb-ssphy.txt | 73 +++++
drivers/phy/qualcomm/Kconfig | 11 +
drivers/phy/qualcomm/Makefile | 1 +
drivers/phy/qualcomm/phy-qcom-usb-ss.c | 347 +++++++++++++++++++++
4 files changed, 432 insertions(+)
create mode 100644 Documentation/devicetree/bindings/usb/qcom,usb-ssphy.txt
create mode 100644 drivers/phy/qualcomm/phy-qcom-usb-ss.c
--
2.7.4
next reply other threads:[~2019-01-29 11:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 11:35 Jorge Ramirez-Ortiz [this message]
2019-01-29 11:35 ` [PATCH v2 1/2] dt-bindings: Add Qualcomm USB Super-Speed PHY bindings Jorge Ramirez-Ortiz
2019-01-29 20:38 ` Bjorn Andersson
2019-01-30 20:02 ` Rob Herring
2019-02-05 11:02 ` Jorge Ramirez
2019-02-06 14:11 ` Jorge Ramirez
2019-02-12 20:47 ` Rob Herring
2019-01-29 11:35 ` [PATCH v2 2/2] phy: qualcomm: usb: Add Super-Speed PHY driver Jorge Ramirez-Ortiz
2019-01-29 20:27 ` Bjorn Andersson
2019-01-30 9:53 ` Jorge Ramirez
2019-01-30 11:38 ` Jorge Ramirez
2019-01-30 12:27 ` Jorge Ramirez
2019-01-30 19:58 ` [PATCH v2 0/2] USB SS PHY for Qualcomm's QCS404 Rob Herring
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=1548761715-4004-1-git-send-email-jorge.ramirez-ortiz@linaro.org \
--to=jorge.ramirez-ortiz@linaro.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jackp@codeaurora.org \
--cc=khasim.mohammed@linaro.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=shawn.guo@linaro.org \
--cc=swboyd@chromium.org \
--cc=vkoul@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).