USB port connected to multiple USB compliant devices

Abstract

At least one downstream interface may be configured to be simultaneously connected to both a USB 3.0 compliant device and a USB 2.0 compliant device. The interface may be used for communicating with a USB 3.0 compliant device via a downstream port and simultaneously communicating with a USB 2.0 compliant device via the downstream port.

Description

BACKGROUND

Universal Serial Bus (USB) technologies have been extremely successful and their application is nearly ubiquitous. The advent of USB 3.0 compliant standards provide enhanced performance through greater data transfer rates. USB 3.0 standards employ SSTX and SSTR—signals (hereinafter, “SuperSpeed” signals) to achieve the greater data transfer rates. In order to maintain the universal nature, backwards compatibility is maintained by also including USB 2.0 compliant D+ and D− signals (hereinafter, “Hi-Speed” signals) so that older USB devices that are not configured to handle the SuperSpeed signals may still communicate using USB 2.0 signals (e.g., Hi-Speed, full-speed and/or low-speed) signals.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate implementations of the concepts conveyed in the present application. Features of the illustrated implementations may be more readily understood by reference to the following description taken in conjunction with the accompanying drawings. Like reference numbers in the various drawings are used wherever feasible to indicate like elements. Further, the left-most numeral of each reference number conveys the figure and associated discussion where the reference number is first introduced.

FIG. 1 is a flowchart of a USB resources utilization method that may be accomplished in accordance with various embodiments.

FIG. 2 shows an embodiment of a system 200 that effectively utilizes USB resources.

FIG. 2A shows an embodiment of an implementation of the scenario 212 in a device 220.

FIG. 2B shows another example of an implementation of scenario 212 in a device 240.

FIGS. 2, 2A, 2B, and 3-7 are USB resource utilization techniques that may be employed in accordance with various embodiments of the invention.

DETAILED DESCRIPTION

This patent relates to Universal Serial Bus (USB) technologies and specifically to utilizing resources available with USB technologies. USB 3.0 is a relatively new standard that offers better performance than existing USB 2.0 technologies. USB 3.0 further maintains backwards compatibility for USB 2.0 devices. Briefly, USB 3.0 compliant interfaces include a first set of SuperSpeed conductors (SSTX and SSRX signals) and a second set of Hi-Speed USB 2.0 conductors (D+ and D− signals).

In many usage scenarios, a USB interface terminates in a USB port that includes a female receptacle. The female receptacle may allow a user to plug a male plug of a downstream device, such as flash memory dongle device, camera, mouse, etc., into the USB port. If the downstream device is USB 3.0 compliant then data communications with the downstream device utilize the first set of SuperSpeed conductors. Otherwise, the second set of Hi-Speed USB 2.0 conductors may be utilized. Such a system offers backwards compatibility so that any unknown USB device that is plugged into the port functions properly.

However, other applications do not have this unknown factor. For instance, USB technologies may be utilized to fixedly connect known components together. In such a case, it is known in advance whether the downstream device is USB 3.0 compliant or USB 2.0 compliant. In such a case, the redundant first and second sets of SuperSpeed conductors and USB 2.0 compliant conductors do not offer enhanced flexibility, but instead simply lead to increased cost and/or decreased performance since one of the connectors is not being used.

As used herein, the term “USB 3.0” or “USB 3.0 Compliant” are used to mean a device (which may include one or more compliant components) that supports SuperSpeed signaling as defined in the USB 3.0 specification by the USB-IF (Implementers Forum), Inc. Similarly, the term “Hi-Speed conductors” is used to refer to the D+/D− lines that may be used for low, full or Hi-Speed signaling as defined in the USB 2.0 specification by the USB-IF. Additionally, it is possible for a USB 3.0 compliant device to support all or some of the capabilities defined by the USB 2.0 specification, and a USB 2.0 compliant device to support some of the capabilities defined by the USB 3.0 specification. These two specifications are used by way of example only and are not intended to be limiting with respect to the spirit of the method and apparatus embodiments described herein or their equivalence.

