mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Kieran Bingham <kieran.bingham@ideasonboard.com>,
	Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org,
	Biju Das <biju.das.jz@bp.renesas.com>,
	Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
	Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [RFC PATCH 00/12] media: ov5645: Add support for streams
Date: Thu, 5 Sep 2024 13:57:36 +0300	[thread overview]
Message-ID: <1eead6a9-87c7-409d-abd6-32c4d0dafe05@ideasonboard.com> (raw)
In-Reply-To: <CA+V-a8svfVrjEjYbSko4eh6z_9kEkfwMHr0YHwaxEPWLKJBPyg@mail.gmail.com>

On 05/09/2024 13:51, Lad, Prabhakar wrote:
> Hi Tomi,
> 
> On Thu, Sep 5, 2024 at 11:29 AM Tomi Valkeinen
> <tomi.valkeinen@ideasonboard.com> wrote:
>>
>> On 05/09/2024 13:27, Lad, Prabhakar wrote:
>>> Hi Tomi,
>>>
>>> On Thu, Sep 5, 2024 at 10:11 AM Tomi Valkeinen
>>> <tomi.valkeinen@ideasonboard.com> wrote:
>>>>
>>> <snip>
>>>>> I think you actually want 1/0->0/0 routing. The error says that the sink
>>>>> side device has routing which does not have a stream at stream ID 1, or
>>>>> no routing support at all, which implies a single stream at stream ID 0.
>>>>
>>>> Looking at patch 12, there's something wrong with the approach here. Are
>>>> you perhaps trying to define the CSI-2 VC with the streams?
>>>>
>>> Yes, based on the previous feedback received, I am implementing
>>> virtual channels as streams. If this isn't the correct approach can
>>> you please guide me on what we should be using to support virtual
>>> channels?
>>
>> Can you describe what kind of hardware you have and how the VCs are
>> supposed to be configured and used there?
>>
> 
>   __________________                       ______________
>      _____________________
> |                                     |                     |
>                  |                   |
>        |
> | OV5645   Sensor        |                     |  RZ/G2L CSI2   |
>               |  RZ/G2L CRU                 |
> | 1ch out of 4x VC         |---------------> |   4x VC
> |-------------->|  1Ch capture out 4xVC  |
> |__________________|                      |_____________|
>       |____________________|

The formatting there is quite broken, but afaiu you have a standard 
setup with single stream. Then it should be as I wrote earlier: a single 
hardcoded 1/0->0/0 route in the sensor, and .get_frame_desc() returns VC 
0 and a suitable DT for that stream.

When you say "implementing virtual channels as streams", what is the 
feature/requirement you are looking at? Do you have some specific need 
to use other VCs than 0?

  Tomi


  reply	other threads:[~2024-09-05 10:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04 21:07 Prabhakar
2024-09-04 21:07 ` [RFC PATCH 01/12] media: i2c: ov5645: Add V4L2_SUBDEV_FL_HAS_EVENTS and subscribe hooks Prabhakar
2024-09-04 21:07 ` [RFC PATCH 02/12] media: i2c: ov5645: Use local `dev` pointer for subdev device assignment Prabhakar
2024-09-04 21:07 ` [RFC PATCH 03/12] media: i2c: ov5645: Enable runtime PM after v4l2_async_register_subdev() Prabhakar
2024-09-04 21:07 ` [RFC PATCH 04/12] media: i2c: ov5645: Use dev_err_probe instead of dev_err Prabhakar
2024-09-04 21:07 ` [RFC PATCH 05/12] media: i2c: ov5645: Use v4l2_async_register_subdev_sensor() Prabhakar
2024-09-04 21:07 ` [RFC PATCH 06/12] media: i2c: ov5645: Drop `power_lock` mutex Prabhakar
2024-09-04 21:07 ` [RFC PATCH 07/12] media: i2c: ov5645: Use subdev active state Prabhakar
2024-09-04 21:07 ` [RFC PATCH 08/12] media: i2c: ov5645: Switch to {enable,disable}_streams Prabhakar
2024-09-04 21:07 ` [RFC PATCH 09/12] media: i2c: ov5645: Add internal image sink pad Prabhakar
2024-09-04 21:07 ` [RFC PATCH 10/12] media: i2c: ov5645: Report internal routes to userspace Prabhakar
2024-09-04 21:07 ` [RFC PATCH 11/12] media: i2c: ov5645: Report streams using frame descriptors Prabhakar
2024-09-04 21:07 ` [RFC PATCH 12/12] media: i2c: ov5645: Add virtual channel support Prabhakar
2024-09-05  6:48 ` [RFC PATCH 00/12] media: ov5645: Add support for streams Tomi Valkeinen
2024-09-05  9:11   ` Tomi Valkeinen
2024-09-05 10:27     ` Lad, Prabhakar
2024-09-05 10:29       ` Tomi Valkeinen
2024-09-05 10:51         ` Lad, Prabhakar
2024-09-05 10:57           ` Tomi Valkeinen [this message]
2024-09-05  9:11   ` Lad, Prabhakar

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=1eead6a9-87c7-409d-abd6-32c4d0dafe05@ideasonboard.com \
    --to=tomi.valkeinen@ideasonboard.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=fabrizio.castro.jz@renesas.com \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=prabhakar.csengg@gmail.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=sakari.ailus@linux.intel.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

all inboxes | Powered by JetHome®