# SERDES camera streaming

**URL:** <https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533>\
**Category:** Jetson Xavier NX\
**Tags:** device-tree, board-design, camera\
**Created:** [May 26, 2023, 9:28am UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533 "2023-05-26T09:28:12Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![sujit.kumar](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sujit.kumar](https://forums.developer.nvidia.com/u/sujit.kumar)\
**Post date:** [May 26, 2023, 9:28am UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/1 "2023-05-26T09:28:12Z")

</div>

[tegra194-p3509-0000-camera-onsemi-sensor-driver-a00.dtsi](https://forums.developer.nvidia.com/uploads/short-url/1PUD33VivEnC1XHNu3HbmLl26h6.dtsi) (1.7 KB)  
[tegra194-p3509-camera-onsemi-sensor-driver.dtsi](https://forums.developer.nvidia.com/uploads/short-url/gE9LaGzl9gm3GNJaSVxksujS7RX.dtsi) (3.6 KB)  
Hi,

I have my own custom board, I am able to bring up camera (streaming as expected) via our heardboard. I am able to add two entry and both are streaming as per my requirement with /dev/video0 and /dev/video1

Now I want to bringup SERDES, I have mounted MAX9296 Deserializer as this driver is supported by NX kernel (I am refering IMX390). My serdes is setting on I2C bus-1 and I can see i2c detecting 0x6C (MAX9296 ), 0x62 (MAX9295 ) and 0x10 AR0233 on same I2C bus-1.  
I have requiremnt of using headboard and serdes camera together, I have created 2 driver, one w/o SERDES setup and one with SERDES setup (as recomended by IMX390) And last I have added DTSI entry for dser/ser. But when boots up I dont see any /dev/video0 and /dev/video1; as well not seeing sensor I2C on bus-1.

Could you help me to understand what configuration I am missing for all video node creation and configuring proper mipi lane for serdes? I have attached my dtsi for your reference.

Below is the schematic which connect Jetson NX to our headboard and DSER.

 ![image](https://global.discourse-cdn.com/nvidia/original/3X/e/c/ecafae6f45628285be947ce0a57d6f0cb00a6327.png)

Kernel Log:  
6.984052] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1  
[6.991198] usb usb2: Product: xHCI Host Controller  
[6.995845] usb usb2: Manufacturer: Linux 5.10.104-tegra xhci-hcd  
[7.001888] usb usb2: SerialNumber: 3610000.xhci  
[7.007088] hub 2-0:1.0: USB hub found  
[7.010420] hub 2-0:1.0: 4 ports detected  
[7.016684] onsemi\_serdes\_driver 1-0010: found reset gpio  
[7.019983] onsemi\_serdes\_driver 1-0010: tegracam sensor driver:onsemi\_serdes\_driver\_v2.0.6  
[7.054392] max9296 1-006c: max9296\_write\_reg:i2c write failed, 0x10 = 1  
[7.055061] max9296 1-006c: max9296\_write\_reg:i2c write failed, 0x10 = 21  
[7.162374] max9295 1-0062: max9295\_write\_reg:i2c write failed, 0x0 = c4  
[7.163036] max9295 1-0062: max9295\_write\_reg:i2c write failed, 0x10 = 21  
[7.163320] max9295 1-0062: max9295\_setup\_control: ERROR: ser device not found  
[7.163485] onsemi\_serdes\_driver 1-0010: gmsl serializer setup failed  
[7.163967] max9296 1-006c: max9296\_write\_reg:i2c write failed, 0x332 = f0  
[7.164249] onsemi\_serdes\_driver 1-0010: onsemi\_serdes\_probe gmsl serdes setup failed  
[7.164497] onsemi\_serdes\_driver: probe of 1-0010 failed with error -121  
[7.165351] irq: IRQ273: trimming hierarchy from :pmc@c360000  
[7.165675] OF: graph: no port node found in /i2c@31e0000/typec-portc@22  
[7.166090] OF: graph: no port node found in /i2c@31e0000/typec-portc@22/connector  
[7.166293] OF: graph: no port node found in /i2c@31e0000/typec-portc@22/connector  
[7.176732] typec\_fusb302 8-0022: name: 8-0022 FUSB302 probe successful  
[7.178201] tegradc 15210000.display: disp1 connected to head1-\>sor  
[7.178429] tegradc 15210000.display: parse\_dp\_settings: No dp-lt-settings node  
[7.178701] tegradc 15210000.display: DT parsed successfully  
[7.178922] tegradc 15210000.display: Display dc.( **ptrval** ) registered with id=1  
[7.179053] nvethernet 2490000.ethernet: Adding to iommu group 28  
[7.181418] tegradc 15210000.display: vblank syncpt # 13 for dc 1  
[7.188085] nvethernet 2490000.ethernet: failed to read skip mac reset flag, default 0  
[7.193849] tegradc 15210000.display: vpulse3 syncpt # 14 for dc 1

[tegra194-camera-onsemi-sensor-driver-a00.dtsi](https://forums.developer.nvidia.com/uploads/short-url/3W5DTV0EZEvAcUVDIcdmOxx0ue1.dtsi) (9.5 KB)

---

<div class="post-metadata">

**Author:** ![ShaneCCC](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/shaneccc/32/14043_2.png) [@ShaneCCC](https://forums.developer.nvidia.com/u/ShaneCCC)\
**Post date:** [May 29, 2023, 5:10am UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/3 "2023-05-29T05:10:24Z")

</div>

Looks like HW problem to detect max929x

---

<div class="post-metadata">

**Author:** ![sujit.kumar](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sujit.kumar](https://forums.developer.nvidia.com/u/sujit.kumar)\
**Post date:** [May 31, 2023, 2:50pm UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/4 "2023-05-31T14:50:51Z")

</div>

Hi,

After comminting one GPIO I am able to detect max9296 as well 9295.

Can you help me to understand below log " **invalid GPIO -2**":  
------------[cut here]------------  
[6.994651] tegradc 15210000.display: vpulse3 syncpt # 14 for dc 1  
[7.002460] tegradc 15210000.display: probed  
[7.005592] invalid GPIO -2  
[7.005657] WARNING: CPU: 2 PID: 106 at drivers/gpio/gpiolib.c:122 gpio\_to\_desc+0xb4/0x100  
[7.052039] Modules linked in:  
[7.052077] CPU: 2 PID: 106 Comm: kworker/2:3 Not tainted 5.10.104-tegra #18  
[7.054930] tegradc 15210000.display: fb registered  
[7.062269] Hardware name: Unknown NVIDIA Jetson Xavier NX Developer Kit/NVIDIA Jetson Xavier NX Developer Kit, BIOS 1.0-d7fb19b 08/10/2022  
[7.062282] Workqueue: events deferred\_probe\_work\_func  
[7.062299] pstate: 60800009 (nZCv daif -PAN +UAO -TCO BTYPE=–)  
[7.062308] pc : gpio\_to\_desc+0xb4/0x100  
[7.070709] hpd: state 7 (Takeover from bootloader), hpd 0, pending\_hpd\_evt 1  
[7.079772] lr : gpio\_to\_desc+0xb4/0x100  
[7.079780] sp : ffff800010b9ba60  
[7.079789] x29: ffff800010b9ba60 x28: ffffbbbef1865380  
[7.084863] hpd: switching from state 7 (Takeover from bootloader) to state 0 (Reset)  
[7.090624] x27: ffff043c402c4cf4 x26: ffff043c44cc2820  
[7.090651] x25: ffffbbbef145e8c8 x24: ffffbbbef145e5c0  
[7.094410] hpd: state 0 (Reset), hpd 0, pending\_hpd\_evt 0

[7.101911] x23: ffffbbbef21e4940 x22: ffff043c44cc2820  
[7.101918] x21: ffffbbbef214f6e8 x20: 00000000fffffffe  
[7.101925] x19: 0000000000000000 x18: 0000000000000001  
[7.156341] x17: 0000000000000007 x16: 0000000000000068  
[7.156350] x15: ffff043c42fbeaf0 x14: ffffffffffffffff  
[7.156357] x13: ffffbbbef2107de8 x12: ffffbbbef2107a16  
[7.156382] tegradc 15210000.display: blank - powerdown  
[7.156403] x11: 0000000000000040 x10: 0000000000000a80  
[7.161883] extcon-disp-state external-connection:disp-state: cable 44 state 0 already set.

[7.167622] x9 : ffff800010b9ba60 x8 : ffff800010b9ba60  
[7.167629] x7 : ffff800010b9ba60 x6 : 000000002d8dd199  
[7.167640] x5 : 000000000000000c  
[7.172973] Extcon DP: HPD disabled  
[7.178136] x4 : 00000000fffff2a7  
[7.183472] hpd: switching from state 0 (Reset) to state 1 (Check Plug)  
[7.191857] x3 : 00000000ffffffff x2 : ffffbbbef1e078e0  
[7.191865] x1 : 0000000000000000 x0 : 0000000000000000  
[7.191873] Call trace:  
[7.191878] gpio\_to\_desc+0xb4/0x100  
[7.191886] max9296\_power\_on+0xbc/0x100  
[7.191890] onsemi\_probe+0x904/0xa20  
[7.191898] i2c\_device\_probe+0xb0/0x2e0  
[7.191927] really\_probe+0xf8/0x3d0  
[7.193437] hpd: state 1 (Check Plug), hpd 0, pending\_hpd\_evt 0  
[7.198514] driver\_probe\_device+0x60/0xc0  
[7.198520] \_\_device\_attach\_driver+0x8c/0xd0  
[7.198525] bus\_for\_each\_drv+0x8c/0xe0  
[7.198550] \_\_device\_attach+0xf8/0x160  
[7.203868] hpd: switching from state 1 (Check Plug) to state 3 (Disabled)  
[7.207433] device\_initial\_probe+0x28/0x40  
[7.207439] bus\_probe\_device+0xa4/0xb0  
[7.207462] deferred\_probe\_work\_func+0x90/0xd0  
[7.207473] process\_one\_work+0x1c4/0x4a0  
[7.298002] worker\_thread+0x200/0x430  
[7.301783] kthread+0x148/0x170  
[7.305091] ret\_from\_fork+0x10/0x24  
[7.308765] —[end trace a8725fff385ba79f]—  
[7.313950] ------------[cut here]------------  
[7.318405] invalid GPIO -2  
[7.321056] WARNING: CPU: 2 PID: 106 at drivers/gpio/gpiolib.c:122 gpio\_to\_desc+0xb4/0x100  
[7.329238] Modules linked in:  
[7.332567] CPU: 2 PID: 106 Comm: kworker/2:3 Tainted: G W 5.10.104-tegra #18  
[7.341045] Hardware name: Unknown NVIDIA Jetson Xavier NX Developer Kit/NVIDIA Jetson Xavier NX Developer Kit, BIOS 1.0-d7fb19b 08/10/2022  
[7.353239] Workqueue: events deferred\_probe\_work\_func  
[7.358641] pstate: 60800009 (nZCv daif -PAN +UAO -TCO BTYPE=–)  
[7.364065] pc : gpio\_to\_desc+0xb4/0x100  
[7.367829] lr : gpio\_to\_desc+0xb4/0x100  
[7.371844] sp : ffff800010b9ba60  
[7.374912] x29: ffff800010b9ba60 x28: ffffbbbef1865380  
[7.380338] x27: ffff043c402c4cf4 x26: ffff043c44cc2820  
[7.386019] x25: ffffbbbef145e8c8 x24: ffffbbbef145e5c0  
[7.391446] x23: ffffbbbef21e4940 x22: ffff043c44cc2820  
[7.396869] x21: ffffbbbef214f6e8 x20: 00000000fffffffe  
[7.402294] x19: 0000000000000000 x18: 0000000000000010  
[7.407632] x17: 0000000000000007 x16: 0000000000000068  
[7.412887] x15: ffff043c42fbeaf0 x14: ffffffffffffffff  
[7.418658] x13: ffff800090b9b707 x12: ffff800010b9b70f  
[7.423912] x11: 0000000000000040 x10: 0000000000000a80  
[7.429595] x9 : ffff800010b9ba60 x8 : 000000000004dbc5  
[7.435109] x7 : ffffbbbef07f1cd0 x6 : c0000000ffffefff  
[7.440619] x5 : 0000000000057fa8 x4 : ffffbbbef1e07968  
[7.445788] x3 : 00000000ffffffff x2 : ffffbbbef1e078e0  
[7.451383] x1 : 0000000000000000 x0 : 0000000000000000  
[7.456735] Call trace:  
[7.459174] gpio\_to\_desc+0xb4/0x100  
[7.462674] max9296\_power\_on+0xcc/0x100  
[7.466628] onsemi\_probe+0x904/0xa20  
[7.470111] i2c\_device\_probe+0xb0/0x2e0  
[7.473874] really\_probe+0xf8/0x3d0  
[7.477548] driver\_probe\_device+0x60/0xc0  
[7.481573] \_\_device\_attach\_driver+0x8c/0xd0  
[7.485876] bus\_for\_each\_drv+0x8c/0xe0  
[7.489623] \_\_device\_attach+0xf8/0x160  
[7.493561] device\_initial\_probe+0x28/0x40  
[7.497342] bus\_probe\_device+0xa4/0xb0  
[7.501348] deferred\_probe\_work\_func+0x90/0xd0  
[7.505640] process\_one\_work+0x1c4/0x4a0  
[7.510099] worker\_thread+0x200/0x430  
[7.513602] kthread+0x148/0x170  
[7.517098] ret\_from\_fork+0x10/0x24  
[7.520773] —[end trace a8725fff385ba7a0]—  
[7.525227] tegra\_cec 3960000.tegra\_cec: Can’t find physical address.  
[7.531643] tegra\_cec 3960000.tegra\_cec: tegra\_cec\_init Done.  
[7.537508] ------------[cut here]------------  
**[7.541900] invalid GPIO -2**  
**[7.544694] WARNING: CPU: 2 PID: 106 at drivers/gpio/gpiolib.c:122 gpio\_to\_desc+0xb4/0x100**  
**[7.553145] Modules linked in:**  
**[7.555960] CPU: 2 PID: 106 Comm: kworker/2:3 Tainted: G W 5.10.104-tegra #18**  
[7.564525] Hardware name: Unknown NVIDIA Jetson Xavier NX Developer Kit/NVIDIA Jetson Xavier NX Developer Kit, BIOS 1.0-d7fb19b 08/10/2022  
[7.576967] Workqueue: events deferred\_probe\_work\_func  
[7.582027] pstate: 60800009 (nZCv daif -PAN +UAO -TCO BTYPE=–)  
[7.587800] pc : gpio\_to\_desc+0xb4/0x100  
[7.591390] lr : gpio\_to\_desc+0xb4/0x100  
[7.595324] sp : ffff800010b9ba60  
[7.598907] x29: ffff800010b9ba60 x28: ffffbbbef1865380  
[7.604178] x27: ffff043c402c4cf4 x26: ffff043c44cc2820  
[7.609846] x25: ffffbbbef145e8c8 x24: ffffbbbef145e5c0  
[7.615012] x23: ffffbbbef21e4940 x22: ffff043c44cc2820  
[7.620694] x21: ffffbbbef214f6e8 x20: 00000000fffffffe  
[7.626119] x19: 0000000000000000 x18: 0000000000000010  
[7.631458] x17: 0000000000000007 x16: 0000000000000068  
[7.636713] x15: ffff043c42fbeaf0 x14: ffffffffffffffff  
[7.642482] x13: ffff800090b9b707 x12: ffff800010b9b70f  
[7.647908] x11: 0000000000000040 x10: 0000000000000a80  
[7.653163] x9 : ffff800010b9ba60 x8 : 00000000000844cc  
[7.658933] x7 : ffffbbbef07f1cd0 x6 : c0000000ffffefff  
[7.664187] x5 : 0000000000057fa8 x4 : ffffbbbef1e07968  
[7.669869] x3 : 00000000ffffffff x2 : ffffbbbef1e078e0  
[7.675208] x1 : 0000000000000000 x0 : 0000000000000000  
[7.680543] Call trace:  
[7.683012] gpio\_to\_desc+0xb4/0x100  
[7.686498] max9296\_power\_on+0xe8/0x100  
[7.690178] onsemi\_probe+0x904/0xa20  
[7.693936] i2c\_device\_probe+0xb0/0x2e0  
[7.697440] really\_probe+0xf8/0x3d0  
[7.701115] driver\_probe\_device+0x60/0xc0  
[7.705398] \_\_device\_attach\_driver+0x8c/0xd0  
[7.709428] bus\_for\_each\_drv+0x8c/0xe0  
[7.713447] \_\_device\_attach+0xf8/0x160  
[7.717385] device\_initial\_probe+0x28/0x40  
[7.721153] bus\_probe\_device+0xa4/0xb0  
[7.724915] deferred\_probe\_work\_func+0x90/0xd0  
[7.729735] process\_one\_work+0x1c4/0x4a0  
[7.733923] worker\_thread+0x200/0x430  
[7.737426] kthread+0x148/0x170  
[7.740681] ret\_from\_fork+0x10/0x24  
[7.744595] —[end trace a8725fff385ba7a1]—  
[7.883614] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x0 = c4  
[7.884369] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x10 = 21  
[7.991579] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x6b = 12  
[7.992365] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x73 = 13  
[7.993105] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x7b = 33  
[7.993867] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x83 = 33  
[7.994624] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x93 = 33  
[7.995416] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x9b = 33  
[7.996215] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0xa3 = 33  
[7.996973] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0xab = 33  
[7.997757] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x8b = 33  
[7.998555] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x44 = 20  
[7.999339] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x45 = 20  
[8.000126] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x2be = 90  
[8.000909] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x2bf = 60  
[8.001723] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x3f1 = 89  
[8.147570] onsemi\_sensor\_driver 1-0010: onsemi\_probe[769]

---

<div class="post-metadata">

**Author:** ![sujit.kumar](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sujit.kumar](https://forums.developer.nvidia.com/u/sujit.kumar)\
**Post date:** [June 2, 2023, 3:23am UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/5 "2023-06-02T03:23:54Z")

</div>

> [@sujit.kumar](#):
>
> [7.884369] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x10 = 21

MAX 9296/9295 will work for all sensor or do we have to do any specific changes for ONSEMI sensors ?

---

<div class="post-metadata">

**Author:** ![ShaneCCC](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/shaneccc/32/14043_2.png) [@ShaneCCC](https://forums.developer.nvidia.com/u/ShaneCCC)\
**Post date:** [June 2, 2023, 4:45am UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/6 "2023-06-02T04:45:18Z")

</div>

Looks like some GPIO control code in max9296\_power\_on{} cause the problem.

---

<div class="post-metadata">

**Author:** ![sujit.kumar](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sujit.kumar](https://forums.developer.nvidia.com/u/sujit.kumar)\
**Post date:** [June 5, 2023, 1:21pm UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/7 "2023-06-05T13:21:13Z")

</div>

Now I am able to configure des/ser properly and video node is also getting created. but not able to detect sensor.  
Any help?

Below is my kernel log:

> [7.194927] tegradc 15200000.display: Display dc.000000004143f7f2 registered with id=0  
> [7.203471] tegra\_nvdisp\_bandwidth\_register\_max\_config: max config iso bw = 15681600 KB/s  
> [7.203939] max9296 1-006c: max9296\_write\_reg:i2c[0x6C] write success, 0x10 = 1  
> [7.211343] tegra\_nvdisp\_bandwidth\_register\_max\_config: max config EMC floor = 933000000 Hz  
> [7.211352] tegra\_nvdisp\_bandwidth\_register\_max\_config: max config hubclk = 300000000 Hz  
> [7.218814] max9296 1-006c: max9296\_write\_reg:i2c[0x6C] write success, 0x10 = 21  
> [7.226965] tegradc 15200000.display: vblank syncpt # 11 for dc 0  
> [7.248364] tegradc 15200000.display: vpulse3 syncpt # 12 for dc 0  
> [7.255677] tegradc 15200000.display: hdmi: invalid prod list prod\_list\_hdmi\_board  
> [7.262002] tegradc 15200000.display: hdmi: tegra\_hdmi\_tmds\_range\_read(bd) failed  
> [7.271785] tegradc 15200000.display: probed  
> [7.274293] Console: switching to colour frame buffer device 80x30  
> [7.280034] tegradc 15200000.display: fb registered  
> [7.284798] irq: IRQ272: trimming hierarchy from :pmc@c360000  
> [7.339958] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x0 = c4  
> [7.340763] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x10 = 21  
> [7.391365] tegra\_cec 3960000.tegra\_cec: Can’t find physical address.  
> [7.391520] tegra\_cec 3960000.tegra\_cec: tegra\_cec\_init Done.  
> [7.447955] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x6b = 12  
> [7.448715] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x73 = 13  
> [7.449522] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x7b = 33  
> [7.450296] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x83 = 33  
> [7.451044] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x93 = 33  
> [7.451863] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x9b = 33  
> [7.452679] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0xa3 = 33  
> [7.453526] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0xab = 33  
> [7.454329] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x8b = 33  
> [7.455114] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x44 = 20  
> [7.455918] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x45 = 20  
> [7.456725] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x2be = 90  
> [7.457508] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x2bf = 60  
> [7.458311] max9295 1-0062: max9295\_write\_reg:i2c[0x62] write success, 0x3f1 = 89  
> [7.462058] max9296 1-006c: max9296\_write\_reg:i2c[0x6C] write success, 0x10 = 3  
> [7.502245] max9296 1-006c: max9296\_write\_reg:i2c[0x6C] write success, 0x10 = 23  
> [7.607949] max9296 1-006c: max9296\_write\_reg:i2c[0x6C] write success, 0x332 = f0  
> [7.608129] onsemi\_serdes\_driver 1-0010: Sujit : onsemi\_serdes\_probe [789]  
> [7.608361] tegra-camrtc-capture-vi tegra-capture-vi: subdev onsemi\_serdes\_driver 1-0010 bound  
> [7.608894] tegra-camrtc-capture-vi tegra-capture-vi: tegra\_channel\_update\_format: preferred\_stride = 0 and alinged  
> [7.609257] tegra-camrtc-capture-vi tegra-capture-vi: tegra\_channel\_update\_format: preferred\_stride = 0 and alinged  
> [7.609463] tegra-camrtc-capture-vi tegra-capture-vi: tegra\_channel\_update\_format: preferred\_stride = 0 and alinged  
> [7.609675] tegra-camrtc-capture-vi tegra-capture-vi: tegra\_channel\_update\_format: preferred\_stride = 0 and alinged  
> [7.610061] onsemi\_serdes\_driver 1-0010: Sujit : onsemi\_serdes\_probe [797]  
> [7.610201] onsemi\_serdes\_driver 1-0010: Detected ONSEMI serdes generic sensor driver  
> **[7.610787] onsemi\_serdes\_driver 1-0010: chip version register read failed**  
> **[7.611005] onsemi\_serdes\_driver 1-0010: chip version 0 detected!!**

Here is my lattest DTSI:  
[tegra194-p3509-0000-camera-onsemi-sensor-driver-a00.dtsi](https://forums.developer.nvidia.com/uploads/short-url/pqYdhbuNjWTB9r4rSzJlAqEZVaP.dtsi) (1.9 KB)  
[tegra194-p3509-camera-onsemi-sensor-driver.dtsi](https://forums.developer.nvidia.com/uploads/short-url/z7DwaSWmm5bKWtlMyKme1Y33VC2.dtsi) (2.9 KB)  
[tegra194-camera-onsemi-sensor-driver-a00.dtsi](https://forums.developer.nvidia.com/uploads/short-url/6Cf9THJGykkNPPwjooOAcZH8UrW.dtsi) (9.5 KB)

---

<div class="post-metadata">

**Author:** ![ShaneCCC](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/shaneccc/32/14043_2.png) [@ShaneCCC](https://forums.developer.nvidia.com/u/ShaneCCC)\
**Post date:** [June 5, 2023, 2:07pm UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/8 "2023-06-05T14:07:52Z")

</div>

Does below failed cause it?

> [@sujit.kumar](#):
>
> onsemi\_serdes\_driver 1-0010: chip version register read failed

---

<div class="post-metadata">

**Author:** ![sujit.kumar](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sujit.kumar](https://forums.developer.nvidia.com/u/sujit.kumar)\
**Post date:** [June 6, 2023, 3:46am UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/9 "2023-06-06T03:46:13Z")

</div>

This I am trying to ready post registry is done successfully and expecting sensor should get discovered here.

```auto
 err = tegracam_v4l2subdev_register(tc_dev, true);
    if (err) {
        dev_err(dev, "tegra camera subdev registration failed\n");
        return err;
    }

    dev_err(dev, "Sujit : %s [%d]\n", __func__ , __LINE__ );
    
    dev_info(dev, "Detected ONSEMI serdes generic sensor driver\n");

    err = onsemi_serdes_read_reg(priv->s_data, 0x3000, &chip_version);
	if (err) {
		dev_err(dev, "chip version register read failed\n");
	}
    dev_err(dev, "chip version %x detected!!\n", chip_version);

```

---

<div class="post-metadata">

**Author:** ![ShaneCCC](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/shaneccc/32/14043_2.png) [@ShaneCCC](https://forums.developer.nvidia.com/u/ShaneCCC)\
**Post date:** [June 6, 2023, 6:56am UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/10 "2023-06-06T06:56:33Z")

</div>

The port-index of onsemi\_sensor\_driver\_b duplicate with first one.

---

<div class="post-metadata">

**Author:** ![sujit.kumar](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sujit.kumar](https://forums.developer.nvidia.com/u/sujit.kumar)\
**Post date:** [June 6, 2023, 7:02am UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/11 "2023-06-06T07:02:49Z")

</div>

> [@ShaneCCC](#):
>
> onsemi\_sensor\_driver\_b

That is for different use case; I am configuring :

1. onsemi\_sensor\_driver\_a for CSI mipi 4 lane  
2, onsemi\_sensor\_driver\_b for CSI mipi 2 lane

Upto here no issue I can see streaming is happning

When I configure onsemi\_sensor\_driver\_c for SERDES then I dont able to do sensor read/write via I2C.  
So please refer onsemi\_sensor\_driver\_c and help me to know if I am configuring something wrongly.

---

<div class="post-metadata">

**Author:** ![sujit.kumar](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sujit.kumar](https://forums.developer.nvidia.com/u/sujit.kumar)\
**Post date:** [June 8, 2023, 6:28am UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/12 "2023-06-08T06:28:13Z")

</div>

Hi,

After reseting max9295 I am able to detect sensor and read/write is working as expected.

I need one clarification regarding confiring CSI, below is how we are connecting CSI. Could you let me know what changes I have to do in DTSI to configure CSI4\_D0 to CSI4\_D4 for 4 Lane MIPI .

 ![image](https://global.discourse-cdn.com/nvidia/original/4X/6/2/2/622651bd5a1d334c90c16416f4e21e303800413b.png)

Thanks,  
Sujit

---

<div class="post-metadata">

**Author:** ![ShaneCCC](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/shaneccc/32/14043_2.png) [@ShaneCCC](https://forums.developer.nvidia.com/u/ShaneCCC)\
**Post date:** [June 8, 2023, 6:40am UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/13 "2023-06-08T06:40:18Z")

</div>

The port-index is 4 for CSI4

---

<div class="post-metadata">

**Author:** ![sujit.kumar](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sujit.kumar](https://forums.developer.nvidia.com/u/sujit.kumar)\
**Post date:** [June 8, 2023, 6:45am UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/14 "2023-06-08T06:45:32Z")

</div>

> [@ShaneCCC](#):
>
> CSI4

I have added port-index 4 in dtsi for CSI4. Attached my DTSI for your quick reference. Could you help me to figureout if any issue in DTSI

[tegra194-camera-onsemi-sensor-driver-a00.dtsi](https://forums.developer.nvidia.com/uploads/short-url/eAoIaV89F2xOVd0vhnZVjz1ZwUK.dtsi) (9.5 KB)

---

<div class="post-metadata">

**Author:** ![sujit.kumar](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sujit.kumar](https://forums.developer.nvidia.com/u/sujit.kumar)\
**Post date:** [June 8, 2023, 7:19am UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/15 "2023-06-08T07:19:44Z")

</div>

I have probed signals and I can see sensor to serilizer data is coming but not getting data at deserilizer end. So suspecting some DTSI configuration I have done wrongly. Could you please suggest any help

---

<div class="post-metadata">

**Author:** ![ShaneCCC](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/shaneccc/32/14043_2.png) [@ShaneCCC](https://forums.developer.nvidia.com/u/ShaneCCC)\
**Post date:** [June 8, 2023, 8:24am UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/16 "2023-06-08T08:24:09Z")

</div>

I would suggest consult to consult with MAX to check the driver configure.

---

<div class="post-metadata">

**Author:** ![sujit.kumar](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sujit.kumar](https://forums.developer.nvidia.com/u/sujit.kumar)\
**Post date:** [June 8, 2023, 11:51am UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/17 "2023-06-08T11:51:37Z")

</div>

Can you please confirm the max9296 kernel driver is for max9296a or max9296b ?

---

<div class="post-metadata">

**Author:** ![ShaneCCC](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/shaneccc/32/14043_2.png) [@ShaneCCC](https://forums.developer.nvidia.com/u/ShaneCCC)\
**Post date:** [June 8, 2023, 12:11pm UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/18 "2023-06-08T12:11:44Z")

</div>

I don’t know you need to know it from vendor.

Thanks

---

<div class="post-metadata">

**Author:** ![sujit.kumar](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sujit.kumar](https://forums.developer.nvidia.com/u/sujit.kumar)\
**Post date:** [June 28, 2023, 3:51am UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/20 "2023-06-28T03:51:54Z")

</div>

Hi ShaneCCC,

Thank you for your help.  
I am able to get data packets post gitting right configuration of deserlizer.

Could you let me know what is this error:  
[311.845964] tegra-camrtc-capture-vi tegra-capture-vi: corr\_err: discarding frame 0, flags: 0, err\_data 512  
[311.875491] tegra-camrtc-capture-vi tegra-capture-vi: corr\_err: discarding frame 0, flags: 0, err\_data 512

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/system/32/68080_2.png) [@system](https://forums.developer.nvidia.com/u/system)\
**Post date:** [July 12, 2023, 3:51am UTC](https://forums.developer.nvidia.com/t/serdes-camera-streaming/254533/21 "2023-07-12T03:51:58Z")

</div>

Closed on July 12, 2023, 3:51am UTC

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
