usb: gadget: bcm63xx_udc: don't touch gadget.dev.driver

udc-core now handles that for us, which means
we can remove it from our driver.

Signed-off-by: Felipe Balbi <balbi@ti.com>

diff --git a/drivers/usb/gadget/bcm63xx_udc.c b/drivers/usb/gadget/bcm63xx_udc.c
index e7d2cd0b8f94b96cf0de2752bd1566cad0319ca5..904d4746922dd3108b2ff9296b05f2801b78c2c2 100644 (file)
--- a/drivers/usb/gadget/bcm63xx_udc.c
+++ b/drivers/usb/gadget/bcm63xx_udc.c
@@ -1819,7 +1819,6 @@ static int bcm63xx_udc_start(struct usb_gadget *gadget,
 
        udc->driver = driver;
        driver->driver.bus = NULL;
-       udc->gadget.dev.driver = &driver->driver;
        udc->gadget.dev.of_node = udc->dev->of_node;
 
        spin_unlock_irqrestore(&udc->lock, flags);
@@ -1841,7 +1840,6 @@ static int bcm63xx_udc_stop(struct usb_gadget *gadget,
        spin_lock_irqsave(&udc->lock, flags);
 
        udc->driver = NULL;
-       udc->gadget.dev.driver = NULL;
 
        /*
         * If we switch the PHY too abruptly after dropping D+, the host