From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Isaac Scott <isaac.scott@ideasonboard.com>
Cc: linux-media@vger.kernel.org, dafna@fastmail.com,
mchehab@kernel.org, heiko@sntech.de,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/6] media: rkisp1-resizer: Add YUV source formats to resizer
Date: Wed, 4 Feb 2026 18:43:56 +0200 [thread overview]
Message-ID: <20260204164356.GC170964@killaraus> (raw)
In-Reply-To: <20260204112506.3706049-2-isaac.scott@ideasonboard.com>
On Wed, Feb 04, 2026 at 11:25:01AM +0000, Isaac Scott wrote:
> To be able to use YUV bypass, YUV formats need to be available on the
> source pad of the rkisp1 resizer. Add them.
>
> Signed-off-by: Isaac Scott <isaac.scott@ideasonboard.com>
> ---
> .../platform/rockchip/rkisp1/rkisp1-resizer.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/drivers/media/platform/rockchip/rkisp1/rkisp1-resizer.c b/drivers/media/platform/rockchip/rkisp1/rkisp1-resizer.c
> index 8e6b753d3081..e72b76ab078c 100644
> --- a/drivers/media/platform/rockchip/rkisp1/rkisp1-resizer.c
> +++ b/drivers/media/platform/rockchip/rkisp1/rkisp1-resizer.c
> @@ -23,11 +23,26 @@ struct rkisp1_rsz_yuv_mbus_info {
> };
>
> static const struct rkisp1_rsz_yuv_mbus_info rkisp1_rsz_yuv_src_formats[] = {
> + {
> + .mbus_code = MEDIA_BUS_FMT_UYVY8_2X8, /* YUV422 */
> + .hdiv = 1,
> + .vdiv = 1,
> + },
> + {
> + .mbus_code = MEDIA_BUS_FMT_VYUY8_2X8, /* YUV422 */
> + .hdiv = 1,
> + .vdiv = 1,
> + },
> {
> .mbus_code = MEDIA_BUS_FMT_YUYV8_2X8, /* YUV422 */
> .hdiv = 2,
> .vdiv = 1,
> },
> + {
> + .mbus_code = MEDIA_BUS_FMT_YVYU8_2X8, /* YUV422 */
> + .hdiv = 1,
Shouldn't hdiv be 2 for all those new formats ?
But overall, I don't think those formats are needed. I would be very
surprised if the resizer used different YUV orders on its output bus.
Can't you use MEDIA_BUS_FMT_YUYV8_2X8 unconditionally ?
> + .vdiv = 1,
> + },
> {
> .mbus_code = MEDIA_BUS_FMT_YUYV8_1_5X8, /* YUV420 */
> .hdiv = 2,
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2026-02-04 16:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 11:25 [PATCH v1 0/6] media: rkisp1: Add YUV bypass support for rkisp1 Isaac Scott
2026-02-04 11:25 ` [PATCH v1 1/6] media: rkisp1-resizer: Add YUV source formats to resizer Isaac Scott
2026-02-04 16:43 ` Laurent Pinchart [this message]
2026-02-04 11:25 ` [PATCH v1 2/6] media: rkisp1-isp: Add in_bypass flag for YUV bypass Isaac Scott
2026-02-04 17:04 ` Laurent Pinchart
2026-02-04 11:25 ` [PATCH v1 3/6] media: rkisp1-isp: Add target_format Isaac Scott
2026-02-04 11:37 ` Laurent Pinchart
2026-02-04 13:28 ` Isaac Scott
2026-02-04 11:25 ` [PATCH v1 4/6] media: rkisp1-isp: Propagate sink -> source format in YUV passthough Isaac Scott
2026-02-04 15:28 ` Laurent Pinchart
2026-02-04 11:25 ` [PATCH v1 5/6] media: rkisp1: Give buffers back instead of dropping in bypass mode Isaac Scott
2026-02-04 15:40 ` Laurent Pinchart
2026-02-04 16:36 ` Isaac Scott
2026-02-04 11:25 ` [PATCH v1 6/6] media: rkisp1: Treat 8 bus width and 16 bus width formats the same Isaac Scott
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=20260204164356.GC170964@killaraus \
--to=laurent.pinchart@ideasonboard.com \
--cc=dafna@fastmail.com \
--cc=heiko@sntech.de \
--cc=isaac.scott@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
/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