FIG. 1 is an embodiment of method 100 that may be employed to offer the user increased performance and/or decreased cost for a given system configuration. At 102, the method supplies a USB 3.0 compliant interface to a downstream device that is known to be USB 3.0 compliant and therefore only uses the SuperSpeed portion of the interface. At 104, the method provides an unused USB 2.0 compliant portion of the USB 3.0 interface to a USB 2.0 compliant device. Thus, a single USB 3.0 interface may be utilized to communicate with two different downstream devices. In one case, the USB 3.0 compliant interface may include a downstream port that includes SuperSpeed conductors and Hi-Speed conductors. The SuperSpeed conductors may be connected to a USB 3.0 compliant device and the Hi-Speed conductors may be connected to a USB 2.0 compliant device. Thus, a single port may service two devices. Accordingly, the end user or consumer may receive better and/or more functionality for a given set of system resources than was previously possible.

In some embodiments, method 100 and/or other methods for accomplishing the present concepts may be stored on computer-readable storage media as computer-readable instructions. A processor, such as a controller, may execute the computer-readable instructions to perform the method.

FIG. 2 shows an embodiment of a system 200 that effectively utilizes USB resources. System 200 includes a host device 202, and two downstream devices 204 and 206. In this case, downstream device 204 is known to be a USB 3.0 compliant (or at least USB 3.0 capable) device and downstream device 206 is known to be a USB 2.0 compliant device. For purposes of explanation, system 200 is explained relative to a first scenario 210 and a second scenario 212 that will be discussed in more detail below.

Host 202 may supply an interface 214 that includes a first set of conductors 216 and a second set of conductors 218. The interface 214 may be USB 3.0 compliant. In this case, the first set of conductors 216 are SuperSpeed (USB 3.0) compliant SSTX and SSTR lines. Similarly, the second set of conductors 218 may be Hi-Speed (USB 2.0) compliant D+ and D− lines.

In the embodiment depicted in scenario 210, downstream device 204 is a known USB 3.0 compliant device. Accordingly, the first set of conductors 216 are utilized for communications between host device 202 and downstream device 204, while the second set of conductors 218 remain unutilized as indicated at 220. Thus, from a resource usage perspective, interface 214 is under-utilized as a resource in scenario 210. A contrasting example is described below relative to scenario 212.

In the embodiment depicted in scenario 212, downstream device 204 is connected to host device 202 in the same manner as scenario 210. However, second set of conductors 218 is connected to downstream device 206 to increase resource utilization. Accordingly, interface 214 which in scenario 210 was connected with a single downstream device may now be utilized to connect to two downstream devices. Thus, for a given cost of host device 202, the end user may be provided with more functionality in scenario 212 than in scenario 210. Among other cases, scenario 212 may be realized in instances where it is known that downstream device 204 is a USB 3.0 compliant device and that downstream device 204 is to be connected to interface 214 in a generally permanent manner. As used herein, a generally permanent manner means that the end user does not expect to readily and frequently disconnect downstream device 204 and connect some other downstream device.

FIG. 2A shows an embodiment of an implementation of the scenario 212 in a device 220. In this case, device 220 includes a motherboard 222 coupled to a graphics card 224 that is a known USB 3.0 capable device and an audio card 226 that is a known USB 2.0 device via a single USB interface 228 that includes a port 230. The USB interface provides SuperSpeed connectors 232 to the graphics card 224 and Hi-Speed connectors 234 to audio card 226.

FIG. 2B shows another example of an implementation of scenario 212 in a device 240. In this case, device 240 includes a motherboard 242 coupled to a graphics card 244 that is a known USB 3.0 device. The motherboard is also coupled to an external USB 2.0 compliant connector 246. The external USB 2.0 compliant connector 246 may be manifest as a female USB receptacle that may receive any USB 2.0 compliant device, such as a memory stick, card reader, keyboard, mouse, etc. The motherboard is connected to the graphics card and the external USB 2.0 compliant connector 246 via a single USB interface 248 that includes a port 250. The USB interface 248 provides SuperSpeed connectors 252 to the graphics card 244 and Hi-Speed connectors 254 to external USB 2.0 compliant connector 246.

