mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Palash Kambar <quic_pkambar@quicinc.com>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: <James.Bottomley@hansenpartnership.com>,
	<martin.petersen@oracle.com>, <linux-arm-msm@vger.kernel.org>,
	<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<quic_nitirawa@quicinc.com>
Subject: Re: [PATCH] ufs: ufs-qcom: disable lane clocks during phy hibern8
Date: Wed, 13 Aug 2025 17:01:48 +0530	[thread overview]
Message-ID: <9caa5f38-db78-4a0a-9eea-1df2ab9f1ffa@quicinc.com> (raw)
In-Reply-To: <w5mkkhxhhndrqhlfomvwohssndtl2njcw7khupyh7qechsynns@kl5ykxtwqawt>



On 8/13/2025 3:49 PM, Manivannan Sadhasivam wrote:
> On Tue, Jul 15, 2025 at 09:35:24PM GMT, Palash Kambar wrote:
>> The UFS lane clocks ensure that the PHY is adequately powered and
>> synchronized before initiating the link. Currently, these clocks
>> remain enabled even after the link enters the Hibern8 state and
>> are only turned off during runtime or system suspend.
>>
>> Modify the behavior to disable the lane clocks immediately after
>> the link transitions to Hibern8, thereby reducing the power
>> consumption.
>>
> 
> This statement is technically misleading. You are disabling lane clocks in
> ufs_qcom_setup_clocks(), which gets called during suspend/resume/clk_gate phase.
> 
> But if you want to disable the clocks immediately after Hibern8, you may want to
> add the disable/enable logic in hibern8_notify() callback.
> 
> If that is not a strict requirement and you want to do it in
> ufs_qcom_setup_clocks(), you have to reword the description.
> 

Hi Mani,
Hibern8 entry and exit can be initiated from various contexts, including
clock scaling. Given this, it may not be ideal to toggle the lane clock on
every Hibern8 transition. Moreover, since all resources related to the PHY
and controller are managed within ufs_qcom_setup_clocks(), it seems more
appropriate to handle this logic within that function. Additionally, since
ufs_qcom_setup_clock() is invoked immediately after the link enters
Hibern8 via gate work, any delay appears to be minimal.

I’ll ensure these points are clearly reflected in the commit message.

-Palash K

> 
>> Signed-off-by: Palash Kambar <quic_pkambar@quicinc.com>
>> ---
>>  drivers/ufs/host/ufs-qcom.c | 10 ++++++++++
>>  1 file changed, 10 insertions(+)
>>
>> diff --git a/drivers/ufs/host/ufs-qcom.c b/drivers/ufs/host/ufs-qcom.c
>> index 318dca7fe3d7..50e174d9b406 100644
>> --- a/drivers/ufs/host/ufs-qcom.c
>> +++ b/drivers/ufs/host/ufs-qcom.c
>> @@ -1141,6 +1141,13 @@ static int ufs_qcom_setup_clocks(struct ufs_hba *hba, bool on,
>>  	case PRE_CHANGE:
>>  		if (on) {
>>  			ufs_qcom_icc_update_bw(host);
>> +			if (ufs_qcom_is_link_hibern8(hba)) {
>> +				err = ufs_qcom_enable_lane_clks(host);
>> +				if (err) {
>> +					dev_err(hba->dev, "enable lane clks failed, ret=%d\n", err);
>> +					return err;
>> +				}
>> +			}
>>  		} else {
>>  			if (!ufs_qcom_is_link_active(hba)) {
>>  				/* disable device ref_clk */
>> @@ -1166,6 +1173,9 @@ static int ufs_qcom_setup_clocks(struct ufs_hba *hba, bool on,
>>  			if (ufshcd_is_hs_mode(&hba->pwr_info))
>>  				ufs_qcom_dev_ref_clk_ctrl(host, true);
>>  		} else {
>> +			if (ufs_qcom_is_link_hibern8(hba))
>> +				ufs_qcom_disable_lane_clks(host);
>> +
>>  			ufs_qcom_icc_set_bw(host, ufs_qcom_bw_table[MODE_MIN][0][0].mem_bw,
>>  					    ufs_qcom_bw_table[MODE_MIN][0][0].cfg_bw);
>>  		}
>> -- 
>> 2.34.1
>>
> 


      reply	other threads:[~2025-08-13 11:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15 16:05 Palash Kambar
2025-08-13 10:19 ` Manivannan Sadhasivam
2025-08-13 11:31   ` Palash Kambar [this message]

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=9caa5f38-db78-4a0a-9eea-1df2ab9f1ffa@quicinc.com \
    --to=quic_pkambar@quicinc.com \
    --cc=James.Bottomley@hansenpartnership.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=martin.petersen@oracle.com \
    --cc=quic_nitirawa@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

all inboxes | Powered by JetHome®