From: "Asutosh Das (asd)" <asutoshd@codeaurora.org>
To: Bart Van Assche <bvanassche@acm.org>,
asutoshd@qti.qualcomm.com, linux-scsi@vger.kernel.org
Subject: Re: [<RFC PATCH v1> 1/2] scsi: ufs: add write booster feature support
Date: Mon, 16 Mar 2020 14:13:43 -0700 [thread overview]
Message-ID: <d941590e-7bfc-645d-2b69-dc67e680911c@codeaurora.org> (raw)
In-Reply-To: <a5a45551-8852-a8de-3ea5-f7cf761c7a15@acm.org>
On 2/21/2020 6:40 PM, Bart Van Assche wrote:
> On 2020-02-21 16:38, Asutosh Das wrote:
>> @@ -371,6 +379,12 @@ UFS_GEOMETRY_DESC_PARAM(enh4_memory_max_alloc_units,
>> _ENM4_MAX_NUM_UNITS, 4);
>> UFS_GEOMETRY_DESC_PARAM(enh4_memory_capacity_adjustment_factor,
>> _ENM4_CAP_ADJ_FCTR, 2);
>> +UFS_GEOMETRY_DESC_PARAM(wb_max_alloc_units, _WB_MAX_ALLOC_UNITS, 4);
>> +UFS_GEOMETRY_DESC_PARAM(wb_max_wb_luns, _WB_MAX_WB_LUNS, 1);
>> +UFS_GEOMETRY_DESC_PARAM(wb_buff_cap_adj, _WB_BUFF_CAP_ADJ, 1);
>> +UFS_GEOMETRY_DESC_PARAM(wb_sup_red_type, _WB_SUP_RED_TYPE, 1);
>> +UFS_GEOMETRY_DESC_PARAM(wb_sup_wb_type, _WB_SUP_WB_TYPE, 1);
>> +
>>
>> static struct attribute *ufs_sysfs_geometry_descriptor[] = {
>
> This patch converts a bunch of single blank lines into double blank
> lines. Are such changes useful?
No its not useful, let me re-look that.
>
>> + /* Enable WB only for UFS-3.1 OR if desc len >= 0x59 */
>> + if (dev_info->wspecversion >= 0x310) {
>> + hba->dev_info.d_ext_ufs_feature_sup =
>> + desc_buf[DEVICE_DESC_PARAM_EXT_UFS_FEATURE_SUP]
>> + << 24 |
>> + desc_buf[DEVICE_DESC_PARAM_EXT_UFS_FEATURE_SUP + 1]
>> + << 16 |
>> + desc_buf[DEVICE_DESC_PARAM_EXT_UFS_FEATURE_SUP + 2]
>> + << 8 |
>> + desc_buf[DEVICE_DESC_PARAM_EXT_UFS_FEATURE_SUP + 3];
>
> Please use get_unaligned_be32() instead of open-coding it.
>
>> + res = wb_buf[0] << 24 | wb_buf[1] << 16 |
>> + wb_buf[2] << 8 | wb_buf[3];
>
> Same comment here.
Ok.
>
> Thanks,
>
> Bart.
>
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
Linux Foundation Collaborative Project
next prev parent reply other threads:[~2020-03-16 21:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 0:38 [<RFC PATCH v1> 0/2] Write Booster Implementation Asutosh Das
2020-02-22 0:38 ` [<RFC PATCH v1> 1/2] scsi: ufs: add write booster feature support Asutosh Das
2020-02-22 0:47 ` Asutosh Das
2020-02-22 2:40 ` Bart Van Assche
2020-03-16 21:13 ` Asutosh Das (asd) [this message]
2020-02-23 9:03 ` Avri Altman
2020-03-16 23:45 ` Asutosh Das (asd)
2020-02-25 10:58 ` Avri Altman
2020-02-25 11:21 ` Avri Altman
2020-02-25 12:50 ` Avri Altman
2020-02-26 17:57 ` Asutosh Das (asd)
2020-03-16 23:52 ` Asutosh Das (asd)
2020-02-22 0:38 ` [<RFC PATCH v1> 2/2] ufs-qcom: scsi: configure write booster type Asutosh Das
2020-02-22 0:47 ` Asutosh Das
2020-02-22 0:47 ` [<RFC PATCH v1> 0/2] Write Booster Implementation Asutosh Das
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=d941590e-7bfc-645d-2b69-dc67e680911c@codeaurora.org \
--to=asutoshd@codeaurora.org \
--cc=asutoshd@qti.qualcomm.com \
--cc=bvanassche@acm.org \
--cc=linux-scsi@vger.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: 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