From: Can Guo <can.guo@oss.qualcomm.com>
To: Bean Huo <beanhuo@iokpp.de>,
avri.altman@wdc.com, bvanassche@acm.org, beanhuo@micron.com,
martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org,
Manivannan Sadhasivam <mani@kernel.org>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"open list:ARM/QUALCOMM MAILING LIST"
<linux-arm-msm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 08/11] scsi: ufs: ufs-qcom: Implement vops tx_eqtr_notify()
Date: Fri, 6 Mar 2026 21:33:39 +0800 [thread overview]
Message-ID: <29ada0cc-709f-40eb-b399-cb870059c831@oss.qualcomm.com> (raw)
In-Reply-To: <ce70f471d5c6bfd3c6ffcffe9c34a823e7b557b9.camel@iokpp.de>
Hi Bean,
On 3/6/2026 5:17 AM, Bean Huo wrote:
> On Wed, 2026-03-04 at 05:53 -0800, Can Guo wrote:
>> freq)
>> return min_t(u32, gear, hba->max_pwr_info.info.gear_rx);
>> }
>>
>> +static int ufs_qcom_change_power_mode(struct ufs_hba *hba,
>> + struct ufs_pa_layer_attr *pwr_mode,
>> + enum ufshcd_pmc_policy pmc_policy)
>> +{
>> + int ret;
>> +
>> + ret = ufs_qcom_pwr_change_notify(hba, PRE_CHANGE, pwr_mode);
>> + if (ret) {
>> + dev_err(hba->dev, "Power change notify (PRE_CHANGE) failed:
>> %d\n",
>> + ret);
>> + return ret;
>> + }
>> +
>> + ret = ufshcd_change_power_mode(hba, pwr_mode, pmc_policy);
>> + if (ret)
>> + return ret;
>> +
>> + ufs_qcom_pwr_change_notify(hba, POST_CHANGE, pwr_mode);
>> +
>> + return ret;
>> +}
> seems Qcom UFS driver does duplicate notify now, above
> ufs_qcom_change_power_mode() does PRE/POST itself, then calls core
> ufshcd_change_power_mode() which already does PRE/POST, double side effects? or
> I am wrong?
You are right... I made a mistake when I cleaned up the code. Thanks for
catching it.
Best Regards,
Can Guo.
>
> Kind regards,
> Bean
>
next prev parent reply other threads:[~2026-03-06 13:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260304135313.413688-1-can.guo@oss.qualcomm.com>
2026-03-04 13:53 ` [PATCH v2 01/11] scsi: ufs: core: Introduce a new ufshcd vops negotiate_pwr_mode() Can Guo
2026-03-05 12:53 ` Krzysztof Kozlowski
2026-03-06 12:25 ` Can Guo
2026-03-05 21:03 ` Bean Huo
2026-03-06 12:41 ` Can Guo
2026-03-04 13:53 ` [PATCH v2 07/11] scsi: ufs: ufs-qcom: Fixup PAM-4 TX L0_L1_L2_L3 adaptation pattern length Can Guo
2026-03-04 15:10 ` Manivannan Sadhasivam
2026-03-06 11:14 ` Can Guo
2026-03-04 13:53 ` [PATCH v2 08/11] scsi: ufs: ufs-qcom: Implement vops tx_eqtr_notify() Can Guo
2026-03-04 15:20 ` Manivannan Sadhasivam
2026-03-06 13:41 ` Can Guo
2026-03-05 21:17 ` Bean Huo
2026-03-06 13:33 ` Can Guo [this message]
2026-03-04 13:53 ` [PATCH v2 09/11] scsi: ufs: ufs-qcom: Implement vops get_rx_fom() Can Guo
2026-03-04 15:39 ` Manivannan Sadhasivam
2026-03-06 14:04 ` Can Guo
2026-03-04 13:53 ` [PATCH v2 10/11] scsi: ufs: ufs-qcom: Implement vops apply_tx_eqtr_settings() Can Guo
2026-03-04 15:41 ` Manivannan Sadhasivam
2026-03-06 14:05 ` Can Guo
2026-03-04 13:53 ` [PATCH v2 11/11] scsi: ufs: ufs-qcom: Enable TX Equalization Can Guo
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=29ada0cc-709f-40eb-b399-cb870059c831@oss.qualcomm.com \
--to=can.guo@oss.qualcomm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@iokpp.de \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--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 \
/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