public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter Wang (王信友)" <peter.wang@mediatek.com>
To: "beanhuo@micron.com" <beanhuo@micron.com>,
	"avri.altman@wdc.com" <avri.altman@wdc.com>,
	"quic_rampraka@quicinc.com" <quic_rampraka@quicinc.com>,
	"quic_cang@quicinc.com" <quic_cang@quicinc.com>,
	"quic_nguyenb@quicinc.com" <quic_nguyenb@quicinc.com>,
	"quic_nitirawa@quicinc.com" <quic_nitirawa@quicinc.com>,
	"bvanassche@acm.org" <bvanassche@acm.org>,
	"quic_ziqichen@quicinc.com" <quic_ziqichen@quicinc.com>,
	"junwoo80.lee@samsung.com" <junwoo80.lee@samsung.com>,
	"mani@kernel.org" <mani@kernel.org>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "ahalaney@redhat.com" <ahalaney@redhat.com>,
	"neil.armstrong@linaro.org" <neil.armstrong@linaro.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"manivannan.sadhasivam@linaro.org"
	<manivannan.sadhasivam@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	"James.Bottomley@HansenPartnership.com"
	<James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH v4 5/8] scsi: ufs: core: Enable multi-level gear scaling
Date: Tue, 11 Feb 2025 09:28:30 +0000	[thread overview]
Message-ID: <5c2ae6c27ef0679d6664a759959ae604e560f60a.camel@mediatek.com> (raw)
In-Reply-To: <20250210100212.855127-6-quic_ziqichen@quicinc.com>

