[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200916061500.1970090-1-hch@lst.de>
Date: Wed, 16 Sep 2020 08:14:53 +0200
From: Christoph Hellwig <hch@....de>
To: iommu@...ts.linux-foundation.org,
Russell King <linux@...linux.org.uk>,
Santosh Shilimkar <ssantosh@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Jim Quinlan <james.quinlan@...adcom.com>,
Nathan Chancellor <natechancellor@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
Robin Murphy <robin.murphy@....com>,
Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
Ohad Ben-Cohen <ohad@...ery.com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
linux-remoteproc@...r.kernel.org, linux-usb@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-sh@...r.kernel.org, linux-pci@...r.kernel.org,
linux-acpi@...r.kernel.org, devicetree@...r.kernel.org
Subject: support range based offsets in dma-direct v3
Hi all,
this series adds range-based offsets to the dma-direct implementation. The
guts of the change are a patch from Jim with some modifications from me,
but to do it nicely we need to ARM patches to prepare for it as well.
Changes since v2:
- fix a mismerge
- return (phys_addr_t)-1 from translate_dma_to_phys when there is no
matching range to fix dma_capable checks
Changes since v1:
- rebased on top of the latests dma-mapping for-next tree
- add two more trivial ARM cleanups
- remove the DMA property inheritance hack in usb
- move the remaining copy of the ranges into the remoteproc driver
as it should not be seen as a general API, but as a quirk for
remoteproc that we need to fix ASAP
Diffstat:
Powered by blists - more mailing lists