Skip to contentSkip to conversation

usb: xhci: Fix vendor command error if the request

U-Boot Anand Moon 2 participants 6 messages Mar 5, 2016 – Mar 14, 2016

Subsystems (2)
lore
Share & tools
lore

Anand Moon

author
#0 lore raw

From: Ted Chen <[email protected]>

From: Ted Chen <[email protected]>

type is USB_REQ_SET_ADDRESS or USB_REQ_SET_CONFIGURATION.
To: marex at denx.de, swarren at nvidia.com, u-boot at lists.denx.de
Cc: linux.amoon at gmail.com, Ted Chen <[email protected]>

Add a condition of set_address and set_configuration to check if the request is standardized.

---
Resend this patch it some how got missed
Changes since v1: None.

Tested on Odroid XU4: with Ethernet USB3.0 RT8153-VB

---
 drivers/usb/host/xhci.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/usb/host/xhci.c +4 -2
index ca598aa..cb8a04b 100644
@@ -941,10 +941,12 @@ static int _xhci_submit_control_msg(struct usb_device *udev, unsigned long pipe,
 	if (usb_pipedevice(pipe) == ctrl->rootdev)
 		return xhci_submit_root(udev, pipe, buffer, setup);
 
-	if (setup->request == USB_REQ_SET_ADDRESS)
+	if (setup->request == USB_REQ_SET_ADDRESS &&
+	   (setup->requesttype & USB_TYPE_MASK) == USB_TYPE_STANDARD)
 		return xhci_address_device(udev, root_portnr);
 
-	if (setup->request == USB_REQ_SET_CONFIGURATION) {
+	if (setup->request == USB_REQ_SET_CONFIGURATION &&
+	   (setup->requesttype & USB_TYPE_MASK) == USB_TYPE_STANDARD) {
 		ret = xhci_set_configuration(udev);
 		if (ret) {
 			puts("Failed to configure xHCI endpoint\n");
Signature · 1 line
1.9.1
#1 lore raw
Quoted 10 lines · Anand Moon

From: Ted Chen <[email protected]>

From: Ted Chen <[email protected]>

type is USB_REQ_SET_ADDRESS or USB_REQ_SET_CONFIGURATION.
To: marex at denx.de, swarren at nvidia.com, u-boot at lists.denx.de
Cc: linux.amoon at gmail.com, Ted Chen <[email protected]>

Add a condition of set_address and set_configuration to check if the request is standardized.

Can you please rephrase the commit message ? It's really hard to understand. I believe such a patch will be needed for ehci as well, can you prepare one ?

Quoted 20 lines

---
Resend this patch it some how got missed
Changes since v1: None.

Tested on Odroid XU4: with Ethernet USB3.0 RT8153-VB

---
 drivers/usb/host/xhci.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/usb/host/xhci.c +0 -1
index ca598aa..cb8a04b 100644
@@ -941,10 +941,12 @@ static int _xhci_submit_control_msg(struct usb_device *udev, unsigned long pipe,
 	if (usb_pipedevice(pipe) == ctrl->rootdev)
 		return xhci_submit_root(udev, pipe, buffer, setup);
 
-	if (setup->request == USB_REQ_SET_ADDRESS)

drivers/usb/host/xhci.c static int _xhci_submit_control_msg(struct usb_device *udev, unsigned long pipe, · line 952

Quoted 10 lines
drivers/usb/host/xhci.c +4 -1
+	if (setup->request == USB_REQ_SET_ADDRESS &&
+	   (setup->requesttype & USB_TYPE_MASK) == USB_TYPE_STANDARD)
 		return xhci_address_device(udev, root_portnr);
 
-	if (setup->request == USB_REQ_SET_CONFIGURATION) {
+	if (setup->request == USB_REQ_SET_CONFIGURATION &&
+	   (setup->requesttype & USB_TYPE_MASK) == USB_TYPE_STANDARD) {
 		ret = xhci_set_configuration(udev);
 		if (ret) {
 			puts("Failed to configure xHCI endpoint\n");

What happens to the non-standard requests ?

Signature · 2 lines
Best regards,
Marek Vasut
author
#2 lore raw

Hi Marek,

Quoted 9 lines · Marek Vasut
Quoted 8 lines · Anand Moon

From: Ted Chen <[email protected]>

From: Ted Chen <[email protected]>

type is USB_REQ_SET_ADDRESS or USB_REQ_SET_CONFIGURATION.
To: marex at denx.de, swarren at nvidia.com, u-boot at lists.denx.de
Cc: linux.amoon at gmail.com, Ted Chen <[email protected]>

Quoted 6 lines
Quoted 2 lines

Add a condition of set_address and set_configuration to check if the request is standardized.

Can you please rephrase the commit message ? It's really hard to understand. I believe such a patch will be needed for ehci as well, can you prepare one ?

I could not find any need for such check in ehci-hcd driver.

Sorry for this mess in commit message, I completely missed formatting the statement
because of it got warped up in the message
Will send this message again with proper commit message.

Quoted 24 lines
Quoted 24 lines

---
Resend this patch it some how got missed
Changes since v1: None.

Tested on Odroid XU4: with Ethernet USB3.0 RT8153-VB

---
 drivers/usb/host/xhci.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/usb/host/xhci.c +2 -1
index ca598aa..cb8a04b 100644
@@ -941,10 +941,12 @@ static int _xhci_submit_control_msg(struct usb_device *udev, unsigned long pipe,
      if (usb_pipedevice(pipe) == ctrl->rootdev)
              return xhci_submit_root(udev, pipe, buffer, setup);
 
-     if (setup->request == USB_REQ_SET_ADDRESS)
+     if (setup->request == USB_REQ_SET_ADDRESS &&
+        (setup->requesttype & USB_TYPE_MASK) == USB_TYPE_STANDARD)
              return xhci_address_device(udev, root_portnr);
 
Quoted 10 lines

drivers/usb/host/xhci.c static int _xhci_submit_control_msg(struct usb_device *udev, unsigned long pipe, · line 952

Quoted 7 lines
drivers/usb/host/xhci.c +2 -1
-     if (setup->request == USB_REQ_SET_CONFIGURATION) {
+     if (setup->request == USB_REQ_SET_CONFIGURATION &&
+        (setup->requesttype & USB_TYPE_MASK) == USB_TYPE_STANDARD) {
              ret = xhci_set_configuration(udev);
              if (ret) {
                      puts("Failed to configure xHCI endpoint\n");

What happens to the non-standard requests ?

Device will not able to detect leaving message "scanning usb for ethernet devices... Non standard request in USB vendor command"

Quoted 3 lines

--
Best regards,
Marek Vasut

Here is the modified commit message

"Add a condition of set_address and set_configuration to check if the requesttype is of standardized in the USB vendor request so that usb device is detected"

Do you agree with this modified commit statement.

Best regards,
-Anand Moon

#3 lore raw
Quoted 1 line · Anand Moon

Hi Marek,

Hi!

Quoted 10 lines · Marek Vasut
Quoted 9 lines · Anand Moon
Quoted 8 lines

From: Ted Chen <[email protected]>

From: Ted Chen <[email protected]>

type is USB_REQ_SET_ADDRESS or USB_REQ_SET_CONFIGURATION.
To: marex at denx.de, swarren at nvidia.com, u-boot at lists.denx.de
Cc: linux.amoon at gmail.com, Ted Chen <[email protected]>

Quoted 8 lines
Quoted 6 lines
Quoted 2 lines

Add a condition of set_address and set_configuration to check if the request is standardized.

Can you please rephrase the commit message ? It's really hard to understand. I believe such a patch will be needed for ehci as well, can you prepare one ?

I could not find any need for such check in ehci-hcd driver.

Please explain why this is not needed.

Quoted 4 lines

Sorry for this mess in commit message, I completely missed formatting the statement
because of it got warped up in the message
Will send this message again with proper commit message.

Yes, the message is complete chaos.

Quoted 34 lines
Quoted 24 lines
Quoted 24 lines

---
Resend this patch it some how got missed
Changes since v1: None.

Tested on Odroid XU4: with Ethernet USB3.0 RT8153-VB

---
 drivers/usb/host/xhci.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/usb/host/xhci.c +2 -1
index ca598aa..cb8a04b 100644
@@ -941,10 +941,12 @@ static int _xhci_submit_control_msg(struct usb_device *udev, unsigned long pipe,
      if (usb_pipedevice(pipe) == ctrl->rootdev)
              return xhci_submit_root(udev, pipe, buffer, setup);
 
-     if (setup->request == USB_REQ_SET_ADDRESS)
+     if (setup->request == USB_REQ_SET_ADDRESS &&
+        (setup->requesttype & USB_TYPE_MASK) == USB_TYPE_STANDARD)
              return xhci_address_device(udev, root_portnr);
 
Quoted 10 lines

drivers/usb/host/xhci.c static int _xhci_submit_control_msg(struct usb_device *udev, unsigned long pipe, · line 952

Quoted 7 lines
drivers/usb/host/xhci.c +2 -1
-     if (setup->request == USB_REQ_SET_CONFIGURATION) {
+     if (setup->request == USB_REQ_SET_CONFIGURATION &&
+        (setup->requesttype & USB_TYPE_MASK) == USB_TYPE_STANDARD) {
              ret = xhci_set_configuration(udev);
              if (ret) {
                      puts("Failed to configure xHCI endpoint\n");

What happens to the non-standard requests ?

Quoted 3 lines

Device will not able to detect leaving message "scanning usb for ethernet devices... Non standard request in USB vendor command"

Let me re-phrase, how are the non-standard requests handled ?

Quoted 9 lines
Quoted 3 lines

--
Best regards,
Marek Vasut

Here is the modified commit message

"Add a condition of set_address and set_configuration to check if the requesttype is of standardized in the USB vendor request so that usb device is detected"

Add test into xhci_submit_control_message for usb requesttype in USB vendor request being of standardized type. This fixes detection of certain USB fixes, for example <fill here>.

Quoted 5 lines

Do you agree with this modified commit statement.

Best regards,
-Anand Moon

Signature · 2 lines
Best regards,
Marek Vasut
author
#4 lore raw

Hi Marek

Sorry for late replay.

Quoted 18 lines · Marek Vasut
Quoted 1 line · Anand Moon

Hi Marek,

Hi!

Quoted 13 lines · Marek Vasut
Quoted 12 lines · Anand Moon
Quoted 10 lines

From: Ted Chen <[email protected]>

From: Ted Chen <[email protected]>

type is USB_REQ_SET_ADDRESS or USB_REQ_SET_CONFIGURATION.
To: marex at denx.de, swarren at nvidia.com, u-boot at lists.denx.de
Cc: linux.amoon at gmail.com, Ted Chen <[email protected]>

Add a condition of set_address and set_configuration to check if the request is standardized.

Quoted 7 lines
Quoted 5 lines
Quoted 3 lines

Can you please rephrase the commit message ? It's really hard to understand. I believe such a patch will be needed for ehci as well, can you prepare one ?

I could not find any need for such check in ehci-hcd driver.

Please explain why this is not needed.

I had give this a try but it failed to detect device connected to usb device connected to USB 2.0 port.
But I will work on this and send a different patch.

Quoted 42 lines
Quoted 5 lines

Sorry for this mess in commit message, I completely missed formatting the statement
because of it got warped up in the message
Will send this message again with proper commit message.

Yes, the message is complete chaos.

Quoted 34 lines
Quoted 34 lines
Quoted 21 lines

---
Resend this patch it some how got missed
Changes since v1: None.

Tested on Odroid XU4: with Ethernet USB3.0 RT8153-VB

---
 drivers/usb/host/xhci.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/usb/host/xhci.c +0 -1
index ca598aa..cb8a04b 100644
@@ -941,10 +941,12 @@ static int _xhci_submit_control_msg(struct usb_device *udev, unsigned long pipe,
      if (usb_pipedevice(pipe) == ctrl->rootdev)
              return xhci_submit_root(udev, pipe, buffer, setup);
 
-     if (setup->request == USB_REQ_SET_ADDRESS)

drivers/usb/host/xhci.c static int _xhci_submit_control_msg(struct usb_device *udev, unsigned long pipe, · line 952

Quoted 10 lines
drivers/usb/host/xhci.c +4 -1
+     if (setup->request == USB_REQ_SET_ADDRESS &&
+        (setup->requesttype & USB_TYPE_MASK) == USB_TYPE_STANDARD)
              return xhci_address_device(udev, root_portnr);
 
-     if (setup->request == USB_REQ_SET_CONFIGURATION) {
+     if (setup->request == USB_REQ_SET_CONFIGURATION &&
+        (setup->requesttype & USB_TYPE_MASK) == USB_TYPE_STANDARD) {
              ret = xhci_set_configuration(udev);
              if (ret) {
                      puts("Failed to configure xHCI endpoint\n");

What happens to the non-standard requests ?

Quoted 5 lines
Quoted 3 lines

Device will not able to detect leaving message "scanning usb for ethernet devices... Non standard request in USB vendor command"

Let me re-phrase, how are the non-standard requests handled ?

Note: With this patch such request are ignored.

I have tried various way to handle this situation but nothing work perfectly.

Quoted 6 lines
Quoted 6 lines
Quoted 3 lines

--
Best regards,
Marek Vasut

Here is the modified commit message

Quoted 8 lines
Quoted 3 lines

"Add a condition of set_address and set_configuration to check if the requesttype is of standardized in the USB vendor request so that usb device is detected"

Add test into xhci_submit_control_message for usb requesttype in USB vendor request being of standardized type. This fixes detection of certain USB fixes, for example <fill here>.

I will update the commit message.

Quoted 10 lines
Quoted 5 lines

Do you agree with this modified commit statement.

Best regards,
-Anand Moon

--
Best regards,
Marek Vasut

OdroidXU4 development board 2 USB 3 port, 1 usb port and RTL8153 Ethernet connected to USB 3.0.
--------------------------------------------------------------------------------------------------------------------------------------------------

U-Boot 2016.03-rc3-01571-g76aab9e-dirty (Mar 13 2016 - 19:43:54 +1030) for ODROID-XU3

CPU:   Exynos5422 @ 800 MHz
Model: Odroid XU3 based on EXYNOS5422
Board: Odroid XU3 based on EXYNOS5422
Type:  xu4
DRAM:  2 GiB
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1

*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Hit any key to stop autoboot:  0

ODROID-XU3 #
ODROID-XU3 #
ODROID-XU3 #
ODROID-XU3 # usb start
starting USB...

USB0:   USB EHCI 1.00
USB1:   Register 2000140 NbrPorts 2

Starting the controller
USB XHCI 1.00
USB2: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 2 USB Device(s) found scanning bus 2 for devices... 2 USB Device(s) found
scanning usb for ethernet devices... 1 Ethernet Device(s) found
ODROID-XU3 # usb info
1: Hub, USB Revision 2.0
- u-boot EHCI Host Controller
- Class: Hub
- PacketSize: 64 Configurations: 1
- Vendor: 0x0000 Product 0x0000 Version 1.0
Configuration: 1
- Interfaces: 1 Self Powered 0mA
Interface: 0
- Alternate Setting 0, Endpoints: 1
- Class Hub
- Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

1: Hub, USB Revision 3.0
- U-Boot XHCI Host Controller
- Class: Hub
- PacketSize: 9 Configurations: 1
- Vendor: 0x0000 Product 0x0000 Version 1.0
Configuration: 1
- Interfaces: 1 Self Powered 0mA
Interface: 0
- Alternate Setting 0, Endpoints: 1
- Class Hub
- Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Hub, USB Revision 2.10
- GenesysLogic USB2.0 Hub
- Class: Hub
- PacketSize: 64 Configurations: 1
- Vendor: 0x05e3 Product 0x0610 Version 146.34
Configuration: 1
- Interfaces: 1 Self Powered Remote Wakeup 100mA
Interface: 0
- Alternate Setting 0, Endpoints: 1
- Class Hub
- Endpoint 1 In Interrupt MaxPacket 1 Interval 12ms
- Endpoint 1 In Interrupt MaxPacket 1 Interval 12ms

1: Hub, USB Revision 3.0
- U-Boot XHCI Host Controller
- Class: Hub
- PacketSize: 9 Configurations: 1
- Vendor: 0x0000 Product 0x0000 Version 1.0
Configuration: 1
- Interfaces: 1 Self Powered 0mA
Interface: 0
- Alternate Setting 0, Endpoints: 1
- Class Hub
- Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Vendor specific, USB Revision 2.10
- Realtek USB 10/100/1000 LAN 000001000000
- Class: (from Interface) Vendor specific
- PacketSize: 64 Configurations: 2
- Vendor: 0x0bda Product 0x8153 Version 48.0
Configuration: 1
- Interfaces: 1 Bus Powered Remote Wakeup 180mA
Interface: 0
- Alternate Setting 0, Endpoints: 3
- Class Vendor specific
- Endpoint 1 In Bulk MaxPacket 512
- Endpoint 2 Out Bulk MaxPacket 512
- Endpoint 3 In Interrupt MaxPacket 2 Interval 8ms

ODROID-XU3 #

Best Regards
-Anand Moon

#5 lore raw
Quoted 1 line · Anand Moon

Hi Marek

Hi!

Quoted 25 lines

Sorry for late replay.

Quoted 22 lines · Marek Vasut
Quoted 1 line · Anand Moon

Hi Marek,

Hi!

Quoted 17 lines · Marek Vasut
Quoted 15 lines · Anand Moon
Quoted 10 lines

From: Ted Chen <[email protected]>

From: Ted Chen <[email protected]>

type is USB_REQ_SET_ADDRESS or USB_REQ_SET_CONFIGURATION.
To: marex at denx.de, swarren at nvidia.com, u-boot at lists.denx.de
Cc: linux.amoon at gmail.com, Ted Chen <[email protected]>

Add a condition of set_address and set_configuration to check if the request is standardized.

Can you please rephrase the commit message ? It's really hard to understand. I believe such a patch will be needed for ehci as well, can you prepare one ?

Quoted 7 lines
Quoted 3 lines
Quoted 1 line

I could not find any need for such check in ehci-hcd driver.

Please explain why this is not needed.

I had give this a try but it failed to detect device connected to usb device connected to USB 2.0 port.
But I will work on this and send a different patch.

So USB 2.0 code does need similar fix ?

Quoted 41 lines
Quoted 41 lines
Quoted 4 lines

Sorry for this mess in commit message, I completely missed formatting the statement
because of it got warped up in the message
Will send this message again with proper commit message.

Yes, the message is complete chaos.

Quoted 34 lines
Quoted 34 lines
Quoted 21 lines

---
Resend this patch it some how got missed
Changes since v1: None.

Tested on Odroid XU4: with Ethernet USB3.0 RT8153-VB

---
 drivers/usb/host/xhci.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/usb/host/xhci.c +0 -1
index ca598aa..cb8a04b 100644
@@ -941,10 +941,12 @@ static int _xhci_submit_control_msg(struct usb_device *udev, unsigned long pipe,
      if (usb_pipedevice(pipe) == ctrl->rootdev)
              return xhci_submit_root(udev, pipe, buffer, setup);
 
-     if (setup->request == USB_REQ_SET_ADDRESS)

drivers/usb/host/xhci.c static int _xhci_submit_control_msg(struct usb_device *udev, unsigned long pipe, · line 952

Quoted 10 lines
drivers/usb/host/xhci.c +4 -1
+     if (setup->request == USB_REQ_SET_ADDRESS &&
+        (setup->requesttype & USB_TYPE_MASK) == USB_TYPE_STANDARD)
              return xhci_address_device(udev, root_portnr);
 
-     if (setup->request == USB_REQ_SET_CONFIGURATION) {
+     if (setup->request == USB_REQ_SET_CONFIGURATION &&
+        (setup->requesttype & USB_TYPE_MASK) == USB_TYPE_STANDARD) {
              ret = xhci_set_configuration(udev);
              if (ret) {
                      puts("Failed to configure xHCI endpoint\n");

What happens to the non-standard requests ?

Quoted 7 lines
Quoted 5 lines
Quoted 3 lines

Device will not able to detect leaving message "scanning usb for ethernet devices... Non standard request in USB vendor command"

Let me re-phrase, how are the non-standard requests handled ?

Note: With this patch such request are ignored.

This should be stated in the commit message for sure, thanks!

Quoted 1 line

I have tried various way to handle this situation but nothing work perfectly.

Got it.

Can you just update the commit message, send a V3 and let me pick it up? Thanks!

Quoted 135 lines
Quoted 6 lines
Quoted 6 lines
Quoted 3 lines

--
Best regards,
Marek Vasut

Here is the modified commit message

Quoted 8 lines
Quoted 3 lines

"Add a condition of set_address and set_configuration to check if the requesttype is of standardized in the USB vendor request so that usb device is detected"

Add test into xhci_submit_control_message for usb requesttype in USB vendor request being of standardized type. This fixes detection of certain USB fixes, for example <fill here>.

I will update the commit message.

Quoted 10 lines
Quoted 5 lines

Do you agree with this modified commit statement.

Best regards,
-Anand Moon

--
Best regards,
Marek Vasut

OdroidXU4 development board 2 USB 3 port, 1 usb port and RTL8153 Ethernet connected to USB 3.0.
--------------------------------------------------------------------------------------------------------------------------------------------------

U-Boot 2016.03-rc3-01571-g76aab9e-dirty (Mar 13 2016 - 19:43:54 +1030) for ODROID-XU3

CPU:   Exynos5422 @ 800 MHz
Model: Odroid XU3 based on EXYNOS5422
Board: Odroid XU3 based on EXYNOS5422
Type:  xu4
DRAM:  2 GiB
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1

*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Hit any key to stop autoboot:  0

ODROID-XU3 #
ODROID-XU3 #
ODROID-XU3 #
ODROID-XU3 # usb start
starting USB...

USB0:   USB EHCI 1.00
USB1:   Register 2000140 NbrPorts 2

Starting the controller
USB XHCI 1.00
USB2: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 2 USB Device(s) found scanning bus 2 for devices... 2 USB Device(s) found
scanning usb for ethernet devices... 1 Ethernet Device(s) found
ODROID-XU3 # usb info
1: Hub, USB Revision 2.0
- u-boot EHCI Host Controller
- Class: Hub
- PacketSize: 64 Configurations: 1
- Vendor: 0x0000 Product 0x0000 Version 1.0
Configuration: 1
- Interfaces: 1 Self Powered 0mA
Interface: 0
- Alternate Setting 0, Endpoints: 1
- Class Hub
- Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

1: Hub, USB Revision 3.0
- U-Boot XHCI Host Controller
- Class: Hub
- PacketSize: 9 Configurations: 1
- Vendor: 0x0000 Product 0x0000 Version 1.0
Configuration: 1
- Interfaces: 1 Self Powered 0mA
Interface: 0
- Alternate Setting 0, Endpoints: 1
- Class Hub
- Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Hub, USB Revision 2.10
- GenesysLogic USB2.0 Hub
- Class: Hub
- PacketSize: 64 Configurations: 1
- Vendor: 0x05e3 Product 0x0610 Version 146.34
Configuration: 1
- Interfaces: 1 Self Powered Remote Wakeup 100mA
Interface: 0
- Alternate Setting 0, Endpoints: 1
- Class Hub
- Endpoint 1 In Interrupt MaxPacket 1 Interval 12ms
- Endpoint 1 In Interrupt MaxPacket 1 Interval 12ms

1: Hub, USB Revision 3.0
- U-Boot XHCI Host Controller
- Class: Hub
- PacketSize: 9 Configurations: 1
- Vendor: 0x0000 Product 0x0000 Version 1.0
Configuration: 1
- Interfaces: 1 Self Powered 0mA
Interface: 0
- Alternate Setting 0, Endpoints: 1
- Class Hub
- Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Vendor specific, USB Revision 2.10
- Realtek USB 10/100/1000 LAN 000001000000
- Class: (from Interface) Vendor specific
- PacketSize: 64 Configurations: 2
- Vendor: 0x0bda Product 0x8153 Version 48.0
Configuration: 1
- Interfaces: 1 Bus Powered Remote Wakeup 180mA
Interface: 0
- Alternate Setting 0, Endpoints: 3
- Class Vendor specific
- Endpoint 1 In Bulk MaxPacket 512
- Endpoint 2 Out Bulk MaxPacket 512
- Endpoint 3 In Interrupt MaxPacket 2 Interval 8ms

ODROID-XU3 #

Best Regards
-Anand Moon
_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Signature · 2 lines
Best regards,
Marek Vasut