Patent Application
20080019357
The following drawings illustrate some of the many possible embodiments of this disclosure in order to provide a basic understanding of this disclosure. These drawings do not provided an extensive overview of all embodiments of this disclosure. These drawings are not intended to identify key or critical elements of the disclosure or to delineate or otherwise limit the scope of the claims. The following drawings merely present some concepts of the disclosure in a general form. Thus, for a detailed understanding of this disclosure, reference should be made to the following detailed descriptions taken in conjunction with the accompanying drawings in which like elements have been given like numerals.
For purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, or other purposes. For example, an IHS may be a personal computer, a network storage device, or any other suitable device and may vary in size; shape, performance, functionality, and price. The IHS may include random access memory (RAM), one or more processing resources such as a central processing unit (CPU) or hardware or software control logic, ROM, and/or other types of nonvolatile memory. Additional components of the IHS may include one or more disk drives, one or more network ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. The IHS may also include one or more buses operable to transmit communications between the various hardware components.
Referring to
Fixed data storage 25 commonly stores the OS, application programs, and other data for use by IHS 5. Fixed data storage refers to permanent (non-volatile) storage. Fixed data storage devices include but are not limited to: a hard disk drive, and a magnetic tape drive. An array of hard disk drives may be controlled by a disk array controller and may be part of a storage server. In addition, mobile data storage device 65 may interface with bus 40 for transferring data to or from IHS 5. Examples of mobile data storage include, but are not limited to: an external portable hard drive; a solid state semiconductor storage device, such as flash memory; and an optical disc storage device, such as CD and DVD. IHS 5 may further comprise a video display adapter 45, a plurality of input interfaces 50, a modem/network interface card (NIC) 55, a plurality of output interfaces 60, and a mobile data storage device 65, all of which may also be coupled to the local interface 40. Output interface 60 may transmit hard copy data to printer 90.
IHS 5 may be coupled to an external network 95 through NIC 55 thus allowing the IHS 5 to send and receive data via the external network 95 to remote device. As shown, the external network 95 may be a local area network (LAN), a wide area network (WAN), or other similar network. As described in
An interface may be utilized for making hardware and data connections between any combination and number of devices, non-limiting examples of devices include IHS's, and components and peripherals therefor, and any combinations thereof. An interface connector refers to one of the pair of mating connectors that comprises an interface. The pair of connectors is sometimes referred to as a receptacle and plug, or female and male connectors, respectively.
There exist in the IHS industry a number of interface standards for making connections between any combination and number of devices, non-limiting examples of which include IHS's, components and peripherals therefor. As a non-limiting example, there exists the Advanced Technology Attachment (ATA) standard and the Small Computer System Interface (SCSI) standard. These standards define both the physical interface and the protocol used to communicate over the physical interface. Both standards have evolved over time through the release of new ATA and SCSI specifications, specifically, the Serial ATA (SATA) specification and the Serial Attached SCSI (SAS) specification. As used throughout this disclosure, reference to ATA, SCSI, SATA and SAS is intended to encompass all versions and releases of the associated specifications.
Physical and electrical interfaces may be configured that comply with both SATA and SAS standards. A common interface connector as used herein is one that can suitably interface with a corresponding mating connector of a different interface standard. A non-limiting example of a common interface connector would be a connector that can interface with at least both a SAS compliant interface connector and a SATA compliant interface connector. Ideally, a device connected through a common interface connector would operate identically whether connected with one standard of interface or another standard of interface. However, this disclosure also contemplates that a device might operate differently when connected through a common interface with a first type of plug as opposed to a second type of plug. As a non-limiting example, this disclosure contemplates that a device might operate the same or differently when connected to a SAS receptacle with a SAS plug as opposed to a SATA plug.
While common interface connector 21 does not have to be so limited, as shown in
It should be understood that when connecting a first device together with a second device, whether the interface receptacle is on the first or second device, and the whether the corresponding mating interface plug is on the other device, generally is not a factor is determining operation or performance. Thus, in the absence of any industry standard or convention, it is matter of personal choice as to which device is provided with the interface receptacle and which is provided with the corresponding mating interface plug. As a non-limiting example, it is not uncommon commercially to find hard drives equipped with an interface plug and hard drive controllers equipped with the corresponding mating interface receptacle. Of course, this disclosure is not to be read as assigning an interface receptacle and an interface plug to any particular device, but rather is to be read as contemplating any combination.
As used herein, “device of ‘X’ interface type,” means a device which interfaces using interface standard “X.” As used herein, a SAS device refers to any device equipped with a SAS interface connector. Likewise, a SATA device refers to any device equipped with a SATA interface connector.
There are a number of reasons to determine the standard of the device connected to a common connector, non-limiting examples of which include to communicate with the device using the proper protocol and to determine if the device has the desired standard.
This disclosure provides non-limiting examples of methods and apparatus for determining if a device connected to a SAS receptacle is (1) a SAS device, (2) a SATA device, or (3) neither a SAS device nor a SATA device and for determining whether a device is present.
Although Interface connector 301 will be described with particularity, it should be understood that the description is meant to be that of a non-limiting SAS connector embodiment as shown in FIG, 3, and that other embodiments of any present or future contemplated interface standard may be configured as desired having any suitable number and arrangement of ports, transmit (“TX”) wires (i.e., “pins”), receive wires (“RX”), and ground wires (“GND”).
The non-limiting embodiment of
A device detector may be in communication with interface connector 301 and may produce at least three data states indicative of the interface type of any device coupled to the interface connector. As a non-limiting example, the device detector may comprise a detection circuit, a non-limiting example of which includes detection circuit 334. In the non-limiting embodiment as shown, detection circuit 334 may be coupled to any one or more of the ground pins of port 302 and to any one of the ground pins of port 304, and detects whether coupled to interface 301 is (1) a SAS device, (2) a SATA device or (3) neither a SAS device nor a SATA device or no device present. It should be understood that a detection circuit may be utilized that would detect whether coupled to interface 301 is (1) a SAS device, (2) a SATA device, (3) a device that is neither a SAS device, or (4) no device present. In the non-limiting embodiment as shown in
Detection circuit 334 may be any circuit capable of producing indicator data indicative of three or more different states, one state each associated with a connection to (1) a SAS device, (2) a SATA device, or (3) neither a SAS device nor a SATA device or no device. Non-limiting examples of types of indicator data include any that can be utilized to communicate device type, non-limiting examples of which include voltage, impedance, resistance, amperage, capacitance, vibration, sound, sound train, light, light train, any suitable analog output or signal, any suitable digital output or signal, and the like.
As a non-limiting example, detection circuit 334 may be any circuit capable of producing three or more different voltage levels or states, one unique voltage level each associated with a connection to (1) a SAS device, (2) a SATA device, or (3) a device that is neither a SAS device nor a SATA device or no device. The A to D converter 343 translates the several voltage levels into several digital states for use by a processor or CPLD in determining the type of device connected via the interface. The voltage levels are not necessarily precise voltage levels and the term voltage level includes a range of voltages, which may be distinguished from other levels and ranges.
In the non-limiting embodiment as shown in
As shown, detection circuit 334 may also include capacitors 335 and 338, each of approximately 1 uF. Any suitable number and type of capacitors may be utilized and may be selected to ensure a low impedance AC current return path to the GND pins. Accordingly, capacitor 335 and capacitor 338 reduce the adverse effect of detection circuit 334 on signal clarity of the interface 301.
Detection circuit 334 is coupled to a voltage source 340 via the pull up resistor 336. While any suitable voltage source and voltage level may be utilized, in the non-limiting embodiment of
In another aspect, detection circuit 334 may be coupled to a logic device 342 (e.g., a processor or a complex programmable logic device (“CPLD”), a field programmable gate array (“FPGA”) or a comparator circuit) for use in determining the device presence and/or type.
The interface connector 401 of
Although interface connector 401 will be described with particularity, it should be understood that the description is meant to be that of a non-limiting SAS connector embodiment as shown in
The non-limiting embodiment of
Similar to the SAS storage device 400, the SATA storage device 500 is capable of being coupled to interface 300 of
Although Interface connector 501 will be described with particularity, it should be understood that the description is meant to be that of a non-limiting SATA connector embodiment as shown in
The non-limiting embodiment of
As discussed above, the detection circuit 334 determines (e.g., detects) whether a SAS storage device a SATA storage device, or whether neither a SAS nor SATA or no device, is coupled to the interface 301.
A non-limiting method embodiment of this disclosure includes any or all of determining a device's interface type and generating indicator data based thereon. The discussion above as it relates to interface type and indicator data is applicable here.
In a “SAS” solution of detection circuit 334, if SAS device 400 is coupled with SAS device 300, the respective pins on connectors 301 and 401 will connect. Resistor 337 is connected to GND pin 332, which is in turn connected to GND pin 432, and resistor 339 is connected to GND pin 318, which is in turn connected to GND pin 418. The 5V is therefore dropped across pull-up resistor 336 in series with parallel resistors 337 and 339, indicating a first data or a first voltage of 1.67V at converter 343.
In a “SATA” solution of detection circuit 334, if SATA device 500 is coupled with SAS device 300, the respective pins on connectors 301 and 501 will connect. Resistor 339 is connected to GND pin 318, which is in turn connected to GND pin 516. Since port 304 of connector 301 has no counterpart port on connector 501, resistor 337 is connected to GND pin 332, which is not connected to any counterpart on connector 501. Thus, the 5V is dropped across pull-up resistor 336 in series with only resister 339, indicating a second data or a second voltage of 2.5V at converter 343.
In a “no device present” solution of detection circuit 334, if no device is coupled with SAS device 300, there are no respective pins to connect with the pins of connector 301. Both resistor 337 and resister 339 are not grounded. Thus, the 5V is dropped only across pull-up resistor 336, indicating a third data or a third voltage of 5V at converter 343.
It is also possible that a device connected is neither a SAS nor SATA device. In a “neither SAS nor SATA” solution of detection circuit 334, if such a device is coupled with SAS device 300, and there are no respective pins to connect with the pins of connector 301, then both resistor 337 and resister 339 are not grounded. Thus, the 5V is dropped only across pull-up resistor 336, indicating a third data or a third voltage of 5V at converter 343.
The present disclosure also provides a computer-receivable media carrying a multi-state signal, the multi-state signal having three or more states, the states including a first state identifying a device of a first type, a second state identifying a device of a second type, and a third state identifying a device of a third type, the multi-state signal being transmittable to an information handling system processor,
The present disclosure is to be taken as illustrative rather than as limiting the scope or nature of the claims below While specific embodiments have been discussed herein, it should be understood that other embodiments, numerous modifications, and variations will become apparent to those skilled in the art after studying the disclosure, including use of equivalent functional and/or structural substitutes for elements described herein, use of equivalent functional couplings for couplings described herein, and/or use of equivalent functional actions for actions described herein. Such other embodiments, modifications, and variations are to be considered within the scope of the claims below.
Given the above disclosure of general concepts and specific embodiments, the scope of protection sought is to be defined by the claims appended hereto The issued claims are not to be taken as limiting Applicant's right to claim disclosed, but not yet literally claimed subject matter by way of one or more further applications including those filed pursuant to the laws of the United States and/or international treaty,
