From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
linux-kernel@vger.kernel.org
Cc: Kukjin Kim <kgene@kernel.org>,
Thierry Reding <treding@nvidia.com>,
Anand Moon <linux.amoon@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
linux-samsung-soc@vger.kernel.org,
Lukasz Majewski <l.majewski@samsung.com>,
linux-arm-kernel@lists.infradead.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH] ARM: exynos_defconfig: Enable USB Video Class support
Date: Tue, 8 Sep 2015 10:40:58 +0200 [thread overview]
Message-ID: <55EE9F1A.9030703@osg.samsung.com> (raw)
In-Reply-To: <55EE9820.2010202@samsung.com>
[adding Bartlomiej to cc]
Hello Krzysztof,
On 09/08/2015 10:11 AM, Krzysztof Kozlowski wrote:
> On 08.09.2015 06:45, Javier Martinez Canillas wrote:
>> The Exynos5420 Peach Pit and Exynos5800 Peach Pi boards have a built-in
>> Silicon Motion USB UVC WebCam. Enable support for the USB Video Class
>> driver and its needed media Kconfig symbols so the camera is supported.
>>
>> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
>>
>> ---
>>
>> arch/arm/configs/exynos_defconfig | 4 ++++
>> 1 file changed, 4 insertions(+)
>
> The patch itself looks good but now I wonder whether we are not putting
> to much stuff built-in. The exynos_defconfig does not replace the
> distribution distro. For a fully working board the distro should prepare
> it's own config.
>
Agreed that exynos_defconfig is not meant to replace a distro config.
> I understand that in this case the USB webcams are parts of device (like
> on all laptops)... a little bit similar as camera sensors on mobile
> phones. Yet on mobile phone usually the camera itself is part of SoC,
> only the sensor is external.
>
> Actually what we need is a kind of policy for exynos_defconfig - what
> should be inside as built-in and what as module?
>
I had the same conversation with Bartlomiej before in [0] when I tried to
enable the SBS battery driver as module. I save you a click and quote him:
"the current most popular use case for exynos_defconfig
(not multi_v7_defconfig) seems to be to build kernel image
alone and use it without any modules"
Which seems to be true, so my understanding is that exynos_defconfig is a
minimal defconfig for Exynos platforms and for easy of test/use, everything
should be built-in while multi_v7_defconfig would be more similar to a conf
used by distros where most things would be built as a module when possible.
Other SoC specific deconfig do it differently, OMAP for example does the
opposite and tries to build as much stuff as possible as a module.
> Best regards,
> Krzysztof
>
>
[0]: http://lists.infradead.org/pipermail/linux-arm-kernel/2014-August/278757.html
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
WARNING: multiple messages have this Message-ID (diff)
From: javier@osg.samsung.com (Javier Martinez Canillas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: exynos_defconfig: Enable USB Video Class support
Date: Tue, 8 Sep 2015 10:40:58 +0200 [thread overview]
Message-ID: <55EE9F1A.9030703@osg.samsung.com> (raw)
In-Reply-To: <55EE9820.2010202@samsung.com>
[adding Bartlomiej to cc]
Hello Krzysztof,
On 09/08/2015 10:11 AM, Krzysztof Kozlowski wrote:
> On 08.09.2015 06:45, Javier Martinez Canillas wrote:
>> The Exynos5420 Peach Pit and Exynos5800 Peach Pi boards have a built-in
>> Silicon Motion USB UVC WebCam. Enable support for the USB Video Class
>> driver and its needed media Kconfig symbols so the camera is supported.
>>
>> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
>>
>> ---
>>
>> arch/arm/configs/exynos_defconfig | 4 ++++
>> 1 file changed, 4 insertions(+)
>
> The patch itself looks good but now I wonder whether we are not putting
> to much stuff built-in. The exynos_defconfig does not replace the
> distribution distro. For a fully working board the distro should prepare
> it's own config.
>
Agreed that exynos_defconfig is not meant to replace a distro config.
> I understand that in this case the USB webcams are parts of device (like
> on all laptops)... a little bit similar as camera sensors on mobile
> phones. Yet on mobile phone usually the camera itself is part of SoC,
> only the sensor is external.
>
> Actually what we need is a kind of policy for exynos_defconfig - what
> should be inside as built-in and what as module?
>
I had the same conversation with Bartlomiej before in [0] when I tried to
enable the SBS battery driver as module. I save you a click and quote him:
"the current most popular use case for exynos_defconfig
(not multi_v7_defconfig) seems to be to build kernel image
alone and use it without any modules"
Which seems to be true, so my understanding is that exynos_defconfig is a
minimal defconfig for Exynos platforms and for easy of test/use, everything
should be built-in while multi_v7_defconfig would be more similar to a conf
used by distros where most things would be built as a module when possible.
Other SoC specific deconfig do it differently, OMAP for example does the
opposite and tries to build as much stuff as possible as a module.
> Best regards,
> Krzysztof
>
>
[0]: http://lists.infradead.org/pipermail/linux-arm-kernel/2014-August/278757.html
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2015-09-08 8:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 21:45 [PATCH] ARM: exynos_defconfig: Enable USB Video Class support Javier Martinez Canillas
2015-09-07 21:45 ` Javier Martinez Canillas
2015-09-08 8:11 ` Krzysztof Kozlowski
2015-09-08 8:11 ` Krzysztof Kozlowski
2015-09-08 8:11 ` Krzysztof Kozlowski
2015-09-08 8:40 ` Javier Martinez Canillas [this message]
2015-09-08 8:40 ` Javier Martinez Canillas
2015-09-08 13:12 ` Krzysztof Kozlowski
2015-09-08 13:12 ` Krzysztof Kozlowski
2015-09-08 13:32 ` Javier Martinez Canillas
2015-09-08 13:32 ` Javier Martinez Canillas
2015-09-09 0:06 ` Krzysztof Kozlowski
2015-09-09 0:06 ` Krzysztof Kozlowski
2015-09-09 7:41 ` Javier Martinez Canillas
2015-09-09 7:41 ` 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=55EE9F1A.9030703@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=l.majewski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=linux@arm.linux.org.uk \
--cc=treding@nvidia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.