CM5 USB VBUS brought up too early

[Randomblock1]

Describe the bug

USB VBUS is immediately enabled instead of waiting for the rest of the USB stack to initialize. This means that any BC1.2 capable device does not detect the CM5 as a downstream port, since it checks to see if the data lines are initialized and they aren't.

Steps to reproduce the behaviour

On a CM5 IO Board:

1. Plug in an Android (I used Google Pixel 10).
2. Observe that the Pi can see it.
3. Reboot the Pi.
4. See that the Pi cannot see it, and the phone thinks it is attached to an AC charger, not a computer.
5. Toggle VBUS:

pinctrl set USB_VBUS_EN op dl
sleep 1
pinctrl set USB_VBUS_EN op dh

6. Observe that the Pi can now see the phone.

Device (s)

Raspberry Pi CM5

System

https://pastebin.com/2Dmj9x9q

Logs

No response

Additional context

Physically replugging the phone also makes VBUS drop, which makes the phone discoverable again. I am communicating to the phones over adb.

[P33M]

This is unrelated to Linux. It's a function of the CM5IO board and/or bootloader. Please post technical support questions to the revelant section of the forum: https://forums.raspberrypi.com/viewforum.php?f=98