From: Joonhoe Kim <26rote@gmail.com>
To: andersson@kernel.org, konradybcio@kernel.org
Cc: abelvesa@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, mani@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] arm64: dts: qcom: kaanapali: Describe the UFS MCQ registers
Date: Sun, 22 Nov 2026 01:44:53 +0900 [thread overview]
Message-ID: <20261121164453.26-1-26rote@gmail.com> (raw)
The UFS host on Kaanapali supports Multi-Circular Queue (MCQ) mode, but
its node only describes the standard register space, so ufshcd falls
back to the legacy single doorbell.
Describe the MCQ register region and the ITS MSI parent used for Event
Specific Interrupts (ESI). The region has the same address and size as
on Eliza, and the ITS device ID 0x60 is taken from the downstream
device tree.
On a Lenovo Y700 Gen 5 (TB323FU, Kaanapali) this more than doubles 4k
random read throughput (fio, 4 jobs, QD32): 186k to 431k IOPS on the
first run after boot.
Signed-off-by: Joonhoe Kim <26rote@gmail.com>
---
arch/arm64/boot/dts/qcom/kaanapali.dtsi | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/qcom/kaanapali.dtsi b/arch/arm64/boot/dts/qcom/kaanapali.dtsi
index 132577d540bf..c841a1e1e1f4 100644
--- a/arch/arm64/boot/dts/qcom/kaanapali.dtsi
+++ b/arch/arm64/boot/dts/qcom/kaanapali.dtsi
@@ -2536,10 +2536,15 @@ ufs_mem_hc: ufs@1d84000 {
compatible = "qcom,kaanapali-ufshc",
"qcom,ufshc",
"jedec,ufs-2.0";
- reg = <0x0 0x01d84000 0x0 0x3000>;
+ reg = <0x0 0x01d84000 0x0 0x3000>,
+ <0x0 0x01da0000 0x0 0x15000>;
+ reg-names = "std",
+ "mcq";
interrupts = <GIC_SPI 265 IRQ_TYPE_LEVEL_HIGH>;
+ msi-parent = <&gic_its 0x60>;
+
clocks = <&gcc GCC_UFS_PHY_AXI_CLK>,
<&gcc GCC_AGGRE_UFS_PHY_AXI_CLK>,
<&gcc GCC_UFS_PHY_AHB_CLK>,
base-commit: 909ef7a9a30fa139e69e555e3606680f5cca7726
--
2.53.0
reply other threads:[~2026-11-21 16:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261121164453.26-1-26rote@gmail.com \
--to=26rote@gmail.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.