From: Bart Van Assche <bvanassche@acm.org>
To: Nitin Rawat <quic_nitirawa@quicinc.com>,
vkoul@kernel.org, kishon@kernel.org,
manivannan.sadhasivam@linaro.org,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com, konrad.dybcio@oss.qualcomm.com
Cc: quic_rdwivedi@quicinc.com, linux-arm-msm@vger.kernel.org,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, Can Guo <quic_cang@quicinc.com>
Subject: Re: [PATCH V2 6/6] scsi: ufs: host : Introduce phy_power_on/off wrapper function
Date: Tue, 18 Mar 2025 10:46:32 -0700 [thread overview]
Message-ID: <adb6f7cb-36b1-47d8-8fa1-00fcf5242699@acm.org> (raw)
In-Reply-To: <20250318144944.19749-7-quic_nitirawa@quicinc.com>
On 3/18/25 7:49 AM, Nitin Rawat wrote:
Just like the other patches in this series, the subject of this patch
should have the prefix "scsi: ufs: qcom:" instead of "scsi: ufs: host:"
> diff --git a/drivers/ufs/host/ufs-qcom.h b/drivers/ufs/host/ufs-qcom.h
> index d0e6ec9128e7..3db29fbcd40b 100644
> --- a/drivers/ufs/host/ufs-qcom.h
> +++ b/drivers/ufs/host/ufs-qcom.h
> @@ -252,6 +252,10 @@ struct ufs_qcom_host {
> u32 phy_gear;
>
> bool esi_enabled;
> + /* flag to check if phy is powered on */
> + bool is_phy_pwr_on;
> + /* Protect the usage of is_phy_pwr_on against racing */
> + struct mutex phy_mutex;
> };
Please reorder the above two structure members. Synchronization objects
should occur before the data members protected by these synchronization
objects in structure definitions.
It seems to me that phy_mutex not only serializes is_phy_pwr_on accesses
but that it also serializes phy_power_on() / phy_power_off() calls. If
this is the case, please mention this.
Thanks,
Bart.
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2025-03-18 17:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 14:49 [PATCH V2 0/6] Refactor phy powerup sequence Nitin Rawat
2025-03-18 14:49 ` [PATCH V2 1/6] phy: qcom-qmp-ufs: Rename qmp_ufs_enable and qmp_ufs_power_on Nitin Rawat
2025-03-18 15:05 ` neil.armstrong
2025-03-18 14:49 ` [PATCH V2 2/6] phy: qcom-qmp-ufs: Refactor phy_power_on and phy_calibrate callbacks Nitin Rawat
2025-03-18 15:09 ` neil.armstrong
2025-04-10 9:13 ` Nitin Rawat
2025-04-10 20:00 ` Dmitry Baryshkov
2025-03-18 14:49 ` [PATCH V2 3/6] phy: qcom-qmp-ufs: Refactor UFS PHY reset Nitin Rawat
2025-03-18 15:13 ` neil.armstrong
2025-04-10 9:09 ` Nitin Rawat
2025-03-18 19:46 ` Bjorn Andersson
2025-04-10 15:37 ` Nitin Rawat
2025-03-18 14:49 ` [PATCH V2 4/6] phy: qcom-qmp-ufs: Refactor qmp_ufs_exit callback Nitin Rawat
2025-03-18 15:15 ` neil.armstrong
2025-03-18 14:49 ` [PATCH V2 5/6] scsi: ufs: qcom : Refactor phy_power_on/off calls Nitin Rawat
2025-03-18 14:49 ` [PATCH V2 6/6] scsi: ufs: host : Introduce phy_power_on/off wrapper function Nitin Rawat
2025-03-18 17:46 ` Bart Van Assche [this message]
2025-03-18 19:50 ` Bjorn Andersson
2025-04-10 15:41 ` Nitin Rawat
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=adb6f7cb-36b1-47d8-8fa1-00fcf5242699@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=martin.petersen@oracle.com \
--cc=quic_cang@quicinc.com \
--cc=quic_nitirawa@quicinc.com \
--cc=quic_rdwivedi@quicinc.com \
--cc=vkoul@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