All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamin Lin via <qemu-devel@nongnu.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Bin Meng" <bmeng.cn@gmail.com>,
	"open list:SD (Secure Card)" <qemu-block@nongnu.org>,
	"open list:All patches CC here" <qemu-devel@nongnu.org>
Cc: <jamin_lin@aspeedtech.com>, <troy_lee@aspeedtech.com>,
	<yunlin.tang@aspeedtech.com>
Subject: [PATCH v2 0/2] sd:sdhci Fix data transfer did not complete
Date: Fri, 13 Dec 2024 11:12:03 +0800	[thread overview]
Message-ID: <20241213031205.641009-1-jamin_lin@aspeedtech.com> (raw)

v1:
1. Fix boundary_count overflow
2. Fix data transfer did not complete if data size is bigger then SDMA Buffer Boundary

v2:
1. fix typo
2. update to none RFC patch
3. check the most upper byte of SDMA System Address Register (0x00) is written,
   then restarts SDMA data transfer.

Jamin Lin (2):
  hw/sd/sdhci: Fix boundary_count overflow in
    sdhci_sdma_transfer_multi_blocks
  hw/sd/sdhci: Fix data transfer did not complete if data size is bigger
    than SDMA Buffer Boundary

 hw/sd/sdhci.c | 20 ++++++++++++++++----
 1 file changed, 16 insertions(+), 4 deletions(-)

-- 
2.34.1



             reply	other threads:[~2024-12-13  3:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13  3:12 Jamin Lin via [this message]
2024-12-13  3:12 ` [PATCH v2 1/2] hw/sd/sdhci: Fix boundary_count overflow in sdhci_sdma_transfer_multi_blocks Jamin Lin via
2024-12-13  3:12 ` [PATCH v2 2/2] hw/sd/sdhci: Fix data transfer did not complete if data size is bigger than SDMA Buffer Boundary Jamin Lin via
2025-01-07  7:10   ` Bernhard Beschow
2025-01-07 10:36     ` Philippe Mathieu-Daudé
2025-01-02  2:36 ` [PATCH v2 0/2] sd:sdhci Fix data transfer did not complete Jamin Lin

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=20241213031205.641009-1-jamin_lin@aspeedtech.com \
    --to=qemu-devel@nongnu.org \
    --cc=bmeng.cn@gmail.com \
    --cc=jamin_lin@aspeedtech.com \
    --cc=philmd@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=troy_lee@aspeedtech.com \
    --cc=yunlin.tang@aspeedtech.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 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.