From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753159AbcC2BZe (ORCPT <rfc822;w@1wt.eu>);
	Mon, 28 Mar 2016 21:25:34 -0400
Received: from mailout2.w1.samsung.com ([210.118.77.12]:60597 "EHLO
	mailout2.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750827AbcC2BZb (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 28 Mar 2016 21:25:31 -0400
X-AuditID: cbfec7f5-f792a6d000001302-d6-56f9d98627dc
Subject: Re: [PATCH v2] ARM: exynos_defconfig: Enable Samsung media platform
 drivers as modules
To: Javier Martinez Canillas <javier@osg.samsung.com>,
        linux-kernel@vger.kernel.org
References: <1458779208-6144-1-git-send-email-javier@osg.samsung.com>
 <56F33C46.8060501@samsung.com> <56F4AD53.2020307@osg.samsung.com>
 <56F8B2D0.9010609@samsung.com> <56F8BD99.9050907@osg.samsung.com>
 <56F94A79.4020808@osg.samsung.com>
Cc: linux-samsung-soc@vger.kernel.org,
        Tobias Jakobi <tjakobi@math.uni-bielefeld.de>,
        Kukjin Kim <kgene@kernel.org>
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Message-id: <56F9D982.8030800@samsung.com>
Date: Tue, 29 Mar 2016 10:25:22 +0900
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.6.0
MIME-version: 1.0
In-reply-to: <56F94A79.4020808@osg.samsung.com>
Content-type: text/plain; charset=windows-1252
Content-transfer-encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrELMWRmVeSWpSXmKPExsVy+t/xq7ptN3+GGXz5JWzx5u0aJovXLwwt
	+h+/Zra4vGsOm8WM8/uYLNpWf2B1YPPYtKqTzePfMXaPLf132T36tqxi9Pi8SS6ANYrLJiU1
	J7MstUjfLoEr49zLw2wFN5grdp6axdzA+IWpi5GTQ0LARGLaty2sELaYxIV769lAbCGBpYwS
	RydGdDFyAdlPGSVevF7IApIQFkiU+PVhNTOILSIQKvHv4m1GiIZPjBL9r4tBbGaBUolPi86A
	DWUTMJbYvHwJ2FBeAS2J7otdYDaLgKrEuz/T2UFsUYEIiSdzTzJC1AhK/Jh8D2wXp4C+xLwn
	bUCHcgDN1JO4f1ELYry8xOY1b5knMArMQtIxC6FqFpKqBYzMqxhFU0uTC4qT0nON9IoTc4tL
	89L1kvNzNzFCQvrrDsalx6wOMQpwMCrx8EYs+hkmxJpYVlyZe4hRgoNZSYQ3/AZQiDclsbIq
	tSg/vqg0J7X4EKM0B4uSOO/MXe9DhATSE0tSs1NTC1KLYLJMHJxSDYyeWgavVh4/1bhFUnZb
	gbaF/gv/qwx/eVxe2Zw3lG6sUdl3Y6nKnVluM4TmTd5ncCzsq6erVdO7nTNmrX7QccZ4jmG8
	wMR1V5YmPBTk4oh+wrB6WsbNKRNn8F9f/lNRN/LNtda5nYyl/2zmyhqJNPby+93it+bMPvOO
	K3tf7sN5HjL1zJznnOqUWIozEg21mIuKEwETjBNKZQIAAA==
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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.
> 
> Like is the case for the other components (G2D, GSC, Mixer, etc).

Roger that.

BR,
Krzysztof