From: hongwus@codeaurora.org
To: Can Guo <cang@codeaurora.org>
Cc: Bean Huo <huobean@gmail.com>,
asutoshd@codeaurora.org, nguyenb@codeaurora.org,
ziqichen@codeaurora.org, rnayak@codeaurora.org,
linux-scsi@vger.kernel.org, kernel-team@android.com,
saravanak@google.com, salyzyn@google.com,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Tomas Winkler <tomas.winkler@intel.com>,
Bean Huo <beanhuo@micron.com>,
Stanley Chu <stanley.chu@mediatek.com>,
Bart Van Assche <bvanassche@acm.org>,
Satya Tangirala <satyat@google.com>,
open list <linux-kernel@vger.kernel.org>,
cang=codeaurora.org@codeaurora.org
Subject: Re: [PATCH v2 1/2] scsi: ufs: Refector ufshcd_setup_clocks() to remove skip_ref_clk
Date: Wed, 25 Nov 2020 10:01:05 +0800 [thread overview]
Message-ID: <2bdcfeaa104a380425faa68a0479534d@codeaurora.org> (raw)
In-Reply-To: <d112935400a5ef115a384a4c753b6d04@codeaurora.org>
On 2020-11-25 08:53, Can Guo wrote:
> On 2020-11-25 05:09, Bean Huo wrote:
>> On Mon, 2020-11-23 at 23:28 -0800, Can Guo wrote:
>>> +++ b/drivers/scsi/ufs/ufshcd.h
>>> @@ -229,6 +229,8 @@ struct ufs_dev_cmd {
>>> * @max_freq: maximum frequency supported by the clock
>>> * @min_freq: min frequency that can be used for clock scaling
>>> * @curr_freq: indicates the current frequency that it is set to
>>> + * @always_on_while_link_active: indicate that the clk should not be
>>> disabled if
>>> + link is still active
>>> * @enabled: variable to check against multiple enable/disable
>>> */
>>> struct ufs_clk_info {
>>> @@ -238,6 +240,7 @@ struct ufs_clk_info {
>>> u32 max_freq;
>>> u32 min_freq;
>>> u32 curr_freq;
>>> + bool always_on_while_link_active;
>>
>> Can,
>> using a sentence as a parameter name looks a little bit clumsy to me.
>> The meaning has been explained in the comments section. How about
>> simplify it and in line with other parameters in the structure?
>>
>
> Do you have a better name in mind?
>
> Thanks,
>
> Can Guo.
>
>> Thanks,
>> Bean
>>
>>> bool enabled;
>>> };
>>>
Looks good to me. The variable name is not a problem.
Reviewed-by: Hongwu Su<hongwus@codeaurora.org>
next prev parent reply other threads:[~2020-11-25 2:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 7:28 [PATCH v2 0/2] Refector ufshcd_setup_clocks() to remove param skip_ref_clk Can Guo
2020-11-24 7:28 ` [PATCH v2 1/2] scsi: ufs: Refector ufshcd_setup_clocks() to remove skip_ref_clk Can Guo
2020-11-24 21:09 ` Bean Huo
2020-11-25 0:53 ` Can Guo
2020-11-25 2:01 ` hongwus [this message]
2020-11-25 11:54 ` Bean Huo
2020-11-25 12:28 ` Can Guo
2020-11-25 19:02 ` Bean Huo
2020-11-26 1:45 ` Can Guo
2020-11-26 0:58 ` Stanley Chu
2020-11-26 1:25 ` Can Guo
2020-11-24 7:28 ` [PATCH v2 2/2] scsi: ufs-qcom: Keep core_clk_unipro ON while link is active Can Guo
2020-11-25 2:02 ` hongwus
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=2bdcfeaa104a380425faa68a0479534d@codeaurora.org \
--to=hongwus@codeaurora.org \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang=codeaurora.org@codeaurora.org \
--cc=cang@codeaurora.org \
--cc=huobean@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=nguyenb@codeaurora.org \
--cc=rnayak@codeaurora.org \
--cc=salyzyn@google.com \
--cc=saravanak@google.com \
--cc=satyat@google.com \
--cc=stanley.chu@mediatek.com \
--cc=tomas.winkler@intel.com \
--cc=ziqichen@codeaurora.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