From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org
Subject: [PATCH v3 0/5] phy: qcom-qmp-usb: split away legacy USB+DP code
Date: Wed, 31 May 2023 05:34:10 +0300 [thread overview]
Message-ID: <20230531023415.1209301-1-dmitry.baryshkov@linaro.org> (raw)
While working on the QMP binding cleanup, I noticed that USB QMP driver
supports both simple USB PHYs (which should be updated) and USB-only
part of USB+DP PHYs (which are largely legacy and don't need to be
updated). To ease further cleanup perform a quick cleanup of the last
remaining USB+DP PHY (on sm8150 platform) and split the legacy codepath
from the USB QMP PHY driver.
Changes since v2:
- Fixed phy subnode names (noted by Caleb)
Changes since v1:
- Rebased on top of phy/next
Dmitry Baryshkov (5):
dt-bindings: phy: qcom,sc7180-qmp-usb3-dp-phy: add sm8150 USB+DP PHY
phy: qcom-qmp-combo: add support for the USB+DP PHY on SM8150 platform
arm64: dts: qcom: sm8150: turn first USB PHY into USB+DP PHY
dt-bindings: phy: qcom,msm8996-qmp-usb3-phy: drop legacy bindings
phy: qcom-qmp-usb: split off the legacy USB+dp_com support
.../phy/qcom,msm8996-qmp-usb3-phy.yaml | 80 -
.../phy/qcom,sc7180-qmp-usb3-dp-phy.yaml | 2 +
arch/arm64/boot/dts/qcom/sm8150.dtsi | 19 +-
drivers/phy/qualcomm/Kconfig | 10 +
drivers/phy/qualcomm/Makefile | 1 +
drivers/phy/qualcomm/phy-qcom-qmp-combo.c | 4 +
.../phy/qualcomm/phy-qcom-qmp-usb-legacy.c | 1407 +++++++++++++++++
drivers/phy/qualcomm/phy-qcom-qmp-usb.c | 556 -------
8 files changed, 1438 insertions(+), 641 deletions(-)
create mode 100644 drivers/phy/qualcomm/phy-qcom-qmp-usb-legacy.c
--
2.39.2
next reply other threads:[~2023-05-31 2:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 2:34 Dmitry Baryshkov [this message]
2023-05-31 2:34 ` [PATCH v3 1/5] dt-bindings: phy: qcom,sc7180-qmp-usb3-dp-phy: add sm8150 USB+DP PHY Dmitry Baryshkov
2023-05-31 2:34 ` [PATCH v3 2/5] phy: qcom-qmp-combo: add support for the USB+DP PHY on SM8150 platform Dmitry Baryshkov
2023-05-31 11:35 ` Konrad Dybcio
2023-05-31 12:13 ` Dmitry Baryshkov
2023-05-31 12:16 ` Konrad Dybcio
2023-07-10 3:27 ` Bjorn Andersson
2023-05-31 2:34 ` [PATCH v3 3/5] arm64: dts: qcom: sm8150: turn first USB PHY into USB+DP PHY Dmitry Baryshkov
2023-05-31 2:34 ` [PATCH v3 4/5] dt-bindings: phy: qcom,msm8996-qmp-usb3-phy: drop legacy bindings Dmitry Baryshkov
2023-06-09 15:37 ` Rob Herring
2023-05-31 2:34 ` [PATCH v3 5/5] phy: qcom-qmp-usb: split off the legacy USB+dp_com support Dmitry Baryshkov
2023-07-11 7:44 ` [PATCH v3 0/5] phy: qcom-qmp-usb: split away legacy USB+DP code Vinod Koul
2023-07-11 7:47 ` Vinod Koul
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=20230531023415.1209301-1-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.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).