[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <384b42df01c0af973002fba0d5f02068e7f2e7b3.camel@suse.de>
Date: Tue, 15 Oct 2019 09:48:22 +0200
From: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
To: Catalin Marinas <catalin.marinas@....com>
Cc: linux-s390@...r.kernel.org, f.fainelli@...il.com,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
hch@...radead.org, iommu@...ts.linux-foundation.org,
mbrugger@...e.com, bcm-kernel-feedback-list@...adcom.com,
linux-rpi-kernel@...ts.infradead.org,
Robin Murphy <robin.murphy@....com>,
linux-arm-kernel@...ts.infradead.org, wahrenst@....net
Subject: Re: [PATCH RFC 0/5] ARM: Raspberry Pi 4 DMA support
On Mon, 2019-10-14 at 21:59 +0100, Catalin Marinas wrote:
> 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
Yes, forgot to mention it. It's relevant for the first patch.
>
> which I queued here:
>
>
https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/log/?h=for-next/zone-dma
Thanks!
A little off topic but I was wondering if you have a preferred way to refer to
the arm architecture in a way that it unambiguously excludes arm64 (for example
arm32 would work).
Regards,
Nicolas
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists