From: Iskren Chernev <iskren.chernev@gmail.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Vinod Koul <vkoul@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Iskren Chernev <iskren.chernev@gmail.com>
Subject: [PATCH v2 0/2] Add UFS PHY support for SM6115/4250
Date: Fri, 13 Aug 2021 23:11:49 +0300 [thread overview]
Message-ID: <20210813201151.974512-1-iskren.chernev@gmail.com> (raw)
The UFS PHY found on SM6115/4250 is named v3-660, found on cheaper qcom devices
(possibly starting with sdm660), but up until recently wasn't used much due to
prevalence of sdhc port for internal storage/sdcard.
The name is a bit misleading, because most of the registers found on v3-660
don't share much in common with v3.
The register values/sequences are taken from OnePlus repo [1].
[1] https://github.com/OnePlusOSS/android_kernel_oneplus_sm4250
v1: https://lkml.org/lkml/2021/8/5/235
Changes from v1:
- Suggested by Vinod
- removed v3-660 constants for regs with same name and value as v3 regs
Iskren Chernev (2):
dt-bindings: phy: qcom,qmp: Add SM6115 UFS PHY bindings
phy: qcom-qmp: Add support for SM6115 UFS phy
.../devicetree/bindings/phy/qcom,qmp-phy.yaml | 1 +
drivers/phy/qualcomm/phy-qcom-qmp.c | 124 ++++++++++++++++
drivers/phy/qualcomm/phy-qcom-qmp.h | 134 ++++++++++++++++++
3 files changed, 259 insertions(+)
base-commit: 8d4b477da1a807199ca60e0829357ce7aa6758d5
--
2.32.0
next reply other threads:[~2021-08-13 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 20:11 Iskren Chernev [this message]
2021-08-13 20:11 ` [PATCH v2 1/2] dt-bindings: phy: qcom,qmp: Add SM6115 UFS PHY bindings Iskren Chernev
2021-08-13 20:11 ` [PATCH v2 2/2] phy: qcom-qmp: Add support for SM6115 UFS phy Iskren Chernev
2021-08-17 5:34 ` 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=20210813201151.974512-1-iskren.chernev@gmail.com \
--to=iskren.chernev@gmail.com \
--cc=agross@kernel.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=linux-phy@lists.infradead.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).