From: tze.yee.ng@altera.com
To: Adrian Hunter <adrian.hunter@intel.com>,
Ulf Hansson <ulfh@kernel.org>,
Tanmay Kathpalia <tanmay.kathpalia@altera.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: [PATCH 0/4] mmc: sdhci-cadence: SD6HC DDR50 read-path tuning and fixes
Date: Tue, 22 Sep 2026 19:12:34 +0800 [thread overview]
Message-ID: <cover.1790074790.git.tze.yee.ng@altera.com> (raw)
From: Tze Yee Ng <tze.yee.ng@altera.com>
This series enables DDR50 on the Cadence SD6HC (SD/eMMC v6) PHY. DDR50
has no CMD19 tuning, so the read path must be centred by static,
board/SoC-characterised PHY settings. Bringing it up on Agilex5 also
exposed PHY issues affecting the existing tuned modes.
- Patch 1: add the post-tuning settle delay the PHY needs after the
DLL re-locks, matching sdhci_cdns6_phy_init().
- Patch 2: program PHONY_DQS_TIMING (left 0 in all modes); in
extended-read DDR it must be the rebar pulse width in clk_phy cycles
minus 1, else one DDR beat is duplicated.
- Patch 3: document three optional SD6HC DDR50 read-path properties.
- Patch 4: read those properties at probe and apply them in DDR50,
and fix the DQS_TIMING read-modify-write so USE_LPBK_DQS is cleared
before being reprogrammed.
The new cdns,ddr50-* properties are unused in this series; they will be
consumed by the socfpga_agilex5_socdk and socfpga_agilex5_socdk_emmc
device trees, submitted as a separate series.
Tested on Agilex5 SoCDK: SD DDR50 and eMMC DDR52.
Tze Yee Ng (4):
mmc: sdhci-cadence6: add PHY settle delay after tuning DLL re-lock
mmc: sdhci-cadence6: program PHONY_DQS_TIMING for extended-read DDR
dt-bindings: mmc: cdns,sdhci: add SD6HC DDR50 read-path tuning
mmc: sdhci-cadence: read SD6HC DDR50 tuning from device tree
.../devicetree/bindings/mmc/cdns,sd6hc.yaml | 27 ++++++
drivers/mmc/host/sdhci-cadence-phy-v6.c | 90 ++++++++++++++++++-
2 files changed, 116 insertions(+), 1 deletion(-)
--
2.43.7
next reply other threads:[~2026-09-22 11:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 11:12 tze.yee.ng [this message]
2026-09-22 11:12 ` [PATCH 1/4] mmc: sdhci-cadence6: add PHY settle delay after tuning DLL re-lock tze.yee.ng
2026-09-24 6:41 ` Adrian Hunter
2026-09-30 11:11 ` NG, TZE YEE
2026-09-24 8:49 ` Kathpalia, Tanmay
2026-09-30 11:11 ` NG, TZE YEE
2026-09-26 10:44 ` Kathpalia, Tanmay
2026-09-30 12:05 ` NG, TZE YEE
2026-09-22 11:12 ` [PATCH 2/4] mmc: sdhci-cadence6: program PHONY_DQS_TIMING for extended-read DDR tze.yee.ng
2026-09-24 6:41 ` Adrian Hunter
2026-09-26 10:45 ` Kathpalia, Tanmay
2026-09-30 10:24 ` NG, TZE YEE
2026-09-22 11:12 ` [PATCH 3/4] dt-bindings: mmc: cdns,sdhci: add SD6HC DDR50 read-path tuning tze.yee.ng
2026-09-26 10:48 ` Kathpalia, Tanmay
2026-09-30 12:31 ` NG, TZE YEE
2026-09-30 13:16 ` NG, TZE YEE
2026-09-28 8:05 ` Krzysztof Kozlowski
2026-09-30 13:13 ` NG, TZE YEE
2026-09-22 11:12 ` [PATCH 4/4] mmc: sdhci-cadence: read SD6HC DDR50 tuning from device tree tze.yee.ng
2026-09-24 6:40 ` Adrian Hunter
2026-09-30 13:24 ` NG, TZE YEE
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=cover.1790074790.git.tze.yee.ng@altera.com \
--to=tze.yee.ng@altera.com \
--cc=adrian.hunter@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tanmay.kathpalia@altera.com \
--cc=ulfh@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
all inboxes | Powered by JetHome®