[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3165610.Gdh8F6ejPI@wuerfel>
Date: Thu, 17 Mar 2016 17:14:34 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Sinan Kaya <okaya@...eaurora.org>
Cc: Robin Murphy <robin.murphy@....com>,
linux-arm-kernel@...ts.infradead.org, timur@...eaurora.org,
cov@...eaurora.org, nwatters@...eaurora.org,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
Max Filippov <jcmvbkbc@...il.com>,
Joe Perches <joe@...ches.com>,
"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@....com>,
Jisheng Zhang <jszhang@...vell.com>,
Dean Nelson <dnelson@...hat.com>,
"Suzuki K. Poulose" <suzuki.poulose@....com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: dma-mapping: fix dma_to_phys API for IOMMU attached devices
On Thursday 17 March 2016 12:07:26 Sinan Kaya wrote:
> On 3/17/2016 11:57 AM, Robin Murphy wrote:
>
> Let me know which direction I should go.
>
> 1. Fix phys_to_dma and keep dma_to_phys as in the patch.
> 2. Remove both of the API from header file, move it to where it is needed. Rename them as swio_phys_to_dma etc.
Use 2.
It has been a long way to remove all virt_to_bus/bus_to_virt users
from the common architectures, we are not putting them back under
a different name.
Drivers already know the physical address because that is what they
put into dma_map_*() in the first place.
Arnd
Powered by blists - more mailing lists