From: cang@codeaurora.org To: Vinod Koul <vkoul@kernel.org> Cc: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>, asutoshd@codeaurora.org, nguyenb@codeaurora.org, Rajendra Nayak <rnayak@codeaurora.org>, linux-scsi@vger.kernel.org, kernel-team@android.com, saravanak@google.com, Mark Salyzyn <salyzyn@google.com>, Andy Gross <agross@kernel.org>, Alim Akhtar <alim.akhtar@samsung.com>, Avri Altman <avri.altman@wdc.com>, Pedro Sousa <pedrom.sousa@synopsys.com>, "James E.J. Bottomley" <jejb@linux.ibm.com>, "Martin K. Petersen" <martin.petersen@oracle.com>, "open list:ARM/QUALCOMM SUPPORT" <linux-arm-msm@vger.kernel.org>, open list <linux-kernel@vger.kernel.org> Subject: Re: [PATCH v5 2/7] scsi: ufs-qcom: Add reset control support for host controller Date: Thu, 19 Dec 2019 15:12:25 +0800 Message-ID: <983c21bb5ad2d38e11c074528d8898b9@codeaurora.org> (raw) In-Reply-To: <20191218041200.GP2536@vkoul-mobl> On 2019-12-18 12:12, Vinod Koul wrote: > On 18-12-19, 02:44, cang@codeaurora.org wrote: > >> Hi Vinod and Jeffrey, >> >> Let me summary here, now the 1000000us timeout works for both 845 and >> 8998. >> However, 8150 still fails. >> >> > > The bigger question is why is the reset causing the timeout to be >> > > increased for sdm845 and not to work in case of sm8150! (Vinod) >> >> I would not say this patch increases the timeout. With this patch, >> the PCS polling timeout, per my profiling, the PCS ready usually needs >> less than 5000us, which is the actual time needed for PCS bit to be >> ready. >> >> The reason why 1000us worked for you is because, w/o the patch, UFS >> PHY >> registers are retained from pre-kernel stage (bootloader i.e.), the >> PCS >> ready >> bit was set to 1 in pre-kernel stage, so when kernel driver reads it, >> it >> returns >> 1, not even to be polled at all. It may seem "faster", but not the >> right >> thing to do, because kernel stage may need different PHY settings than >> pre-kernel stage, keeping the settings configured in pre-kernel stage >> is not >> always right, so this patch is needed. And increasing 1000us to >> 1000000us >> is the right thing to do, but not a hack. >> >> As reg for the phy initialization timeout on 8150, I found there is >> something >> wrong with its settings in /drivers/phy/qualcomm/phy-qcom-qmp.c >> >> static const struct qmp_phy_init_tbl sm8150_ufsphy_serdes_tbl[] = { >> QMP_PHY_INIT_CFG(QPHY_POWER_DOWN_CONTROL, 0x01), >> QMP_PHY_INIT_CFG(QSERDES_V4_COM_SYSCLK_EN_SEL, 0xd9), >> >> "QMP_PHY_INIT_CFG(QPHY_POWER_DOWN_CONTROL, 0x01)" should NOT appear in >> the >> serdes >> table! I haven't check who made this change, but please have a try >> after >> remove >> this line from sm8150_ufsphy_serdes_tbl. > > That is me :) Looks like I made an error while porting from downstream. > I > did a quick check to remove this and it doesn't work yet, let me > recheck > the settings again ... > > Thanks for your help! Hi Vinod, Indeed, you need to tweak your settings. I spent some time help you figure this out. Try below change and please let me know if it can resolve your problem. I would not say this is a regression caused by my patch, it is just my patch reveals something incorrect in the settings. diff --git a/drivers/phy/qualcomm/phy-qcom-qmp.c b/drivers/phy/qualcomm/phy-qcom-qmp.c index 8e642a6..0cc9044 100755 --- a/drivers/phy/qualcomm/phy-qcom-qmp.c +++ b/drivers/phy/qualcomm/phy-qcom-qmp.c @@ -66,7 +66,7 @@ /* QPHY_V3_PCS_MISC_CLAMP_ENABLE register bits */ #define CLAMP_EN BIT(0) /* enables i/o clamp_n */ -#define PHY_INIT_COMPLETE_TIMEOUT 1000 +#define PHY_INIT_COMPLETE_TIMEOUT 1000000 #define POWER_DOWN_DELAY_US_MIN 10 #define POWER_DOWN_DELAY_US_MAX 11 @@ -166,6 +166,7 @@ static const unsigned int sdm845_ufsphy_regs_layout[] = { }; static const unsigned int sm8150_ufsphy_regs_layout[] = { + [QPHY_SW_RESET] = 0x08, [QPHY_START_CTRL] = 0x00, [QPHY_PCS_READY_STATUS] = 0x180, }; @@ -885,7 +886,6 @@ static const struct qmp_phy_init_tbl msm8998_usb3_pcs_tbl[] = { }; static const struct qmp_phy_init_tbl sm8150_ufsphy_serdes_tbl[] = { - QMP_PHY_INIT_CFG(QPHY_POWER_DOWN_CONTROL, 0x01), QMP_PHY_INIT_CFG(QSERDES_V4_COM_SYSCLK_EN_SEL, 0xd9), QMP_PHY_INIT_CFG(QSERDES_V4_COM_HSCLK_SEL, 0x11), QMP_PHY_INIT_CFG(QSERDES_V4_COM_HSCLK_HS_SWITCH_SEL, 0x00), @@ -1390,7 +1390,6 @@ static const struct qmp_phy_cfg sm8150_ufsphy_cfg = { .pwrdn_ctrl = SW_PWRDN, .is_dual_lane_phy = true, - .no_pcs_sw_reset = true, }; static void qcom_qmp_phy_configure(void __iomem *base, --- Aside of the phy settings, your DT needs some modifications too, seems you copied most of them from sdm845. https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git/commit/?h=for-next&id=3834a2e92229ef26d30de28acb698b2b23d3e397 <--snip--> > + ufs_mem_phy: phy@1d87000 { > + compatible = "qcom,sm8150-qmp-ufs-phy"; > + reg = <0 0x01d87000 0 0x18c>; The size 0x18c is wrong, in the code you are even accessing registers whose offsets are beyond 0x18c, see #define QSERDES_V4_COM_BIN_VCOCAL_CMP_CODE1_MODE0 0x1ac #define QSERDES_V4_COM_BIN_VCOCAL_CMP_CODE2_MODE0 0x1b0 #define QSERDES_V4_COM_BIN_VCOCAL_CMP_CODE1_MODE1 0x1b4 #define QSERDES_V4_COM_BIN_VCOCAL_HSCLK_SEL 0x1bc #define QSERDES_V4_COM_BIN_VCOCAL_CMP_CODE2_MODE1 0x1b8 FYI, the total size of serdes registers is 0x1c0. <--snip--> > + ufs_mem_phy_lanes: lanes@1d87400 { > + reg = <0 0x01d87400 0 0x108>, > + <0 0x01d87600 0 0x1e0>, > + <0 0x01d87c00 0 0x1dc>, Same as above, see #define QPHY_V4_MULTI_LANE_CTRL1 0x1e0 FYI, the total size of PCS registers is 0x200 > + <0 0x01d87800 0 0x108>, > + <0 0x01d87a00 0 0x1e0>; > + #phy-cells = <0>; > + }; <--snip-->
next prev parent reply index Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-15 6:09 [PATCH v5 0/7] UFS driver general fixes bundle 3 Can Guo 2019-11-15 6:09 ` [PATCH v5 1/7] scsi: ufs: Add device reset in link recovery path Can Guo 2019-11-15 6:25 ` Stanley Chu 2019-11-15 6:09 ` [PATCH v5 2/7] scsi: ufs-qcom: Add reset control support for host controller Can Guo 2019-11-15 10:08 ` Avri Altman 2019-12-16 19:04 ` Vinod Koul 2019-12-16 19:12 ` Jeffrey Hugo 2019-12-17 0:37 ` cang 2019-12-17 4:13 ` Vinod Koul 2019-12-17 7:10 ` cang 2019-12-17 9:24 ` Vinod Koul 2019-12-17 10:09 ` cang 2019-12-17 15:08 ` Vinod Koul 2019-12-17 16:00 ` Jeffrey Hugo 2019-12-17 18:44 ` cang 2019-12-18 4:12 ` Vinod Koul 2019-12-19 7:12 ` cang [this message] 2019-12-19 14:21 ` Vinod Koul 2019-12-19 14:25 ` Jeffrey Hugo 2019-12-19 14:52 ` Vinod Koul 2019-12-20 0:30 ` cang 2019-11-15 6:09 ` [PATCH v5 3/7] scsi: ufs: Fix up auto hibern8 enablement Can Guo 2019-11-15 6:35 ` Stanley Chu 2019-11-15 7:03 ` Can Guo 2019-11-15 7:18 ` Stanley Chu 2019-11-15 12:27 ` Can Guo 2019-11-15 13:46 ` Stanley Chu 2019-11-15 6:09 ` [PATCH v5 4/7] scsi: ufs: Fix register dump caused sleep in atomic context Can Guo 2019-11-15 6:09 ` [PATCH v5 5/7] scsi: ufs: Fix irq return code Can Guo 2019-11-15 6:09 ` [PATCH v5 6/7] scsi: ufs: Abort gating if clock on request is pending Can Guo 2019-11-15 6:09 ` [PATCH v5 7/7] scsi: ufs: Fix error handing during hibern8 enter Can Guo 2019-11-15 10:12 ` Avri Altman 2019-11-17 16:36 ` [EXT] " Bean Huo (beanhuo) 2019-11-19 4:28 ` [PATCH v5 0/7] UFS driver general fixes bundle 3 Martin K. Petersen
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=983c21bb5ad2d38e11c074528d8898b9@codeaurora.org \ --to=cang@codeaurora.org \ --cc=agross@kernel.org \ --cc=alim.akhtar@samsung.com \ --cc=asutoshd@codeaurora.org \ --cc=avri.altman@wdc.com \ --cc=jeffrey.l.hugo@gmail.com \ --cc=jejb@linux.ibm.com \ --cc=kernel-team@android.com \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-scsi@vger.kernel.org \ --cc=martin.petersen@oracle.com \ --cc=nguyenb@codeaurora.org \ --cc=pedrom.sousa@synopsys.com \ --cc=rnayak@codeaurora.org \ --cc=salyzyn@google.com \ --cc=saravanak@google.com \ --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
Linux-SCSI Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-scsi/0 linux-scsi/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-scsi linux-scsi/ https://lore.kernel.org/linux-scsi \ linux-scsi@vger.kernel.org public-inbox-index linux-scsi Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-scsi AGPL code for this site: git clone https://public-inbox.org/public-inbox.git