From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: vkoul@kernel.org, kishon@ti.com, robh+dt@kernel.org
Cc: bjorn.andersson@linaro.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: [PATCH 0/3] Add support for PCIe PHY in SDX55
Date: Tue, 27 Apr 2021 12:23:57 +0530 [thread overview]
Message-ID: <20210427065400.18958-1-manivannan.sadhasivam@linaro.org> (raw)
Hi,
This series adds support for PCIe PHY found in Qualcomm SDX55 platform.
The PHY version is v4.20 which has different register offsets compared with
previous v4.0x versions. So separate defines are introducted to handle the
differences.
This series has been tested on Telit FN980 EVB with an out of tree PCIe Endpoint
driver.
Thanks,
Mani
Manivannan Sadhasivam (3):
dt-bindings: phy: qcom,qmp: Add binding for SDX55 PCIe PHY
phy: qcom-qmp: Use phy_status field for the status bit offset
phy: qcom-qmp: Add support for SDX55 QMP PCIe PHY
.../devicetree/bindings/phy/qcom,qmp-phy.yaml | 2 +
drivers/phy/qualcomm/phy-qcom-qmp.c | 160 +++++++++++++++++-
drivers/phy/qualcomm/phy-qcom-qmp.h | 64 ++++++-
3 files changed, 224 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2021-04-27 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 6:53 Manivannan Sadhasivam [this message]
2021-04-27 6:53 ` [PATCH 1/3] dt-bindings: phy: qcom,qmp: Add binding for SDX55 PCIe PHY Manivannan Sadhasivam
2021-05-03 19:13 ` Rob Herring
2021-05-29 16:25 ` Bjorn Andersson
2021-04-27 6:53 ` [PATCH 2/3] phy: qcom-qmp: Use phy_status field for the status bit offset Manivannan Sadhasivam
2021-05-29 17:02 ` Bjorn Andersson
2021-04-27 6:54 ` [PATCH 3/3] phy: qcom-qmp: Add support for SDX55 QMP PCIe PHY Manivannan Sadhasivam
2021-05-29 17:05 ` Bjorn Andersson
2021-05-31 6:08 ` [PATCH 0/3] Add support for PCIe PHY in SDX55 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=20210427065400.18958-1-manivannan.sadhasivam@linaro.org \
--to=manivannan.sadhasivam@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).