On Mon, 2025-02-10 at 18:02 +0800, Ziqi Chen wrote:
> 
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> 
> 
> From: Can Guo <quic_cang@quicinc.com>
> 
> With OPP V2 enabled, devfreq can scale clocks amongst multiple
> frequency
> plans. However, the gear speed is only toggled between min and max
> during
> clock scaling. Enable multi-level gear scaling by mapping clock
> frequencies
> to gear speeds, so that when devfreq scales clock frequencies we can
> put
> the UFS link at the appropriate gear speeds accordingly.
> 
> Signed-off-by: Can Guo <quic_cang@quicinc.com>
> Co-developed-by: Ziqi Chen <quic_ziqichen@quicinc.com>
> Signed-off-by: Ziqi Chen <quic_ziqichen@quicinc.com>
> Reviewed-by: Bean Huo <beanhuo@micron.com>
> Reviewed-by: Bart Van Assche <bvanassche@acm.org>
> Tested-by: Neil Armstrong <neil.armstrong@linaro.org>
> ---
> 
> v1 -> v2:
> Rename the lable "do_pmc" to "config_pwr_mode".
> 
> v2 -> v3:
> Use assignment instead memcpy() in function ufshcd_scale_gear().
> 
> v3 -> v4:
> Typo fixed for commit message.
> ---
>  drivers/ufs/core/ufshcd.c | 51 +++++++++++++++++++++++++++++++------
> --
>  1 file changed, 41 insertions(+), 10 deletions(-)
> 
> diff --git a/drivers/ufs/core/ufshcd.c b/drivers/ufs/core/ufshcd.c
> index 8d295cc827cc..ebab897080a6 100644
> --- a/drivers/ufs/core/ufshcd.c
> +++ b/drivers/ufs/core/ufshcd.c
> @@ -1308,16 +1308,26 @@ static int
> ufshcd_wait_for_doorbell_clr(struct ufs_hba *hba,
>  /**
>   * ufshcd_scale_gear - scale up/down UFS gear
>   * @hba: per adapter instance
> + * @target_gear: target gear to scale to
>   * @scale_up: True for scaling up gear and false for scaling down
>   *
>   * Return: 0 for success; -EBUSY if scaling can't happen at this
> time;
>   * non-zero for any other errors.
>   */
> -static int ufshcd_scale_gear(struct ufs_hba *hba, bool scale_up)
> +static int ufshcd_scale_gear(struct ufs_hba *hba, u32 target_gear,
> bool scale_up)
>  {
>         int ret = 0;
>         struct ufs_pa_layer_attr new_pwr_info;
> 
> +       if (target_gear) {
> +               new_pwr_info = hba->pwr_info;
> +               new_pwr_info.gear_tx = target_gear;
> +               new_pwr_info.gear_rx = target_gear;
> +
> +               goto config_pwr_mode;
> +       }
> +
> +       /* Legacy gear scaling, in case vops_freq_to_gear_speed() is
> not implemented */
>         if (scale_up) {
>                 memcpy(&new_pwr_info, &hba-
> >clk_scaling.saved_pwr_info,
>                        sizeof(struct ufs_pa_layer_attr));
> @@ -1338,6 +1348,7 @@ static int ufshcd_scale_gear(struct ufs_hba
> *hba, bool scale_up)
>                 }
>         }
> 
> +config_pwr_mode:
>         /* check if the power mode needs to be changed or not? */
>         ret = ufshcd_config_pwr_mode(hba, &new_pwr_info);
>         if (ret)
> @@ -1408,15 +1419,26 @@ static void
> ufshcd_clock_scaling_unprepare(struct ufs_hba *hba, int err, bool sc
>  static int ufshcd_devfreq_scale(struct ufs_hba *hba, unsigned long
> freq,
>                                 bool scale_up)
>  {
> +       u32 old_gear = hba->pwr_info.gear_rx;
> +       int new_gear = 0;
>         int ret = 0;
> 
> +       new_gear = ufshcd_vops_freq_to_gear_speed(hba, freq);
> +       if (new_gear < 0)
> +               /*
> +                * return negative value means that the
> vops_freq_to_gear_speed() is not
> +                * implemented or didn't find matched gear speed,
> assign '0' to new_gear
> +                * to switch to legacy gear scaling sequence in
> ufshcd_scale_gear().
> +                */
> +               new_gear = 0;
> +
> 

Hi Ziqi,

I think remove help function is better. 
No need change new_gear type when use.
The readability is higher, and no need add that large amount comments.

       u32_new_gear = 0;
       if (hba->vops && hba->vops->freq_to_gear_speed)
               new_gear = hba->vops->freq_to_gear_speed(hba, freq);


Thanks.
Peter



>         ret = ufshcd_clock_scaling_prepare(hba, 1 * USEC_PER_SEC);
>         if (ret)
>                 return ret;
> 
>         /* scale down the gear before scaling down clocks */
>         if (!scale_up) {
> -               ret = ufshcd_scale_gear(hba, false);
> +               ret = ufshcd_scale_gear(hba, (u32)new_gear, false);
>                 if (ret)
>                         goto out_unprepare;
>         }
> @@ -1424,13 +1446,13 @@ static int ufshcd_devfreq_scale(struct
> ufs_hba *hba, unsigned long freq,
>         ret = ufshcd_scale_clks(hba, freq, scale_up);
>         if (ret) {
>                 if (!scale_up)
> -                       ufshcd_scale_gear(hba, true);
> +                       ufshcd_scale_gear(hba, old_gear, true);
>                 goto out_unprepare;
>         }
> 
>         /* scale up the gear after scaling up clocks */
>         if (scale_up) {
> -               ret = ufshcd_scale_gear(hba, true);
> +               ret = ufshcd_scale_gear(hba, (u32)new_gear, true);
>                 if (ret) {
>                         ufshcd_scale_clks(hba, hba->devfreq-
> >previous_freq,
>                                           false);
> @@ -1723,6 +1745,8 @@ static ssize_t
> ufshcd_clkscale_enable_store(struct device *dev,
>                 struct device_attribute *attr, const char *buf,
> size_t count)
>  {
>         struct ufs_hba *hba = dev_get_drvdata(dev);
> +       struct ufs_clk_info *clki;
> +       unsigned long freq;
>         u32 value;
>         int err = 0;
> 
> @@ -1746,14 +1770,21 @@ static ssize_t
> ufshcd_clkscale_enable_store(struct device *dev,
> 
>         if (value) {
>                 ufshcd_resume_clkscaling(hba);
> -       } else {
> -               ufshcd_suspend_clkscaling(hba);
> -               err = ufshcd_devfreq_scale(hba, ULONG_MAX, true);
> -               if (err)
> -                       dev_err(hba->dev, "%s: failed to scale clocks
> up %d\n",
> -                                       __func__, err);
> +               goto out_rel;
>         }
> 
> +       clki = list_first_entry(&hba->clk_list_head, struct
> ufs_clk_info, list);
> +       freq = clki->max_freq;
> +
> +       ufshcd_suspend_clkscaling(hba);
> +       err = ufshcd_devfreq_scale(hba, freq, true);
> +       if (err)
> +               dev_err(hba->dev, "%s: failed to scale clocks up
> %d\n",
> +                               __func__, err);
> +       else
> +               hba->clk_scaling.target_freq = freq;
> +
> +out_rel:
>         ufshcd_release(hba);
>         ufshcd_rpm_put_sync(hba);
>  out:
> --
> 2.34.1
> 


  reply	other threads:[~2025-02-11  9:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 10:02 [PATCH v4 0/8] Support Multi-frequency scale for UFS Ziqi Chen
2025-02-10 10:02 ` [PATCH v4 1/8] scsi: ufs: core: Pass target_freq to clk_scale_notify() vop Ziqi Chen
2025-02-11  3:52   ` Peter Wang (王信友)
2025-02-11 10:04     ` Ziqi Chen
2025-02-10 10:02 ` [PATCH v4 2/8] scsi: ufs: qcom: Pass target_freq to clk scale pre and post change Ziqi Chen
2025-02-10 10:02 ` [PATCH v4 3/8] scsi: ufs: core: Add a vop to map clock frequency to gear speed Ziqi Chen
2025-02-11  6:02   ` Peter Wang (王信友)
2025-02-11 10:14     ` Ziqi Chen
2025-02-10 10:02 ` [PATCH v4 4/8] scsi: ufs: qcom: Implement the freq_to_gear_speed() vop Ziqi Chen
2025-02-10 10:02 ` [PATCH v4 5/8] scsi: ufs: core: Enable multi-level gear scaling Ziqi Chen
2025-02-11  9:28   ` Peter Wang (王信友) [this message]
2025-02-11 10:28     ` Ziqi Chen
2025-02-10 10:02 ` [PATCH v4 6/8] scsi: ufs: core: Check if scaling up is required when disable clkscale Ziqi Chen
2025-02-10 18:17   ` Bean Huo
2025-02-11 12:58   ` Peter Wang (王信友)
2025-02-10 10:02 ` [PATCH v4 7/8] scsi: ufs: core: Toggle Write Booster during clock scaling base on gear speed Ziqi Chen
2025-02-11 12:59   ` Peter Wang (王信友)
2025-02-10 10:02 ` [PATCH v4 8/8] ABI: sysfs-driver-ufs: Add missing UFS sysfs attributes Ziqi Chen
2025-02-10 18:24   ` Bean Huo
2025-02-13  7:55     ` Ziqi Chen

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=5c2ae6c27ef0679d6664a759959ae604e560f60a.camel@mediatek.com \
    --to=peter.wang@mediatek.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=ahalaney@redhat.com \
    --cc=alim.akhtar@samsung.com \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=junwoo80.lee@samsung.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=martin.petersen@oracle.com \
    --cc=neil.armstrong@linaro.org \
    --cc=quic_cang@quicinc.com \
    --cc=quic_nguyenb@quicinc.com \
    --cc=quic_nitirawa@quicinc.com \
    --cc=quic_rampraka@quicinc.com \
    --cc=quic_ziqichen@quicinc.com \
    /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