Revision tags: v9.2.2, v9.2.1, v9.2.0, v9.1.2 |
|
#
96fda137 |
| 12-Nov-2024 |
Guenter Roeck <linux@roeck-us.net> |
usb/uhci: Move PCI-related code into a separate file
Some machines (like Aspeed ARM) only have a sysbus UHCI controller. The current UHCI implementation only supports PCI based UHCI controllers. Mov
usb/uhci: Move PCI-related code into a separate file
Some machines (like Aspeed ARM) only have a sysbus UHCI controller. The current UHCI implementation only supports PCI based UHCI controllers. Move the UHCI-PCI device code into a separate file so that it is possible to create a sysbus UHCI device without PCI dependency.
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
show more ...
|
#
3fdd8e54 |
| 12-Nov-2024 |
Guenter Roeck <linux@roeck-us.net> |
usb/uhci: Move PCI-related code into a separate file
Some machines (like Aspeed ARM) only have a sysbus UHCI controller. The current UHCI implementation only supports PCI based UHCI controllers. Mov
usb/uhci: Move PCI-related code into a separate file
Some machines (like Aspeed ARM) only have a sysbus UHCI controller. The current UHCI implementation only supports PCI based UHCI controllers. Move the UHCI-PCI device code into a separate file so that it is possible to create a sysbus UHCI device without PCI dependency.
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
show more ...
|
#
27af7e00 |
| 12-Nov-2024 |
Guenter Roeck <linux@roeck-us.net> |
usb/uhci: Move PCI-related code into a separate file
Some machines (like Aspeed ARM) only have a sysbus UHCI controller. The current UHCI implementation only supports PCI based UHCI controllers. Mov
usb/uhci: Move PCI-related code into a separate file
Some machines (like Aspeed ARM) only have a sysbus UHCI controller. The current UHCI implementation only supports PCI based UHCI controllers. Move the UHCI-PCI device code into a separate file so that it is possible to create a sysbus UHCI device without PCI dependency.
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
show more ...
|