From: "Asutosh Das (asd)" <asutoshd@codeaurora.org>
To: Stanley Chu <stanley.chu@mediatek.com>,
linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
avri.altman@wdc.com, alim.akhtar@samsung.com, jejb@linux.ibm.com
Cc: bvanassche@acm.org, andy.teng@mediatek.com,
chun-hung.wu@mediatek.com, kuohong.wang@mediatek.com,
linux-kernel@vger.kernel.org, cang@codeaurora.org,
linux-mediatek@lists.infradead.org, peter.wang@mediatek.com,
matthias.bgg@gmail.com, linux-arm-kernel@lists.infradead.org,
beanhuo@micron.com
Subject: Re: [PATCH v8 8/8] scsi: ufs: cleanup WriteBooster feature
Date: Fri, 8 May 2020 09:19:22 -0700 [thread overview]
Message-ID: <ca589cd1-bf28-7227-02d7-1c7789f6f6e9@codeaurora.org> (raw)
In-Reply-To: <20200508080115.24233-9-stanley.chu@mediatek.com>
On 5/8/2020 1:01 AM, Stanley Chu wrote:
> Small cleanup as below items,
>
> 1. Use ufshcd_is_wb_allowed() directly instead of ufshcd_wb_sup()
> since ufshcd_wb_sup() just returns the result of
> ufshcd_is_wb_allowed().
>
> 2. In ufshcd_suspend(), "else if (!ufshcd_is_runtime_pm(pm_op))
> can be simplified to "else" since both have the same meaning.
>
> This patch does not change any functionality.
>
> Signed-off-by: Stanley Chu <stanley.chu@mediatek.com>
> Reviewed-by: Avri Altman <avri.altman@wdc.com>
> ---
The whole series looks good to me.
Reviewed-by: Asutosh Das <asutoshd@codeaurora.org>
> drivers/scsi/ufs/ufshcd.c | 20 +++++++-------------
> 1 file changed, 7 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
> index b6a0d77d47ac..426073a518ef 100644
> --- a/drivers/scsi/ufs/ufshcd.c
> +++ b/drivers/scsi/ufs/ufshcd.c
> @@ -253,7 +253,6 @@ static int ufshcd_scale_clks(struct ufs_hba *hba, bool scale_up);
> static irqreturn_t ufshcd_intr(int irq, void *__hba);
> static int ufshcd_change_power_mode(struct ufs_hba *hba,
> struct ufs_pa_layer_attr *pwr_mode);
> -static bool ufshcd_wb_sup(struct ufs_hba *hba);
> static int ufshcd_wb_buf_flush_enable(struct ufs_hba *hba);
> static int ufshcd_wb_buf_flush_disable(struct ufs_hba *hba);
> static int ufshcd_wb_ctrl(struct ufs_hba *hba, bool enable);
> @@ -285,7 +284,7 @@ static inline void ufshcd_wb_config(struct ufs_hba *hba)
> {
> int ret;
>
> - if (!ufshcd_wb_sup(hba))
> + if (!ufshcd_is_wb_allowed(hba))
> return;
>
> ret = ufshcd_wb_ctrl(hba, true);
> @@ -5197,18 +5196,13 @@ static void ufshcd_bkops_exception_event_handler(struct ufs_hba *hba)
> __func__, err);
> }
>
> -static bool ufshcd_wb_sup(struct ufs_hba *hba)
> -{
> - return ufshcd_is_wb_allowed(hba);
> -}
> -
> static int ufshcd_wb_ctrl(struct ufs_hba *hba, bool enable)
> {
> int ret;
> u8 index;
> enum query_opcode opcode;
>
> - if (!ufshcd_wb_sup(hba))
> + if (!ufshcd_is_wb_allowed(hba))
> return 0;
>
> if (!(enable ^ hba->wb_enabled))
> @@ -5264,7 +5258,7 @@ static int ufshcd_wb_buf_flush_enable(struct ufs_hba *hba)
> int ret;
> u8 index;
>
> - if (!ufshcd_wb_sup(hba) || hba->wb_buf_flush_enabled)
> + if (!ufshcd_is_wb_allowed(hba) || hba->wb_buf_flush_enabled)
> return 0;
>
> index = ufshcd_wb_get_flag_index(hba);
> @@ -5286,7 +5280,7 @@ static int ufshcd_wb_buf_flush_disable(struct ufs_hba *hba)
> int ret;
> u8 index;
>
> - if (!ufshcd_wb_sup(hba) || !hba->wb_buf_flush_enabled)
> + if (!ufshcd_is_wb_allowed(hba) || !hba->wb_buf_flush_enabled)
> return 0;
>
> index = ufshcd_wb_get_flag_index(hba);
> @@ -5336,7 +5330,7 @@ static bool ufshcd_wb_keep_vcc_on(struct ufs_hba *hba)
> int ret;
> u32 avail_buf;
>
> - if (!ufshcd_wb_sup(hba))
> + if (!ufshcd_is_wb_allowed(hba))
> return false;
> /*
> * The ufs device needs the vcc to be ON to flush.
> @@ -8235,12 +8229,12 @@ static int ufshcd_suspend(struct ufs_hba *hba, enum ufs_pm_op pm_op)
> * configured WB type is 70% full, keep vcc ON
> * for the device to flush the wb buffer
> */
> - if ((hba->auto_bkops_enabled && ufshcd_wb_sup(hba)) ||
> + if ((hba->auto_bkops_enabled && ufshcd_is_wb_allowed(hba)) ||
> ufshcd_wb_keep_vcc_on(hba))
> hba->dev_info.keep_vcc_on = true;
> else
> hba->dev_info.keep_vcc_on = false;
> - } else if (!ufshcd_is_runtime_pm(pm_op)) {
> + } else {
> hba->dev_info.keep_vcc_on = false;
> }
>
>
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
Linux Foundation Collaborative Project
_______________________________________________
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:[~2020-05-08 16:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 8:01 [PATCH v8 0/8] scsi: ufs: support LU Dedicated buffer mode for WriteBooster Stanley Chu
2020-05-08 8:01 ` [PATCH v8 1/8] scsi: ufs: enable WriteBooster on some pre-3.1 UFS devices Stanley Chu
2020-05-08 8:01 ` [PATCH v8 2/8] scsi: ufs: introduce fixup_dev_quirks vops Stanley Chu
2020-05-08 8:01 ` [PATCH v8 3/8] scsi: ufs: export ufs_fixup_device_setup() function Stanley Chu
2020-05-08 8:01 ` [PATCH v8 4/8] scsi: ufs-mediatek: add fixup_dev_quirks vops Stanley Chu
2020-05-08 8:01 ` [PATCH v8 5/8] scsi: ufs: add "index" in parameter list of ufshcd_query_flag() Stanley Chu
2020-05-08 8:01 ` [PATCH v8 6/8] scsi: ufs: add LU Dedicated buffer mode support for WriteBooster Stanley Chu
2020-05-08 8:01 ` [PATCH v8 7/8] scsi: ufs-mediatek: enable WriteBooster capability Stanley Chu
2020-05-08 8:01 ` [PATCH v8 8/8] scsi: ufs: cleanup WriteBooster feature Stanley Chu
2020-05-08 16:19 ` Asutosh Das (asd) [this message]
2020-05-08 8:40 ` [PATCH v8 0/8] scsi: ufs: support LU Dedicated buffer mode for WriteBooster Avri Altman
2020-05-12 3:28 ` 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=ca589cd1-bf28-7227-02d7-1c7789f6f6e9@codeaurora.org \
--to=asutoshd@codeaurora.org \
--cc=alim.akhtar@samsung.com \
--cc=andy.teng@mediatek.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=chun-hung.wu@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=kuohong.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=peter.wang@mediatek.com \
--cc=stanley.chu@mediatek.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;
as well as URLs for NNTP newsgroup(s).