<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-linux/arch/arm/include/asm/dma-mapping.h, branch jd/unified-crypt-queue</title>
<subtitle>WireGuard for the Linux kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-linux/atom/arch/arm/include/asm/dma-mapping.h?h=jd%2Funified-crypt-queue</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-linux/atom/arch/arm/include/asm/dma-mapping.h?h=jd%2Funified-crypt-queue'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/'/>
<updated>2019-09-11T10:43:26Z</updated>
<entry>
<title>xen/arm: use dev_is_dma_coherent</title>
<updated>2019-09-11T10:43:26Z</updated>
<author>
<name>Christoph Hellwig</name>
<email>hch@lst.de</email>
</author>
<published>2019-07-24T12:06:54Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=a8e6d950cdc1012aede8a84d85f902a53d895174'/>
<id>urn:sha1:a8e6d950cdc1012aede8a84d85f902a53d895174</id>
<content type='text'>
Use the dma-noncoherent dev_is_dma_coherent helper instead of the home
grown variant.  Note that both are always initialized to the same
value in arch_setup_dma_ops.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Reviewed-by: Julien Grall &lt;julien.grall@arm.com&gt;
Reviewed-by: Stefano Stabellini &lt;sstabellini@kernel.org&gt;
</content>
</entry>
<entry>
<title>arm: use swiotlb for bounce buffering on LPAE configs</title>
<updated>2019-07-24T15:29:01Z</updated>
<author>
<name>Christoph Hellwig</name>
<email>hch@lst.de</email>
</author>
<published>2019-07-23T09:33:12Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=ad3c7b18c5b362be5dbd0f2c0bcf1fd5fd659315'/>
<id>urn:sha1:ad3c7b18c5b362be5dbd0f2c0bcf1fd5fd659315</id>
<content type='text'>
The DMA API requires that 32-bit DMA masks are always supported, but on
arm LPAE configs they do not currently work when memory is present
above 4GB.  Wire up the swiotlb code like for all other architectures
to provide the bounce buffering in that case.

