From: Bart Van Assche <bvanassche@acm.org>
To: Can Guo <quic_cang@quicinc.com>,
quic_asutoshd@quicinc.com, quic_nguyenb@quicinc.com,
quic_xiaosenh@quicinc.com, stanley.chu@mediatek.com,
adrian.hunter@intel.com, beanhuo@micron.com, avri.altman@wdc.com,
mani@kernel.org, linux-scsi@vger.kernel.org,
kernel-team@android.com
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"open list:ARM/QUALCOMM SUPPORT" <linux-arm-msm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v2 2/2] scsi: ufs-qcom: Add MCQ support
Date: Thu, 18 Aug 2022 19:48:22 -0700 [thread overview]
Message-ID: <4ad8c00e-f752-dfb2-331e-8cdff02eaa05@acm.org> (raw)
In-Reply-To: <1660213984-37793-3-git-send-email-quic_cang@quicinc.com>
On 8/11/22 03:33, Can Guo wrote:
> +static int ufs_qcom_get_outstanding_cqs(struct ufs_hba *hba,
> + unsigned long *ocqs)
> +{
> + return -EINVAL;
> +}
Why does the get_outstanding_cqs vop exist since the only implementation
of that vop returns EINVAL?
> +static int ufs_qcom_config_mcq_rop(struct ufs_hba *hba)
> +{
> + struct ufshcd_mcq_rop_info_t *rop;
> + struct ufshcd_res_info_t *mem_res, *sqdao_res;
> + int i;
> +
> + mem_res = &hba->res[RES_MEM];
> + sqdao_res = &hba->res[RES_MCQ_SQD];
> +
> + if (!mem_res->base || !sqdao_res->base)
> + return -EINVAL;
> +
> + for (i = 0; i < ROP_MAX; i++) {
> + rop = &hba->mcq_rop[i];
> + rop->offset = sqdao_res->resource->start -
> + mem_res->resource->start + 0x40 * i;
> + rop->stride = 0x100;
> + rop->base = sqdao_res->base + 0x40 * i;
> + }
> +
> + return 0;
> +}
Is there anything in the above function that is specific to the Qualcomm
controller? If not, please move the above code into ufshcd.c.
> +static int ufs_qcom_get_hba_mac(struct ufs_hba *hba)
> +{
> + return MAX_SUPP_MAC;
> +}
Since there is a register in the UFSHCI 4.0 specification from which the
maximum number of outstanding commands can be retrieved, why does the
get_hba_mac vop exist?
Thanks,
Bart.
prev parent reply other threads:[~2022-08-19 2:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 10:33 [RFC PATCH v2 0/2] UFS Multi-Circular Queue (MCQ) Can Guo
2022-08-11 10:33 ` [RFC PATCH v2 1/2] scsi: ufs: Add Multi-Circular Queue support Can Guo
2022-08-12 9:10 ` Manivannan Sadhasivam
2022-08-18 20:24 ` Bart Van Assche
2022-08-19 2:57 ` Asutosh Das (asd)
2022-08-19 2:41 ` Bart Van Assche
2022-08-25 1:42 ` Asutosh Das (asd)
2022-08-25 18:04 ` Bart Van Assche
2022-08-25 18:08 ` Asutosh Das (asd)
2022-08-11 10:33 ` [RFC PATCH v2 2/2] scsi: ufs-qcom: Add MCQ support Can Guo
2022-08-19 2:48 ` Bart Van Assche [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=4ad8c00e-f752-dfb2-331e-8cdff02eaa05@acm.org \
--to=bvanassche@acm.org \
--cc=adrian.hunter@intel.com \
--cc=agross@kernel.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bjorn.andersson@linaro.org \
--cc=jejb@linux.ibm.com \
--cc=kernel-team@android.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_asutoshd@quicinc.com \
--cc=quic_cang@quicinc.com \
--cc=quic_nguyenb@quicinc.com \
--cc=quic_xiaosenh@quicinc.com \
--cc=stanley.chu@mediatek.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