search

intel / ipu6-drivers

GNU General Public License v2.0
179 stars 54 forks source link

Dell Latitude 7440/0982JK with OV02C10 not working #302

Open mana-z opened 6 days ago

mana-z commented 6 days ago

Hi!

My 6.12.1-arch1-1 is not seeing the webcam (my dual-booted windows say it's OV02C10).

Here's output of my sudo dmesg|grep -E "ipu|vsc":

[   26.572740] intel-ipu6 0000:00:05.0: enabling device (0000 -> 0002)
[   26.572857] intel-ipu6 0000:00:05.0: IPU6 in secure mode touch 0x0 mask 0x0
[   26.592894] intel-ipu6 0000:00:05.0: FW version: 20230925
[   26.680029] intel-ipu6 0000:00:05.0: IPU6 in secure mode touch 0x0 mask 0x0
[   26.699795] intel-ipu6 0000:00:05.0: FW version: 20230925
[   26.704658] intel-ipu6 0000:00:05.0: IPU6 in secure mode touch 0x0 mask 0x0
[   26.712049] intel-ipu6 0000:00:05.0: FW version: 20230925
[   26.717708] intel-ipu6 0000:00:05.0: IPU6 in secure mode touch 0x0 mask 0x0
[   26.721363] intel-ipu6 0000:00:05.0: FW version: 20230925
[   26.739735] intel-ipu6 0000:00:05.0: IPU6 in secure mode touch 0x0 mask 0x0
[   26.743106] intel-ipu6 0000:00:05.0: FW version: 20230925
[   26.751462] intel-ipu6 0000:00:05.0: IPU6 in secure mode touch 0x0 mask 0x0
[   26.754649] intel-ipu6 0000:00:05.0: FW version: 20230925
[   26.759632] intel-ipu6 0000:00:05.0: IPU6 in secure mode touch 0x0 mask 0x0
[   26.762598] intel-ipu6 0000:00:05.0: FW version: 20230925
.... repeats a bunch of times ...
[   27.797957] intel-ipu6 0000:00:05.0: IPU6 in secure mode touch 0x0 mask 0x0
[   27.800963] intel-ipu6 0000:00:05.0: FW version: 20230925
[   28.214859] vsc-tp spi-INTC1009:00: wait rom failed ret: -110
[   28.214866] intel_vsc intel_vsc: CMD_DUMP_MEM error -110 token 0
[   28.214872] intel_vsc intel_vsc: hw_reset failed ret = -110
[   28.773944] vsc-tp spi-INTC1009:00: wait rom failed ret: -110
[   28.773951] intel_vsc intel_vsc: CMD_DUMP_MEM error -110 token 0
[   28.773955] intel_vsc intel_vsc: hw_reset failed ret = -110
[   29.334262] vsc-tp spi-INTC1009:00: wait rom failed ret: -110
[   29.334268] intel_vsc intel_vsc: CMD_DUMP_MEM error -110 token 0
[   29.334273] intel_vsc intel_vsc: hw_reset failed ret = -110
[   29.334289] intel_vsc intel_vsc: reset: reached maximal consecutive resets: disabling the device
[   29.334290] intel_vsc intel_vsc: reset failed ret = -19
[   29.334291] intel_vsc intel_vsc: link layer initialization failed.
[   29.334292] intel_vsc intel_vsc: error -ENODEV: init hw failed
[   29.357211] intel-ipu6 0000:00:05.0: IPU6 in secure mode touch 0x0 mask 0x0
[   29.376876] intel-ipu6 0000:00:05.0: FW version: 20230925
[   29.377637] intel-ipu6 0000:00:05.0: IPU6 in secure mode touch 0x0 mask 0x0
[   29.381647] intel-ipu6 0000:00:05.0: FW version: 20230925
[   29.382271] intel-ipu6 0000:00:05.0: IPU6 in secure mode touch 0x0 mask 0x0
[   29.389173] intel-ipu6 0000:00:05.0: FW version: 20230925
... keeps repeating for another ~ 1 sec before stopping ...

Obviously no /dev/video* is present and nothing is available with cam -l.

Trying to fix this, I already compiled in a bunch of patches to my kernel: https://gist.github.com/xTeixeira/36efa073da784609f23dee3d2d017671 https://lore.kernel.org/all/20241031102321.409454-1-stanislaw.gruszka@linux.intel.com/ https://lore.kernel.org/all/20241106220102.40549-1-hdegoede@redhat.com/ https://lore.kernel.org/all/20241108151234.36884-1-hdegoede@redhat.com/ https://bugzilla-attachments.redhat.com/attachment.cgi?id=2059082 plus the three from /patch/v6.12 and DKMS modules from this repo.

The SPI fix from bugzilla did change the error from -22 to -110.

lspci does show Multimedia controller: Intel Corporation Device a75d (rev 01)

EDIT: retried today with full in-tree method to same result. I haven't removed any of the patches.

sgruszka commented 5 days ago

Hi,

Could you please test this patch? vsc-tp-test.patch.txt on top of patches you already have and those additional two: https://lore.kernel.org/all/20241112075514.680712-1-stanislaw.gruszka@linux.intel.com/ https://lore.kernel.org/all/20241112075514.680712-2-stanislaw.gruszka@linux.intel.com/

We track this issue here: https://bugzilla.redhat.com/show_bug.cgi?id=2316918

So would be good if you add your info there as well, to keep information in one place (there is also a wired workaround for the issue described in this bugzilla ).