From: robin.murphy@arm.com (Robin Murphy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm64: dma-mapping: implement dma_get_sgtable()
Date: Mon, 20 Jul 2015 18:00:57 +0100 [thread overview]
Message-ID: <55AD2949.2040401@arm.com> (raw)
In-Reply-To: <20150720163645.GM9908@arm.com>
Hi Will,
On 20/07/15 17:36, Will Deacon wrote:
> On Fri, Jul 17, 2015 at 04:58:21PM +0100, Robin Murphy wrote:
>> The default dma_common_get_sgtable() implementation relies on the CPU
>> address of the buffer being a regular lowmem address. This is not always
>> the case on arm64, since allocations from the various DMA pools may have
>> remapped vmalloc addresses, rendering the use of virt_to_page() invalid.
>>
>> Fix this by providing our own implementation based on the fact that we
>> can safely derive a physical address from the DMA address in both cases.
>>
>> CC: Jon Medhurst <tixy@linaro.org>
>> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
>> ---
>> arch/arm64/mm/dma-mapping.c | 14 ++++++++++++++
>> 1 file changed, 14 insertions(+)
>>
>> diff --git a/arch/arm64/mm/dma-mapping.c b/arch/arm64/mm/dma-mapping.c
>> index d16a1ce..4b9b600 100644
>> --- a/arch/arm64/mm/dma-mapping.c
>> +++ b/arch/arm64/mm/dma-mapping.c
>> @@ -337,10 +337,24 @@ static int __swiotlb_mmap(struct device *dev,
>> return __dma_common_mmap(dev, vma, cpu_addr, dma_addr, size);
>> }
>>
>> +int __swiotlb_get_sgtable(struct device *dev, struct sg_table *sgt,
>> + void *cpu_addr, dma_addr_t handle, size_t size,
>> + struct dma_attrs *attrs)
>> +{
>> + int ret = sg_alloc_table(sgt, 1, GFP_KERNEL);
>> +
>> + if (!ret)
>> + sg_set_page(sgt->sgl, phys_to_page(dma_to_phys(dev, handle)),
>> + PAGE_ALIGN(size), 0);
>> +
>> + return ret;
>> +}
>
> Any reason not to do this in dma_common_get_sgtable?
Summarising the discussion over at [1], most architectures seem to
depend on dma_common_get_sgtable, but only a handful implement
dma_to_phys (plus this approach seems to match the original intent).
There doesn't seem to be a nice solution for doing this in common code
without a big cross-architecture patch, and it's somewhat questionable
how widely this is actually needed.
Robin.
[1]:http://thread.gmane.org/gmane.linux.kernel/1998795
>
> Will
>
prev parent reply other threads:[~2015-07-20 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 15:58 [PATCH 1/2] arm64: dma-mapping: implement dma_get_sgtable() Robin Murphy
2015-07-17 15:58 ` [PATCH 2/2] arm64: dma-mapping: consolidate __swiotlb_mmap() Robin Murphy
2015-07-20 16:36 ` [PATCH 1/2] arm64: dma-mapping: implement dma_get_sgtable() Will Deacon
2015-07-20 17:00 ` Robin Murphy [this message]
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=55AD2949.2040401@arm.com \
--to=robin.murphy@arm.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