From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
linux-kernel@vger.kernel.org
Cc: linux-samsung-soc@vger.kernel.org,
Tobias Jakobi <tjakobi@math.uni-bielefeld.de>,
Kukjin Kim <kgene@kernel.org>,
Seung-Woo Kim <sw0312.kim@samsung.com>
Subject: Re: [PATCH v2] ARM: exynos_defconfig: Enable Samsung media platform drivers as modules
Date: Thu, 21 Apr 2016 10:39:48 -0400 [thread overview]
Message-ID: <5718E634.3010902@osg.samsung.com> (raw)
In-Reply-To: <56F9D982.8030800@samsung.com>
[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
prev parent reply other threads:[~2016-04-21 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1458779208-6144-1-git-send-email-javier@osg.samsung.com>
2016-03-24 1:00 ` [PATCH v2] ARM: exynos_defconfig: Enable Samsung media platform drivers as modules Krzysztof Kozlowski
2016-03-25 3:15 ` Javier Martinez Canillas
2016-03-28 4:28 ` Krzysztof Kozlowski
2016-03-28 5:14 ` Javier Martinez Canillas
2016-03-28 15:15 ` Javier Martinez Canillas
2016-03-29 1:25 ` Krzysztof Kozlowski
2016-04-21 14:39 ` Javier Martinez Canillas [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=5718E634.3010902@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sw0312.kim@samsung.com \
--cc=tjakobi@math.uni-bielefeld.de \
/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