From: Nicolas Dufresne <nicolas@ndufresne.ca>
To: "Sven Püschel" <s.pueschel@pengutronix.de>,
"Jacob Chen" <jacob-chen@iotwrt.com>,
"Ezequiel Garcia" <ezequiel@vanguardiasur.com.ar>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Heiko Stuebner" <heiko@sntech.de>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Hans Verkuil" <hverkuil@kernel.org>
Cc: linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
kernel@pengutronix.de, sebastian.reichel@collabora.com
Subject: Re: [PATCH v5 12/29] media: rockchip: rga: avoid odd frame sizes for YUV formats
Date: Tue, 12 May 2026 11:09:35 -0400 [thread overview]
Message-ID: <b354afdfd28ec3736791755d9ce8cae49a744a96.camel@ndufresne.ca> (raw)
In-Reply-To: <e6d562e7-a9d2-4a1a-a139-c6e05eb4aaef@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 4650 bytes --]
Le mardi 12 mai 2026 à 16:56 +0200, Sven Püschel a écrit :
> Hi Nicolas,
>
> On 5/8/26 11:18 PM, Nicolas Dufresne wrote:
> > Le mardi 28 avril 2026 à 11:00 +0200, Sven Püschel a écrit :
> > > Avoid odd frame sizes for YUV formats, as they may cause undefined
> > > behavior. This is done in preparation for the RGA3, which hangs when the
> > > output format is set to 129x129 pixel YUV420 SP (NV12).
> > >
> > > This requirement is documented explicitly for the RGA3 in section 5.6.3
> > > of the RK3588 TRM Part 2. For the RGA2 the RK3588 TRM Part 2
> > > (section 6.1.2) and RK3568 TRM Part 2 (section 14.2) only mentions the
> > > x/y offsets and stride aligning requirements. But the vendor driver for
> > > the RGA2 also contains checks for the width and height to be aligned to
> > > 2 bytes.
> > >
> > > Signed-off-by: Sven Püschel <s.pueschel@pengutronix.de>
> > > ---
> > > drivers/media/platform/rockchip/rga/rga.c | 19 ++++++++++++++-----
> > > 1 file changed, 14 insertions(+), 5 deletions(-)
> > >
> > > diff --git a/drivers/media/platform/rockchip/rga/rga.c b/drivers/media/platform/rockchip/rga/rga.c
> > > index f599c992829dd..77b8c7ab74274 100644
> > > --- a/drivers/media/platform/rockchip/rga/rga.c
> > > +++ b/drivers/media/platform/rockchip/rga/rga.c
> > > @@ -337,6 +337,19 @@ static int vidioc_try_fmt(struct file *file, void *priv, struct v4l2_format *f)
> > > struct rga_ctx *ctx = file_to_rga_ctx(file);
> > > const struct rga_hw *hw = ctx->rga->hw;
> > > struct rga_fmt *fmt;
> > > + struct v4l2_frmsize_stepwise frmsize = {
> > > + .min_width = hw->min_width,
> > > + .max_width = hw->max_width,
> > > + .min_height = hw->min_height,
> > > + .max_height = hw->max_height,
> > > + .step_width = 1,
> > > + .step_height = 1,
> > > + };
> > > +
> > > + if (v4l2_is_format_yuv(v4l2_format_info(pix_fmt->pixelformat))) {
> > > + frmsize.step_width = 2;
> > > + frmsize.step_height = 2;
> > I think its fine like this, so let's start with:
> >
> > Reviewed-by: Nicolas Dufresne <nicolas.dufresne@collabora.com>
> >
> > But it does not feel like a hardware alignment to me. When we process in
> > software these things, the minimum alignment is bound to the subsampling, since
> > there is no way to store half or quarter pixels, the padded width/height
> > requires a step that follow the subsampling, something like:
> >
> > frmsize.step_width = finfo->hdiv;
> > frmsize.step_height = finfo->vdiv;
>
> I agree that this looks better. My main intention is to be more
> conservative, as the Rockchip related code/docs seem to always ensure a
> 2 pixel alignment in both directions even for formats like YUV422, where
> we shouldn't have an alignment requirement in the height. Besides the
> vendor driver and TRM mentioned in the datasheet, the librga and it's
> docs also mention an alignment of 2 (pixels?!) for all YUV formats (see
> format alignment list in [1] and Q2.5 in [2]).
>
> Given that the driver currently doesn't have any way to get the cores
> unstuck/reset in case of a hang, I'd like to play it more safely by
> adhering to what the vendor does instead of trying to do more and
> therefore allowing some potential breaking format. E.g. I've also
> experimented with sizes of 68x2, which the librga allows as input/output
> of the RGA3 (whereas the TRM specifies a min size of 128x128), but
> quickly dropped it as it produced some interesting broken outputs.
Agreed, simply preserve my Rb in next version.
cheers,
Nicolas
>
> Sincerely
> Sven
>
>
> [1]
> https://codeberg.org/airockchip/librga/src/branch/main/docs/Rockchip_Developer_Guide_RGA_EN.md#image-format-alignment-instructions
>
> [2]
> https://codeberg.org/airockchip/librga/src/branch/main/docs/Rockchip_FAQ_RGA_EN.md
>
> >
> > Nicolas
> >
> >
> > > + }
> > >
> > > if (V4L2_TYPE_IS_CAPTURE(f->type)) {
> > > const struct rga_frame *frm;
> > > @@ -358,11 +371,7 @@ static int vidioc_try_fmt(struct file *file, void *priv, struct v4l2_format *f)
> > > if (!fmt)
> > > fmt = &hw->formats[0];
> > >
> > > - pix_fmt->width = clamp(pix_fmt->width,
> > > - hw->min_width, hw->max_width);
> > > - pix_fmt->height = clamp(pix_fmt->height,
> > > - hw->min_height, hw->max_height);
> > > -
> > > + v4l2_apply_frmsize_constraints(&pix_fmt->width, &pix_fmt->height, &frmsize);
> > > v4l2_fill_pixfmt_mp(pix_fmt, fmt->fourcc, pix_fmt->width, pix_fmt->height);
> > > pix_fmt->field = V4L2_FIELD_NONE;
> > >
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-05-12 15:09 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 9:00 [PATCH v5 00/29] media: platform: rga: Add RGA3 support Sven Püschel
2026-04-28 9:00 ` [PATCH v5 01/29] media: dt-bindings: media: rockchip-rga: add rockchip,rk3588-rga3 Sven Püschel
2026-04-28 9:00 ` [PATCH v5 02/29] media: v4l2-common: sort RGB formats in v4l2_format_info Sven Püschel
2026-04-28 9:00 ` [PATCH v5 03/29] media: v4l2-common: add missing 1 and 2 byte RGB formats to v4l2_format_info Sven Püschel
2026-04-28 9:00 ` [PATCH v5 04/29] media: v4l2-common: add has_alpha " Sven Püschel
2026-04-28 9:00 ` [PATCH v5 05/29] media: v4l2-common: add v4l2_fill_pixfmt_mp_aligned helper Sven Püschel
2026-05-08 21:09 ` Nicolas Dufresne
2026-04-28 9:00 ` [PATCH v5 06/29] media: rockchip: rga: fix too small buffer size Sven Püschel
2026-05-08 21:11 ` Nicolas Dufresne
2026-05-12 14:14 ` Sven Püschel
2026-04-28 9:00 ` [PATCH v5 07/29] media: rockchip: rga: use clk_bulk api Sven Püschel
2026-04-28 9:00 ` [PATCH v5 08/29] media: rockchip: rga: use stride for offset calculation Sven Püschel
2026-04-28 9:00 ` [PATCH v5 09/29] media: rockchip: rga: remove redundant rga_frame variables Sven Püschel
2026-04-28 9:00 ` [PATCH v5 10/29] media: rockchip: rga: announce and sync colorimetry Sven Püschel
2026-04-28 9:00 ` [PATCH v5 11/29] media: rockchip: rga: move hw specific parts to a dedicated struct Sven Püschel
2026-04-28 9:00 ` [PATCH v5 12/29] media: rockchip: rga: avoid odd frame sizes for YUV formats Sven Püschel
2026-05-08 21:18 ` Nicolas Dufresne
2026-05-12 14:56 ` Sven Püschel
2026-05-12 15:09 ` Nicolas Dufresne [this message]
2026-04-28 9:00 ` [PATCH v5 13/29] media: rockchip: rga: calculate x_div/y_div using v4l2_format_info Sven Püschel
2026-04-28 9:00 ` [PATCH v5 14/29] media: rockchip: rga: move cmdbuf to rga_ctx Sven Püschel
2026-04-28 9:00 ` [PATCH v5 15/29] media: rockchip: rga: align stride to 4 bytes Sven Püschel
2026-04-28 9:00 ` [PATCH v5 16/29] media: rockchip: rga: split flip and rotate into separate function Sven Püschel
2026-05-08 22:11 ` Nicolas Dufresne
2026-05-12 14:08 ` Sven Püschel
2026-05-12 14:15 ` Nicolas Dufresne
2026-04-28 9:00 ` [PATCH v5 17/29] media: rockchip: rga: prepare cmdbuf on streamon Sven Püschel
2026-04-28 9:00 ` [PATCH v5 18/29] media: rockchip: rga: check scaling factor Sven Püschel
2026-05-08 23:11 ` Nicolas Dufresne
2026-04-28 9:00 ` [PATCH v5 19/29] media: rockchip: rga: use card type to specify rga type Sven Püschel
2026-04-28 9:00 ` [PATCH v5 20/29] media: rockchip: rga: change offset to dma_addresses Sven Püschel
2026-04-28 9:00 ` [PATCH v5 21/29] media: rockchip: rga: support external iommus Sven Püschel
2026-04-28 9:00 ` [PATCH v5 22/29] media: rockchip: rga: share the interrupt when an external iommu is used Sven Püschel
2026-04-28 9:00 ` [PATCH v5 23/29] media: rockchip: rga: remove size from rga_frame Sven Püschel
2026-04-28 9:00 ` [PATCH v5 24/29] media: rockchip: rga: remove stride " Sven Püschel
2026-04-28 9:01 ` [PATCH v5 25/29] media: rockchip: rga: move rga_fmt to rga-hw.h Sven Püschel
2026-04-28 9:01 ` [PATCH v5 26/29] media: rockchip: rga: add feature flags Sven Püschel
2026-04-28 9:01 ` [PATCH v5 27/29] media: rockchip: rga: disable multi-core support Sven Püschel
2026-04-28 9:01 ` [PATCH v5 28/29] media: rockchip: rga: add rga3 support Sven Püschel
2026-04-28 9:01 ` [PATCH v5 29/29] arm64: dts: rockchip: add rga3 dt nodes Sven Püschel
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=b354afdfd28ec3736791755d9ce8cae49a744a96.camel@ndufresne.ca \
--to=nicolas@ndufresne.ca \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=heiko@sntech.de \
--cc=hverkuil@kernel.org \
--cc=jacob-chen@iotwrt.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--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 \
--cc=robh@kernel.org \
--cc=s.pueschel@pengutronix.de \
--cc=sebastian.reichel@collabora.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