From: Shuah Khan <skhan@linuxfoundation.org>
To: Pavan Bobba <opensource206@gmail.com>,
kieran.bingham@ideasonboard.com, mchehab@kernel.org
Cc: 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, 5 Nov 2025 10:13:27 -0700 [thread overview]
Message-ID: <959ac74b-a8b7-4d4e-9d34-3b3d971f9f8a@linuxfoundation.org> (raw)
In-Reply-To: <20251101052651.6197-1-opensource206@gmail.com>
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
next prev parent reply other threads:[~2025-11-05 17:13 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 [this message]
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
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=959ac74b-a8b7-4d4e-9d34-3b3d971f9f8a@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®