Fixes: 21e07dba9fb11 ("scsi: reduce use of block bounce buffers").
Reported-by: Roger Quadros &lt;rogerq@ti.com&gt;
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Tested-by: Vignesh Raghavendra &lt;vigneshr@ti.com&gt;
</content>
</entry>
<entry>
<title>dma-mapping: remove dma_max_pfn</title>
<updated>2019-07-10T11:17:30Z</updated>
<author>
<name>Christoph Hellwig</name>
<email>hch@lst.de</email>
</author>
<published>2019-06-25T09:20:42Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=79a986721decf428ba539e6e2c941c987acce655'/>
<id>urn:sha1:79a986721decf428ba539e6e2c941c987acce655</id>
<content type='text'>
These days, the DMA mapping code must bounce buffers for any unsupported
address. If the driver needs to optimize for natively supported ranges,
then it should use dma_get_required_mask.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Acked-by: Marc Gonzalez &lt;marc.w.gonzalez@free.fr&gt;
Signed-off-by: Ulf Hansson &lt;ulf.hansson@linaro.org&gt;
</content>
</entry>
<entry>
<title>dma-mapping: add a kconfig symbol for arch_teardown_dma_ops availability</title>
<updated>2019-02-13T18:12:50Z</updated>
<author>
<name>Christoph Hellwig</name>
<email>hch@lst.de</email>
</author>
<published>2018-12-21T21:14:44Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=dc2acded38957dfa6b7b7e0203b4b8cb8d818ce6'/>
<id>urn:sha1:dc2acded38957dfa6b7b7e0203b4b8cb8d818ce6</id>
<content type='text'>
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Acked-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; # arm64
</content>
</entry>
<entry>
<title>dma-mapping: add a kconfig symbol for arch_setup_dma_ops availability</title>
<updated>2019-02-13T18:12:33Z</updated>
<author>
<name>Christoph Hellwig</name>
<email>hch@lst.de</email>
</author>
<published>2019-01-07T18:36:20Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=347cb6af8710b72cf9685fdc09d07873cf42d51f'/>
<id>urn:sha1:347cb6af8710b72cf9685fdc09d07873cf42d51f</id>
<content type='text'>
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Acked-by: Paul Burton &lt;paul.burton@mips.com&gt; # MIPS
Acked-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; # arm64
</content>
</entry>
<entry>
<title>dma-mapping: bypass indirect calls for dma-direct</title>
<updated>2018-12-13T20:06:18Z</updated>
<author>
<name>Christoph Hellwig</name>
<email>hch@lst.de</email>
</author>
<published>2018-12-06T21:39:32Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=356da6d0cde3323236977fce54c1f9612a742036'/>
<id>urn:sha1:356da6d0cde3323236977fce54c1f9612a742036</id>
<content type='text'>
Avoid expensive indirect calls in the fast path DMA mapping
operations by directly calling the dma_direct_* ops if we are using
the directly mapped DMA operations.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Acked-by: Jesper Dangaard Brouer &lt;brouer@redhat.com&gt;
Tested-by: Jesper Dangaard Brouer &lt;brouer@redhat.com&gt;
Tested-by: Tony Luck &lt;tony.luck@intel.com&gt;
</content>
</entry>
<entry>
<title>arm-nommu: don't define arch_teardown_dma_ops</title>
<updated>2018-09-08T09:19:10Z</updated>
<author>
<name>Christoph Hellwig</name>
<email>hch@lst.de</email>
</author>
<published>2018-08-24T07:47:20Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=58643a3a8097e93b1c965d0ad3f0d65613b95b2c'/>
<id>urn:sha1:58643a3a8097e93b1c965d0ad3f0d65613b95b2c</id>
<content type='text'>
We can just use the default implementation.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Reviewed-by: Robin Murphy &lt;robin.murphy@arm.com&gt;
</content>
</entry>
<entry>
<title>dma-direct: rename dma_noop to dma_direct</title>
<updated>2018-01-15T08:35:06Z</updated>
<author>
<name>Christoph Hellwig</name>
<email>hch@lst.de</email>
</author>
<published>2018-01-09T15:30:23Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=002e67454f61bb67d8071ac4d0cacb86a01d18e0'/>
<id>urn:sha1:002e67454f61bb67d8071ac4d0cacb86a01d18e0</id>
<content type='text'>
The trivial direct mapping implementation already does a virtual to
physical translation which isn't strictly a noop, and will soon learn
to do non-direct but linear physical to dma translations through the
device offset and a few small tricks.  Rename it to a better fitting
name.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Reviewed-by: Vladimir Murzin &lt;vladimir.murzin@arm.com&gt;
</content>
</entry>
<entry>
<title>dma-mapping: move dma_mark_clean to dma-direct.h</title>
<updated>2018-01-10T15:41:12Z</updated>
<author>
<name>Christoph Hellwig</name>
<email>hch@lst.de</email>
</author>
<published>2018-01-09T21:11:31Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=b49efd76248242169f28ffd20ada05064d01ed9f'/>
<id>urn:sha1:b49efd76248242169f28ffd20ada05064d01ed9f</id>
<content type='text'>
And unlike the other helpers we don't require a &lt;asm/dma-direct.h&gt; as
this helper is a special case for ia64 only, and this keeps it as
simple as possible.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
</content>
</entry>
<entry>
<title>dma-mapping: move swiotlb arch helpers to a new header</title>
<updated>2018-01-10T15:40:54Z</updated>
<author>
<name>Christoph Hellwig</name>
<email>hch@lst.de</email>
</author>
<published>2018-01-10T15:21:13Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=ea8c64ace86647260ec4255f483e5844d62af2df'/>
<id>urn:sha1:ea8c64ace86647260ec4255f483e5844d62af2df</id>
<content type='text'>
phys_to_dma, dma_to_phys and dma_capable are helpers published by
architecture code for use of swiotlb and xen-swiotlb only.  Drivers are
not supposed to use these directly, but use the DMA API instead.

Move these to a new asm/dma-direct.h helper, included by a
linux/dma-direct.h wrapper that provides the default linear mapping
unless the architecture wants to override it.

In the MIPS case the existing dma-coherent.h is reused for now as
untangling it will take a bit of work.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Acked-by: Robin Murphy &lt;robin.murphy@arm.com&gt;
</content>
</entry>
</feed>
