Am 22.12.22 um 03:26 schrieb Matthias Kaehlcke:
Some boards with an onboard USB hub supported by the onboard_hub driver have a device tree node for the hub, but the node doesn't specify all properties needed by the driver (which is not a DT error per se). For such a hub no onboard_hub platform device is created. However the USB portion of the onboard hub driver still probes and uses _find_onboard_hub() to find the platform device that corresponds to the hub. If the DT node of the hub doesn't have an associated platform device the function looks for a "peer-hub" node (to get the platform device from there), if that doesn't exist either it logs an error and returns -EINVAL.
The absence of a platform device is expected in some configurations, so drop the error log and fail silently with -ENODEV.
Fixes: 8bc063641ceb ("usb: misc: Add onboard_usb_hub driver") Signed-off-by: Matthias Kaehlcke mka@chromium.org
Tested-by: Stefan Wahren stefan.wahren@i2se.com