I wrote a new camera sensor driver based on ov5693, and reused the ov5693 device name (for now). After a lot of hacking, it seems to be up based on the printk’s I put in the module. But I can’t find the video device - should it be /dev/video0.
I’m pretty sure the device registration call is working and I see a printk…
6: tegracam sensor driver:ov5693_v2.0.6
in the log.
What should I be seeing after the driver is up?
Thanks
Larry@FLIR
Should be have below message.
[ 7.645747] ov5693 2-0036: probing v4l2 sensor.
[ 7.649146] ov5693 2-0036: tegracam sensor driver:ov5693_v2.0.6
[ 8.581873] tegra194-vi5 15c10000.vi: subdev ov5693 2-0036 bound
Thanks. We those from your board? I don’t see them all w/ my setup - the last one is missing.
Sep 25 14:08:57 flir-agx kernel: [ 1404.421274] ov5693_eeprom_device_release: Entered
Sep 25 14:15:32 flir-agx kernel: [ 1799.661404] FLIR probing v4l2 sensor.
Sep 25 14:15:32 flir-agx kernel: [ 1799.661534] ov5693 2-0036: ov5693_parse_dt: Entered
Sep 25 14:15:32 flir-agx kernel: [ 1799.661728] ov5693 2-0036: FLIR found DT match
Sep 25 14:15:32 flir-agx kernel: [ 1799.661845] ov5693 2-0036: FLIR alloc ok
Sep 25 14:15:32 flir-agx kernel: [ 1799.661934] ov5693 2-0036: FLIR clocks ok
Sep 25 14:15:32 flir-agx kernel: [ 1799.662857] ov5693 2-0036: FLIR gpio ok
Sep 25 14:15:32 flir-agx kernel: [ 1799.663089] ov5693 2-0036: FLIR gpio reset ok
Sep 25 14:15:32 flir-agx kernel: [ 1799.663194] ov5693 2-0036: FLIR use cam bool ok
Sep 25 14:15:32 flir-agx kernel: [ 1799.663289] ov5693 2-0036: FLIR avdd ok
Sep 25 14:15:32 flir-agx kernel: [ 1799.663370] ov5693 2-0036: FLIR eeprom ok
Sep 25 14:15:32 flir-agx kernel: [ 1799.663454] ov5693 2-0036: ov5693_power_get: Entered
Sep 25 14:15:32 flir-agx kernel: [ 1799.668926] ov5693 2-0036: tegracam sensor driver:ov5693_v2.0.6
Sep 25 14:15:32 flir-agx kernel: [ 1799.669070] ov5693 2-0036: ov5693_board_setup: Entered
Sep 25 14:15:32 flir-agx kernel: [ 1799.669161] ov5693_eeprom_device_init: Entered
Sep 25 14:15:32 flir-agx kernel: [ 1799.669165] ov5693 2-0036: FLIR passed eprom config
Sep 25 14:15:32 flir-agx kernel: [ 1799.670056] ov5693 2-0036: ov5693_board_setup: passed mck
Sep 25 14:15:32 flir-agx kernel: [ 1799.670196] ov5693_power_on: Entered
Sep 25 14:15:32 flir-agx kernel: [ 1799.670234] ov5693_gpio_set: Entered
Sep 25 14:15:32 flir-agx kernel: [ 1799.672290] ov5693_gpio_set: Entered
Sep 25 14:15:32 flir-agx kernel: [ 1799.674428] ov5693 2-0036: ov5693_board_setup: Paassed poweron
Sep 25 14:15:32 flir-agx kernel: [ 1799.674577] ov5693 2-0036: ov5693_board_setup: passed read eeprom
Sep 25 14:15:32 flir-agx kernel: [ 1799.674709] ov5693_otp_setup: Entered
Sep 25 14:15:32 flir-agx kernel: [ 1799.674713] ov5693_fuse_id_setup: Entered
Sep 25 14:15:32 flir-agx kernel: [ 1799.674719] ov5693 2-0036: ov5693_board_setup: Passed fuse
Sep 25 14:15:32 flir-agx kernel: [ 1799.674840] ov5693 2-0036: Done with board setup
Sep 25 14:15:32 flir-agx kernel: [ 1799.674931] ov5693 2-0036: ov5693_power_off: Entered
Sep 25 14:15:32 flir-agx kernel: [ 1799.675085] ov5693_gpio_set: Entered
Sep 25 14:15:32 flir-agx kernel: [ 1799.675108] ov5693_gpio_set: Entered
Sep 25 14:15:32 flir-agx kernel: [ 1799.679100] ov5693 2-0036: ov5693_board_setup: End Setup of function error is 0
Sep 25 14:15:32 flir-agx kernel: [ 1799.679486] ov5693_fill_string_ctrl: Entered
Sep 25 14:15:32 flir-agx kernel: [ 1799.679720] ov5693_fill_string_ctrl: Entered
Sep 25 14:15:32 flir-agx kernel: [ 1799.679850] ov5693_fill_string_ctrl: Entered
Sep 25 14:15:32 flir-agx kernel: [ 1799.679889] ov5693 2-0036: FLIR registration seems to have passed - check it.
Sep 25 14:15:32 flir-agx kernel: [ 1799.680053] ov5693_debugfs_create: Entered
Does your kernel message have nvcsi/vi initialize message?
[ 6.025898] tegra194-vi5 15c10000.vi: using default number of vi channels, 36
[ 6.029853] tegra194-vi5 15c10000.vi: initialized
[ 6.033803] tegra194-vi5 15c10000.vi: subdev 15a00000.nvcsi--1 bound
[ 1.586481] t194-nvcsi 15a00000.nvcsi: initialized
[ 6.033803] tegra194-vi5 15c10000.vi: subdev 15a00000.nvcsi--1 bound
This is what I found. I can’r really decipher it.
Thanks
lc
tegra194-vi5 15c10000.vi: using default number of vi channels, 36
Sep 28 09:38:05 flir-agx kernel: [ 5.967537] tegra194-vi5 15c10000.vi: initialized
Sep 28 09:38:05 flir-agx kernel: [ 5.971186] tegra194-vi5 15c10000.vi: ep of_device is not enabled /host1x/vi@15c10000/ports/portt
@0/endpoint.
Sep 28 09:38:05 flir-agx kernel: [ 5.972138] tegradc 15210000.nvdisplay: disp1 connected to head1->/host1x/sor
Sep 28 09:38:05 flir-agx kernel: [ 5.972170] tegradc 15210000.nvdisplay: parse_dp_settings: No dp-lt-settings node
Sep 28 09:38:05 flir-agx kernel: [ 5.972451] tegradc 15210000.nvdisplay: DT parsed successfully
Sep 28 09:38:05 flir-agx kernel: [ 5.972518] tegradc 15210000.nvdisplay: Display dc.ffffff800fd50000 registered with id=1
Sep 28 09:38:05 flir-agx kernel: [ 5.972763] tegradc 15210000.nvdisplay: vblank syncpt # 15 for dc 1
Sep 28 09:38:05 flir-agx kernel: [ 5.972767] tegradc 15210000.nvdisplay: vpulse3 syncpt # 16 for dc 1
Sep 28 09:38:05 flir-agx kernel: [ 5.974421] tegra-xusb 3610000.xhci: USB2 port 0 has OTG_CAP
Sep 28 09:38:05 flir-agx kernel: [ 5.974425] tegra-xusb 3610000.xhci: USB3 port 2 has OTG_CAP
Sep 28 09:38:05 flir-agx kernel: [ 5.977639] tegra-xusb 3610000.xhci: extcon 0: ffffffc7c7f40000 id
Sep 28 09:38:05 flir-agx kernel: [ 5.978187] tegra-xudc-new 3550000.xudc: PMQOS CPU boost enabled
Sep 28 09:38:05 flir-agx kernel: [ 5.978234] tegra-xudc-new 3550000.xudc: device count: 1
Sep 28 09:38:05 flir-agx kernel: [ 5.979045] tegra-xudc-new 3550000.xudc: vbus state: 1
Sep 28 09:38:05 flir-agx kernel: [ 5.979060] tegra-xudc-new 3550000.xudc: device mode on: 0
Sep 28 09:38:05 flir-agx kernel: [ 5.979357] tegra-xudc-new 3550000.xudc: active: 0 => 1
Sep 28 09:38:05 flir-agx kernel: [ 5.979365] tegra-xudc-new 3550000.xudc: Initialize boost_cpufreq work
Shane:
At this point I don’t have my camera/fpga on the dev kit. Is that causing this issue?
I have a mipi adapter board and a test camera I can use. Would that work?
Larry
Doesn’t matter if the driver probe function didn’t return any error like access failed.
Does any nvcsi kernel message?
What is the cause of this…
Sep 28 09:38:05 flir-agx kernel: [ 5.971186] tegra194-vi5 15c10000.vi: ep of_device is not enabled /host1x/vi@15c10000/ports/portt
@0/endpoint.
It could be the status in the DT of the VI scope setted as disable.
Thanks. I’ll look at that. Don’t think we touched that, but you never know.
lc
hi,
whice DT file did you modified?