Linux Media Controller development
 help / color / mirror / Atom feed
From: Sowjanya Komatineni <skomatineni@nvidia.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	Thierry Reding <treding@nvidia.com>,
	<linux-media@vger.kernel.org>
Subject: Re: Suggestion regarding x8 gang mode device tree changes
Date: Thu, 29 Oct 2020 10:07:42 -0700	[thread overview]
Message-ID: <542bbb61-049e-85d8-c2d7-9f38e6625b3d@nvidia.com> (raw)
In-Reply-To: <20201029165245.GB6899@valkosipuli.retiisi.org.uk>


On 10/29/20 9:52 AM, Sakari Ailus wrote:
> On Thu, Oct 29, 2020 at 09:49:57AM -0700, Sowjanya Komatineni wrote:
>> On 10/29/20 8:36 AM, Sowjanya Komatineni wrote:
>>> On 10/29/20 7:50 AM, Sakari Ailus wrote:
>>>> Hi Sowjanya,
>>>>
>>>> On Wed, Oct 28, 2020 at 06:48:59PM -0700, Sowjanya Komatineni wrote:
>>>>> Hi Sakari,
>>>>>
>>>>> Missed to add you to below patch series for HDMI2CSI bridge support
>>>>>
>>>>> https://patchwork.kernel.org/project/linux-media/cover/1603768763-25590-1-git-send-email-skomatineni@nvidia.com/
>>>>>
>>>>>
>>>>> Patch-10 of this series is for x8 capture from HDMI2CSI bridge.
>>>>>
>>>>> Would like to get your suggestion on x8 gang/combined ports capture
>>>>> implementation.
>>>> The majority of CSI-2 receiver devices support partitioning the
>>>> lanes among
>>>> different PHYs in various ways. They do support usually up to four
>>>> lanes,
>>>> but adding four more lanes is not a reason for making the API different.
>>>>
>>>> So instead, you should implement this as a single port that simply has 8
>>>> lanes.
>>>>
>>> Thanks Sakari for your reply.
>>>
>>> current v2 series treats as 8 lanes. You mean to not expose 2nd port in
>>> device tree as VI/CSI side takes care of 2nd port as combined to treat
>>> as 8 lane?
> Correct.
>
> Although you can have the second port connected if fewer lanes are assigned
> to the first one.
>
> How does it work for this device, are the lanes statically allocated to
> ports, apart from the special 8 lane mode?

Tegra CSI each port supports max 4 lanes. For x8, 2 x4 ports together 
are programmed for simultaneous streaming during the same video/subdev 
stream ops.

Physically, CSI RX side 4 lanes goes to x4 port and other 4 lanes goes 
to another x4 port.

HDMI Bridge TX0 -> CSI RX0 (x4 port)

HDMI Bridge TX1 -> CSI RX1 (x4 port)

HDMI bridge side single image is split into 2 x4 ports and on RX side 
image from both ports are captured simultaneously with buffer offsets 
adjusted side-by-side to get combined image for same video buf of video 
device.

Both these 2 x4 ports together are used for streaming by Tegra VI and 
buffer offsets are adjusted side by side for these ports and for video 
device node stream, its single buffer which contains combined image from 
capture.

>> AS csi2 bus type supports max 4 data lanes with endpoint parse API.
>>
>> Currently with x8 as single port, I am using bus-width with bus type as
>> parallel in device tree and when using x4 using data-lanes with csi2 bus
>> type and driver gets lanes based on either of this from DT.
>>
>> Instead should we update endpoint parse API for max up to 8 lanes for
>> data-lanes?
> Yes, please. Could you send a patch?
>
> The standard AFAIK supports up to four lanes but as we know, hardware
> sometimes has more than that.

Sure once Hans also agrees with this to have it as single x8 port (just 
like I have now in v2), will send v3 to update endpoint parse to allow 
upto max 8 data-lanes and will also update Tegra CSI driver accordingly 
to retrieve lanes using csi2 bus type.

Hans, Please confirm if you agree with this.


  reply	other threads:[~2020-10-29 17:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e253fee3-5358-aaf1-d317-162dc8e98afc@nvidia.com>
2020-10-29  9:33 ` Suggestion regarding x8 gang mode device tree changes Hans Verkuil
2020-10-29 15:34   ` Sowjanya Komatineni
2020-10-29 14:50 ` Sakari Ailus
2020-10-29 15:36   ` Sowjanya Komatineni
2020-10-29 16:49     ` Sowjanya Komatineni
2020-10-29 16:52       ` Sakari Ailus
2020-10-29 17:07         ` Sowjanya Komatineni [this message]
2020-10-30  9:31           ` Hans Verkuil
2020-10-30  9:56             ` Sakari Ailus
2020-10-30 10:06               ` Hans Verkuil
2020-10-30 15:26                 ` Sowjanya Komatineni
2020-10-30 16:50                   ` Sowjanya Komatineni
2020-10-30 22:31                 ` Sakari Ailus
2020-10-31  9:57                   ` Hans Verkuil

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=542bbb61-049e-85d8-c2d7-9f38e6625b3d@nvidia.com \
    --to=skomatineni@nvidia.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@iki.fi \
    --cc=treding@nvidia.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