[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f5ac07e3-3fde-4ac8-8cfc-fb7918ffb2a7@linaro.org>
Date: Wed, 30 Oct 2024 08:56:13 +0000
From: Tudor Ambarus <tudor.ambarus@...aro.org>
To: Peter Griffin <peter.griffin@...aro.org>, alim.akhtar@...sung.com,
James.Bottomley@...senPartnership.com, martin.petersen@...cle.com,
avri.altman@....com, bvanassche@....org, krzk@...nel.org
Cc: andre.draszik@...aro.org, kernel-team@...roid.com,
willmcvicker@...gle.com, linux-scsi@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
ebiggers@...nel.org
Subject: Re: [PATCH v2 04/11] scsi: ufs: exynos: Add
EXYNOS_UFS_OPT_SKIP_CONFIG_PHY_ATTR check
On 10/25/24 2:14 PM, Peter Griffin wrote:
> The values calculated in exynos_ufs_specify_phy_time_attr() are only used
> in exynos_ufs_config_phy_time_attr() and exynos_ufs_config_phy_cap_attr()
all values set in exynos_ufs_specify_phy_time_attr() are used *only* in
exynos_ufs_config_phy_time_attr(). Or did I miss something?
> if EXYNOS_UFS_OPT_SKIP_CONFIG_PHY_ATTR flag is not set.
yep, wonderful.
>
> Add a check for this flag to exynos_ufs_specify_phy_time_attr() and
> return for platforms that don't set it.
>
> Signed-off-by: Peter Griffin <peter.griffin@...aro.org>
> ---
> drivers/ufs/host/ufs-exynos.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/ufs/host/ufs-exynos.c b/drivers/ufs/host/ufs-exynos.c
> index d685d3e93ea1..a1a2fdcb8a40 100644
> --- a/drivers/ufs/host/ufs-exynos.c
> +++ b/drivers/ufs/host/ufs-exynos.c
> @@ -546,6 +546,9 @@ static void exynos_ufs_specify_phy_time_attr(struct exynos_ufs *ufs)
> struct exynos_ufs_uic_attr *attr = ufs->drv_data->uic_attr;
> struct ufs_phy_time_cfg *t_cfg = &ufs->t_cfg;
>
> + if (ufs->opts & EXYNOS_UFS_OPT_SKIP_CONFIG_PHY_ATTR)
> + return;
> +
> t_cfg->tx_linereset_p =
> exynos_ufs_calc_time_cntr(ufs, attr->tx_dif_p_nsec);
> t_cfg->tx_linereset_n =
tx_linereset_n, rx_hibern8_wait is set but not used anywhere. Can we
remove it? Not related to this patch though.
Powered by blists - more mailing lists