From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Cc: kernel test robot <lkp@intel.com>,
Dafna Hirschfeld <dafna@fastmail.com>,
Keke Li <keke.li@amlogic.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Dan Scally <dan.scally@ideasonboard.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
oe-kbuild-all@lists.linux.dev, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 5/8] media: v4l2-core: Introduce v4l2-params.c
Date: Mon, 15 Sep 2025 17:40:40 +0300 [thread overview]
Message-ID: <20250915144040.GA8821@pendragon.ideasonboard.com> (raw)
In-Reply-To: <jhynzoppwi22vnrdzrvqixsbvntsli7sj2vtsxrevtmxluveps@q6yzgvlqmxxb>
On Mon, Sep 15, 2025 at 03:31:58PM +0200, Jacopo Mondi wrote:
> Question for media maintainers...
>
> I'm not sure how I should better handle this one
>
> On Sun, Aug 24, 2025 at 07:16:21AM +0800, kernel test robot wrote:
> > Hi Jacopo,
> >
> > kernel test robot noticed the following build errors:
> >
> > [auto build test ERROR on a75b8d198c55e9eb5feb6f6e155496305caba2dc]
> >
> > url: https://github.com/intel-lab-lkp/linux/commits/Jacopo-Mondi/media-uapi-Introduce-V4L2-extensible-params/20250820-210503
> > base: a75b8d198c55e9eb5feb6f6e155496305caba2dc
> > patch link: https://lore.kernel.org/r/20250820-extensible-parameters-validation-v4-5-30fe5a99cb1f%40ideasonboard.com
> > patch subject: [PATCH v4 5/8] media: v4l2-core: Introduce v4l2-params.c
> > config: nios2-randconfig-002-20250824 (https://download.01.org/0day-ci/archive/20250824/202508240704.AZwGXBaw-lkp@intel.com/config)
> > compiler: nios2-linux-gcc (GCC) 9.5.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250824/202508240704.AZwGXBaw-lkp@intel.com/reproduce)
> >
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202508240704.AZwGXBaw-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>):
> >
> > nios2-linux-ld: drivers/media/v4l2-core/v4l2-params.o: in function `v4l2_params_buffer_validate':
> > v4l2-params.c:(.text+0x124): undefined reference to `vb2_plane_vaddr'
> > >> v4l2-params.c:(.text+0x124): relocation truncated to fit: R_NIOS2_CALL26 against `vb2_plane_vaddr'
>
> Clearly v4l2-params.c (now v4l2-isp.c) depends on VIDEOBUF2_CORE
>
> Right now v4l2-params.c gets compiled in as part of the
> videodev-objs Makefile target. IOW is not gated by a KConfig option.
>
> To select (or better, depend) on VIDEOBUF2_CORE I should guard
> v4l2-params.c with a KConfig option so that I can 'depend on
> VIDEOBUF2_CORE'. Drivers that use the v4l2-params.c helper would then
> have to 'select V4L2_PARAMS` (or similar).
Make it V4L2_ISP :-)
> Is this the best approach or are there alternatives I might be missing ?
We don't want VIDEODEV depending on VB2. I think it also makes sense to
have a separate Kconfig option for these helpers, are they will be used
by a small number of drivers.
Make CONFIG_V4L2_ISP an option that drivers select, not depend on.
--
Regards,
Laurent Pinchart
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-09-15 14:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 12:58 [PATCH v4 0/8] media: Introduce V4L2 extensible parameters Jacopo Mondi
2025-08-20 12:58 ` [PATCH v4 1/8] media: uapi: Introduce V4L2 extensible params Jacopo Mondi
2025-09-08 7:35 ` Laurent Pinchart
2025-09-15 8:31 ` Jacopo Mondi
2025-09-15 8:41 ` Laurent Pinchart
2025-08-20 12:58 ` [PATCH v4 2/8] media: uapi: Convert RkISP1 to " Jacopo Mondi
2025-09-08 7:39 ` Laurent Pinchart
2025-09-15 8:59 ` Jacopo Mondi
2025-08-20 12:58 ` [PATCH v4 3/8] media: uapi: Convert Amlogic C3 " Jacopo Mondi
2025-08-20 12:58 ` [PATCH v4 4/8] media: Documentation: uapi: Add V4L2 extensible parameters Jacopo Mondi
2025-08-20 12:58 ` [PATCH v4 5/8] media: v4l2-core: Introduce v4l2-params.c Jacopo Mondi
2025-08-23 23:16 ` kernel test robot
2025-09-15 13:31 ` Jacopo Mondi
2025-09-15 14:40 ` Laurent Pinchart [this message]
2025-09-08 8:18 ` Laurent Pinchart
2025-08-20 12:58 ` [PATCH v4 6/8] media: rkisp1: Use v4l2-params for validation Jacopo Mondi
2025-08-20 12:58 ` [PATCH v4 7/8] media: amlogic-c3: " Jacopo Mondi
2025-08-20 12:58 ` [PATCH v4 8/8] media: Documentation: kapi: Add v4l2 extensible parameters Jacopo Mondi
2025-09-05 10:14 ` [PATCH v4 0/8] media: Introduce V4L2 " Antoine Bouyer
2025-09-05 10:39 ` Jacopo Mondi
2025-09-08 13:45 ` Antoine Bouyer
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=20250915144040.GA8821@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=dafna@fastmail.com \
--cc=dan.scally@ideasonboard.com \
--cc=heiko@sntech.de \
--cc=jacopo.mondi@ideasonboard.com \
--cc=keke.li@amlogic.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lkp@intel.com \
--cc=mchehab@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sakari.ailus@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox