From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Nitin Rawat <quic_nitirawa@quicinc.com>
Cc: mani@kernel.org, agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, jejb@linux.ibm.com,
martin.petersen@oracle.com, quic_cang@quicinc.com,
quic_nguyenb@quicinc.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH V8 0/5] scsi: ufs: qcom: Align programming sequence as per HW spec
Date: Wed, 13 Sep 2023 21:16:21 -0400 [thread overview]
Message-ID: <yq1led9eeqr.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20230905052400.13935-1-quic_nitirawa@quicinc.com> (Nitin Rawat's message of "Tue, 5 Sep 2023 10:53:55 +0530")
Nitin,
> This patch series adds programming support for Qualcomm UFS V4 and
> above to align avoid with Hardware Specification. This patch series
> will address stability and performance issues.
Applied to 6.7/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2023-09-14 1:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 5:23 [PATCH V8 0/5] scsi: ufs: qcom: Align programming sequence as per HW spec Nitin Rawat
2023-09-05 5:23 ` [PATCH V8 1/5] scsi: ufs: qcom: Update MAX_CORE_CLK_1US_CYCLES for UFS V4 and above Nitin Rawat
2023-09-05 5:23 ` [PATCH V8 2/5] scsi: ufs: qcom: Add multiple frequency support for MAX_CORE_CLK_1US_CYCLES Nitin Rawat
2023-11-08 16:30 ` Dmitry Baryshkov
2023-11-09 1:35 ` Can Guo
2023-11-09 8:14 ` Nitin Rawat
2023-11-09 9:59 ` Dmitry Baryshkov
2023-09-05 5:23 ` [PATCH V8 3/5] scsi: ufs: qcom: Add support to Configure PA_VS_CORE_CLK_40NS_CYCLES Nitin Rawat
2023-09-05 5:23 ` [PATCH V8 4/5] scsi: ufs: qcom: Align programing of unipro clk attributes Nitin Rawat
2023-09-05 5:24 ` [PATCH V8 5/5] scsi: ufs: qcom: Configure SYS1CLK_1US_REG for UFS V4 and above Nitin Rawat
2023-09-11 6:42 ` [PATCH V8 0/5] scsi: ufs: qcom: Align programming sequence as per HW spec Can Guo
2023-09-14 1:16 ` Martin K. Petersen [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=yq1led9eeqr.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=konrad.dybcio@linaro.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=quic_cang@quicinc.com \
--cc=quic_nguyenb@quicinc.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