linux-kernel - Re: [PATCH] media: vimc: add RGB/YUV input entity implementation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c64985f5-f1e5-4880-876d-0a3c9d83629c@linuxfoundation.org>
Date: Thu, 6 Nov 2025 17:11:53 -0700
From: Shuah Khan <skhan@...uxfoundation.org>
To: opensource india <opensource206@...il.com>
Cc: kieran.bingham@...asonboard.com, mchehab@...nel.org,
 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 11/5/25 22:03, opensource india wrote:
> Hi Shuah,
> 
> On Wed, Nov 5, 2025 at 10:43 PM Shuah Khan <skhan@...uxfoundation.org> wrote:
>>
>> 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
> 
> even though all 4 patches are part of vimc driver,
> these are independent patches

Independent in the sense that they can be applied and tested
independently?

thanks,
-- Shuah