Re: ipu-bridge: software nodes are never unregistered; PCI remove/rescan of IPU6 fails with -EEXIST and leaves dangling properties

[Sakari Ailus]

Hi D.,

On Fri, Aug 28, 2026 at 01:26:36AM +0200, D. Manresa wrote:
> Observed behaviour (live, 2026-08-27)
> -------------------------------------
> Attempting to recover a wedged ISYS by PCI remove/rescan:
> 
>   echo 1 > /sys/bus/pci/devices/0000:00:05.0/remove
>   modprobe -r intel_ipu6_isys intel_ipu6    # ipu_bridge unloads too
>   echo 1 > /sys/bus/pci/rescan
>   modprobe intel_ipu6

I recall unbinding the ipu6 driver successfully in the past. Do you ensure
above all sub-device drivers have been unbound first? I guess the V4L2
framework nor the ipu6 driver necessarily ensure that right now.

In general, unloading and loading modules may work, and in this case there
are lifetime issues to be addressed (MC device, as well as V4L2 sub-device
nodes), too, but for testing purposes this should just work.

-- 
Regards,

Sakari Ailus