Fix device error logs kselftest failures on mt8186-steelix

[nfraprado]

Current device error logs kselftest failures on mt8186-steelix on linux-next:

# # mtk-cpufreq mtk-cpufreq: failed to initialize dvfs info for cpu0
# # mtk-cpufreq mtk-cpufreq: failed to initialize dvfs info for cpu0

• +platform:mtk-cpufreq: Sent fix: https://lore.kernel.org/all/20240628-mtk-cpufreq-dvfs-fail-init-err-v1-1-19c55db23011@collabora.com

---

# # it6505 3-005c: can not get extcon device!

• +i2c:3-005c: The DPI node fails to probe as mentioned in Fix DT kselftest failures on mt8186-steelix #400 , so this is a real error that needs to be fixed as described there. But for now should be silenced by https://lore.kernel.org/all/[email protected]/

---

# # mtk-scp 10500000.scp: error -EINVAL: invalid resource (null)

• +platform:10500000.scp: Sent fix: https://lore.kernel.org/all/20240627-scp-invalid-resource-l1tcm-v1-1-7d221e6c495a@collabora.com

---

# # hid-generic 0003:0BDA:1100.0002: device has no listeners, quitting

• +hid:0003:0BDA:1100.0002: This is the same device that I wasn't sure if should be probe tested in Enable 'discoverable devices probe' kselftest on MediaTek Chromebooks kernelci-pipeline#579 . udevmon info -t (https://lava.collabora.dev/scheduler/job/14649661) shows a bit more info on the device, though it's still not clear what it is (could be the pen interface)

│ │ │ │   │   └─0003:0BDA:1100.0001
│ │ │ │   │     ┆ P: [0;1;37m/devices/platform/soc/11281000.usb/11280000.usb/usb2/2-1/2-1.5/2-1.5:1.0/0003:0BDA:1100.0001[0m
│ │ │ │   │     ┆ M: [0;1;37m0003:0BDA:1100.0001[0m
│ │ │ │   │     ┆ R: [0;1;37m0001[0m
│ │ │ │   │     ┆ U: [0;1;32mhid[0m
│ │ │ │   │     ┆ E: DEVPATH=/devices/platform/soc/11281000.usb/11280000.usb/usb2/2-1/2-1.5/2-1.5:1.0/0003:0BDA:1100.0001
│ │ │ │   │     ┆ E: SUBSYSTEM=hid
│ │ │ │   │     ┆ E: HID_ID=0003:00000BDA:00001100
│ │ │ │   │     ┆ E: HID_NAME=Realtek HID Device
│ │ │ │   │     ┆ E: HID_PHYS=usb-11280000.usb-1.5/input0
│ │ │ │   │     ┆ E: HID_UNIQ=
│ │ │ │   │     ┆ E: MODALIAS=hid:b0003g0001v00000BDAp00001100

[nfraprado]

For further debugging of the hid error, this is the stack trace at that point:

[    5.600482]  dump_backtrace+0x94/0xec
[    5.604144]  show_stack+0x18/0x24
[    5.607456]  dump_stack_lvl+0x78/0x90
[    5.611115]  dump_stack+0x18/0x24
[    5.614423]  hid_connect+0x51c/0x524
[    5.617996]  hid_hw_start+0x58/0x74
[    5.621480]  hid_generic_probe+0x34/0x44
[    5.625399]  hid_device_probe+0x130/0x1e0
[    5.629403]  really_probe+0xbc/0x2a0
[    5.632977]  __driver_probe_device+0x78/0x12c
[    5.637330]  driver_probe_device+0x40/0x160
[    5.641508]  __device_attach_driver+0xb8/0x134
[    5.645948]  bus_for_each_drv+0x84/0xe0
[    5.649780]  __device_attach+0xa8/0x1b0
[    5.653609]  device_initial_probe+0x14/0x20
[    5.657786]  bus_probe_device+0xa8/0xac
[    5.661618]  device_add+0x590/0x750
[    5.665102]  hid_add_device+0xdc/0x2c0
[    5.668846]  usbhid_probe+0x27c/0x398
[    5.672502]  usb_probe_interface+0xd4/0x2b4
[    5.676679]  really_probe+0xbc/0x2a0
[    5.680251]  __driver_probe_device+0x78/0x12c
[    5.684604]  driver_probe_device+0x40/0x160
[    5.688784]  __device_attach_driver+0xb8/0x134
[    5.693224]  bus_for_each_drv+0x84/0xe0
[    5.697055]  __device_attach+0xa8/0x1b0
[    5.700884]  device_initial_probe+0x14/0x20
[    5.705060]  bus_probe_device+0xa8/0xac
[    5.708891]  device_add+0x590/0x750
[    5.712374]  usb_set_configuration+0x524/0x924
[    5.716811]  usb_generic_driver_probe+0x60/0x88
[    5.721335]  usb_probe_device+0x3c/0x11c
[    5.725253]  really_probe+0xbc/0x2a0
[    5.728824]  __driver_probe_device+0x78/0x12c
[    5.733178]  driver_probe_device+0x40/0x160
[    5.737356]  __device_attach_driver+0xb8/0x134
[    5.741796]  bus_for_each_drv+0x84/0xe0
[    5.745634]  __device_attach+0xa8/0x1b0
[    5.749461]  device_initial_probe+0x14/0x20
[    5.753637]  bus_probe_device+0xa8/0xac