All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petko Manolov <petko.manolov@konsulko.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Jacopo Mondi <jacopo@jmondi.org>,
	linux-media@vger.kernel.org,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Xavier Roumegue <xavier.roumegue@oss.nxp.com>
Subject: Re: Re: imx8m-mini csi-2 limitations
Date: Thu, 18 Aug 2022 18:44:19 +0300	[thread overview]
Message-ID: <Yv5eU57/Yxy8JqLZ@p310.k.g> (raw)
In-Reply-To: <6573133.31r3eYUQgx@steina-w>

On 22-08-18 14:41:18, Alexander Stein wrote:
> Hi Petko,

Hi Alexander,

<snip>

> While it does not exactly answer your question, the i.MX8M Mini Datasheet 
> (both for Commercial and Industrial) mentions "four-lane MIPI camera serial 
> interfaces, which operates up to a maximum bit rate of 1.5 Gbps". I would 
> assume the bridge is capable of handling the full link speed on four lanes, 
> otherwise this would be quite useless.

Ahem, if that the case (useless), it won't be a first.

In theory the d-phy should support 2.5gbps, but in practice it is only 1.5gbps.  
If CSIS to CSI (bridge) can't be made to transfer 16bit words for 12 bit raw 
format and if the frequency between both can go up to 500mhz, this leaves us 
with 4gbps (8bit x 500mhz) max bandwidth.

If the above calculation is correct, this leaves us with only one option - limit 
the speed of the camera sensor.


cheers,
Petko

  reply	other threads:[~2022-08-18 15:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 13:52 imx8m-mini csi-2 limitations Petko Manolov
2022-08-18  9:27 ` Petko Manolov
2022-08-18 10:51   ` Jacopo Mondi
2022-08-18 12:41     ` Alexander Stein
2022-08-18 15:44       ` Petko Manolov [this message]
2022-08-18 15:37     ` Petko Manolov
2022-08-18 22:38       ` Laurent Pinchart
2022-09-01 15:20     ` Petko Manolov

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=Yv5eU57/Yxy8JqLZ@p310.k.g \
    --to=petko.manolov@konsulko.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=jacopo@jmondi.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=xavier.roumegue@oss.nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.