Devicetree
 help / color / mirror / Atom feed
From: Jai Luthra <jai.luthra@ideasonboard.com>
To: Rishikesh Donadkar <r-donadkar@ti.com>,
	Tomi Valkeinen <tomi.valkeinen@ideasonboard.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,
	changhuang.liang@starfivetech.com, jack.zhu@starfivetech.com,
	sjoerd@collabora.com, dan.carpenter@linaro.org,
	hverkuil+cisco@kernel.org, linux-kernel@vger.kernel.org,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v8 13/18] media: ti: j721e-csi2rx: add multistream support
Date: Tue, 09 Dec 2025 17:36:39 +0530	[thread overview]
Message-ID: <176528199956.20066.17866034505160159556@freya> (raw)
In-Reply-To: <4854792f-e682-4291-89c4-c0139a6c24bc@ideasonboard.com>

Quoting Tomi Valkeinen (2025-12-09 17:22:08)
> Hi,
> 
> On 09/12/2025 12:36, Jai Luthra wrote:
> > Hi Rishikesh,
> > 
> > Quoting Rishikesh Donadkar (2025-12-09 15:38:33)
> >>
> >> On 01/12/25 18:33, Tomi Valkeinen wrote:
> >>> Hi,
> >>
> >>
> >> Hi Tomi,
> >>
> >> Thank you for the review !
> >>
> >>>
> >>> On 12/11/2025 13:54, Rishikesh Donadkar wrote:
> >>>> From: Jai Luthra <j-luthra@ti.com>
> >>>>
> >>>> Each CSI2 stream can be multiplexed into 4 independent streams, each
> >>> Well, that's not true, at least generally speaking (there can be more
> >>> than 4). Is that specific to TI hardware?
> >>
> >>
> >> Yes, The commit message talks about how TI CSI does the multiplexing of 
> >> CSI stream from the sensor into 4 streams as show in the Figure 12-388 
> >> in AM62A TRM[1]. I will modify the commit message to mention that this 
> >> is TI CSI specific.
> > 
> > Figure 12-388 shows the internal pixel stream coming from Cadence to
> > different hardware blocks like TI's Shim (DMA) and VP0 (ISP) and VP1. I
> > don't see that being related to CSI2 VC/DT support, which is handled by the
> > Shim using different DMA contexts and channels.
> > 
> > In the TRM, under 12.6.1.1.1 CSI_RX_IF Features, I see:
> >  * Compliant to MIPI CSI v1.3
> >  * Supports up to 16 virtual channels per input (partial MIPI CSI v2.0 feature)
> > 
> > So 16 VCs is supported by TI's CSI pipeline, despite it being MIPI CSI2
> > v1.3 compliant otherwise. I think I might have been confused with DS90UB960
> > while writing this commit message originally, which strictly supports a
> > maximum of 4 VCs.
> > 
> > Secondly, even with just CSI2 v1.0 compliant source, this could
> > theoretically handle 8 "streams" of data with 4 different VCs x 2 data
> > types each. So please update the paragraph in next revision.
> Where does the "8" come from? Do we have 8 context registers, to which
> we program the VC + DT filter?

Indeed, 8 was just an example. The hardware can support upto 32
combinations, as that is the total number of DMA contexts available.

Thanks,
    Jai

