[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250713230109.GA10401@pendragon.ideasonboard.com>
Date: Mon, 14 Jul 2025 02:01:09 +0300
From: Laurent Pinchart <laurent.pinchart@...asonboard.com>
To: "Dr. David Alan Gilbert" <linux@...blig.org>
Cc: mchehab@...nel.org, michal.simek@....com, linux-media@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: of xvip_enum_frame_size and xvip_get_format_by_code
On Sun, Jul 13, 2025 at 04:51:08PM +0000, Dr. David Alan Gilbert wrote:
> Hi,
> I noticed in xilinx-cip.c there's xvip_enum_frame_size()
> which was added back in 2013 but seems unused in tree, however
> I had a dig and I found
> https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841638/Xilinx+V4L2+TPG+driver
> has a commit:
> https://github.com/Xilinx/linux-xlnx/commit/1c113b4aef14004152fefc0e8b8dbbcc2314566f#diff-bb594682a92148570df8826933cf8629
> from 2014 that uses it - but it looks like that commit never went
> anywhere.
>
> So is xvip_enum_frame_size() or not?
> I also see xvip_get_format_by_code() looks unused, but I don't
> see any uses of it, even digging in that wiki.
Those functions seem to have never been used in the mainline kernel.
They were likely added to support drivers that have not been upstreamed.
Both functions are used in the Xilinx BSP kernel.
--
Regards,
Laurent Pinchart
Powered by blists - more mailing lists