From: Arthur Simchaev <Arthur.Simchaev@wdc.com>
To: martin.petersen@oracle.com
Cc: beanhuo@micron.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Arthur Simchaev <Arthur.Simchaev@wdc.com>
Subject: [PATCH v5 3/4] ufs: core: Remove len parameter from ufshcd_set_active_icc_lvl
Date: Sun, 11 Dec 2022 15:05:10 +0200 [thread overview]
Message-ID: <1670763911-8695-4-git-send-email-Arthur.Simchaev@wdc.com> (raw)
In-Reply-To: <1670763911-8695-1-git-send-email-Arthur.Simchaev@wdc.com>
len argument is not used anymore in ufshcd_set_active_icc_lvl function.
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
Reviewed-by: Bean Huo <beanhuo@micron.com>
Signed-off-by: Arthur Simchaev <Arthur.Simchaev@wdc.com>
---
drivers/ufs/core/ufshcd.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/ufs/core/ufshcd.c b/drivers/ufs/core/ufshcd.c
index bb032bc..b6ef92d3 100644
--- a/drivers/ufs/core/ufshcd.c
+++ b/drivers/ufs/core/ufshcd.c
@@ -7394,12 +7394,11 @@ static u32 ufshcd_get_max_icc_level(int sup_curr_uA, u32 start_scan,
* In case regulators are not initialized we'll return 0
* @hba: per-adapter instance
* @desc_buf: power descriptor buffer to extract ICC levels from.
- * @len: length of desc_buff
*
* Returns calculated ICC level
*/
static u32 ufshcd_find_max_sup_active_icc_level(struct ufs_hba *hba,
- const u8 *desc_buf, int len)
+ const u8 *desc_buf)
{
u32 icc_level = 0;
@@ -7457,8 +7456,7 @@ static void ufshcd_set_active_icc_lvl(struct ufs_hba *hba)
goto out;
}
- icc_level = ufshcd_find_max_sup_active_icc_level(hba, desc_buf,
- QUERY_DESC_MAX_SIZE);
+ icc_level = ufshcd_find_max_sup_active_icc_level(hba, desc_buf);
dev_dbg(hba->dev, "%s: setting icc_level 0x%x", __func__, icc_level);
ret = ufshcd_query_attr_retry(hba, UPIU_QUERY_OPCODE_WRITE_ATTR,
--
2.7.4
next prev parent reply other threads:[~2022-12-11 13:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 13:05 [PATCH v5 0/4] ufs: core: Always read the descriptors with max length Arthur Simchaev
2022-12-11 13:05 ` [PATCH v5 1/4] ufs: core: Remove redundant wb check Arthur Simchaev
2022-12-13 5:32 ` Stanley Chu
2022-12-11 13:05 ` [PATCH v5 2/4] ufs: core: Remove redundant desc_size variable from hba Arthur Simchaev
2022-12-12 0:11 ` Bart Van Assche
2022-12-11 13:05 ` Arthur Simchaev [this message]
2022-12-11 13:05 ` [PATCH v5 4/4] ufs: core: Remove ufshcd_map_desc_id_to_length function Arthur Simchaev
2022-12-12 0:18 ` Bart Van Assche
2022-12-12 9:10 ` Arthur Simchaev
2022-12-12 19:25 ` Bart Van Assche
2022-12-12 19:26 ` Bart Van Assche
2022-12-30 21:50 ` [PATCH v5 0/4] ufs: core: Always read the descriptors with max length 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=1670763911-8695-4-git-send-email-Arthur.Simchaev@wdc.com \
--to=arthur.simchaev@wdc.com \
--cc=beanhuo@micron.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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