Same unique name in nvargus_nvraw

[chester.tseng]

I’m trying to port Leopard AR0233 RAW GMSL2 camera to Jetpack5 with L4T 35.1. Then I came across a tool nvargus_nvraw to check driver is workable or not. However, when I dump all camera’s info by the following command:

$> nvargus_nvraw --lps
nvargus_nvraw version 1.13.1
Number of supported sensor entries 8
Entry  Source Mode      Uniquename             Resolution   FR  BitDepth  Mode
Index  Index  Index                                             CSI Dyn   Type
  0      0      0        ar0233_rear_liar0233   2048x1280   29  12  12    Bayer       
  1      1      0        ar0233_rear_liar0233   2048x1280   29  12  12    Bayer       
  2      2      0        ar0233_rear_liar0233   2048x1280   29  12  12    Bayer       
  3      3      0        ar0233_rear_liar0233   2048x1280   29  12  12    Bayer       
  4      4      0        ar0233_rear_liar0233   2048x1280   29  12  12    Bayer       
  5      5      0        ar0233_rear_liar0233   2048x1280   29  12  12    Bayer       
  6      6      0        ar0233_rear_liar0233   2048x1280   29  12  12    Bayer       
  7      7      0        ar0233_rear_liar0233   2048x1280   29  12  12    Bayer 

All 8 cameras shows the same uniquename. (ar0233_rear_liar0233)

I guess this slot is acquired by the device tree (tegra-camera-platform node):

/ {
  tegra-camera-platform {
    modules {
      module0 {
        ...
        badge = "ar0233_rear_liar0233";
        ...
      };
      module1 {
        ...
        badge = "ar0233_front_liar0233";
        ...
      };
      ...
    };
  };
};

However, I double check my dts settings are set correctly.

$> cat /proc/device-tree/tegra-camera-platform/modules/module*/badge
ar0233_rear_liar0233
ar0233_front_liar0233
ar0233_topright_liar0233
ar0233_bottomright_liar0233
ar0233_topleft_liar0233
ar0233_centerright_liar0233
ar0233_centerleft_liar0233
ar0233_bottomleft_liar0233

Is this problem is caused by nvargus_nvraw it self ?

[ShaneCCC]

It’s known issue, please ignore it.