mipi rx0通过serdes接入两个800M 的ovx8b摄像头，出现丢帧问题

上传了配置文件,在压缩文件 ovx8b_config.zip 。该Des和nvidia平台mipi dphy接口对接，速率可以达到2.4G。 nvidia平台 在dphy速率超过1.5G后，需要使用deskew功能。不知道J5平台是否支持

"deserial_0":{ "deserial_name":"max9296", "deserial_addr":"0x6f", "bus_type":0, "bus_num":1, "power_mode":0, "gpio_pin":[453,309], "lane_speed":2500, "gpio_level":[0,0] },

加一个这个 "lane_speed":2500

lane speed 配置的是对的。发现解串器发送deskew消息，地平线soc的dphy芯片会有下面的报错信息。 地平线的dphy芯片对deskew消息有什么要求吗，譬如initial calibration，校准长度之类的。
vps mipi_host0: irq status 0x500bf vps mipi_host0: phy_fatal: 0xf vps mipi_host0: pkt_fatal: 0x1 vps mipi_host0: bndry_frm_fatal: 0x5 vps mipi_host0: seq_frm_fatal: 0x1 vps mipi_host0: crc_frm_fatal: 0x1 vps mipi_host0: pld_crc_fatal: 0x1 vps mipi_host0: ecc_corrected: 0x5 vps mipi_host0: phy: 0x2 vps mipi_host0: ipi: 0x2 vps mipi_host0: irq status 0x500bf vps mipi_host0: phy_fatal: 0xf vps mipi_host0: pkt_fatal: 0x1 vps mipi_host0: bndry_frm_fatal: 0x5 vps mipi_host0: seq_frm_fatal: 0x1 vps mipi_host0: crc_frm_fatal: 0x1 vps mipi_host0: pld_crc_fatal: 0x1 vps mipi_host0: ecc_corrected: 0x5 vps mipi_host0: phy: 0x2 vps mipi_host0: ipi: 0x2 --> reset [S0] vio_push_drop_info frame id 114 cim_set_mipi_ipi_reset: mipi rx0 vc_mask 0x1 vps mipi_host0 stl: int fatal 1(phy_fatal):0xf error vps mipi_host0 stl: event 10:0xf01 code=152 ignored vps mipi_host0 stl: event 10:0x102 code=152 ignored vps mipi_host0: irq status 0x500a2 vps mipi_host0 stl: event 10:0x504 code=152 ignored vps mipi_host0: pkt_fatal: 0x1 vps mipi_host0 stl: event 10:0x105 code=152 ignored vps mipi_host0: pld_crc_fatal: 0x1 vps mipi_host0: ecc_corrected: 0x1 vps mipi_host0 stl: event 10:0x106 code=152 ignored vps mipi_host0: phy: 0x2 vps mipi_host0 stl: event 10:0x107 code=152 ignored vps mipi_host0: ipi: 0x2 reset [S0] vio_push_drop_info frame id 114 cim_set_mipi_ipi_reset: mipi rx0 vc_mask 0x1 vps mipi_host0 stl: int fatal 1(phy_fatal):0xf error vps mipi_host0 stl: event 10:0xf01 code=152 ignored vps mipi_host0 stl: event 10:0x102 code=152 ignored vps mipi_host0: irq status 0x500a2 vps mipi_host0 stl: event 10:0x504 code=152 ignored vps mipi_host0: pkt_fatal: 0x1 vps mipi_host0 stl: event 10:0x105 code=152 ignored vps mipi_host0: pld_crc_fatal: 0x1 vps mipi_host0: ecc_corrected: 0x1 vps mipi_host0 stl: event 10:0x106 code=152 ignored vps mipi_host0: phy: 0x2 vps mipi_host0 stl: event 10:0x107 code=152 ignored vps mipi_host0: ipi: 0x2 --> reset cim_set_mipi_ipi_reset: mipi rx0 vc_mask 0x1

[ 1543.357384] cim_set_mipi_ipi_reset: mipi rx0 vc_mask 0x1 [ 1543.357383] vps mipi_host0 stl: event 10:0x509 code=152 ignored [ 1543.357392] vps mipi_host0 stl: event 10:0x20a code=152 ignored [ 1543.357400] vps mipi_host0 stl: event 10:0x20d code=152 ignored [ 1543.357405] [fchm_ncf_irq_handler, 105]NON-Critical error happened, module_name:mipihost0, ncf = 152! [ 1543.422191] [A][time_1 :946686341 s, 946808 us], ncf = 204! [ 1543.422201] cim ipi0 height error [ 1543.422211] [S0] vio_push_drop_info frame id 115 [ 1543.422239] [CIM stl]:cim_size_err_check ipi0 size error

