From: "Alim Akhtar" <alim.akhtar@samsung.com> To: "'Chanho Park'" <chanho61.park@samsung.com>, "'Kishon Vijay Abraham I'" <kishon@ti.com>, "'Vinod Koul'" <vkoul@kernel.org>, "'Krzysztof Kozlowski'" <krzysztof.kozlowski@linaro.org> Cc: <linux-phy@lists.infradead.org>, <linux-arm-kernel@lists.infradead.org> Subject: RE: [PATCH] phy: samsung: exynosautov9-ufs: correct TSRV register configurations Date: Fri, 3 Jun 2022 06:57:23 +0530 [thread overview] Message-ID: <000901d876e9$150a3e40$3f1ebac0$@samsung.com> (raw) In-Reply-To: <20220531082657.53158-1-chanho61.park@samsung.com> >-----Original Message----- >From: Chanho Park [mailto:chanho61.park@samsung.com] >Sent: Tuesday, May 31, 2022 1:57 PM >To: Kishon Vijay Abraham I <kishon@ti.com>; Vinod Koul ><vkoul@kernel.org>; Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>; >Alim Akhtar <alim.akhtar@samsung.com> >Cc: linux-phy@lists.infradead.org; linux-arm-kernel@lists.infradead.org; >Chanho Park <chanho61.park@samsung.com> >Subject: [PATCH] phy: samsung: exynosautov9-ufs: correct TSRV register >configurations > >For exynos auto v9's UFS MPHY, We should use 0x50 offset of TSRV register >configurations. So, it must be > >s/PHY_TRSV_REG_CFG/PHY_TRSV_REG_CFG/g > You mean s/PHY_TRSV_REG_CFG/PHY_TRSV_REG_CFG_AUTOV9/g >Fixes: d64519249e1d ("phy: samsung-ufs: support exynosauto ufs phy driver") >Signed-off-by: Chanho Park <chanho61.park@samsung.com> >--- > drivers/phy/samsung/phy-exynosautov9-ufs.c | 18 +++++++++--------- > 1 file changed, 9 insertions(+), 9 deletions(-) > >diff --git a/drivers/phy/samsung/phy-exynosautov9-ufs.c >b/drivers/phy/samsung/phy-exynosautov9-ufs.c >index 36398a15c2db..d043dfdb598a 100644 >--- a/drivers/phy/samsung/phy-exynosautov9-ufs.c >+++ b/drivers/phy/samsung/phy-exynosautov9-ufs.c >@@ -31,22 +31,22 @@ static const struct samsung_ufs_phy_cfg >exynosautov9_pre_init_cfg[] = { > PHY_COMN_REG_CFG(0x023, 0xc0, PWR_MODE_ANY), > PHY_COMN_REG_CFG(0x023, 0x00, PWR_MODE_ANY), > >- PHY_TRSV_REG_CFG(0x042, 0x5d, PWR_MODE_ANY), >- PHY_TRSV_REG_CFG(0x043, 0x80, PWR_MODE_ANY), >+ PHY_TRSV_REG_CFG_AUTOV9(0x042, 0x5d, PWR_MODE_ANY), >+ PHY_TRSV_REG_CFG_AUTOV9(0x043, 0x80, PWR_MODE_ANY), > > END_UFS_PHY_CFG, > }; > > /* Calibration for HS mode series A/B */ static const struct >samsung_ufs_phy_cfg exynosautov9_pre_pwr_hs_cfg[] = { >- PHY_TRSV_REG_CFG(0x032, 0xbc, PWR_MODE_HS_ANY), >- PHY_TRSV_REG_CFG(0x03c, 0x7f, PWR_MODE_HS_ANY), >- PHY_TRSV_REG_CFG(0x048, 0xc0, PWR_MODE_HS_ANY), >+ PHY_TRSV_REG_CFG_AUTOV9(0x032, 0xbc, PWR_MODE_HS_ANY), >+ PHY_TRSV_REG_CFG_AUTOV9(0x03c, 0x7f, PWR_MODE_HS_ANY), >+ PHY_TRSV_REG_CFG_AUTOV9(0x048, 0xc0, PWR_MODE_HS_ANY), > >- PHY_TRSV_REG_CFG(0x04a, 0x00, PWR_MODE_HS_G3_SER_B), >- PHY_TRSV_REG_CFG(0x04b, 0x10, PWR_MODE_HS_G1_SER_B | >- PWR_MODE_HS_G3_SER_B), >- PHY_TRSV_REG_CFG(0x04d, 0x63, PWR_MODE_HS_G3_SER_B), >+ PHY_TRSV_REG_CFG_AUTOV9(0x04a, 0x00, >PWR_MODE_HS_G3_SER_B), >+ PHY_TRSV_REG_CFG_AUTOV9(0x04b, 0x10, >PWR_MODE_HS_G1_SER_B | >+ PWR_MODE_HS_G3_SER_B), >+ PHY_TRSV_REG_CFG_AUTOV9(0x04d, 0x63, >PWR_MODE_HS_G3_SER_B), > > END_UFS_PHY_CFG, > }; >-- >2.36.1 -- linux-phy mailing list linux-phy@lists.infradead.org https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: "Alim Akhtar" <alim.akhtar@samsung.com> To: "'Chanho Park'" <chanho61.park@samsung.com>, "'Kishon Vijay Abraham I'" <kishon@ti.com>, "'Vinod Koul'" <vkoul@kernel.org>, "'Krzysztof Kozlowski'" <krzysztof.kozlowski@linaro.org> Cc: <linux-phy@lists.infradead.org>, <linux-arm-kernel@lists.infradead.org> Subject: RE: [PATCH] phy: samsung: exynosautov9-ufs: correct TSRV register configurations Date: Fri, 3 Jun 2022 06:57:23 +0530 [thread overview] Message-ID: <000901d876e9$150a3e40$3f1ebac0$@samsung.com> (raw) In-Reply-To: <20220531082657.53158-1-chanho61.park@samsung.com> >-----Original Message----- >From: Chanho Park [mailto:chanho61.park@samsung.com] >Sent: Tuesday, May 31, 2022 1:57 PM >To: Kishon Vijay Abraham I <kishon@ti.com>; Vinod Koul ><vkoul@kernel.org>; Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>; >Alim Akhtar <alim.akhtar@samsung.com> >Cc: linux-phy@lists.infradead.org; linux-arm-kernel@lists.infradead.org; >Chanho Park <chanho61.park@samsung.com> >Subject: [PATCH] phy: samsung: exynosautov9-ufs: correct TSRV register >configurations > >For exynos auto v9's UFS MPHY, We should use 0x50 offset of TSRV register >configurations. So, it must be > >s/PHY_TRSV_REG_CFG/PHY_TRSV_REG_CFG/g > You mean s/PHY_TRSV_REG_CFG/PHY_TRSV_REG_CFG_AUTOV9/g >Fixes: d64519249e1d ("phy: samsung-ufs: support exynosauto ufs phy driver") >Signed-off-by: Chanho Park <chanho61.park@samsung.com> >--- > drivers/phy/samsung/phy-exynosautov9-ufs.c | 18 +++++++++--------- > 1 file changed, 9 insertions(+), 9 deletions(-) > >diff --git a/drivers/phy/samsung/phy-exynosautov9-ufs.c >b/drivers/phy/samsung/phy-exynosautov9-ufs.c >index 36398a15c2db..d043dfdb598a 100644 >--- a/drivers/phy/samsung/phy-exynosautov9-ufs.c >+++ b/drivers/phy/samsung/phy-exynosautov9-ufs.c >@@ -31,22 +31,22 @@ static const struct samsung_ufs_phy_cfg >exynosautov9_pre_init_cfg[] = { > PHY_COMN_REG_CFG(0x023, 0xc0, PWR_MODE_ANY), > PHY_COMN_REG_CFG(0x023, 0x00, PWR_MODE_ANY), > >- PHY_TRSV_REG_CFG(0x042, 0x5d, PWR_MODE_ANY), >- PHY_TRSV_REG_CFG(0x043, 0x80, PWR_MODE_ANY), >+ PHY_TRSV_REG_CFG_AUTOV9(0x042, 0x5d, PWR_MODE_ANY), >+ PHY_TRSV_REG_CFG_AUTOV9(0x043, 0x80, PWR_MODE_ANY), > > END_UFS_PHY_CFG, > }; > > /* Calibration for HS mode series A/B */ static const struct >samsung_ufs_phy_cfg exynosautov9_pre_pwr_hs_cfg[] = { >- PHY_TRSV_REG_CFG(0x032, 0xbc, PWR_MODE_HS_ANY), >- PHY_TRSV_REG_CFG(0x03c, 0x7f, PWR_MODE_HS_ANY), >- PHY_TRSV_REG_CFG(0x048, 0xc0, PWR_MODE_HS_ANY), >+ PHY_TRSV_REG_CFG_AUTOV9(0x032, 0xbc, PWR_MODE_HS_ANY), >+ PHY_TRSV_REG_CFG_AUTOV9(0x03c, 0x7f, PWR_MODE_HS_ANY), >+ PHY_TRSV_REG_CFG_AUTOV9(0x048, 0xc0, PWR_MODE_HS_ANY), > >- PHY_TRSV_REG_CFG(0x04a, 0x00, PWR_MODE_HS_G3_SER_B), >- PHY_TRSV_REG_CFG(0x04b, 0x10, PWR_MODE_HS_G1_SER_B | >- PWR_MODE_HS_G3_SER_B), >- PHY_TRSV_REG_CFG(0x04d, 0x63, PWR_MODE_HS_G3_SER_B), >+ PHY_TRSV_REG_CFG_AUTOV9(0x04a, 0x00, >PWR_MODE_HS_G3_SER_B), >+ PHY_TRSV_REG_CFG_AUTOV9(0x04b, 0x10, >PWR_MODE_HS_G1_SER_B | >+ PWR_MODE_HS_G3_SER_B), >+ PHY_TRSV_REG_CFG_AUTOV9(0x04d, 0x63, >PWR_MODE_HS_G3_SER_B), > > END_UFS_PHY_CFG, > }; >-- >2.36.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-03 1:27 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CGME20220531082658epcas2p1a6f22a304ce8031c39c97daa90372715@epcas2p1.samsung.com> 2022-05-31 8:26 ` [PATCH] phy: samsung: exynosautov9-ufs: correct TSRV register configurations Chanho Park 2022-05-31 8:26 ` Chanho Park 2022-05-31 9:07 ` Krzysztof Kozlowski 2022-05-31 9:07 ` Krzysztof Kozlowski 2022-06-03 1:27 ` Alim Akhtar [this message] 2022-06-03 1:27 ` Alim Akhtar 2022-06-03 4:56 ` Chanho Park 2022-06-03 4:56 ` Chanho Park
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='000901d876e9$150a3e40$3f1ebac0$@samsung.com' \ --to=alim.akhtar@samsung.com \ --cc=chanho61.park@samsung.com \ --cc=kishon@ti.com \ --cc=krzysztof.kozlowski@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-phy@lists.infradead.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.