From: Sakari Ailus <sakari.ailus@iki.fi>
To: Sowjanya Komatineni <skomatineni@nvidia.com>
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 16:50:13 +0200 [thread overview]
Message-ID: <20201029145013.GA6899@valkosipuli.retiisi.org.uk> (raw)
In-Reply-To: <e253fee3-5358-aaf1-d317-162dc8e98afc@nvidia.com>
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.
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2020-10-29 14:50 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 [this message]
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
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=20201029145013.GA6899@valkosipuli.retiisi.org.uk \
--to=sakari.ailus@iki.fi \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=skomatineni@nvidia.com \
--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