From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org
Subject: [RFC PATCH 0/5] phy: qcom-qmp: split the QMP PHY driver
Date: Mon, 16 May 2022 14:45:20 +0300 [thread overview]
Message-ID: <20220516114525.3596196-1-dmitry.baryshkov@linaro.org> (raw)
While adding support for the PCIe EP mode support to the QMP driver I
couldn't help but notice that the QMP PHY driver has slowly become the a
beast with tons of conditions and corner cases being inserted here and
there.r
This an RFC for an attempt to to cleanup the QMP driver by splitting the
QMP PHY driver into four smaller drivers, each targeting a particular
family of PHY backends (DP/combo, PCIe, UFS and USB). Yes, this results
in some code duplication, but I hope that the end result is still better
than the current situation.
If the idea looks good, I will continue polishing the drivers. A
feedback regarding the common functions (ones, left in the
phy-qcom-qmp.c file) would be appreciated.
Dmitry Baryshkov (5):
phy: qcom-qmp: split combo PHY support
phy: qcom-qmp: split DP data to DP-specific structures
phy: qcom-qmp: split UFS PHY support
phy: qcom-qmp: split PCIe PHY support
phy: qcom-qmp: complete split of the QMP driver
drivers/phy/qualcomm/Makefile | 2 +-
drivers/phy/qualcomm/phy-qcom-qmp-combo.c | 1362 +++++
drivers/phy/qualcomm/phy-qcom-qmp-lib.h | 290 +
drivers/phy/qualcomm/phy-qcom-qmp-pcie.c | 1945 +++++++
drivers/phy/qualcomm/phy-qcom-qmp-ufs.c | 863 +++
drivers/phy/qualcomm/phy-qcom-qmp-usb.c | 2104 ++++++++
drivers/phy/qualcomm/phy-qcom-qmp.c | 5983 +--------------------
drivers/phy/qualcomm/phy-qcom-qmp.h | 43 +
8 files changed, 6732 insertions(+), 5860 deletions(-)
create mode 100644 drivers/phy/qualcomm/phy-qcom-qmp-combo.c
create mode 100644 drivers/phy/qualcomm/phy-qcom-qmp-lib.h
create mode 100644 drivers/phy/qualcomm/phy-qcom-qmp-pcie.c
create mode 100644 drivers/phy/qualcomm/phy-qcom-qmp-ufs.c
create mode 100644 drivers/phy/qualcomm/phy-qcom-qmp-usb.c
--
2.35.1
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next reply other threads:[~2022-05-16 11:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 11:45 Dmitry Baryshkov [this message]
2022-05-16 11:45 ` [RFC PATCH 1/5] phy: qcom-qmp: split combo PHY support Dmitry Baryshkov
2022-05-16 11:45 ` [RFC PATCH 2/5] phy: qcom-qmp: split DP data to DP-specific structures Dmitry Baryshkov
2022-05-16 11:45 ` [RFC PATCH 3/5] phy: qcom-qmp: split UFS PHY support Dmitry Baryshkov
2022-05-16 11:45 ` [RFC PATCH 4/5] phy: qcom-qmp: split PCIe " Dmitry Baryshkov
2022-05-16 11:45 ` [RFC PATCH 5/5] phy: qcom-qmp: complete split of the QMP driver Dmitry Baryshkov
2022-05-16 11:50 ` [RFC PATCH 0/5] phy: qcom-qmp: split the QMP PHY driver Dmitry Baryshkov
2022-05-16 11:52 ` Vinod Koul
2022-05-16 12:01 ` Dmitry Baryshkov
2022-05-16 12:23 ` 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=20220516114525.3596196-1-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=kishon@ti.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--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).