linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Prathyush K <prathyush@chromium.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: 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: Fri, 28 Dec 2012 09:53:47 +0530	[thread overview]
Message-ID: <CAH=HWYP5r18qjQSc_2121vikbTMpYv6DKOfW=hpOpGB7rUyNRA@mail.gmail.com> (raw)
In-Reply-To: <50DC580C.7080507@samsung.com>

[-- Attachment #1: Type: text/plain, Size: 2033 bytes --]

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);



>
>  Signed-off-by: Prathyush K <prathyush.k@samsung.com>
>> ---
>>   arch/arm/mm/dma-mapping.c | 3 +++
>>   1 file changed, 3 insertions(+)
>>
>> diff --git a/arch/arm/mm/dma-mapping.c b/arch/arm/mm/dma-mapping.c
>> index 6b2fb87..c0f0f43 100644
>> --- a/arch/arm/mm/dma-mapping.c
>> +++ b/arch/arm/mm/dma-mapping.c
>> @@ -1797,6 +1797,7 @@ err2:
>>   err:
>>         return ERR_PTR(err);
>>   }
>> +EXPORT_SYMBOL(arm_iommu_**create_mapping);
>>
>
> EXPORT_SYMOBL_GPL() ?
>
>
Right, it should be EXPORT_SYMOBL_GPL().

Will update in next patch.



>
>    static void release_iommu_mapping(struct kref *kref)
>>   {
>> @@ -1813,6 +1814,7 @@ void arm_iommu_release_mapping(**struct
>> dma_iommu_mapping *mapping)
>>         if (mapping)
>>                 kref_put(&mapping->kref, release_iommu_mapping);
>>   }
>> +EXPORT_SYMBOL(arm_iommu_**release_mapping);
>>     /**
>>    * arm_iommu_attach_device
>> @@ -1841,5 +1843,6 @@ int arm_iommu_attach_device(struct device *dev,
>>         pr_debug("Attached IOMMU controller to %s device.\n",
>> dev_name(dev));
>>         return 0;
>>   }
>> +EXPORT_SYMBOL(arm_iommu_**attach_device);
>>     #endif
>>
>
> Best regards
> --
> Marek Szyprowski
> Samsung Poland R&D Center
>
>
> Regards,
Prathyush

[-- Attachment #2: Type: text/html, Size: 4018 bytes --]

  reply	other threads:[~2012-12-28  4:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-27  7:14 Prathyush K
2012-12-27 14:15 ` Marek Szyprowski
2012-12-28  4:23   ` Prathyush K [this message]
2012-12-29  6:53     ` Olof Johansson
2013-01-01  1:07       ` Subash Patel

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='CAH=HWYP5r18qjQSc_2121vikbTMpYv6DKOfW=hpOpGB7rUyNRA@mail.gmail.com' \
    --to=prathyush@chromium.org \
    --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=prathyush.k@samsung.com \
    /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