Devicetree
 help / color / mirror / Atom feed
From: Jai Luthra <jai.luthra@ideasonboard.com>
To: Rishikesh Donadkar <r-donadkar@ti.com>,
	jai.luthra@linux.dev, laurent.pinchart@ideasonboard.com,
	mripard@kernel.org
Cc: r-donadkar@ti.com, y-abhilashchandra@ti.com, devarsht@ti.com,
	vaishnav.a@ti.com, s-jain1@ti.com, vigneshr@ti.com,
	mchehab@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, sakari.ailus@linux.intel.com,
	hverkuil-cisco@xs4all.nl, tomi.valkeinen@ideasonboard.com,
	changhuang.liang@starfivetech.com, jack.zhu@starfivetech.com,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v5 01/14] media: ti: j721e-csi2rx: Remove word size alignment on frame width
Date: Fri, 05 Sep 2025 16:37:35 +0530	[thread overview]
Message-ID: <175707045529.8095.7424566069689990352@freya> (raw)
In-Reply-To: <20250825142522.1826188-2-r-donadkar@ti.com>

Hi Rishikesh,

Quoting Rishikesh Donadkar (2025-08-25 19:55:09)
> 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].

Is there no limitation for the step size, or also not limitation for the
minimum size of transfer?

> 
> Remove this limitation from the driver.
> 
> Link: https://www.ti.com/lit/pdf/spruj16
> Signed-off-by: Rishikesh Donadkar <r-donadkar@ti.com>
> ---
>  .../platform/ti/j721e-csi2rx/j721e-csi2rx.c     | 17 +++--------------
>  1 file changed, 3 insertions(+), 14 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..b3a27f4c3210 100644
> --- a/drivers/media/platform/ti/j721e-csi2rx/j721e-csi2rx.c
> +++ b/drivers/media/platform/ti/j721e-csi2rx/j721e-csi2rx.c
> @@ -260,9 +260,6 @@ static void ti_csi2rx_fill_fmt(const struct ti_csi2rx_fmt *csi_fmt,
>                              MAX_WIDTH_BYTES * 8 / csi_fmt->bpp);

Here the pix->width is restricted to be at minimum pixels_in_word.
So TRY_FMT/S_FMT with a width = 1 will be clamped by the driver.

>         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 +357,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;

But here, in ENUM_FRAMESIZES we allow width to go as low as 1.

Can you make sure both of them match whatever is correct (and possible by
the hardware)?

> +       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;
> -- 
> 2.34.1
> 

Thanks,
    Jai

  parent reply	other threads:[~2025-09-05 11:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 14:25 [PATCH v5 00/14] media: cadence,ti: CSI2RX Multistream Support Rishikesh Donadkar
2025-08-25 14:25 ` [PATCH v5 01/14] media: ti: j721e-csi2rx: Remove word size alignment on frame width Rishikesh Donadkar
2025-09-05 10:10   ` Yemike Abhilash Chandra
2025-09-05 11:07   ` Jai Luthra [this message]
2025-09-08  8:21     ` Rishikesh Donadkar
2025-08-25 14:25 ` [PATCH v5 02/14] dt-bindings: media: ti,j721e-csi2rx-shim: Support 32 dma chans Rishikesh Donadkar
2025-08-25 14:25 ` [PATCH v5 03/14] media: ti: j721e-csi2rx: separate out device and context Rishikesh Donadkar
2025-08-25 14:25 ` [PATCH v5 04/14] media: ti: j721e-csi2rx: prepare SHIM code for multiple contexts Rishikesh Donadkar
2025-08-25 14:25 ` [PATCH v5 05/14] media: ti: j721e-csi2rx: allocate DMA channel based on context index Rishikesh Donadkar
2025-08-25 14:25 ` [PATCH v5 06/14] media: ti: j721e-csi2rx: add a subdev for the core device Rishikesh Donadkar
2025-08-25 14:25 ` [PATCH v5 07/14] media: ti: j721e-csi2rx: get number of contexts from device tree Rishikesh Donadkar
2025-08-28 11:11   ` Jai Luthra
2025-08-25 14:25 ` [PATCH v5 08/14] media: cadence: csi2rx: add get_frame_desc wrapper Rishikesh Donadkar
2025-08-25 14:25 ` [PATCH v5 09/14] media: ti: j721e-csi2rx: add support for processing virtual channels Rishikesh Donadkar
2025-08-28 11:13   ` Jai Luthra
2025-08-25 14:25 ` [PATCH v5 10/14] media: cadence: csi2rx: add multistream support Rishikesh Donadkar
2025-08-25 14:25 ` [PATCH v5 11/14] media: ti: j721e-csi2rx: " Rishikesh Donadkar
2025-08-25 14:25 ` [PATCH v5 12/14] media: ti: j721e-csi2rx: Submit all available buffers Rishikesh Donadkar
2025-08-25 14:25 ` [PATCH v5 13/14] media: ti: j721e-csi2rx: Change the drain architecture for multistream Rishikesh Donadkar
2025-08-25 14:25 ` [PATCH v5 14/14] media: ti: j721e-csi2rx: Wait for the last drain completion Rishikesh Donadkar
2025-09-05 10:13   ` Yemike Abhilash Chandra
2025-09-05 11:11   ` Jai Luthra
2025-09-08  9:51     ` Rishikesh Donadkar

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=175707045529.8095.7424566069689990352@freya \
    --to=jai.luthra@ideasonboard.com \
    --cc=changhuang.liang@starfivetech.com \
    --cc=conor+dt@kernel.org \
    --cc=devarsht@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jack.zhu@starfivetech.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=r-donadkar@ti.com \
    --cc=robh@kernel.org \
    --cc=s-jain1@ti.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=tomi.valkeinen@ideasonboard.com \
    --cc=vaishnav.a@ti.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