scsi: ufs-mediatek: Add UFS support for Mediatek SoC chips
Subsystems (6)
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 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 | 36 ++ .../devicetree/bindings/ufs/ufs-mediatek.txt | 44 +++ drivers/phy/mediatek/Kconfig | 9 + 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
v4 cover scsi: ufs-mediatek: Add ufshci and ufsphy support for Mediatek SoC chips
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 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 | 36 ++ .../devicetree/bindings/ufs/ufs-mediatek.txt | 44 +++ drivers/phy/mediatek/Kconfig | 9 + 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
Signature · 1 line
2.18.0
PATCH v4 1/7 scsi: ufs: Introduce ufshcd_get_pwr_dev_param
In reply to Stanley Chuufshcd_get_pwr_dev_param is for vendors to decide finally agreed attributes for power mode change if vendors define their host capability in struct ufs_dev_params.
This api is using by both ufs-qcom and ufs-hisi now. Simply re-factor it and then every vendors can reuse it.
--- drivers/scsi/ufs/ufshcd-pltfrm.c | 98 ++++++++++++++++++++++++++++++++ drivers/scsi/ufs/ufshcd-pltfrm.h | 21 +++++++ 2 files changed, 119 insertions(+)
drivers/scsi/ufs/ufshcd-pltfrm.c +98 -0
@@ -39,6 +39,7 @@#include "ufshcd.h" #include "ufshcd-pltfrm.h" +#include "unipro.h" #define UFSHCD_DEFAULT_LANES_PER_DIRECTION 2
@@ -289,6 +290,103 @@ static void ufshcd_init_lanes_per_dir(struct ufs_hba *hba) } } +/** +* ufshcd_get_pwr_dev_param - get finally agreed attributes for +* power mode change +* @pltfrm_param: pointer to platform parameters +* @dev_max: pointer to device attributes +* @agreed_pwr: returned agreed attributes +* +* Returns 0 on success, non-zero value on failure +*/ +int ufshcd_get_pwr_dev_param (struct ufs_dev_params *pltfrm_param, +struct ufs_pa_layer_attr *dev_max, +struct ufs_pa_layer_attr *agreed_pwr) +{ +int min_pltfrm_gear; +int min_dev_gear; +bool is_dev_sup_hs = false; +bool is_pltfrm_max_hs = false; + +if (dev_max->pwr_rx ==FAST_MODE ) + is_dev_sup_hs = true; + +if (pltfrm_param->desired_working_mode ==UFS_HS_MODE ) { + is_pltfrm_max_hs = true; + min_pltfrm_gear =min_t (u32, pltfrm_param->hs_rx_gear, + pltfrm_param->hs_tx_gear); + }else { + min_pltfrm_gear =min_t (u32, pltfrm_param->pwm_rx_gear, + pltfrm_param->pwm_tx_gear); + } + +/* +* device doesn't support HS but +* pltfrm_param->desired_working_mode is HS, +* thus device and pltfrm_param don't agree +*/ +if (!is_dev_sup_hs && is_pltfrm_max_hs) { +pr_info ("%s: device doesn't support HS\n" , + __func__); +return -ENOTSUPP ; + }else if (is_dev_sup_hs && is_pltfrm_max_hs) { +/* +* since device supports HS, it supports FAST_MODE. +* since pltfrm_param->desired_working_mode is also HS +* then final decision (FAST/FASTAUTO) is done according +* to pltfrm_params as it is the restricting factor +*/ + agreed_pwr->pwr_rx = pltfrm_param->rx_pwr_hs; + agreed_pwr->pwr_tx = agreed_pwr->pwr_rx; + }else { +/* +* here pltfrm_param->desired_working_mode is PWM. +* it doesn't matter whether device supports HS or PWM, +* in both cases pltfrm_param->desired_working_mode will +* determine the mode +*/ + agreed_pwr->pwr_rx = pltfrm_param->rx_pwr_pwm; + agreed_pwr->pwr_tx = agreed_pwr->pwr_rx; + } + +/* +* we would like tx to work in the minimum number of lanes +* between device capability and vendor preferences. +* the same decision will be made for rx +*/ + agreed_pwr->lane_tx =min_t (u32, dev_max->lane_tx, + pltfrm_param->tx_lanes); + agreed_pwr->lane_rx =min_t (u32, dev_max->lane_rx, + pltfrm_param->rx_lanes); + +/* device maximum gear is the minimum between device rx and tx gears */ + min_dev_gear =min_t (u32, dev_max->gear_rx, dev_max->gear_tx); + +/* +* if both device capabilities and vendor pre-defined preferences are +* both HS or both PWM then set the minimum gear to be the chosen +* working gear. +* if one is PWM and one is HS then the one that is PWM get to decide +* what is the gear, as it is the one that also decided previously what +* pwr the device will be configured to. +*/ +if ((is_dev_sup_hs && is_pltfrm_max_hs) || + (!is_dev_sup_hs && !is_pltfrm_max_hs)) { + agreed_pwr->gear_rx = +min_t (u32, min_dev_gear, min_pltfrm_gear); + }else if (!is_dev_sup_hs) { + agreed_pwr->gear_rx = min_dev_gear; + }else { + agreed_pwr->gear_rx = min_pltfrm_gear; + } + agreed_pwr->gear_tx = agreed_pwr->gear_rx; + + agreed_pwr->hs_rate = pltfrm_param->hs_rate; + +return 0 ; +} +EXPORT_SYMBOL_GPL (ufshcd_get_pwr_dev_param); +/** * ufshcd_pltfrm_init - probe routine of the driver * @pdev: pointer to Platform device handle
drivers/scsi/ufs/ufshcd-pltfrm.h +21 -0
@@ -16,6 +16,27 @@#include "ufshcd.h" +#define UFS_PWM_MODE 1 +#define UFS_HS_MODE 2 + +struct ufs_dev_params { +u32 pwm_rx_gear;/* pwm rx gear to work in */ +u32 pwm_tx_gear;/* pwm tx gear to work in */ +u32 hs_rx_gear;/* hs rx gear to work in */ +u32 hs_tx_gear;/* hs tx gear to work in */ +u32 rx_lanes;/* number of rx lanes */ +u32 tx_lanes;/* number of tx lanes */ +u32 rx_pwr_pwm;/* rx pwm working pwr */ +u32 tx_pwr_pwm;/* tx pwm working pwr */ +u32 rx_pwr_hs;/* rx hs working pwr */ +u32 tx_pwr_hs;/* tx hs working pwr */ +u32 hs_rate;/* rate A/B to work in HS */ +u32 desired_working_mode; +}; + +int ufshcd_get_pwr_dev_param (struct ufs_dev_params *dev_param, +struct ufs_pa_layer_attr *dev_max, +struct ufs_pa_layer_attr *agreed_pwr);int ufshcd_pltfrm_init (struct platform_device *pdev,struct ufs_hba_variant_ops *vops);void ufshcd_pltfrm_shutdown (struct platform_device *pdev);
Signature · 1 line
2.18.0
PATCH v4 2/7 scsi: ufs-qcom: Re-factor ufshcd_get_pwr_dev_param
In reply to Stanley Chuufshcd_get_pwr_dev_param function and ufs_dev_params struct are re-factored to ufs common driver thus change the way this driver used.
--- drivers/scsi/ufs/ufs-qcom.c | 106 ++---------------------------------- 1 file changed, 4 insertions(+), 102 deletions(-)
drivers/scsi/ufs/ufs-qcom.c +4 -102
@@ -595,104 +595,6 @@ static int ufs_qcom_resume(struct ufs_hba *hba, enum ufs_pm_op pm_op)return err; } -struct ufs_qcom_dev_params { -u32 pwm_rx_gear;/* pwm rx gear to work in */ -u32 pwm_tx_gear;/* pwm tx gear to work in */ -u32 hs_rx_gear;/* hs rx gear to work in */ -u32 hs_tx_gear;/* hs tx gear to work in */ -u32 rx_lanes;/* number of rx lanes */ -u32 tx_lanes;/* number of tx lanes */ -u32 rx_pwr_pwm;/* rx pwm working pwr */ -u32 tx_pwr_pwm;/* tx pwm working pwr */ -u32 rx_pwr_hs;/* rx hs working pwr */ -u32 tx_pwr_hs;/* tx hs working pwr */ -u32 hs_rate;/* rate A/B to work in HS */ -u32 desired_working_mode; -}; - -static int ufs_qcom_get_pwr_dev_param (struct ufs_qcom_dev_params *qcom_param, -struct ufs_pa_layer_attr *dev_max, -struct ufs_pa_layer_attr *agreed_pwr) -{ -int min_qcom_gear; -int min_dev_gear; -bool is_dev_sup_hs = false; -bool is_qcom_max_hs = false; - -if (dev_max->pwr_rx ==FAST_MODE ) - is_dev_sup_hs = true; - -if (qcom_param->desired_working_mode ==FAST ) { - is_qcom_max_hs = true; - min_qcom_gear =min_t (u32, qcom_param->hs_rx_gear, - qcom_param->hs_tx_gear); - }else { - min_qcom_gear =min_t (u32, qcom_param->pwm_rx_gear, - qcom_param->pwm_tx_gear); - } - -/* -* device doesn't support HS but qcom_param->desired_working_mode is -* HS, thus device and qcom_param don't agree -*/ -if (!is_dev_sup_hs && is_qcom_max_hs) { -pr_err ("%s: failed to agree on power mode (device doesn't support HS but requested power is HS)\n" , - __func__); -return -ENOTSUPP ; - }else if (is_dev_sup_hs && is_qcom_max_hs) { -/* -* since device supports HS, it supports FAST_MODE. -* since qcom_param->desired_working_mode is also HS -* then final decision (FAST/FASTAUTO) is done according -* to qcom_params as it is the restricting factor -*/ - agreed_pwr->pwr_rx = agreed_pwr->pwr_tx = - qcom_param->rx_pwr_hs; - }else { -/* -* here qcom_param->desired_working_mode is PWM. -* it doesn't matter whether device supports HS or PWM, -* in both cases qcom_param->desired_working_mode will -* determine the mode -*/ - agreed_pwr->pwr_rx = agreed_pwr->pwr_tx = - qcom_param->rx_pwr_pwm; - } - -/* -* we would like tx to work in the minimum number of lanes -* between device capability and vendor preferences. -* the same decision will be made for rx -*/ - agreed_pwr->lane_tx =min_t (u32, dev_max->lane_tx, - qcom_param->tx_lanes); - agreed_pwr->lane_rx =min_t (u32, dev_max->lane_rx, - qcom_param->rx_lanes); - -/* device maximum gear is the minimum between device rx and tx gears */ - min_dev_gear =min_t (u32, dev_max->gear_rx, dev_max->gear_tx); - -/* -* if both device capabilities and vendor pre-defined preferences are -* both HS or both PWM then set the minimum gear to be the chosen -* working gear. -* if one is PWM and one is HS then the one that is PWM get to decide -* what is the gear, as it is the one that also decided previously what -* pwr the device will be configured to. -*/ -if ((is_dev_sup_hs && is_qcom_max_hs) || - (!is_dev_sup_hs && !is_qcom_max_hs)) - agreed_pwr->gear_rx = agreed_pwr->gear_tx = -min_t (u32, min_dev_gear, min_qcom_gear); -else if (!is_dev_sup_hs) - agreed_pwr->gear_rx = agreed_pwr->gear_tx = min_dev_gear; -else - agreed_pwr->gear_rx = agreed_pwr->gear_tx = min_qcom_gear; - - agreed_pwr->hs_rate = qcom_param->hs_rate; -return 0 ; -} -#ifdef CONFIG_MSM_BUS_SCALING static int ufs_qcom_get_bus_vote (struct ufs_qcom_host *host,const char *speed_mode)
@@ -920,7 +822,7 @@ static int ufs_qcom_pwr_change_notify(struct ufs_hba *hba, {u32 val;struct ufs_qcom_host *host =ufshcd_get_variant (hba); -struct ufs_qcom_dev_params ufs_qcom_cap; +struct ufs_dev_params ufs_qcom_cap;int ret =0 ;if (!dev_req_params) {
@@ -959,9 +861,9 @@ static int ufs_qcom_pwr_change_notify(struct ufs_hba *hba, ufs_qcom_cap.hs_rx_gear =UFS_HS_G2 ; } - ret =ufs_qcom_get_pwr_dev_param (&ufs_qcom_cap, - dev_max_params, - dev_req_params); + ret =ufshcd_get_pwr_dev_param (&ufs_qcom_cap, + dev_max_params, + dev_req_params);if (ret) {pr_err ("%s: failed to determine capabilities\n" , __func__);
Signature · 1 line
2.18.0
PATCH v4 3/7 scsi: ufs-hisi: Re-factor ufshcd_get_pwr_dev_param
In reply to Stanley Chuufshcd_get_pwr_dev_param function and ufs_dev_params struct are re-factored to ufs common driver thus change the way this driver used.
--- drivers/scsi/ufs/ufs-hisi.c | 109 ++---------------------------------- 1 file changed, 4 insertions(+), 105 deletions(-)
drivers/scsi/ufs/ufs-hisi.c +4 -105
@@ -272,108 +272,7 @@ static int ufs_hi3660_link_startup_notify(struct ufs_hba *hba,return err; } -struct ufs_hisi_dev_params { -u32 pwm_rx_gear;/* pwm rx gear to work in */ -u32 pwm_tx_gear;/* pwm tx gear to work in */ -u32 hs_rx_gear;/* hs rx gear to work in */ -u32 hs_tx_gear;/* hs tx gear to work in */ -u32 rx_lanes;/* number of rx lanes */ -u32 tx_lanes;/* number of tx lanes */ -u32 rx_pwr_pwm;/* rx pwm working pwr */ -u32 tx_pwr_pwm;/* tx pwm working pwr */ -u32 rx_pwr_hs;/* rx hs working pwr */ -u32 tx_pwr_hs;/* tx hs working pwr */ -u32 hs_rate;/* rate A/B to work in HS */ -u32 desired_working_mode; -}; - -static int ufs_hisi_get_pwr_dev_param ( -struct ufs_hisi_dev_params *hisi_param, -struct ufs_pa_layer_attr *dev_max, -struct ufs_pa_layer_attr *agreed_pwr) -{ -int min_hisi_gear; -int min_dev_gear; -bool is_dev_sup_hs = false; -bool is_hisi_max_hs = false; - -if (dev_max->pwr_rx ==FASTAUTO_MODE || dev_max->pwr_rx ==FAST_MODE ) - is_dev_sup_hs = true; - -if (hisi_param->desired_working_mode ==FAST ) { - is_hisi_max_hs = true; - min_hisi_gear =min_t (u32, hisi_param->hs_rx_gear, - hisi_param->hs_tx_gear); - }else { - min_hisi_gear =min_t (u32, hisi_param->pwm_rx_gear, - hisi_param->pwm_tx_gear); - } - -/* -* device doesn't support HS but -* hisi_param->desired_working_mode is HS, -* thus device and hisi_param don't agree -*/ -if (!is_dev_sup_hs && is_hisi_max_hs) { -pr_err ("%s: device not support HS\n" , __func__); -return -ENOTSUPP ; - }else if (is_dev_sup_hs && is_hisi_max_hs) { -/* -* since device supports HS, it supports FAST_MODE. -* since hisi_param->desired_working_mode is also HS -* then final decision (FAST/FASTAUTO) is done according -* to hisi_params as it is the restricting factor -*/ - agreed_pwr->pwr_rx = agreed_pwr->pwr_tx = - hisi_param->rx_pwr_hs; - }else { -/* -* here hisi_param->desired_working_mode is PWM. -* it doesn't matter whether device supports HS or PWM, -* in both cases hisi_param->desired_working_mode will -* determine the mode -*/ - agreed_pwr->pwr_rx = agreed_pwr->pwr_tx = - hisi_param->rx_pwr_pwm; - } - -/* -* we would like tx to work in the minimum number of lanes -* between device capability and vendor preferences. -* the same decision will be made for rx -*/ - agreed_pwr->lane_tx = -min_t (u32, dev_max->lane_tx, hisi_param->tx_lanes); - agreed_pwr->lane_rx = -min_t (u32, dev_max->lane_rx, hisi_param->rx_lanes); - -/* device maximum gear is the minimum between device rx and tx gears */ - min_dev_gear =min_t (u32, dev_max->gear_rx, dev_max->gear_tx); - -/* -* if both device capabilities and vendor pre-defined preferences are -* both HS or both PWM then set the minimum gear to be the chosen -* working gear. -* if one is PWM and one is HS then the one that is PWM get to decide -* what is the gear, as it is the one that also decided previously what -* pwr the device will be configured to. -*/ -if ((is_dev_sup_hs && is_hisi_max_hs) || - (!is_dev_sup_hs && !is_hisi_max_hs)) - agreed_pwr->gear_rx = agreed_pwr->gear_tx = -min_t (u32, min_dev_gear, min_hisi_gear); -else - agreed_pwr->gear_rx = agreed_pwr->gear_tx = min_hisi_gear; - - agreed_pwr->hs_rate = hisi_param->hs_rate; - -pr_info ("ufs final power mode: gear = %d, lane = %d, pwr = %d, rate = %d\n" , - agreed_pwr->gear_rx, agreed_pwr->lane_rx, agreed_pwr->pwr_rx, - agreed_pwr->hs_rate); -return 0 ; -} - -static void ufs_hisi_set_dev_cap (struct ufs_hisi_dev_params *hisi_param) +static void ufs_hisi_set_dev_cap (struct ufs_dev_params *hisi_param) { hisi_param->rx_lanes =UFS_HISI_LIMIT_NUM_LANES_RX ; hisi_param->tx_lanes =UFS_HISI_LIMIT_NUM_LANES_TX ;
@@ -434,7 +333,7 @@ static int ufs_hi3660_pwr_change_notify(struct ufs_hba *hba,struct ufs_pa_layer_attr *dev_max_params, struct ufs_pa_layer_attr *dev_req_params) { - struct ufs_hisi_dev_params ufs_hisi_cap; + struct ufs_dev_params ufs_hisi_cap;int ret =0 ;if (!dev_req_params) {
@@ -447,8 +346,8 @@ static int ufs_hi3660_pwr_change_notify(struct ufs_hba *hba,switch (status) {case PRE_CHANGE :ufs_hisi_set_dev_cap (&ufs_hisi_cap); - ret =ufs_hisi_get_pwr_dev_param ( - &ufs_hisi_cap, dev_max_params, dev_req_params); + ret =ufshcd_get_pwr_dev_param (&ufs_hisi_cap, + dev_max_params, dev_req_params);if (ret) {dev_err (hba->dev,"%s: failed to determine capabilities\n" , __func__);
Signature · 1 line
2.18.0
PATCH v4 4/7 dt-bindings: phy: Add document for phy-mtk-ufs
In reply to Stanley ChuAdd UFS M-PHY node document for MediaTek SoC chips.
--- .../devicetree/bindings/phy/phy-mtk-ufs.txt | 36 +++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 Documentation/devicetree/bindings/phy/phy-mtk-ufs.txt
Documentation/devicetree/bindings/phy/phy-mtk-ufs.txt new file +36 -0
@@ -0,0 +1,36 @@ +MediaTek Universal Flash Storage (UFS) M-PHY binding +-------------------------------------------------------- + +UFS M-PHY nodes are defined to describe on-chip UFS M-PHY hardware macro. +Each UFS M-PHY node should have its own node. + +To bind UFS M-PHY with UFS host controller, the controller node should +contain a phandle reference to UFS M-PHY node. + +Required properties for UFS M-PHY nodes: +- compatible : Compatible list, contains the following controller: + "mediatek,mt8183-ufsphy" for ufs phy + persent on MT81xx chipsets. +- reg : Address and length of the UFS M-PHY register set. +- #phy-cells : This property shall be set to 0 +- clocks : List of phandle and clock specifier pairs. +- clock-names : List of clock input name strings sorted in the same + order as the clocks property. "unipro-clk" and + "mp-clk" are mandatory. + +Example: + + ufsphy: phy@11fa0000 { + compatible = "mediatek,mt8183-ufsphy"; + reg = <0 0x11fa0000 0 0xc000>; + #phy-cells = <0>; + + clocks = <&infracfg_ao INFRACFG_AO_UNIPRO_SCK_CG>, + <&infracfg_ao INFRACFG_AO_UFS_MP_SAP_BCLK_CG>; + clock-names = "unipro-clk", "mp-clk"; + }; + + ufshci@11270000 { + ... + phys = <&ufsphy>; + };
Signature · 1 line
2.18.0
PATCH v4 5/7 dt-bindings: scsi: ufs: Add document for ufs-mediatek
In reply to Stanley ChuAdd UFS and UFS PHY node document for Mediatek SoC chips.
--- .../devicetree/bindings/ufs/ufs-mediatek.txt | 44 +++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 Documentation/devicetree/bindings/ufs/ufs-mediatek.txt
Documentation/devicetree/bindings/ufs/ufs-mediatek.txt new file +44 -0
@@ -0,0 +1,44 @@ +* Mediatek Universal Flash Storage (UFS) Host Controller + +UFS nodes are defined to describe on-chip UFS hardware macro. +Each UFS Host Controller should have its own node. + +To bind UFS PHY with UFS host controller, the controller node should +contain a phandle reference to UFS M-PHY node. + +Required properties for UFS nodes: +- compatible : Compatible list, contains the following controller: + "mediatek,mt8183-ufshci" for MediaTek UFS host controller + present on MT81xx chipsets. +- reg : Address and length of the UFS register set. +- phys : phandle to m-phy. +- clocks : List of phandle and clock specifier pairs. +- clock-names : List of clock input name strings sorted in the same + order as the clocks property. "ufs-clk" is mandatory. +- freq-table-hz : Array of <min max> operating frequencies stored in the same + order as the clocks property. If this property is not + defined or a value in the array is "0" then it is assumed + that the frequency is set by the parent clock or a + fixed rate clock source. +- vcc-supply : Power to the UFS device. +- vcc-fixed-regulator: Specify that vcc-supply is a fixed regulator. + +Example: + + ufsphy: phy@11fa0000 { + ... + }; + + ufshci@11270000 { + compatible = "mediatek,mt8183-ufshci"; + reg = <0 0x11270000 0 0x2300>; + interrupts = <GIC_SPI 104 IRQ_TYPE_LEVEL_LOW>; + phys = <&ufsphy>; + + clocks = <&infracfg_ao INFRACFG_AO_UFS_CG>; + clock-names = "ufs-clk"; + freq-table-hz = <0 0>; + + vcc-supply = <&mt_pmic_vemc_ldo_reg>; + vcc-fixed-regulator; + };
Signature · 1 line
2.18.0
PATCH v4 6/7 phy: mediatek: Add UFS M-PHY driver
In reply to Stanley ChuAdd UFS M-PHY driver on MediaTek chipsets.
--- drivers/phy/mediatek/Kconfig | 9 ++ drivers/phy/mediatek/Makefile | 1 + drivers/phy/mediatek/phy-mtk-ufs.c | 239 +++++++++++++++++++++++++++++ 3 files changed, 249 insertions(+) create mode 100644 drivers/phy/mediatek/phy-mtk-ufs.c
drivers/phy/mediatek/Kconfig +9 -0
@@ -21,3 +21,12 @@ config PHY_MTK_XSPHY Enable this to support the SuperSpeedPlus XS-PHY transceiver for USB3.1 GEN2 controllers on MediaTek chips. The driver supports multiple USB2.0, USB3.1 GEN2 ports. + +config PHY_MTK_UFS + tristate "MediaTek UFS M-PHY driver" + depends on ARCH_MEDIATEK && OF + select GENERIC_PHY + help + Support for UFS M-PHY on MediaTek chipsets. Enable this to provide + vendor-specific initialization, power on and off flow of specified + M-PHYs.
drivers/phy/mediatek/Makefile +1 -0
@@ -5,3 +5,4 @@ obj-$(CONFIG_PHY_MTK_TPHY) += phy-mtk-tphy.o obj-$(CONFIG_PHY_MTK_XSPHY) += phy-mtk-xsphy.o +obj-$(CONFIG_PHY_MTK_UFS) += phy-mtk-ufs.o
drivers/phy/mediatek/phy-mtk-ufs.c new file +239 -0
239 lines not on this page · raw message
Signature · 1 line
2.18.0
PATCH v4 7/7 scsi: ufs-mediatek: Add UFS support for Mediatek SoC chips
In reply to Stanley ChuThis patch adds UFS support for MediaTek SoC chips.
--- drivers/scsi/ufs/Kconfig | 14 ++ drivers/scsi/ufs/Makefile | 1 + drivers/scsi/ufs/ufs-mediatek.c | 368 ++++++++++++++++++++++++++++++++ drivers/scsi/ufs/ufs-mediatek.h | 54 +++++ 4 files changed, 437 insertions(+) create mode 100644 drivers/scsi/ufs/ufs-mediatek.c create mode 100644 drivers/scsi/ufs/ufs-mediatek.h
drivers/scsi/ufs/Kconfig +14 -0
@@ -109,6 +109,20 @@ config SCSI_UFS_QCOM Select this if you have UFS controller on QCOM chipset. If unsure, say N. +config SCSI_UFS_MEDIATEK + tristate "Mediatek specific hooks to UFS controller platform driver" + depends on SCSI_UFSHCD_PLATFORM && ARCH_MEDIATEK + select PHY_MTK_UFS + help + This selects the Mediatek specific additions to UFSHCD platform driver. + UFS host on Mediatek needs some vendor specific configuration before + accessing the hardware which includes PHY configuration and vendor + specific registers. + + Select this if you have UFS controller on Mediatek chipset. + + If unsure, say N. + config SCSI_UFS_HISI tristate "Hisilicon specific hooks to UFS controller platform driver" depends on (ARCH_HISI || COMPILE_TEST) && SCSI_UFSHCD_PLATFORM
drivers/scsi/ufs/Makefile +1 -0
@@ -10,3 +10,4 @@ ufshcd-core-$(CONFIG_SCSI_UFS_BSG) += ufs_bsg.o obj-$(CONFIG_SCSI_UFSHCD_PCI) += ufshcd-pci.o obj-$(CONFIG_SCSI_UFSHCD_PLATFORM) += ufshcd-pltfrm.o obj-$(CONFIG_SCSI_UFS_HISI) += ufs-hisi.o +obj-$(CONFIG_SCSI_UFS_MEDIATEK) += ufs-mediatek.o
drivers/scsi/ufs/ufs-mediatek.c new file +368 -0
368 lines not on this page · raw message
drivers/scsi/ufs/ufs-mediatek.h new file +54 -0
54 lines not on this page · raw message
Signature · 1 line
2.18.0