FIG. 3 shows another embodiment of a system 300 that may effectively utilize USB resources. System 300 includes a device implemented as a docking station 302. The principles described relative to docking station 302 may be utilized with other devices that may employ USB technologies. In this example, docking station 302 includes six external ports positioned relative to a housing 303. One of the external ports is an upstream port 304 that goes to a PC. The remaining five ports are downstream ports in the form of three USB 3.0 compliant USB ports 306(1), 306(2), and 306(3) (illustrated as female USB compliant receptacles), an Ethernet port 308, and a video port 310. Docking station circuit 312 shows a schematic view of docking station 302. In this example, the docking station includes three chipsets: a hub chipset 314, a video chipset 316, and an Ethernet chipset 318. The hub chipset 314 may be configured to function as a 4-port USB hub as indicated at 320. (While a 4-port hub example is shown here, there is nothing critical about this number and other implementations may relate to USB hubs with more or fewer ports).

The video chipset 316 may be configured to provide a USB 3.0 to video functionality as indicated at 322. The Ethernet chipset 318 may be configured to provide a USB 2.0 to Ethernet functionality as indicated at 324. Accordingly, hub chipset 314 is connected to upstream port 304 via an interface 326. Hub chipset 314 is connected to USB 3.0 port 306(1) via interface 328(1), to USB 3.0 port 306(2) via interface 328(2), and to USB 3.0 port 306(3) via interface 328(3). Further, the hub chipset is connected to both video chipset 316 and Ethernet chipset 318 via interface 328(4). Finally, the video chipset 316 is connected to video port 310 via interface 330. Similarly, Ethernet chipset 318 is connected to Ethernet port 308 via interface 332. Note that in this embodiment, the connections between hub chipset 314 and both video chipset 316 and Ethernet chipset 318 via interface 328(4) may be considered relatively “fixed.” For example, short of a failure of one of the chipsets and subsequent replacement, the connections are not intended to be disturbed. One scenario that may be considered relatively fixed is where the chipsets are soldered on a printed circuit board (PCB).

Interface 328(4) may be configured consistent with the description above relative to scenario 212 of FIG. 2. In this implementation, recall that docking station 302 includes a four port USB hub 320. Yet, communication may be established with five downstream mechanisms (e.g., USB 3.0 ports 306(1)-306(3), video chipset 316 and Ethernet chipset 318). Thus, the present implementation makes better use of the resources offered by a four port hub than previous technologies.

While system 300 is explained in the context of a docking station, the present concepts may be implemented in any number of devices, such as hubs, repeaters, splitters, monitors, ASICs, computing devices, camera and storage devices, among others.

FIG. 4 shows yet another embodiment of a system 400 that may effectively utilize USB resources. System 400 includes a device in the form of a notebook computing device 402 that internally contains a PC chipset 404. The principles described relative to notebook computing device 402 may be utilized with other devices that may employ USB technologies. In this example, notebook computing device 402 includes two external USB 3.0 compliant downstream connections or ports 406(1) and 406(2) (illustrated as female USB receptacles), a USB 3.0 solid state drive 408, and a USB 2.0 optical drive 410. The PC chipset 404 includes a USB 3.0 host controller 412 and three USB 3.0 interfaces 414(1), 414(2), and 414(3).

The host controller 412 is coupled to USB 3.0 port 406(1) via USB 3.0 interface 414(1) and to USB 3.0 port 406(2) via USB 3.0 interface 414(2). The host controller 412 is coupled to both USB 3.0 solid state drive 408 and optical drive 410 via USB 3.0 interface 414(3). In this particular case, the interface 414(3) may allow SuperSpeed signals to be communicated between the USB 3.0 host controller 412 and the USB 3.0 solid state drive 408. The interface 414(3) may also allow Hi-Speed (and/or low-speed and/or full-speed signals) to be communicated between the host controller 412 and the optical drive 410. Thus, the present implementation may allow the USB 3.0 host controller 412 to communicate with four ports and/or devices utilizing only three interfaces. Accordingly, this implementation makes better use of the available resources than previous technologies.

