From: Shuah Khan <skhan@linuxfoundation.org>
To: opensource india <opensource206@gmail.com>
Cc: kieran.bingham@ideasonboard.com, mchehab@kernel.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] media: vimc: add RGB/YUV input entity implementation
Date: Wed, 19 Nov 2025 13:05:45 -0700 [thread overview]
Message-ID: <3150f8ed-5de4-48fa-a6ac-136b07955235@linuxfoundation.org> (raw)
In-Reply-To: <CAKPKb8830YHuY=h662wPVPvTz3LcyLio6pRDy9ZGStkqwu_Vdg@mail.gmail.com>
On 11/6/25 22:02, opensource india wrote:
> On Fri, Nov 7, 2025 at 5:41 AM Shuah Khan <skhan@linuxfoundation.org> wrote:
>>
>> On 11/5/25 22:03, opensource india wrote:
>>> Hi Shuah,
>>>
>>> On Wed, Nov 5, 2025 at 10:43 PM Shuah Khan <skhan@linuxfoundation.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@gmail.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?
>
> Yes. all 4 patches can be applied and test independently
>
Sorry for the delay - these four patches especially this one add
new features/functionality to to vimc.
These require updates - Documentation/admin-guide/media/vimc.rst
Please include the documentation patch - please send these as
series 4 patches + doc patch as a series.
The changes look okay to me.
thanks,
-- Shuah
next prev parent reply other threads:[~2025-11-19 20:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-01 5:26 Pavan Bobba
2025-11-05 17:13 ` Shuah Khan
2025-11-06 5:03 ` opensource india
2025-11-07 0:11 ` Shuah Khan
2025-11-07 5:02 ` opensource india
2025-11-19 20:05 ` Shuah Khan [this message]
2025-11-20 8:53 ` opensource india
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=3150f8ed-5de4-48fa-a6ac-136b07955235@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=opensource206@gmail.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
all inboxes | Powered by JetHome®