[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5718E634.3010902@osg.samsung.com>
Date: Thu, 21 Apr 2016 10:39:48 -0400
From: Javier Martinez Canillas <javier@....samsung.com>
To: Krzysztof Kozlowski <k.kozlowski@...sung.com>,
linux-kernel@...r.kernel.org
Cc: linux-samsung-soc@...r.kernel.org,
Tobias Jakobi <tjakobi@...h.uni-bielefeld.de>,
Kukjin Kim <kgene@...nel.org>,
Seung-Woo Kim <sw0312.kim@...sung.com>
Subject: Re: [PATCH v2] ARM: exynos_defconfig: Enable Samsung media platform
drivers as modules
[adding Seung-Woo Kim to cc]
Hello Krzysztof,
On 03/28/2016 09:25 PM, Krzysztof Kozlowski wrote:
> On 29.03.2016 00:15, Javier Martinez Canillas wrote:
>> Tobias mentioned on IRC that the exynos4-is driver conflicts with the
>> Exynos DRM driver since both exynos_drm_fimc and exynos-fimc-is use
>> the FIMC block.
>>
>> So I think we should just discard $SUBJECT and instead add a Kconfig
>> check to not allow both drivers to be built as suggested by Tobias.
>>
I posted the Kconfig change [0] but Seung-Woo explained [1] to me that
there are several instances of the FIMC and device nodes can use the
samsung,{isp,lcd}-wb properties to choose which instance to use.
>> Like is the case for the other components (G2D, GSC, Mixer, etc).
>
> Roger that.
>
So enabling both the V4L2 and DRM drivers is a valid configuration and
$SUBJECT should be picked after all. Sorry for the confusion.
I'll re-post the patch and also include changes for multi_v7_defconfig
in the same series.
> BR,
> Krzysztof
>
[0]: https://lkml.org/lkml/2016/3/28/494
[1]: https://lkml.org/lkml/2016/3/29/7
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
Powered by blists - more mailing lists