FIG. 5 shows yet another embodiment of a system 500 that may effectively utilize USB resources. System 500 includes a host or upstream device 502 and two downstream devices 504 and 506. In this example, downstream device 504 is a known USB 3.0 compliant device and downstream device 506 is a known USB 2.0 compliant device.

Host device 502 includes a host chipset 510 that includes a controller 512 and that defines an interface 514. (Host chipset 510 may also define other interfaces that are not shown here, but are shown for example in FIG. 3). The interface 514 may define a first data or signal path 516 and a second data or signal path 518. The first data path 516 may extend between host device 502 and downstream device 504 to allow communications between the two devices. Similarly, second data path 518 may extend between host device 502 and downstream device 506 to allow communications between the two devices.

First data path 510 may include a first set of conductors 520 while second data path 512 may include a second set of conductors 522. The first set of conductors 520 may be USB 3.0 compliant SSTX and SSTR lines. Similarly, the second set of conductors 522 may be USB 2.0 compliant D+ and D− lines.

Interface 514 may allow data communications between controller 512 and first and second downstream devices 504 and 506. Further, in this implementation, data paths 516 and 518 may allow simultaneous communications between downstream device 504 and the controller 512 and between downstream device 506 and the controller, respectively. For instance, downstream device 504 may send data to the controller over data path 516 while downstream device 506 sends data to the controller over data path 518. This configuration may prevent garbling of data that could occur by simultaneous communication over a shared data path.

FIGS. 6 and 7 show two alternate configurations of embodiments for allowing communication between a host device and two downstream devices over a single interface.

FIG. 6 shows a hub chipset 602, according to one embodiment. The hub chipset includes a controller 604, a bus 606, and an interface 608. The interface forms two data paths 610(1) and 610(2). Data path 610(1) enables SuperSpeed signals to be communicated to bus 606 over interface 608 when the data path is coupled to a USB 3.0 capable device 612. Data path 610(2) enables standard-speed or high-speed signals to be communicated to bus 606 over interface 608 when the data path is coupled to a USB 2.0 capable device 614.

FIG. 7 shows another embodiment of a hub chipset in hub chipset 702. The hub chipset 702 includes two controllers 704(1) and 704(2) and an interface 708. The interface may include two data paths 710(1) and 710(2). Data path 710(1) enables SuperSpeed signals to be communicated over interface 708 when the data path is connected to a USB 3.0 capable device 712. Data path 710(2) enables standard-speed or high-speed signals to be communicated over interface 708 when the data path is connected to a USB 2.0 capable device 714.

The above described implementations allow a single USB 3.0 interface to be coupled to two different downstream devices and to provide satisfactory communications with both downstream devices via the single USB 3.0 interface.

To summarize, the present implementations offer a way to share a single USB 3.0 interface to connect two separate USB devices. Viewed from another perspective, the present techniques offer a way for available lines or conductors on a USB 3.0 host interface to connect a USB 3.0 device using the dedicated USB 3.0 conductors, and a USB 2.0 device using the dedicated USB 2.0 conductors. These techniques enable a designer to save an entire USB 3.0 port in a design where it is known one of the connected devices supports USB 3.0 (e.g., is USB 3.0 capable). Thus, these techniques allow a given design to provide extra ports with a given set of hardware than existing technologies.

Although techniques, methods, devices, systems, etc., pertaining to utilizing USB resources are described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claimed methods, devices, systems, etc.

Claims

1. A device, comprising: a downstream port including a first conductor directly connected to a USB 3.0 capable device and including a second conductor simultaneously directly connected to a USB 2.0 compliant device, wherein the downstream port is configured to communicate USB 3.0 signals with the USB 3.0 capable device via the first conductor and to communicate USB 2.0 signals with the USB 2.0 capable device via the second conductor.

2. The device of claim 1, wherein the one downstream port includes a first set of conductors and a second set of conductors, wherein the first set of conductors are configured to directly connect to the USB 3.0 capable device and to convey USB 3.0 signals to the USB 3.0 capable device and the second set of conductors are configured to directly connect to the USB 2.0 compliant device and to convey USB 2.0 signals to the USB 2.0 compliant device.

