From: Wadim Mueller <wafgo01@gmail.com>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: qemu-devel@nongnu.org, philmd@linaro.org, qemu-block@nongnu.org
Subject: Re: [PATCH] hw/sd/sdhci: complete non-interrupt ADMA descriptor chains in one pass
Date: Thu, 13 Aug 2026 14:35:26 +0200 [thread overview]
Message-ID: <20260813123529.30457-1-wafgo01@gmail.com> (raw)
In-Reply-To: <CAEUhbmX=azsPMmxipdeChe8imyFBwKvS4KRy5Qu-phaUBodOeg@mail.gmail.com>
Hi Bin,
Thanks! I used the Icicle Kit as you suggested and posted the qtest as a
separate patch:
[PATCH] tests/qtest: add Cadence SDHCI ADMA pacing/MMIO reproducer
<https://lore.kernel.org/qemu-devel/20260813123210.28987-1-wafgo01@gmail.com/>
It drives the generic SDHCI model through the Cadence wrapper (SRS window
at 0x20008200) directly over MMIO under -accel qtest, and exercises two
facets against QEMU_CLOCK_VIRTUAL:
- pacing: reports how many SDHC_TRANSFER_DELAY steps a non-interrupt
ADMA2 chain takes to reach Transfer Complete;
- MMIO coupling: after a chain that yields on a DMA-boundary interrupt
descriptor, a bare interrupt-status read must not resume the pending
transfer.
One caveat: the mmio-coupling case is written for the fixed behaviour --
it passes with your "Run ADMA independently of MMIO" (series 515264,
patch 12) applied and fails without it, so it is meant to land alongside
that change rather than on its own.
Happy to respin it or fold it into your series, whatever suits you best.
Thanks,
Wadim
prev parent reply other threads:[~2026-08-13 12:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 8:14 [PATCH] hw/sd/sdhci: complete non-interrupt ADMA descriptor chains in one pass Wadim Mueller
2026-08-04 11:40 ` Bin Meng
2026-08-05 8:05 ` Wadim Mueller
2026-08-05 8:16 ` Bin Meng
2026-08-10 12:45 ` Wadim Mueller
2026-08-12 1:40 ` Bin Meng
2026-08-13 12:35 ` Wadim Mueller [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=20260813123529.30457-1-wafgo01@gmail.com \
--to=wafgo01@gmail.com \
--cc=bmeng.cn@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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.