From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Christoph Hellwig <hch@lst.de>,
Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
Roger Quadros <rogerq@ti.com>
Subject: Re: [PATCH 2/2] arm: use swiotlb for bounce buffer on LPAE configs
Date: Wed, 24 Jul 2019 19:23:50 +0200 [thread overview]
Message-ID: <a447eae1bb46fe753f7a62fb8932e680b79b1635.camel@suse.de> (raw)
In-Reply-To: <20190709142011.24984-3-hch@lst.de>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
On Tue, 2019-07-09 at 07:20 -0700, Christoph Hellwig wrote:
> The DMA API requires that 32-bit DMA masks are always supported, but on
> arm LPAE configs they do not currently work when memory is present
> above 4GB. Wire up the swiotlb code like for all other architectures
> to provide the bounce buffering in that case.
>
> Fixes: 21e07dba9fb11 ("scsi: reduce use of block bounce buffers").
> Reported-by: Roger Quadros <rogerq@ti.com>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
Hi Chistoph,
Out of curiosity, what is the reason stopping us from using dma-direct/swiotlb
instead of arm_dma_ops altogether?
Regards,
Nicolas
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-07-24 17:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 14:20 add swiotlb support to arm32 Christoph Hellwig
2019-07-09 14:20 ` [PATCH 1/2] dma-mapping check pfn validity in dma_common_{mmap,get_sgtable} Christoph Hellwig
2019-07-09 14:20 ` [PATCH 2/2] arm: use swiotlb for bounce buffer on LPAE configs Christoph Hellwig
2019-07-24 17:23 ` Nicolas Saenz Julienne [this message]
2019-07-24 17:55 ` Christoph Hellwig
2019-12-19 13:10 ` Peter Ujfalusi
2019-12-19 15:02 ` Christoph Hellwig
2019-12-19 15:20 ` Peter Ujfalusi
2020-01-08 8:28 ` Peter Ujfalusi
2020-01-08 12:21 ` Robin Murphy
2020-01-08 14:00 ` Peter Ujfalusi
2020-01-08 15:20 ` Robin Murphy
2020-01-09 14:49 ` Christoph Hellwig
2020-01-14 10:43 ` Peter Ujfalusi
2020-01-14 16:43 ` [PoC] arm: dma-mapping: direct: Apply dma_pfn_offset only when it is valid Peter Ujfalusi
2020-01-14 18:19 ` Robin Murphy
2020-01-15 11:50 ` Peter Ujfalusi
2020-01-16 19:13 ` Robin Murphy
2020-01-27 14:00 ` Peter Ujfalusi
2020-01-30 7:53 ` Christoph Hellwig
2020-01-30 13:04 ` Peter Ujfalusi
2020-01-30 16:40 ` Christoph Hellwig
2020-01-31 13:59 ` Peter Ujfalusi
2020-01-31 14:00 ` Peter Ujfalusi
2020-01-31 14:00 ` Peter Ujfalusi
2020-02-03 17:08 ` Christoph Hellwig
2020-02-05 10:19 ` Peter Ujfalusi
2019-07-17 13:21 ` add swiotlb support to arm32 Vignesh Raghavendra
2019-07-19 12:33 ` Christoph Hellwig
2019-07-24 15:37 ` Christoph Hellwig
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=a447eae1bb46fe753f7a62fb8932e680b79b1635.camel@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=rogerq@ti.com \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).