[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191014205859.GA7634@iMac-3.local>
Date: Mon, 14 Oct 2019 21:59:00 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
Cc: Robin Murphy <robin.murphy@....com>,
linux-arm-kernel@...ts.infradead.org,
bcm-kernel-feedback-list@...adcom.com,
linux-rpi-kernel@...ts.infradead.org,
iommu@...ts.linux-foundation.org, linux-s390@...r.kernel.org,
f.fainelli@...il.com, linux-kernel@...r.kernel.org,
hch@...radead.org, mbrugger@...e.com, wahrenst@....net,
linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH RFC 0/5] ARM: Raspberry Pi 4 DMA support
On Mon, Oct 14, 2019 at 08:31:02PM +0200, Nicolas Saenz Julienne wrote:
> the Raspberry Pi 4 offers up to 4GB of memory, of which only the first
> is DMA capable device wide. This forces us to use of bounce buffers,
> which are currently not very well supported by ARM's custom DMA ops.
> Among other things the current mechanism (see dmabounce.c) isn't
> suitable for high memory. Instead of fixing it, this series introduces a
> way of selecting dma-direct as the default DMA ops provider which allows
> for the Raspberry Pi to make use of swiotlb.
I presume these patches go on top of this series:
http://lkml.kernel.org/r/20190911182546.17094-1-nsaenzjulienne@suse.de
which I queued here:
https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/log/?h=for-next/zone-dma
--
Catalin
Powered by blists - more mailing lists