3. The device of claim 1, further comprising a controller coupled to a bus, and wherein the downstream port includes a first data path between the bus and the USB 3.0 capable device and a second data path between the bus and the USB 2.0 compliant device.

4. The device of claim 3, wherein the first and second data paths are separate and distinct from one another.

5. The device of claim 1, further comprising first and second controllers, wherein the downstream port includes first and second data paths, and wherein the first data path couples the USB 3.0 capable device to the first controller and the second data path couples the USB 2.0 compliant device to the second controller.

6. The device of claim 1, wherein the downstream port is configured to convey the USB 3.0 signals and the USB 2.0 signals simultaneously.

7. The device of claim 1, further comprising a host controller, a hub controller, a system on chip that includes the host controller or the hub controller.

8. The device of claim 1, further comprising a USB controller configured to alternate between communicating with the USB 3.0 capable device using USB 3.0 signals and communicating with the USB 2.0 compliant device using USB 2.0 signals.

9. A device, comprising: a downstream port configured to simultaneously provide a first connection to a USB 3.0 capable device using USB 3.0 signals and a second connection to a USB 2.0 compliant device using USB 2.0 signals; anda USB controller configured to alternate between communicating with the USB 3.0 capable device using the USB 3.0 signals and communicating with the USB 2.0 compliant device using the USB 2.0 signals.

10. The device of claim 9, wherein the first connection to the USB 3.0 capable device is independent of the second connection to the USB 2.0 compliant device.

11. The device of claim 9, wherein the downstream port is configured to receive simultaneous communications from the USB 3.0 capable device and the USB 2.0 compliant device.

12. The device of claim 9, wherein the USB 3.0 capable device is a video chipset and the USB 2.0 compliant device is an Ethernet chipset.

13. The device of claim 9, further comprising first and second USB controllers coupled to the downstream port, the first controller configured to handle the USB 3.0 signals and the second controller configured to handle the USB 2.0 signals.

14. The device of claim 9, comprising a USB hub or a USB splitter.

15. A system, comprising: a USB hub device positioned in a housing and that includes an upstream interface and at least one downstream interface; andan individual downstream interface that has a first set of USB 3.0 conductors directly connected to a USB 3.0 compliant chip set and a second set of USB 2.0 conductors simultaneously directly connected to a USB 2.0 compliant chip set.

16. The system of claim 15, wherein the individual downstream interface is configured to provide a first data path and a first buffer for the USB 3.0 compliant chip set and a second data path and a second buffer for the USB 2.0 compliant chip set.

17. The system of claim 16, wherein the USB 3.0 conductors are soldered to the USB 3.0 compliant chip set and the second set of USB 2.0 conductors are soldered to the USB 2.0 compliant chip set.

18. The system of claim 15, wherein the USB hub device includes a controller and wherein the first set of USB 3.0 conductors provide a first data path between the USB 3.0 compliant chip set and the controller and wherein the second set of USB 2.0 conductors provide a second data path between the USB 2.0 compliant chip set and the controller.

19. The system of claim 18, wherein the first data path and the second data path allow simultaneous communications from the USB 3.0 compliant chip set to the controller and from the USB 2.0 compliant chip set to the controller.

20. The system of claim 16, wherein the USB 3.0 compliant chip set is a video chipset that includes a video port positioned on the housing and wherein the USB 2.0 compliant chip set is an Ethernet chipset that includes an Ethernet port on the housing.

21. The system of claim 15, wherein the USB hub device is configured to alternate between communicating with the USB 3.0 compliant chip set using USB 3.0 signals and communicating with the USB compliant chip set using USB 2.0 signals.

22. A method, comprising: communicating with a USB 3.0 compliant device via a downstream port; and simultaneously communicating with a USB 2.0 compliant device via the downstream port, wherein the downstream port is simultaneously directly connected to both the USB 3.0 compliant device and the USB 2.0 compliant device.