From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Linux Media Mailing List <linux-media@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: ": Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
Hans Verkuil <hans.verkuil@cisco.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
robert.foss@linaro.org, stanimir.varbanov@linaro.org,
lkft-triage@lists.linaro.org
Subject: mainline: v4l2 modules missing Kconfigs
Date: Fri, 5 Jun 2020 15:49:07 +0530 [thread overview]
Message-ID: <CA+G9fYuj7ADfxs+-vY3Hbx5zPceYofCLFy1WRe=-w2_v_J7tSA@mail.gmail.com> (raw)
The test v4l2-compliance modprobe-vivid failed
Test error,
VIDEO_DRIVER=vivid.ko
v4l2-existence-check pass
ln: failed to create symbolic link '/lib/modules/5.7.0+/' -> '': No
such file or directory
modprobe: FATAL: Module vivid not found in directory /lib/modules/5.7.0+
modprobe-vivid fail
The investigations shows that,
the following kernel configs are missing on latest mainline builds on
x86, i386 and arm64.
These are still found on arm config.
CONFIG_VIDEOBUF2_CORE=m
CONFIG_VIDEOBUF2_V4L2=m
CONFIG_VIDEOBUF2_MEMOPS=m
CONFIG_VIDEOBUF2_DMA_CONTIG=m
CONFIG_VIDEOBUF2_VMALLOC=m
CONFIG_VIDEO_V4L2_TPG=m
Please suggest the configs required for v4l2 testing.
and any additional test coverage.
We add V4L2 config fragments like this
# Vivid driver for V4L2 tests
CONFIG_VIDEO_VIVID=m
CONFIG_MEDIA_SUPPORT=y
CONFIG_V4L_TEST_DRIVERS=y
CONFIG_MEDIA_CAMERA_SUPPORT=y
CONFIG_VIDEO_V4L2=y
CONFIG_VIDEO_DEV=y
git branch: master
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
GOOD:
git commit: cb8e59cc87201af93dfbb6c3dccc8fcad72a09c2
good config: https://builds.tuxbuild.com/600ssEELJrReeIBY_a4Ghw/kernel.config
BAD:
git commit: 6929f71e46bdddbf1c4d67c2728648176c67c555
bad config: https://builds.tuxbuild.com/2eAqpM2VDo7nnt8HXX2Org/kernel.config
Test ref:
https://lkft.validation.linaro.org/scheduler/job/1471386#L1310
Test results comparison,
https://qa-reports.linaro.org/lkft/linux-mainline-oe/build/v5.7-8602-g15a2bc4dbb9c/testrun/2785598/suite/v4l2-compliance/test/modprobe-vivid/history/
- Naresh
reply other threads:[~2020-06-05 10:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CA+G9fYuj7ADfxs+-vY3Hbx5zPceYofCLFy1WRe=-w2_v_J7tSA@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=hans.verkuil@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mchehab+huawei@kernel.org \
--cc=robert.foss@linaro.org \
--cc=stanimir.varbanov@linaro.org \
--cc=sumit.semwal@linaro.org \
--cc=ulf.hansson@linaro.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).