[PATCH] ARM: multi_v7_defconfig: Select CONFIG_USB_ONBOARD_DEV as built-in

[Fabio Estevam]

On Tue, Apr 30, 2024 at 4:53 AM Arnd Bergmann <arnd at arndb.de> wrote:

> It does sound like this is something the kernel should be able to
> get to work properly in some form, but I don't think making it
> a 'bool' symbol is the correct answer here: if CONFIG_USB is
> set to =m, it would be impossible to include USB_ONBOARD_DEV
> in this case.
>
> Fabio, can you explain how making it built-in addresses the
> problem here? I assume this is related to probe order, so I
> wonder if it's just a matter of making the usb hub driver
> properly handle -EPROBE_DEFER until the onboard dev has been
> initialized.

>From drivers/usb/misc/Kconfig:

"config USB_ONBOARD_DEV
tristate "Onboard USB device support"
.....
  This driver can be used as a module but its state (module vs
  builtin) must match the state of the USB subsystem. Enabling
  this config will enable the driver and it will automatically
  match the state of the USB subsystem. If this driver is a
  module it will be called onboard_usb_dev."

In multi_v7_defconfig:
CONFIG_USB=y and CONFIG_USB_ONBOARD_DEV=m, so there is a mismatch.

My patch enforces CONFIG_USB_ONBOARD_DEV=y to guarantee the matching.

Is there any other way to solve this?