From: Subash Patel <subashrp@gmail.com>
To: Olof Johansson <olof@lixom.net>
Cc: Prathyush K <prathyush@chromium.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Prathyush K <prathyush.k@samsung.com>,
linux-arm-kernel@lists.infradead.org,
linaro-mm-sig@lists.linaro.org, linux-mm@kvack.org
Subject: Re: [PATCH] arm: dma mapping: export arm iommu functions
Date: Mon, 31 Dec 2012 17:07:46 -0800 [thread overview]
Message-ID: <50E236E2.9050305@gmail.com> (raw)
In-Reply-To: <20121229065356.GA13760@quad.lixom.net>
On Friday 28 December 2012 10:53 PM, Olof Johansson wrote:
> On Fri, Dec 28, 2012 at 09:53:47AM +0530, Prathyush K wrote:
>> On Thu, Dec 27, 2012 at 7:45 PM, Marek Szyprowski
>> <m.szyprowski@samsung.com>wrote:
>>
>>> Hello,
>>>
>>>
>>> On 12/27/2012 8:14 AM, Prathyush K wrote:
>>>
>>>> This patch adds EXPORT_SYMBOL calls to the three arm iommu
>>>> functions - arm_iommu_create_mapping, arm_iommu_free_mapping
>>>> and arm_iommu_attach_device. These functions can now be called
>>>> from dynamic modules.
>>>>
>>>
>>> Could You describe a bit more why those functions might be needed by
>>> dynamic modules?
>>>
>>> Hi Marek,
>>
>> We are adding iommu support to exynos gsc and s5p-mfc.
>> And these two drivers need to be built as modules to improve boot time.
>>
>> We're calling these three functions from inside these drivers:
>> e.g.
>> mapping = arm_iommu_create_mapping(&platform_bus_type, 0x20000000, SZ_256M,
>> 4);
>> arm_iommu_attach_device(mdev, mapping);
>
> The driver shouldn't have to call these low-level functions directly,
> something's wrong if you need that.
These are not truly low-level calls, but arm specific wrappers to the
dma-mapping implementations. Drivers need to call former to declare
mappings requirement needed for their IOMMU and later to start using it.
>
> How is the DMA address management different here from other system/io mmus? is
> that 256M window a hardware restriction?
No, each IOMMU is capable of 4G. But to keep the IOMMU address space to
what is required, various sizes were used earlier and later fixed on to
256M. This can be increased if the drivers demand more buffers mapped to
the device at anytime.
Regards,
Subash
>
> -Olof
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2013-01-01 1:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 7:14 [PATCH] arm: dma mapping: export arm iommu functions Prathyush K
2012-12-27 14:15 ` Marek Szyprowski
2012-12-28 4:23 ` Prathyush K
2012-12-29 6:53 ` Olof Johansson
2013-01-01 1:07 ` Subash Patel [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=50E236E2.9050305@gmail.com \
--to=subashrp@gmail.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=olof@lixom.net \
--cc=prathyush.k@samsung.com \
--cc=prathyush@chromium.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).