This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DS90UB953-Q1: two camera sync mode for DS90UB953/DS90UB954

Part Number: DS90UB953-Q1

Dear Sir,

I know 953/954 support two cameras inputs and combine them into one CSI2 stream. left-right or interlace.

I have some questions to be confirmed:

1: both of cameras are same, 1920*1080, 2 data lanes,720Mbps (360Mhz)  mipi clock. I want to know , does 954 can support 4 date lanes while image sensor is with 2 date lanes? if yes, 954 clock is 720Mbps ,is it right?

2: I had seen some questions on  pixel resolution and frame frequency for 953 and 954, it seems no any limit , but data throughput should be under the spec, e.g 4.16Gbs(26Mhz*160).

but I want to confirm:

if two image sensors works at sync mode , whatever the output format, left-right or interlace , it need internal line buffer for merging in 954 chip set, the size of line buffer is related with resolution, for example.

1920 *1080, raw 10, one line buffer size is 1920*10/8 = 2400 Bytes, maybe two line buffers are needed for merging operation.

so , is it no any limit for resolution for this scenario?

3. Also this scenario, a frame sync is from 954, there is about 600us jitters . my image sensors support  external frame sync, but only one pulse is needed to trigger  them, do not need continuous external sync wave(e.g.  30Hz or 60 Hz ), so no jitters between frames.

So, I want to know,  is it  okay  if I just out one pulse to trigger these two sensors?  can 954 merging operation  work at this case( I don't know whether 954 internal merging logical need this sync edge or not)? 

Best regards.

Ben

  • Hi Decai,
    1. Yes, ub954 support diff. CSI2 lanes number. but the csi2 lane rate is fixed at ~800MHz or half.
    2. UB954 has no internal image merging function, but it can support interlacing forwarding mode with diff. sync. modes mentioned in MIPI 2.0.
    3. If has large variation, you can use the async. mode in the UB954 output. in general it has NO 600us frame sync. variation from the UB954 to UB954.

    best regards,
    Steven
  • Dear Steven,

    The comments are below:

    1. Does 954 lane rate vary automatically when image sensor data rate changes?
    2. two 1920*1080 image sensors, as for left-right format, the output resolution is 3840*1080, as for interlace format, the output resolution is 1920*2160, is it right?

    Best regards.

    Ben
  • Dear Steven,

    Can you give me some advice about these two questions?

    Best regards,

    Ben

  • Ben,
    1. Does 954 lane rate vary automatically when image sensor data rate changes?
    -> not. please check the d/s, the ub954 lane rate is fixed and configured in register.

    2. two 1920*1080 image sensors, as for left-right format, the output resolution is 3840*1080, as for interlace format, the output resolution is 1920*2160, is it right?
    -> ub954 provide the physical channel to pass the two 1920x1080 image, and the SoC linked with UB954 can get all these data from UB954 and can replicate the 3840x1080 image in combination of VC0 (for left camera sensor) and VC1 (for right camera sensor)

    best regards,
    Steven
  • Please confirm my concern.
  • Dear Steven,

    It seems 954 can combine two camera videos with two methods:   1, use different VC , this mode is for different resolutions , 2 if both of two cameras have the same resolution, 954 can combine them into L-R  or interleave stream,please see the attached pictures, from 954 ds.

    So ,I want to make sure these two modes are supported?

    Thanks!

  • It is clearly described in d/s as you mentioned.
    Please be noted that UB954 just is on PHY chip, any data from FPD-Link can be forwarded into the CSI2 output based on diff. format.
    so if the input in your application has left and right video, UB954 can forward these two videos into CSI2 based on sync. mode (diff. formats) and async mode (VC identifier).

    Best regards,
    Steven
  • You can say combine if you like. but for UB954, as I mentioned, it is on PHY chip, forwarding anything from FPD-Link based on sync formats (diff. modes in d/s) or async mode (can forward multi-streams based on virtual channel). in the processor side, it can receive these signals and combine into one video if you like.
    so I would like to say "combine" in the processor side NOT in UB954 side. but UB954 can do what you want.

    best regards,
    Steven
  • Dear Steven,

    I will be focus on sync mode with L_R mode or interleave mode, because my camera ISP doesn't support multi VC mode.  if 954 can output L_R or Interleave image with same VC ID, it can be forwarded to my ISP processor. of course, my ISP can separate A  or B camera video stream  from L-R or interleave stream. 

    I don't  understand the following comments you said:

    "so I would like to say "combine" in the processor side NOT in UB954 side. but UB954 can do what you want"

    In both of L_R mode and Interleave mode, two cameras must be synchronized by 954 (with same behaviors, e.g, resolution and frame sync ),and only one package header qualifier (A camera) is used.

    As shown in previous L_R and Interleave mode pictures, It can be treated as ONE CAMERA VIDEO output, back-end processor is responsible to  separate them from this ONE CAMERA VIDEO, according to its sync mode. is it right?

    Thanks.

  • You can think so. sync. mode is used for NO VC identification.


    best regards,
    Steven