Derived from Prophesee linux-sensor-drivers genx320.c + inner driver.

Key call chain:

  genx320_power_on

    → genx320_check_boot    (read 0xF010, expect 0xCAFEBABE)

    → genx320_init

        → genx320_configure_mipi  (0xB000, 0xB010, 0xB024, SRAM)011

        → genx320_apply_format    (0x7044 = EVT21, 0x7000 enable)

        → genx320_tune_analog     (bgen_ctrl + 12 bias registers)

  genx320_start_streaming

    → mipi_csi_ctrl enable (0xB000 bit0)

    → ro_lp_ctrl disable (0x9028 bit1 = 0)

    → ro_time_base_ctrl enable (0x9008 bit0)

    → genx320_start_pixel_array

        → ro_readout_ctrl digital_pipe_en (0x9000 bit9)

        → ro_td_ctrl release 4 resets (0x002C)

        → roi_ctrl px_sw_rstn + roi_td_en (0x0000)

  genx320_roi_window_init (called from genx320_init, MISSING before)

        → roi_master_chicken_bit driver_if_en=0 (0x0044)

        → roi_ctrl td_en+sw_rstn (0x0000)

        → roi_master_ctrl master_en=1 (0x0034)

        → roi_win_array[0] x: 0→320 (0x0400)

        → roi_win_array[0] y: 0→320 (0x0404)

        → roi_master_ctrl run 1 window (0x0034)

Register addresses from genx320_registers.h (all 32-bit aligned).

However, the Sensor doesn't seem to be booting up correctly and the values are not as specified in the Linux drivers repository.
In fact, the camera seems to return these values:
CHIP_ID (0x0014): 0x01617f7f instead of 0xB0602003
BOOT_MAGIC (0xF010): 0x1157f7f instead of 0xCAFEBABE
MIPI_CSI_CTRL(0xB000) reads back 0x00217f7f instead of 0x1000C001, the value which originally wrote in.

I imagine I did something wrong and would appreciate help on how to approach this problem. 
Kind regards,

Hisham