From: "Peter Wang (王信友)" <peter.wang@mediatek.com>
To: "bvanassche@acm.org" <bvanassche@acm.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"beanhuo@micron.com" <beanhuo@micron.com>,
"nitin.rawat@oss.qualcomm.com" <nitin.rawat@oss.qualcomm.com>,
"avri.altman@sandisk.com" <avri.altman@sandisk.com>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"quic_nguyenb@quicinc.com" <quic_nguyenb@quicinc.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>
Subject: Re: [PATCH for rc] ufs: core: Configure MCQ after link startup
Date: Mon, 22 Dec 2025 05:55:45 +0000 [thread overview]
Message-ID: <e9f1df51050a935fc4e1a2a29066e88bf20f8c02.camel@mediatek.com> (raw)
In-Reply-To: <6745d2d0-e8c4-407c-a22d-5577997f1ca3@acm.org>
On Fri, 2025-12-19 at 08:32 -0800, Bart Van Assche wrote:
>
> This has been considered but unfortunately the UFSHCI register set
> definition makes this impossible. hba->host->can_queue must be set
> before scsi_add_host() is called. hba->host->can_queue is derived
> from the controller capabilities register (CAP). MCQ must be enabled
> before NUTRS is extracted from the CAP register. Otherwise NUTRS is
> reported as 32 - 1 instead of 64 - 1 (assuming that the host
> controller supports 64 outstanding commands in MCQ mode).
>
> Thanks,
>
> Bart.
Hi Bart,
Yes, this is indeed a specification limitation.
Thank you for your explanation.
Reviewed-by: Peter Wang <peter.wang@mediatek.com>
next prev parent reply other threads:[~2025-12-22 5:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 23:07 [PATCH for rc] ufs: core: Configure MCQ after link startup Bart Van Assche
2025-12-19 7:32 ` Peter Wang (王信友)
2025-12-19 16:32 ` Bart Van Assche
2025-12-22 5:55 ` Peter Wang (王信友) [this message]
2026-01-04 21:42 ` Martin K. Petersen
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=e9f1df51050a935fc4e1a2a29066e88bf20f8c02.camel@mediatek.com \
--to=peter.wang@mediatek.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=adrian.hunter@intel.com \
--cc=avri.altman@sandisk.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=nitin.rawat@oss.qualcomm.com \
--cc=quic_nguyenb@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