From: Mark Brown <broonie@kernel.org>
To: Radu Pirea <radu.pirea@microchip.com>
Cc: linux-spi@vger.kernel.org, nicolas.ferre@microchip.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] spi: atmel: Fix DMA transfers data corruption
Date: Thu, 16 Nov 2017 10:45:08 +0000 [thread overview]
Message-ID: <20171116104508.rm7xdabyvucowlaj@sirena.org.uk> (raw)
In-Reply-To: <1510763732-10151-3-git-send-email-radu.pirea@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
On Wed, Nov 15, 2017 at 06:35:32PM +0200, Radu Pirea wrote:
> +#ifdef CONFIG_SOC_SAM_V4_V5
> + /*
> + * On Atmel SoCs based on ARM9 cores, the data cache follows the VIVT
> + * model, hence the cache aliases issue can occur when buffers are
> + * allocated from DMA-unsafe areas, by vmalloc() for instance, where
> + * cache coherency is not taken into account or at least not handled
> + * completely (cache lines of aliases are not flushed and invalidated).
> + * This is not a theorical issue: it was reproduced when trying to mount
> + * a UBI file-system on a at91sam9g35ek board.
> + */
> + flush_kernel_vmap_range((void *)xfer->rx_buf, xfer->len);
> +#endif
Shouldn't we be fixing this in the DMA mapping operations for the SoC,
won't this affect everything that does DMA on this platform and not just
this driver? I'd expect that dma_map_sg() and so on would do the right
thing.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-11-16 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 16:35 [RFC PATCH 0/2] Enable DMA transfers for SAM9 and fix cache aliasing Radu Pirea
2017-11-15 16:35 ` [RFC PATCH 1/2] Revert "spi: atmel: fix corrupted data issue on SAM9 family SoCs" Radu Pirea
2017-11-16 10:36 ` Mark Brown
2017-11-15 16:35 ` [RFC PATCH 2/2] spi: atmel: Fix DMA transfers data corruption Radu Pirea
2017-11-15 19:01 ` Trent Piepho
2017-11-16 10:26 ` Radu Nicolae Pirea
2017-11-16 10:45 ` Mark Brown [this message]
2017-12-08 13:26 ` Radu Nicolae Pirea
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=20171116104508.rm7xdabyvucowlaj@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=radu.pirea@microchip.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 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®