From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Rishikesh Donadkar <r-donadkar@ti.com>,
jai.luthra@linux.dev, laurent.pinchart@ideasonboard.com,
mripard@kernel.org
Cc: y-abhilashchandra@ti.com, devarsht@ti.com, s-jain1@ti.com,
vigneshr@ti.com, mchehab@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, p.zabel@pengutronix.de, conor+dt@kernel.org,
sakari.ailus@linux.intel.com, hverkuil-cisco@xs4all.nl,
jai.luthra@ideasonboard.com, changhuang.liang@starfivetech.com,
jack.zhu@starfivetech.com, sjoerd@collabora.com,
hverkuil+cisco@kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v7 01/16] media: ti: j721e-csi2rx: Remove word size alignment on frame width
Date: Mon, 22 Sep 2025 14:56:25 +0300 [thread overview]
Message-ID: <4becc7fc-fe25-4f7c-9434-399b1c2c3cce@ideasonboard.com> (raw)
In-Reply-To: <20250911102832.1583440-2-r-donadkar@ti.com>
Hi,
On 11/09/2025 13:28, Rishikesh Donadkar wrote:
> j721e-csi2rx driver has a limitation of frame width being a multiple
> word size. However, there is no such limitation imposed by the
> hardware [1].
>
> Remove this limitation from the driver.
>
> Link: https://www.ti.com/lit/pdf/spruj16
> Reviewed-by: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
> Signed-off-by: Rishikesh Donadkar <r-donadkar@ti.com>
> ---
> .../platform/ti/j721e-csi2rx/j721e-csi2rx.c | 23 ++++---------------
> 1 file changed, 4 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/media/platform/ti/j721e-csi2rx/j721e-csi2rx.c b/drivers/media/platform/ti/j721e-csi2rx/j721e-csi2rx.c
> index 3992f8b754b7..6a981b5f5d51 100644
> --- a/drivers/media/platform/ti/j721e-csi2rx/j721e-csi2rx.c
> +++ b/drivers/media/platform/ti/j721e-csi2rx/j721e-csi2rx.c
> @@ -250,19 +250,12 @@ static void ti_csi2rx_fill_fmt(const struct ti_csi2rx_fmt *csi_fmt,
> struct v4l2_format *v4l2_fmt)
> {
> struct v4l2_pix_format *pix = &v4l2_fmt->fmt.pix;
> - unsigned int pixels_in_word;
> -
> - pixels_in_word = PSIL_WORD_SIZE_BYTES * 8 / csi_fmt->bpp;
The define for PSIL_WORD_SIZE_BYTES can also be removed, if I'm not
mistaken.
I assume this has been tested, but I'm still a bit curious. Usually
these kind of lines of code don't just appear out of nowhere. You linked
to AM62Ax docs. None of the other SoCs have any limitations here either?
PSIL_WORD_SIZE_BYTES hints to a system DMA level limit, not CSI-2 RX
limit, so I wonder if some earlier SoCs had such limitations in the DMA?
Tomi
>
> /* Clamp width and height to sensible maximums (16K x 16K) */
> pix->width = clamp_t(unsigned int, pix->width,
> - pixels_in_word,
> - MAX_WIDTH_BYTES * 8 / csi_fmt->bpp);
> + 1, MAX_WIDTH_BYTES * 8 / csi_fmt->bpp);
> pix->height = clamp_t(unsigned int, pix->height, 1, MAX_HEIGHT_LINES);
>
> - /* Width should be a multiple of transfer word-size */
> - pix->width = rounddown(pix->width, pixels_in_word);
> -
> v4l2_fmt->type = V4L2_BUF_TYPE_VIDEO_CAPTURE;
> pix->pixelformat = csi_fmt->fourcc;
> pix->bytesperline = pix->width * (csi_fmt->bpp / 8);
> @@ -360,23 +353,15 @@ static int ti_csi2rx_enum_framesizes(struct file *file, void *fh,
> struct v4l2_frmsizeenum *fsize)
> {
> const struct ti_csi2rx_fmt *fmt;
> - unsigned int pixels_in_word;
>
> fmt = find_format_by_fourcc(fsize->pixel_format);
> if (!fmt || fsize->index != 0)
> return -EINVAL;
>
> - /*
> - * Number of pixels in one PSI-L word. The transfer happens in multiples
> - * of PSI-L word sizes.
> - */
> - pixels_in_word = PSIL_WORD_SIZE_BYTES * 8 / fmt->bpp;
> -
> fsize->type = V4L2_FRMSIZE_TYPE_STEPWISE;
> - fsize->stepwise.min_width = pixels_in_word;
> - fsize->stepwise.max_width = rounddown(MAX_WIDTH_BYTES * 8 / fmt->bpp,
> - pixels_in_word);
> - fsize->stepwise.step_width = pixels_in_word;
> + fsize->stepwise.min_width = 1;
> + fsize->stepwise.max_width = MAX_WIDTH_BYTES * 8 / fmt->bpp;
> + fsize->stepwise.step_width = 1;
> fsize->stepwise.min_height = 1;
> fsize->stepwise.max_height = MAX_HEIGHT_LINES;
> fsize->stepwise.step_height = 1;
next prev parent reply other threads:[~2025-09-22 11:56 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 10:28 [PATCH v7 00/16] media: cadence,ti: CSI2RX Multistream Support Rishikesh Donadkar
2025-09-11 10:28 ` [PATCH v7 01/16] media: ti: j721e-csi2rx: Remove word size alignment on frame width Rishikesh Donadkar
2025-09-22 11:56 ` Tomi Valkeinen [this message]
2025-10-17 4:53 ` Donadkar, Rishikesh
2025-09-11 10:28 ` [PATCH v7 02/16] dt-bindings: media: ti,j721e-csi2rx-shim: Support 32 dma chans Rishikesh Donadkar
2025-09-11 10:28 ` [PATCH v7 03/16] media: ti: j721e-csi2rx: separate out device and context Rishikesh Donadkar
2025-09-22 12:03 ` Tomi Valkeinen
2025-09-11 10:28 ` [PATCH v7 04/16] media: ti: j721e-csi2rx: prepare SHIM code for multiple contexts Rishikesh Donadkar
2025-09-22 12:03 ` Tomi Valkeinen
2025-09-11 10:28 ` [PATCH v7 05/16] media: ti: j721e-csi2rx: allocate DMA channel based on context index Rishikesh Donadkar
2025-09-22 12:04 ` Tomi Valkeinen
2025-09-11 10:28 ` [PATCH v7 06/16] media: ti: j721e-csi2rx: add a subdev for the core device Rishikesh Donadkar
2025-09-22 12:38 ` Tomi Valkeinen
2025-11-06 9:53 ` Rishikesh Donadkar
2025-09-11 10:28 ` [PATCH v7 07/16] media: ti: j721e-csi2rx: get number of contexts from device tree Rishikesh Donadkar
2025-09-22 12:39 ` Tomi Valkeinen
2025-09-11 10:28 ` [PATCH v7 08/16] media: cadence: csi2rx: add get_frame_desc wrapper Rishikesh Donadkar
2025-09-22 12:49 ` Tomi Valkeinen
2025-09-11 10:28 ` [PATCH v7 09/16] media: ti: j721e-csi2rx: add support for processing virtual channels Rishikesh Donadkar
2025-09-22 13:30 ` Tomi Valkeinen
2025-11-06 10:35 ` Rishikesh Donadkar
2025-09-11 10:28 ` [PATCH v7 10/16] media: cadence: csi2rx: add multistream support Rishikesh Donadkar
2025-09-22 14:39 ` Tomi Valkeinen
2025-09-25 12:44 ` Tomi Valkeinen
2025-11-10 12:23 ` Rishikesh Donadkar
2025-11-11 9:46 ` Rishikesh Donadkar
2025-09-11 10:28 ` [PATCH v7 11/16] media: ti: j721e-csi2rx: " Rishikesh Donadkar
2025-09-25 12:17 ` Tomi Valkeinen
2025-10-07 11:52 ` Jai Luthra
2025-11-11 12:19 ` Rishikesh Donadkar
2025-09-11 10:28 ` [PATCH v7 12/16] media: ti: j721e-csi2rx: Submit all available buffers Rishikesh Donadkar
2025-09-11 10:28 ` [PATCH v7 13/16] media: ti: j721e-csi2rx: Change the drain architecture for multistream Rishikesh Donadkar
2025-09-11 10:28 ` [PATCH v7 14/16] media: cadence: csi2rx: Support runtime PM Rishikesh Donadkar
2025-09-11 10:28 ` [PATCH v7 15/16] media: ti: j721e-csi2rx: Support runtime suspend Rishikesh Donadkar
2025-09-11 10:28 ` [PATCH v7 16/16] media: ti: j721e-csi2rx: Support system suspend using pm_notifier Rishikesh Donadkar
2025-09-12 9:45 ` [PATCH v7 00/16] media: cadence,ti: CSI2RX Multistream Support Jai Luthra
2025-09-24 9:33 ` Tomi Valkeinen
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=4becc7fc-fe25-4f7c-9434-399b1c2c3cce@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=changhuang.liang@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil+cisco@kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jack.zhu@starfivetech.com \
--cc=jai.luthra@ideasonboard.com \
--cc=jai.luthra@linux.dev \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=r-donadkar@ti.com \
--cc=robh@kernel.org \
--cc=s-jain1@ti.com \
--cc=sakari.ailus@linux.intel.com \
--cc=sjoerd@collabora.com \
--cc=vigneshr@ti.com \
--cc=y-abhilashchandra@ti.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