From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Javier Martinez Canillas <javier@osg.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>
Subject: Re: [PATCH v2] ARM: exynos_defconfig: Enable Samsung media platform drivers as modules
Date: Mon, 28 Mar 2016 13:28:00 +0900 [thread overview]
Message-ID: <56F8B2D0.9010609@samsung.com> (raw)
In-Reply-To: <56F4AD53.2020307@osg.samsung.com>
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
next prev parent reply other threads:[~2016-03-28 4:28 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 [this message]
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
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=56F8B2D0.9010609@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=javier@osg.samsung.com \
--cc=kgene@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--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