From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] crypto: marvell/cesa - replace dma_to_phys with dma_map_single
Date: Fri, 18 Mar 2016 10:30:28 +0100 [thread overview]
Message-ID: <20160318103028.4be15b78@bbrezillon> (raw)
In-Reply-To: <20160317235020.GB19428@n2100.arm.linux.org.uk>
On Thu, 17 Mar 2016 23:50:20 +0000
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> On Thu, Mar 17, 2016 at 07:17:24PM -0400, okaya at codeaurora.org wrote:
> > What is the correct way? I don't want to write engine->sram_dma = sram
>
> Well, what the driver _is_ wanting to do is to go from a CPU physical
> address to a device DMA address. phys_to_dma() looks like the correct
> thing there to me, but I guess that's just an offset and doesn't take
> account of any IOMMU that may be in the way.
>
> If you have an IOMMU, then the whole phys_to_dma() thing is a total
> failure as it only does a linear translation, and there are no
> interfaces in the kernel to take account of an IOMMU in the way. So,
> it needs something designed for the job, implemented and discussed by
> the normal methods of proposing a new cross-arch interface for drivers
> to use.
>
> What I'm certain of, though, is that the change proposed in this patch
> will break current users of this driver: virt_to_page() on an address
> returned by ioremap() is completely undefined, and will result in
> either a kernel oops, or if not poking at memory which isn't a struct
> page, ultimately resulting in something that isn't SRAM being pointed
> to by "engine->sram_dma".
>
Or we could just do
engine->sram_dma = res->start;
which is pretty much what the SRAM/genalloc code is doing already.
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-18 9:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 22:02 [PATCH 1/3] crypto: marvell/cesa - replace dma_to_phys with dma_map_single Sinan Kaya
2016-03-17 22:02 ` [PATCH 2/3] swiotlb: prefix dma_to_phys and phys_to_dma functions Sinan Kaya
2016-03-18 12:12 ` Robin Murphy
2016-03-18 15:00 ` Sinan Kaya
2016-03-28 18:29 ` Konrad Rzeszutek Wilk
2016-03-29 12:44 ` Stefano Stabellini
2016-03-29 12:57 ` Sinan Kaya
2016-03-29 19:32 ` Arnd Bergmann
2016-03-17 22:02 ` [PATCH 3/3] dma-mapping: move swiotlb dma-phys functions to common header Sinan Kaya
2016-03-18 11:31 ` Robin Murphy
2016-03-18 13:55 ` Sinan Kaya
2016-03-17 22:54 ` [PATCH 1/3] crypto: marvell/cesa - replace dma_to_phys with dma_map_single Russell King - ARM Linux
2016-03-17 23:17 ` okaya at codeaurora.org
2016-03-17 23:50 ` Russell King - ARM Linux
2016-03-18 9:30 ` Boris Brezillon [this message]
2016-03-18 11:25 ` Robin Murphy
2016-03-18 11:32 ` Boris Brezillon
2016-03-18 13:51 ` Sinan Kaya
2016-03-18 14:00 ` Sinan Kaya
2016-03-18 14:20 ` Boris Brezillon
2016-03-18 14:21 ` Sinan Kaya
2016-03-18 20:18 ` kbuild test robot
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=20160318103028.4be15b78@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).