不好意思，前面跑错用例了。现在是配置了 "lane_speed":2500 ，配置了2个camera。但是我在logcat中没有看到lane_speed 的打印，不知道怎么看lane_speed是否生效了。或者内核代码是哪个文件，我看下代码

"power_mode":0, "gpio_pin":[453,309], "lane_speed":2500, "gpio_level":[0,0]

哦，那log中怎么看是否是生效呢。hal上层解析是通过脚本解析的吗。
我执行的命令如下，不知道会不会解析lane_speed
sh vio_test_case.sh quad2_sen_cim_isp0_pym0_4k_ovx8b_test

vio_test_case.sh 文件中的命令是

elif test "$1" == "quad2_sen_cim_isp0_pym0_4k_ovx8b_test"; then echo "========= Run $1" ${COMMON_DIR}vpm_gtest -v "/userdata/app/bin/vps/vpm/cfg/quad2_sen_cim_isp0_pym0_4k_ovx8b_test/vpm_config.json" -e 0 -r 1000 -S 1 -c "/userdata/app/bin/vps/vpm/cfg/quad2_sen_cim_isp0_pym0_4k_ovx8b_test/hb_j5dev.json" -M 3\ -x ${cam_rstart} -X ${vio_rstart} \ --gtest_filter=VpmScenarioTest.multi_streams_pym \ # --gtest_output=xml:${OUTPUT_DIR_PREFIX}output/vps_$1_test_result.xml

[4787.585449][VIN]:[hb_vin_board_parse_cfg][738]deserial_num = 1 I/ ( 2120): [4787.585449][VIN]:[hb_vin_deserial_parse_cfg][262]deserial_index 0 bus_type = 0 I/ ( 2120): [4787.585449][VIN]:[hb_vin_deserial_parse_cfg][267]deserial_index 0 bus_num = 1 I/ ( 2120): [4787.585449][VIN]:[hb_vin_deserial_parse_cfg][278]deserial_index 0 serial_addr = 0x6f I/ ( 2120):
[4787.585449][VIN]:[hb_vin_deserial_parse_cfg][283]deserial_index 0 deserial_name = artemis I/ ( 2120):
[4787.585449][VIN]:[hb_vin_deserial_parse_cfg][299]deserial_index 0 power_mode = 0 I/ ( 2120):
[4787.585449][VIN]:[hb_vin_deserial_parse_cfg][310]array_index 0 gpio_pin 453 I/ ( 2120): [4787.585449][VIN]:[hb_vin_deserial_parse_cfg][310]array_index 1 gpio_pin 309 I/ ( 2120): [4787.585449][VIN]:[hb_vin_deserial_parse_cfg][322]deserial_index 0 array_index 0 gpio_level 0 I/ ( 2120):
[4787.585449][VIN]:[hb_vin_deserial_parse_cfg][322]deserial_index 0 array_index 1 gpio_level 0
你就找着一段，有lane speed的打印就说明是加上了吧，没有就通过日志的json看下是不是改对了文件

hb_vin_deserial_parse_cfg 这个函数中没有解析 lane speed ，即使 json 文件配置了 lane speed ，也不会有打印的和起作用的。下面是这个函数的截图

我只在mlx5_ifc.h搜到下面两处和 lane_speed 相关的变量，但是没有在C文件使用，只是定义了变量。你能看下你的内核代码中哪里对 lane_speed 进行了赋值。会不会我们的版本不一样。我的版本是 立昇智能科技提供的J5 SOM EDK

struct mlx5_ifc_plpc_reg_bits {
u8 reserved_at_0[0x4];
u8 profile_id[0xc];
u8 reserved_at_10[0x4];
u8 proto_mask[0x4];
u8 reserved_at_18[0x8];
u8 reserved_at_20[0x10];
u8 lane_speed[0x10];



struct mlx5_ifc_slrg_reg_bits {
u8 status[0x4];
u8 version[0x4];
u8 local_port[0x8];
u8 pnat[0x2];
u8 reserved_at_12[0x2];
u8 lane[0x4];
u8 reserved_at_18[0x8];
u8 time_to_link_up[0x10];
u8 reserved_at_30[0xc];
u8 grade_lane_speed[0x4];

node = CJSON_GetObjectItem(deserial_node, "lane_speeed");if(NULL != node) {g_board_cfg.deserial_info[deserial_index].lane_speed == (uint32_t)node->valueint;vin_dbg("deserial_index %d lane_speed = %d\n", deserrial_index,g_board_cfg.deserial_info[deserial_index].lane_speed); /* PRQA S ALL */ /* print api */nodecJSON_GetObjectItem(deserial_node, "deserial_name")

没有这个？

没有 lane_speed 代码， 如下的代码截图，deserial_name 之前解析的是 deserial_addr。你这个代码版本是多少？我能够从立昇那里获取到吗？