[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <959ac74b-a8b7-4d4e-9d34-3b3d971f9f8a@linuxfoundation.org>
Date: Wed, 5 Nov 2025 10:13:27 -0700
From: Shuah Khan <skhan@...uxfoundation.org>
To: Pavan Bobba <opensource206@...il.com>, kieran.bingham@...asonboard.com,
mchehab@...nel.org
Cc: linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: [PATCH] media: vimc: add RGB/YUV input entity implementation
On 10/31/25 23:26, Pavan Bobba wrote:
> Introduce a new vimc-input entity to simulate a color frame source in the
> Virtual Media Controller (VIMC) pipeline. This entity outputs RGB888 frames
> and allows testing of pipelines that start from a pre-processed RGB/YUV
> source instead of a raw Bayer sensor.
>
> The patch adds vimc-input.c with basic pad operations for format
> enumeration, get/set, and stream enable/disable handlers. The entity is
> registered in the VIMC core configuration, replacing the previous temporary
> use of vimc-sensor. Frame generation is not yet implemented and remains a
> TODO for future work.
>
> This change enables link validation and format negotiation for the
> RGB/YUV input path, paving the way for software frame injection and
> test-pattern generation.
>
> Signed-off-by: Pavan Bobba <opensource206@...il.com>
I see 4 patches - are they dependent then gerenrate a sries
with cover letter explaining the changes you are making.
thanks,
-- Shuah
Powered by blists - more mailing lists