> 
> Also, it could as well be 8 streams, all with VC 0, but each different
> DT (probably unlikely scenario =). But I just want to highlight that VC
> is not the "stream". The "stream" is the VC+DT tuple.
> 
>  Tomi
>

  reply	other threads:[~2025-12-09 12:06 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12 11:54 [PATCH v8 00/18] media: cadence,ti: CSI2RX Multistream Support Rishikesh Donadkar
2025-11-12 11:54 ` [PATCH v8 01/18] media: ti: j721e-csi2rx: Remove word size alignment on frame width Rishikesh Donadkar
2025-11-20 11:58   ` Tomi Valkeinen
2025-11-12 11:54 ` [PATCH v8 02/18] dt-bindings: media: ti,j721e-csi2rx-shim: Support 32 dma chans Rishikesh Donadkar
2025-11-12 11:54 ` [PATCH v8 03/18] media: ti: j721e-csi2rx: separate out device and context Rishikesh Donadkar
2025-11-12 11:54 ` [PATCH v8 04/18] media: ti: j721e-csi2rx: prepare SHIM code for multiple contexts Rishikesh Donadkar
2025-11-12 11:54 ` [PATCH v8 05/18] media: ti: j721e-csi2rx: allocate DMA channel based on context index Rishikesh Donadkar
2025-11-12 11:54 ` [PATCH v8 06/18] media: ti: j721e-csi2rx: add a subdev for the core device Rishikesh Donadkar
2025-11-20 12:39   ` Sakari Ailus
2025-11-21  6:59     ` Rishikesh Donadkar
2025-11-12 11:54 ` [PATCH v8 07/18] media: cadence: csi2rx: Move to .enable/disable_streams API Rishikesh Donadkar
2025-11-20 13:00   ` Tomi Valkeinen
2025-11-21  7:02     ` Rishikesh Donadkar
2025-11-12 11:54 ` [PATCH v8 08/18] media: ti: j721e-csi2rx: " Rishikesh Donadkar
2025-11-20 12:40   ` Sakari Ailus
2025-11-21  7:04     ` Rishikesh Donadkar
2025-11-12 11:54 ` [PATCH v8 09/18] media: ti: j721e-csi2rx: get number of contexts from device tree Rishikesh Donadkar
2025-11-12 11:54 ` [PATCH v8 10/18] media: cadence: csi2rx: add get_frame_desc wrapper Rishikesh Donadkar
2025-11-20 12:40   ` Tomi Valkeinen
2025-12-02  9:03     ` Rishikesh Donadkar
2025-11-12 11:54 ` [PATCH v8 11/18] media: ti: j721e-csi2rx: add support for processing virtual channels Rishikesh Donadkar
2025-11-20 12:32   ` Tomi Valkeinen
2025-12-01  9:25     ` Rishikesh Donadkar
2025-11-12 11:54 ` [PATCH v8 12/18] media: cadence: csi2rx: add multistream support Rishikesh Donadkar
2025-11-20 12:53   ` Sakari Ailus
2025-12-09  9:43     ` Rishikesh Donadkar
2025-12-29 11:14       ` Sakari Ailus
2025-11-20 13:14   ` Tomi Valkeinen
2025-12-09  9:45     ` Rishikesh Donadkar
2025-11-12 11:54 ` [PATCH v8 13/18] media: ti: j721e-csi2rx: " Rishikesh Donadkar
2025-12-01 13:03   ` Tomi Valkeinen
2025-12-09 10:08     ` Rishikesh Donadkar
2025-12-09 10:36       ` Jai Luthra
2025-12-09 11:52         ` Tomi Valkeinen
2025-12-09 12:06           ` Jai Luthra [this message]
2025-11-12 11:54 ` [PATCH v8 14/18] media: ti: j721e-csi2rx: Submit all available buffers Rishikesh Donadkar
2025-11-12 11:54 ` [PATCH v8 15/18] media: ti: j721e-csi2rx: Change the drain architecture for multistream Rishikesh Donadkar
2025-11-12 11:54 ` [PATCH v8 16/18] media: cadence: csi2rx: Support runtime PM Rishikesh Donadkar
2025-12-01 13:11   ` Tomi Valkeinen
2025-12-18  5:35     ` Rishikesh Donadkar
2025-11-12 11:54 ` [PATCH v8 17/18] media: ti: j721e-csi2rx: Support runtime suspend Rishikesh Donadkar
2025-11-20 13:16   ` Sakari Ailus
2025-12-08  7:47     ` Jai Luthra
2025-12-08  9:39       ` Sakari Ailus
2025-12-01 13:22   ` Tomi Valkeinen
2025-12-08  7:36     ` Jai Luthra
2025-12-29 10:07       ` Rishikesh Donadkar
2025-11-12 11:54 ` [PATCH v8 18/18] media: ti: j721e-csi2rx: Support system suspend using pm_notifier Rishikesh Donadkar
2025-12-01 13:46   ` Tomi Valkeinen
2025-12-08  8:01     ` Jai Luthra

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=176528199956.20066.17866034505160159556@freya \
    --to=jai.luthra@ideasonboard.com \
    --cc=changhuang.liang@starfivetech.com \
    --cc=conor+dt@kernel.org \
    --cc=dan.carpenter@linaro.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@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=tomi.valkeinen@ideasonboard.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