From: Stanley Chu <stanley.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
To: linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
chunfeng.yun-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
yingjoe.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
kishon-l0cyMroinI0@public.gmane.org,
martin.petersen-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org,
avri.altman-Sjgp3cTcYWE@public.gmane.org,
alim.akhtar-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
pedrom.sousa-HKixBCOQz3hWk0Htik3J/w@public.gmane.org
Cc: chun-hung.wu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
kuohong.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
liwei213-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
subhashj-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
peter.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org
Subject: scsi: ufs-mediatek: Add UFS support for Mediatek SoC chips
Date: Thu, 14 Mar 2019 12:08:28 +0800 [thread overview]
Message-ID: <1552536516-12723-1-git-send-email-stanley.chu@mediatek.com> (raw)
Hello,
This patch series adds UFS M-PHY and UFS host driver support in MediaTek chipsets.
In the meantime, re-factors ufshcd_get_pwr_dev_param in vendors' drivers. This function is for vendors to decide finally agreed attributes for power mode change if vendors define
their host capability in struct ufs_dev_params. Because it is using by both ufs-qcom and ufs-hisi and also used in ufs-mediatek in this serious, simply re-factor it and then every vendors can reuse it.
Changes since v4:
- phy-mtk-ufs:
* Sort name in Kconfig and Makefile
* Drop "inline" and fix symbol name for mphy_set_bit()/mphy_clr_bit().
- dt-bindings: phy-mtk-ufs: Drop "-clk" in clock names.
- dt-bindings: ufs-mediatek:
* Change clock name "ufs-clk" to "ufs".
* Drop vcc related first. VCC control is planned to be added back by another patch accompanied with VCC/ICC logic fix in ufs common driver.
Changes since v3:
- dt-bindings: Use specific compatible name for both ufs-mediatek and phy-mtk-ufs, remove interrupt-parent and lanes-per-direction in ufs-mediatek, and fix descriptions.
Changes since v2:
- Fix header style with SPDX-License-Identifier declaration used.
- Simplify ufs-phy-mtk to single source file since we has one MPHY version now, and do fixes according to Chunfeng Yun's comments.
- Add dt-bindings of ufs-phy-mtk.
Changes since v1:
- Re-factor ufshcd_get_pwr_dev_param in mediatek/qcom/hisi vendor drivers.
- Introduce ufs-phy-mtk to have a good extension capability for different power control flows in future different MPHY versions.
- Bind ufs-phy-mtk and hook suitable callbacks in ufs-mediatek driver.
- Use PA_LOCAL_TX_LCC_ENABLE attribute defined in unipro.h instead.
- Do some minor format fixes.
Stanley Chu (7):
scsi: ufs: Introduce ufshcd_get_pwr_dev_param
scsi: ufs-qcom: Re-factor ufshcd_get_pwr_dev_param
scsi: ufs-hisi: Re-factor ufshcd_get_pwr_dev_param
dt-bindings: phy: Add document for phy-mtk-ufs
dt-bindings: scsi: ufs: Add document for ufs-mediatek
phy: mediatek: Add UFS M-PHY driver
scsi: ufs-mediatek: Add UFS support for Mediatek SoC chips
.../devicetree/bindings/phy/phy-mtk-ufs.txt | 38 ++
.../devicetree/bindings/ufs/ufs-mediatek.txt | 40 ++
drivers/phy/mediatek/Kconfig | 11 +
drivers/phy/mediatek/Makefile | 1 +
drivers/phy/mediatek/phy-mtk-ufs.c | 239 ++++++++++++
drivers/scsi/ufs/Kconfig | 14 +
drivers/scsi/ufs/Makefile | 1 +
drivers/scsi/ufs/ufs-hisi.c | 109 +-----
drivers/scsi/ufs/ufs-mediatek.c | 368 ++++++++++++++++++
drivers/scsi/ufs/ufs-mediatek.h | 54 +++
drivers/scsi/ufs/ufs-qcom.c | 106 +----
drivers/scsi/ufs/ufshcd-pltfrm.c | 98 +++++
drivers/scsi/ufs/ufshcd-pltfrm.h | 21 +
13 files changed, 893 insertions(+), 207 deletions(-)
create mode 100644 Documentation/devicetree/bindings/phy/phy-mtk-ufs.txt
create mode 100644 Documentation/devicetree/bindings/ufs/ufs-mediatek.txt
create mode 100644 drivers/phy/mediatek/phy-mtk-ufs.c
create mode 100644 drivers/scsi/ufs/ufs-mediatek.c
create mode 100644 drivers/scsi/ufs/ufs-mediatek.h
next reply other threads:[~2019-03-14 4:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 4:08 Stanley Chu [this message]
[not found] ` <1552536516-12723-1-git-send-email-stanley.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-03-14 4:08 ` [PATCH v5 0/7] scsi: ufs-mediatek: Add UFS support for Mediatek SoC chips Stanley Chu
[not found] ` <1552536516-12723-2-git-send-email-stanley.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-03-14 8:28 ` Avri Altman
[not found] ` <SN6PR04MB4925CDFC82326C5AB59E1629FC4B0-UKdxhu0+N/VnT3GYGerMaFM8qxBPnqtHvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2019-03-14 8:36 ` Stanley Chu
2019-03-14 4:08 ` [PATCH v5 1/7] scsi: ufs: Introduce ufshcd_get_pwr_dev_param Stanley Chu
2019-03-14 4:08 ` [PATCH v5 2/7] scsi: ufs-qcom: Re-factor ufshcd_get_pwr_dev_param Stanley Chu
2019-03-14 4:08 ` [PATCH v5 3/7] scsi: ufs-hisi: " Stanley Chu
2019-03-14 4:08 ` [PATCH v5 4/7] dt-bindings: phy: Add document for phy-mtk-ufs Stanley Chu
[not found] ` <1552536516-12723-6-git-send-email-stanley.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-03-14 16:38 ` Rob Herring
2019-03-14 4:08 ` [PATCH v5 5/7] dt-bindings: scsi: ufs: Add document for ufs-mediatek Stanley Chu
[not found] ` <1552536516-12723-7-git-send-email-stanley.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-03-15 23:27 ` Rob Herring
2019-03-14 4:08 ` [PATCH v5 6/7] phy: mediatek: Add UFS M-PHY driver Stanley Chu
[not found] ` <1552536516-12723-8-git-send-email-stanley.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-03-14 8:06 ` Kishon Vijay Abraham I
[not found] ` <a2b91daa-9391-1a81-a298-efcfcaccc775-l0cyMroinI0@public.gmane.org>
2019-03-14 8:29 ` Stanley Chu
2019-03-14 4:08 ` [PATCH v5 7/7] scsi: ufs-mediatek: Add UFS support for Mediatek SoC chips Stanley Chu
-- strict thread matches above, loose matches on Subject: below --
2019-03-16 5:04 Stanley Chu
2019-03-13 4:10 Stanley Chu
2019-02-27 7:23 Stanley Chu
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=1552536516-12723-1-git-send-email-stanley.chu@mediatek.com \
--to=stanley.chu-nus5lvnupcjwk0htik3j/w@public.gmane.org \
--cc=alim.akhtar-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=avri.altman-Sjgp3cTcYWE@public.gmane.org \
--cc=chun-hung.wu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=chunfeng.yun-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kishon-l0cyMroinI0@public.gmane.org \
--cc=kuohong.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=liwei213-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=martin.petersen-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=pedrom.sousa-HKixBCOQz3hWk0Htik3J/w@public.gmane.org \
--cc=peter.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=subhashj-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=yingjoe.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.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).