From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753172AbcC1E2J (ORCPT ); Mon, 28 Mar 2016 00:28:09 -0400 Received: from mailout1.w1.samsung.com ([210.118.77.11]:24170 "EHLO mailout1.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751631AbcC1E2I (ORCPT ); Mon, 28 Mar 2016 00:28:08 -0400 X-AuditID: cbfec7f4-f796c6d000001486-2e-56f8b2d39748 Subject: Re: [PATCH v2] ARM: exynos_defconfig: Enable Samsung media platform drivers as modules To: Javier Martinez Canillas , 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> Cc: linux-samsung-soc@vger.kernel.org, Tobias Jakobi , Kukjin Kim From: Krzysztof Kozlowski Message-id: <56F8B2D0.9010609@samsung.com> Date: Mon, 28 Mar 2016 13:28:00 +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: <56F4AD53.2020307@osg.samsung.com> Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrMLMWRmVeSWpSXmKPExsVy+t/xa7qXN/0IM1i1WNnizds1TBavXxha 9D9+zWxxedccNosZ5/cxWbSt/sDqwOaxaVUnm8e/Y+weW/rvsnv0bVnF6PF5k1wAaxSXTUpq TmZZapG+XQJXxrftm1gLTrBVTH3YxdzAOI+1i5GDQ0LARGLGpuAuRk4gU0ziwr31bF2MXBxC AksZJR4en88C4TxllJg1azojSJWwQKLErw+rmUFsEYFQiX8XbzNCFHUySjx7sxYswSxQKvFp 0RlWEJtNwFhi8/IlbCA2r4CWxPxFL8AGsQioSlz/BTFIVCBC4snck4wQNYISPybfYwGxOQX0 JaZ8/cQMcimzgJ7E/YtaEOPlJTavecs8gVFgFpKOWQhVs5BULWBkXsUomlqaXFCclJ5rqFec mFtcmpeul5yfu4kREtRfdjAuPmZ1iFGAg1GJhzfD8keYEGtiWXFl7iFGCQ5mJRHenRuBQrwp iZVVqUX58UWlOanFhxilOViUxHnn7nofIiSQnliSmp2aWpBaBJNl4uCUamBceu24g/z0GxOK nK+7+IeL+pYIrubhCzxZd2Clyqb6neG6a0TrFBZ+PqKWZfOkoH4mW9d0ttsvnfx45S97zvQ/ xtl/5ICSAOtM7ZQPL1rMjdW23py/+Nr8zs224T1BbSkPPQuDqwI/2McV2FScM0iJcBVyY5LO FKq5yn5+28Lry15f3Lq+840SS3FGoqEWc1FxIgCXQq2mZgIAAA== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 25.03.2016 12:15, Javier Martinez Canillas wrote: >> >> How about doing the same for multi_v7? >> > > I didn't consider multi_v7 because media drivers aren't necessary for booting > the boards and so it could increase build times for not real benefits in most > machines. But I can enable it in multi_v7 as a follow-up if you think that it > makes sense there too. I consider use cases of multi_v7 the same as exynos (except the difference in policy: use always modules). This means that if it makes sense to enable some media drivers on exynos (for build coverage, boot testing and real usage) then it makes sense to do the same for multi_v7. In ideal future we would move entirely from exynos-specific image to one common image for testing: the multi_v7. It would make things simpler. Best regards, Krzysztof