From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Inki Dae <inki.dae@samsung.com>,
dri-devel@lists.freedesktop.org,
linux-samsung-soc@vger.kernel.org
Cc: Joonyoung Shim <jy0922.shim@samsung.com>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
Andrzej Hajda <a.hajda@samsung.com>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH 08/10] drm/exynos: initialize DMA ops for virtual Exynos DRM device
Date: Fri, 12 Feb 2016 09:44:25 +0100 [thread overview]
Message-ID: <56BD9B69.6000400@samsung.com> (raw)
In-Reply-To: <56BD73E7.8060304@samsung.com>
Hello,
On 2016-02-12 06:55, Inki Dae wrote:
> Hi Marek,
>
> 2016년 02월 03일 21:42에 Marek Szyprowski 이(가) 쓴 글:
>> Virtual DRM device is used for memory allocation for GEM objects. On
>> some architectures null dma operations are assigned for virtual devices
>> if no explicit initialization has been made.
>>
>> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
>> ---
>> drivers/gpu/drm/exynos/exynos_drm_drv.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/gpu/drm/exynos/exynos_drm_drv.c b/drivers/gpu/drm/exynos/exynos_drm_drv.c
>> index 68f0f36..a33ea44 100644
>> --- a/drivers/gpu/drm/exynos/exynos_drm_drv.c
>> +++ b/drivers/gpu/drm/exynos/exynos_drm_drv.c
>> @@ -144,6 +144,7 @@ static int exynos_drm_load(struct drm_device *dev, unsigned long flags)
>> init_waitqueue_head(&private->wait);
>> spin_lock_init(&private->lock);
>>
>> + arch_setup_dma_ops(dev->dev, 0, DMA_BIT_MASK(32), false, false);
> As you got the report, above function incurrs build error below,
> ERROR: "arch_setup_dma_ops" [drivers/gpu/drm/exynos/exynosdrm.ko] undefined!
>
> Exynos drm can be built as a module. In this case, arch_setup_dma_ops cannot be accessed by the module.
>
> I could fix it easily like below but I'm not sure that it's reasonable.
>
> +extern void arch_setup_dma_ops(struct device *dev, u64 dma_base,
> + u64 size, struct iommu_ops *iommu,
> + bool coherent) { };
I don't think this is a good idea - the result will be same as not applying
the patch at all. Please drop this patch for now, I will rework it while
adding support for generic IOMMU for ARM and ARM64.
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
next prev parent reply other threads:[~2016-02-12 8:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 12:42 [PATCH 00/10] Exynos DRM: various fixes for 64bit and Exynos5433 Marek Szyprowski
2016-02-03 12:42 ` [PATCH 01/10] drm/exynos: depend on ARCH_EXYNOS for DRM_EXYNOS Marek Szyprowski
2016-02-11 11:17 ` Inki Dae
2016-02-03 12:42 ` [PATCH 02/10] drm/exynos: ipp: fix incorrect format specifiers in debug messages Marek Szyprowski
2016-02-04 2:17 ` Krzysztof Kozlowski
2016-02-04 2:34 ` Inki Dae
2016-02-04 2:45 ` Krzysztof Kozlowski
2016-02-03 12:42 ` [PATCH 03/10] drm/exynos: fix types for compilation on 64bit architectures Marek Szyprowski
2016-02-03 12:42 ` [PATCH 04/10] drm/exynos: mic: use devm_clk interface Marek Szyprowski
2016-02-03 12:42 ` [PATCH 05/10] drm/exynos: mic: convert to component framework Marek Szyprowski
2016-02-03 12:42 ` [PATCH 06/10] drm/exynos: mic: make all functions static Marek Szyprowski
2016-02-03 12:42 ` [PATCH 07/10] drm/exynos: dsi: restore support for drm bridge Marek Szyprowski
2016-02-03 12:42 ` [PATCH 08/10] drm/exynos: initialize DMA ops for virtual Exynos DRM device Marek Szyprowski
2016-02-12 5:55 ` Inki Dae
2016-02-12 8:44 ` Marek Szyprowski [this message]
2016-02-03 12:42 ` [PATCH 09/10] drm/exynos: exynos5433_decon: fix wrong state assignment in decon_enable Marek Szyprowski
2016-02-03 12:42 ` [PATCH 10/10] drm/exynos: exynos5433_decon: fix wrong state in decon_vblank_enable Marek Szyprowski
2016-02-08 11:14 ` [PATCH 00/10] Exynos DRM: various fixes for 64bit and Exynos5433 Emil Velikov
2016-02-12 9:19 ` Andrzej Hajda
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=56BD9B69.6000400@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=a.hajda@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=jy0922.shim@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sw0312.kim@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