From: Abel Vesa <abel.vesa@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
"vkoul@kernel.org" <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Johan Hovold <johan@kernel.org>
Subject: [PATCH v4 0/6] phy: qualcomm: Add UFS support for SM8550
Date: Tue, 17 Jan 2023 16:20:09 +0200 [thread overview]
Message-ID: <20230117142015.509675-1-abel.vesa@linaro.org> (raw)
The v3 of this patchset is:
https://lore.kernel.org/all/20230117125555.163087-1-abel.vesa@linaro.org/
Changes since v3:
* correctly ordered the compatible in schema file
Abel Vesa (6):
dt-bindings: phy: Add QMP UFS PHY comptible for SM8550
phy: qcom-qmp: qserdes-com: Add v6 register offsets
phy: qcom-qmp: qserdes-txrx: Add v6 register offsets
phy: qcom-qmp: qserdes-txrx-ufs: Add v6 register offsets
phy: qcom-qmp: pcs-ufs: Add v6 register offsets
phy: qcom-qmp-ufs: Add SM8550 support
.../phy/qcom,sc8280xp-qmp-ufs-phy.yaml | 1 +
.../phy/qualcomm/phy-qcom-qmp-pcs-ufs-v6.h | 31 ++++++
.../qualcomm/phy-qcom-qmp-qserdes-com-v6.h | 82 +++++++++++++++
.../phy-qcom-qmp-qserdes-txrx-ufs-v6.h | 30 ++++++
.../qualcomm/phy-qcom-qmp-qserdes-txrx-v6.h | 77 +++++++++++++++
drivers/phy/qualcomm/phy-qcom-qmp-ufs.c | 99 +++++++++++++++++++
drivers/phy/qualcomm/phy-qcom-qmp.h | 3 +
7 files changed, 323 insertions(+)
create mode 100644 drivers/phy/qualcomm/phy-qcom-qmp-pcs-ufs-v6.h
create mode 100644 drivers/phy/qualcomm/phy-qcom-qmp-qserdes-com-v6.h
create mode 100644 drivers/phy/qualcomm/phy-qcom-qmp-qserdes-txrx-ufs-v6.h
create mode 100644 drivers/phy/qualcomm/phy-qcom-qmp-qserdes-txrx-v6.h
--
2.34.1
next reply other threads:[~2023-01-17 14:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 14:20 Abel Vesa [this message]
2023-01-17 14:20 ` [PATCH v4 1/6] dt-bindings: phy: Add QMP UFS PHY comptible for SM8550 Abel Vesa
2023-01-23 9:48 ` Johan Hovold
2023-01-17 14:20 ` [PATCH v4 2/6] phy: qcom-qmp: qserdes-com: Add v6 register offsets Abel Vesa
2023-01-17 14:28 ` Dmitry Baryshkov
2023-01-17 14:20 ` [PATCH v4 3/6] phy: qcom-qmp: qserdes-txrx: " Abel Vesa
2023-01-17 14:20 ` [PATCH v4 4/6] phy: qcom-qmp: qserdes-txrx-ufs: " Abel Vesa
2023-01-17 14:42 ` Dmitry Baryshkov
2023-01-23 10:56 ` Abel Vesa
2023-01-17 14:20 ` [PATCH v4 5/6] phy: qcom-qmp: pcs-ufs: " Abel Vesa
2023-01-17 14:29 ` Dmitry Baryshkov
2023-01-17 14:20 ` [PATCH v4 6/6] phy: qcom-qmp-ufs: Add SM8550 support Abel Vesa
2023-01-17 14:47 ` Dmitry Baryshkov
2023-01-23 9:49 ` Johan Hovold
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=20230117142015.509675-1-abel.vesa@linaro.org \
--to=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan@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-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.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).