From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: jmaselbas@zdiv.net, ore@pengutronix.de
Subject: [PATCH master 0/2] mci: sdhci: fix memory corruption on DMA
Date: Mon, 11 Sep 2023 14:11:54 +0200 [thread overview]
Message-ID: <20230911121156.2632668-1-a.fatoum@pengutronix.de> (raw)
Recent changes to teach SDHCI 64-bit support inadvertently changed
the address used for cache maintenance away from the DMA buffer address
with the result that unrelated cache lines were dropped and memory
corruption. This series fixes this. I must admit I don't understand
how the SDMA boundary mechanism works, so I did not change too much
about it.
Ahmad Fatoum (2):
mci: sdhci: unmap the DMA buffers actually used
mci: sdhci: hardcode SDMA boundary for DMA
drivers/mci/sdhci.c | 9 ++-------
drivers/mci/sdhci.h | 3 +++
2 files changed, 5 insertions(+), 7 deletions(-)
--
2.39.2
next reply other threads:[~2023-09-11 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 12:11 Ahmad Fatoum [this message]
2023-09-11 12:11 ` [PATCH master 1/2] mci: sdhci: unmap the DMA buffers actually used Ahmad Fatoum
2023-09-11 12:11 ` [PATCH master 2/2] mci: sdhci: hardcode SDMA boundary for DMA Ahmad Fatoum
2023-09-12 9:19 ` [PATCH master 0/2] mci: sdhci: fix memory corruption on DMA Sascha Hauer
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=20230911121156.2632668-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jmaselbas@zdiv.net \
--cc=ore@pengutronix.de \
/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