Try adding

initcall_blacklist=xhci_hcd_init

to your kernel parameters. Or maybe xhci_init_driver. You'll have to experiment here.

Also take a look at the "quirks" available in drivers/usb/host/xhci.h. Specifically, if this is an Intel-only limitation, you could try XHCI_NEC_HOST. There's also XHCI_EP_LIMIT_QUIRK, though I honestly have no idea what it does.

If the experiments are fruitless, you'll have to build a custom kernel.

Try adding

initcall_blacklist=xhci_hcd_init

to your kernel parameters (/boot/firmware/cmdline.txt). Or maybe xhci_init_driver. You'll have to experiment here.

Also take a look at the "quirks" available in drivers/usb/host/xhci.h. Specifically, if this is an Intel-only limitation, you could try XHCI_NEC_HOST. There's also XHCI_EP_LIMIT_QUIRK, though I honestly have no idea what it does.

If the experiments are fruitless, you'll have to build a custom kernel.

Try adding

initcall_blacklist=xhci_hcd_init

to your kernel parameters (/boot/cmdline.txt). Or maybe xhci_init_driver. You'll have to experiment here.

If the experiments are fruitless, you'll have to build a custom kernel.

Try adding

initcall_blacklist=xhci_hcd_init

to your kernel parameters. Or maybe xhci_init_driver. You'll have to experiment here.

Also take a look at the "quirks" available in drivers/usb/host/xhci.h. Specifically, if this is an Intel-only limitation, you could try XHCI_NEC_HOST. There's also XHCI_EP_LIMIT_QUIRK, though I honestly have no idea what it does.

If the experiments are fruitless, you'll have to build a custom kernel.