usb: Update for new sequence numbers

Use the new sequence number in all cases. Since all devices are assigned
a number when bound, this hack should not be needed.

Signed-off-by: Simon Glass <sjg@chromium.org>

diff --git a/drivers/usb/host/ehci-vf.c b/drivers/usb/host/ehci-vf.c
index 79ee975873e055f84b90f9916bdd4ea6f3a3b122..25f76c9fa9182620dadd6f1ed94c3949c283feb4 100644 (file)
--- a/drivers/usb/host/ehci-vf.c
+++ b/drivers/usb/host/ehci-vf.c
@@ -296,16 +296,14 @@ static const struct ehci_ops vf_ehci_ops = {
 
 static int vf_usb_bind(struct udevice *dev)
 {
-       static int num_controllers;
-
        /*
         * Without this hack, if we return ENODEV for USB Controller 0, on
         * probe for the next controller, USB Controller 1 will be given a
         * sequence number of 0. This conflicts with our requirement of
         * sequence numbers while initialising the peripherals.
+        *
+        * FIXME: Check that this still works OK with the new sequence numbers
         */
-       dev->req_seq = num_controllers;
-       num_controllers++;
 
        return 0;
 }