From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@collabora.com
Subject: Re: media/master bisection: v4l2-compliance-vivid.device-presence on qemu_x86_64
Date: Wed, 15 Apr 2020 14:21:47 +0200 [thread overview]
Message-ID: <20200415142147.1ed3487e@coco.lan> (raw)
In-Reply-To: <a99d49d9-656d-6c5c-4953-6e7c56c0beba@collabora.com>
Em Wed, 15 Apr 2020 10:36:04 +0100
Guillaume Tucker <guillaume.tucker@collabora.com> escreveu:
> On 15/04/2020 10:28, Guillaume Tucker wrote:
> > On 14/04/2020 22:43, Guillaume Tucker wrote:
> >> On 14/04/2020 22:33, Mauro Carvalho Chehab wrote:
> >>> Em Tue, 14 Apr 2020 22:23:52 +0100
> >>> Guillaume Tucker <guillaume.tucker@collabora.com> escreveu:
> >>>
> >>>> Please see the bisection report below about absence of the vivid
> >>>> driver, which caused v4l2-compliance to fail to run.
> >>>>
> >>>> Presumably we need to update the configuration fragment used by
> >>>> kernelci.org to enable platform drivers. Until now we've been
> >>>> using this:
> >>>>
> >>>> CONFIG_MEDIA_SUPPORT=y
> >>>> CONFIG_MEDIA_CAMERA_SUPPORT=y
> >>>> CONFIG_VIDEO_DEV=y
> >>>> CONFIG_VIDEO_V4L2=y
> >>>> CONFIG_V4L_TEST_DRIVERS=y
> >>>> CONFIG_VIDEO_VIVID=y
> >>>> CONFIG_VIDEO_VIVID_MAX_DEVS=64
> >>>>
> >>>> Do we simply need to add this one in v5.7 onwards?
> >>>>
> >>>> CONFIG_MEDIA_PLATFORM_SUPPORT=y
> >>>
> >>> No, this shouldn't be needed.
> >>>
> >>> Helen sent us a patch that should likely fix it:
> >>>
> >>> https://git.linuxtv.org/media_tree.git/commit/?id=860b511766a3d95308a942ac09a34e4d1839e706
> >>>
> >>> Could you please check if this solves the issue?
> >>
> >> I see, thanks. This revision is being built and tested at the
> >> moment, I'll check the results when they land in my inbox.
> >
> > Helen's patch was needed, but there were still a couple of
> > issues. First we need to enable this extra option now in the
> > config fragment:
> >
> > CONFIG_MEDIA_TEST_SUPPORT=y
Yes.
Another option would be to do:
# MEDIA_SUPPORT_FILTER is not set
With this option (enabled by default if EMBEDDED or EXPERT),
all CONFIG_MEDIA_*_SUPPORT will be selected[1].
[1] except for CONFIG_MEDIA_CEC_SUPPORT. This doesn't
depend on MEDIA_SUPPORT anymore.
> >
> > as test_drivers/Kconfig starts with "if MEDIA_TEST_SUPPORT".
>
> Actually, this "if" seems redundant now in test_drivers/Kconfig
> with my patch to include the file conditionally... Please let me
> know if we should also drop it and I'll send a v2, or if this
> should be fixed in a different way.
Just one "if MEDIA_TEST_SUPPORT" at the main media/Kconfig
should be enough.
Feel free to send a v2.
Thanks,
Mauro
prev parent reply other threads:[~2020-04-15 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5e960bf5.1c69fb81.8a349.6851@mx.google.com>
2020-04-14 21:23 ` media/master bisection: v4l2-compliance-vivid.device-presence on qemu_x86_64 Guillaume Tucker
2020-04-14 21:33 ` Mauro Carvalho Chehab
2020-04-14 21:43 ` Guillaume Tucker
2020-04-15 9:28 ` Guillaume Tucker
2020-04-15 9:36 ` Guillaume Tucker
2020-04-15 12:21 ` Mauro Carvalho Chehab [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=20200415142147.1ed3487e@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=guillaume.tucker@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).