WO2013115798A1 - Flexible port configuration based on interface coupling - Google Patents

Flexible port configuration based on interface coupling Download PDF

Info

Publication number
WO2013115798A1
WO2013115798A1 PCT/US2012/023347 US2012023347W WO2013115798A1 WO 2013115798 A1 WO2013115798 A1 WO 2013115798A1 US 2012023347 W US2012023347 W US 2012023347W WO 2013115798 A1 WO2013115798 A1 WO 2013115798A1
Authority
WO
WIPO (PCT)
Prior art keywords
port
flexible
input
configuration
interface
Prior art date
Application number
PCT/US2012/023347
Other languages
French (fr)
Inventor
Jonathan D. Bassett
Raphael Gay
Linden H. Mcclure
Original Assignee
Hewlett-Packard Development Company, L.P.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hewlett-Packard Development Company, L.P. filed Critical Hewlett-Packard Development Company, L.P.
Priority to CN201280067226.2A priority Critical patent/CN104054064B/en
Priority to US14/374,681 priority patent/US10140231B2/en
Priority to EP12867016.3A priority patent/EP2810173B1/en
Priority to PCT/US2012/023347 priority patent/WO2013115798A1/en
Priority to TW102103093A priority patent/TWI551994B/en
Publication of WO2013115798A1 publication Critical patent/WO2013115798A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38Information transfer, e.g. on bus
    • G06F13/40Bus structure
    • G06F13/4004Coupling between buses
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38Information transfer, e.g. on bus
    • G06F13/382Information transfer, e.g. on bus using universal interface adapter
    • G06F13/385Information transfer, e.g. on bus using universal interface adapter for adaptation of a particular data processing system to different peripheral devices
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38Information transfer, e.g. on bus
    • G06F13/40Bus structure
    • G06F13/4004Coupling between buses
    • G06F13/4022Coupling between buses using switching circuits, e.g. switching matrix, connection or expansion network
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38Information transfer, e.g. on bus
    • G06F13/40Bus structure
    • G06F13/4063Device-to-bus coupling
    • G06F13/4068Electrical coupling
    • G06F13/4081Live connection to bus, e.g. hot-plugging
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38Information transfer, e.g. on bus
    • G06F13/42Bus transfer protocol, e.g. handshake; Synchronisation
    • G06F13/4204Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus
    • G06F13/4221Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus being an input/output bus, e.g. ISA bus, EISA bus, PCI bus, SCSI bus

Definitions

  • Computing devices today are configured with various Input/Output interfaces. Examples of these interfaces include Peripheral Component Interconnect buses, Universal Serial Buses, and Serial Advanced Technology Attachment buses.
  • An Input/Output Controller can be used to interface between these interfaces and a processor of a computing device.
  • FIGs. 1A and 1 B are block diagrams of computing devices capable of configuring a flexible port based on a detected system configuration, according to various examples
  • FIGs. 2A and 2B are diagrams of computing systems capable of detecting a system configuration based on a physical detection device, according to various examples
  • FIGs. 3A and 3B are diagrams of computing systems capable of detecting a system configuration based on cable detection, according to various examples
  • FIGs. 4A - 4D are diagrams of computing systems capable of detecting a system configuration based on using a daughter card interface, according to various examples;
  • FIGs. 5A and 5B are diagrams of computing systems capable of detecting a system configuration based on the presence of a device, according to various examples;
  • FIGs. 6A and 6B are diagrams of computing systems that can be used to program a flexible port to provide an interface of a particular protocol or provide additional bandwidth to another interface, according to various examples;
  • FIGs. 7A and 7B are diagrams of computing systems capable of detecting a system configuration based on the presence of a chassis or power supply, according to various examples.
  • FIG. 8 is a flowchart of a method for configuring a flexible input/output port based on a detected configuration of a computing system, according to one example.
  • I/O Input/Output
  • Manufacturers use particular hardware, such as processors, I/O Controllers, etc. in their devices. Many of these I/O Controllers permanently define the I/O port types that can be used. Other I/O Controllers allow for flexible ports where one or more of the ports can be configured.
  • a flexible port is a set of I/O connectors (e.g., pins, balls, etc.) of an I/O controller that can be used to provide a first I/O interface using a first protocol or a second I/O interface using a second protocol.
  • I/O controllers can be used to implement the first I/O interface or the second I/O interface.
  • some I/O Controllers may allow a set of pins associated with the hub to be used as a Universal Serial Bus (USB) port, a Peripheral Component Interconnect Express (PCIe) port, a Serial Advanced Technology Attachment (SATA) port, or other ports. This allows a chip manufacturer to reduce the variations of chips that it makes because another chip design need not be used to support the varying ports.
  • PCAs printed circuit assemblies
  • manufacturers may set the flexible ports to permanently define I/O port types to be used. This may be done because supporting hardware would be connected via a printed circuit board and this hardware and/or wire routing would be specialized for particular ports.
  • this approach is not very expandable and can be difficult to customize for a particular user's or system's needs. Further, configuring the ports using user intervention can be time consuming and undesirable for a user.
  • various embodiments disclosed herein relate to detecting a desired I/O configuration of a computing device and configuring a flexible port.
  • the detection of the configuration can include detection based on the coupling of an interface to the flexible port.
  • detection based on the coupling of an interface to the flexible port means that the connection of a component to at least the signals of the flexible port is used to detect the configuration.
  • the coupling of the interface can also include a coupling of a general purpose input/output (GPIO) of the interface connection.
  • GPIO general purpose input/output
  • a GPIO is a generic connector (e.g., a pin) on a chip whose behavior can be controlled using software executable by a controller.
  • the interface is connected internal to the computing device, while in other embodiments, the interface is connected external to the computing device.
  • FIGs. 1A and 1 B are block diagrams of computing devices capable of configuring a flexible port based on a detected system configuration, according to various examples.
  • Computing devices 100a, 100b include components that can be utilized to configure flexible ports based on a system configuration.
  • the respective computing devices 100a, 100b may be a notebook computer, a desktop computer, a server, a workstation, or any other computing device that may use one or more flexible ports.
  • computing device 100a may include an input/output controller 1 10, a system configuration detection module 1 12, and a port configuration module 1 14.
  • computing device 100b can also include a multiplexer 1 16, a processor 130, and a machine-readable storage medium 132.
  • the input/output controller 1 10 can include a flexible port 140.
  • the input/output controller 1 10 is a chip that can connect peripheral components to a processor.
  • the I/O controller 1 10 can be called a Southbridge, an I/O Controller Hub, a Fusion Controller Hub, etc.
  • the I/O controller 1 10 can be incorporated as part of a Northbridge or similar chip or chipset.
  • the I/O controller 1 10 can include a flexible port 140. More than one flexible port 140 can be included in the I/O controller 1 10.
  • a flexible port 140 is a set of pins of the I/O controller 1 10 that can be used to provide a first I/O interface using a first protocol or a second I/O interface using a second protocol.
  • Example interfaces include USB, PCIe, SATA, Small Computer System Interface (SCSI), Integrated Drive Electronics (IDE), PCI, etc.
  • the flexible port 140 can be configured to use the first protocol or the second protocol.
  • the port may be configured to be able to use additional protocols and/or interface. For example a single flexible port may be able to support three different types of interfaces.
  • the system configuration detection module 1 12 can be used to detect a desired input/output configuration of the computing device 100 based on a coupling of an interface to the flexible port 140.
  • the detection of the desired I/O configuration of the computing device 100 based on the coupling of an interface to the flexible port 140 means that the connection of a component of the computing device 100 to at least the signals of the flexible port 140 associated with a protocol is used to detect the configuration.
  • the configuration can be based on trial and error detection done by the computing device 100 (e.g., performed by a Basic Input Output System (BIOS) of the computing devices) or using a hardware configuration as further described in FIGs. 2A - 7B.
  • BIOS Basic Input Output System
  • a multiplexer 1 16 can be used to split one or more signal connectors (e.g., wiring, connections of a Printed Circuit Board (PCB), etc.) of a bus associated with the flexible port 140 to two or more port connectors to avoid conflicts.
  • the use of a multiplexer is not needed.
  • the multiplexer 1 16 is external to the I/O controller 1 10.
  • the multiplexer 1 16 is internal to the I/O controller 1 10.
  • the port connectors can be used to connect the flexible port 140 with a peripheral device or to another connector leading to the peripheral device.
  • the port connectors can be different types of ports using different types of protocols. Examples of port connector types include SATA, PCIe, IDE, SCSI, and USB.
  • the multiplexer 1 16 can be controlled using a selection signal to determine which of the port connectors to connect.
  • the multiplexer 1 16 can also be implemented using one or more transistors that can be turned on/off using a selection signal. When the transistors are turned on, the individual lines of the flexible port 140 are connected to the respective port connector that should be on.
  • the other port connectors connected to the multiplexer 1 16 and/or transistors to connect to the flexible port 140 can be turned off.
  • the system configuration detection module 1 12 can set the flexible port 140 to communicate using a first protocol (e.g., PCIe,
  • the multiplexer 1 16 can also be set to associate the flexible port 140 with a port connector associated with the first protocol.
  • the system configuration detection module 1 12 can then cause the flexible port 140 to perform a component discovery process based on the first protocol. This discovery process can learn if there is a peripheral device connected to the first port connector and/or is compatible with the first protocol.
  • the port configuration module 1 14 can configure the flexible port 140 based on the component discovery process. In certain examples, the discovery of the peripheral device to the first port connector leads to an inference that this is the desired I/O configuration of a user/manufacturer of the computing device 100. Such inferences can be programmed into the system configuration detection module 1 12.
  • the port configuration module 1 14 sets the flexible port 140 to work with the first port connector using the first protocol. In another example, if a peripheral device is not found, the port configuration module 1 14 can perform another task, for example, set the flexible port 140 to a default configuration and/or set the flexible port 140 based on further discovery.
  • the peripheral device is not found using the first protocol.
  • the component discovery process determines that there is an absence of a connected component to the first port.
  • the system configuration detection module 1 12 configures the flexible port 140 to communicate using a second protocol and/or a second port connector. This can include setting the multiplexer 1 16 to connect the second port connector to the flexible port.
  • the system configuration detection module 1 12 can then cause the flexible port 140 to perform a second component discovery process based on the second protocol.
  • the port configuration module 1 14 can then select the second port connector to connect to the bus associated with the flexible port 140 based on the second component discovery process. For example, the selection of the second port connector can occur if a peripheral device is found on at the second port connector.
  • a default condition can be set by the port configuration module 1 14 (e.g., a setting to the first port connector, a setting to the second port connector, a setting to another port connector, disabling the flexible port, etc.).
  • An inference can be made that the default condition is the desired I/O configuration based on the lack of a peripheral device on the first port connector and/or the second port connector.
  • other iterations of the discovery process for example, at a third and/or fourth port connector, can be performed.
  • multiple flexible ports can be set in this manner.
  • the system configuration detection module 1 12 can determine the intended/desired configuration of the flexible port 140 based on other hardware coupling of one or more interfaces to the flexible port 140 as further detailed in FIGs. 2A - 7B. Further, in certain embodiments, the system configuration detection module 1 12 and/or port configuration module 1 14 can be implemented as part of a Basic Input Output System (BIOS) or other firmware executed by the computing device 100. In some embodiments, the examples of FIGs. 2A - 7B can be implemented with the help of a multiplexer. In other embodiments, these examples can be implemented without a multiplexer. In certain examples, a multiplexer can be used to help maintain signal integrity.
  • BIOS Basic Input Output System
  • a multiplexer can be used to prevent physical damage to/from a peripheral device connected to the flexible port to/from another peripheral device and/or the flexible port. This may occur, for example, if the electrical characteristics of a protocol associated with the flexible port are different from the electrical characteristics of a connected peripheral device.
  • a processor 130 such as a central processing unit (CPU) or a microprocessor suitable for retrieval and execution of instructions and/or electronic circuits can be configured to perform the functionality of any of the modules 1 12, 1 14 described herein.
  • instructions and/or other information can be included in machine-readable storage medium 132 or other memory.
  • Input/output interfaces may additionally be provided by the computing device 100b.
  • input devices such as a keyboard, a touch interface, a mouse, a microphone, etc. can be utilized to receive input from an environment surrounding the computing device 100b.
  • an output device such as a display, can be utilized to present information to users. Examples of output devices include speakers, display devices, amplifiers, etc.
  • These input and/or output devices can be configured to be connected via a non- flexible port and/or on the flexible port(s).
  • some components can be utilized to implement functionality of other components described herein.
  • Each of the modules 1 12, 1 14 may include, for example, hardware devices including electronic circuitry for implementing the functionality described herein.
  • each module 1 12, 1 14 may be implemented as a series of instructions encoded on machine-readable storage medium 132 of computing device 100 and executable by processor 130. It should be noted that, in some embodiments, some modules are implemented as hardware devices, while other modules are implemented as executable instructions.
  • Processor 130 may be, at least one central processing unit (CPU), at least one semiconductor-based microprocessor, at least one graphics processing unit (GPU), other hardware devices suitable for retrieval and execution of instructions stored in machine-readable storage medium 132, or combinations thereof.
  • the processor 130 may include multiple cores on a chip, include multiple cores across multiple chips, multiple cores across multiple devices (e.g., if the computing device 100 includes multiple node devices), or combinations thereof.
  • Processor 130 may fetch, decode, and execute instructions to implement system detection, configuration, and implementation tasks.
  • processor 130 may include at least one integrated circuit (IC), other control logic, other electronic circuits, or combinations thereof that include a number of electronic components for performing the functionality of one or more modules.
  • IC integrated circuit
  • Machine-readable storage medium 132 may be any electronic, magnetic, optical, or other physical storage device that contains or stores executable instructions.
  • machine-readable storage medium 132 may be, for example, Random Access Memory (RAM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a storage drive, a Compact Disc Read Only Memory (CD-ROM), and the like.
  • RAM Random Access Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • CD-ROM Compact Disc Read Only Memory
  • the machine- readable storage medium 132 can be non-transitory.
  • machine-readable storage medium 132 may be encoded with a series of executable instructions for performing various tasks, for example, the tasks of FIG. 8.
  • FIGs. 2A and 2B are diagrams of computing systems capable of detecting a system configuration based on a physical detection device, according to various examples.
  • a main system board or PCA 200 can include an I/O controller 202 that has a flexible port (not shown) that is connected to a first port connector 204 and a second port connector 206 via a multiplexer 208.
  • a general purpose input can be connected to a switch 210 that is actuated when hardware, such as a component 212 associated with a first protocol is installed in a computing system 214.
  • the component 212 is a hard drive, an optical drive, a solid state drive, a hybrid drive, etc.
  • the switch When the component is installed in a drive bay, the switch is actuated, triggering a GPIO to a particular state.
  • the state itself can change depending on implementation.
  • This corresponding GPIO can be used to control the flexible port to communicate via the first port connector 204 that has its interface coupled to the component 212.
  • the switch 210 and GPIO can be considered as part as the coupling interface because both are physically connected simultaneously.
  • the GPIO 0, indicating that the second port connector 206 is the desired I/O configuration for flexible port.
  • the flexible port can be configured for the second port connector 206 using a second protocol.
  • the first port connector 204 is a SATA connector and the second port connector 206 is a PCIe slot.
  • the GPIO can be used to directly control the flexible port on the I/O controller 202.
  • the GPIO can be connected to another component, such as a module controlled by a BIOS or other firmware to detect the desired configuration. The module can then be used to program the I/O controller 202.
  • the GPIO states here are shown as 0 and 1 , however, it is contemplated that other states (e.g., 00, 01 , 10, 1 1 , 000, etc.) can be used as GPIO.
  • other input mechanisms can be used.
  • a multi-level coding can be used on the GPIO.
  • the input can be provided to an analog to digital converter to provide state information.
  • the state information can be based on voltage levels of the input instead of being binary. This can be used to add expandability for PCAs.
  • the diagrams shown in FIGs. 3A - 7B can also be implemented in this manner.
  • FIGs. 3A and 3B are diagrams of computing systems capable of detecting a system configuration based on cable detection, according to various examples.
  • Computing system 300 includes a main system board or PCA 302 that can include an I/O controller 304 that includes a flexible port that is connected to a first port connector 306 and a second port connector 308 via a multiplexer 310.
  • the first port connector 306 can be a header.
  • the header can include pins that can be configured to drive a GPIO to a state when a cable 312 is connected.
  • the cable 312 can include a loop back that connects at least two of the header pins together when the cable 312 is connected to the header.
  • the cable coupling with the GPIO as well as the rest of the first port connector 306 can be used to determine the desired input/output configuration of the computing system 300.
  • the state of the GPIO used can vary based on implementation.
  • the flexible port is configured for the first protocol, for example, a USB protocol. If the cable 312 is not present, the first protocol and first port connector 306 is disabled and the second port connector 308 associated with a second protocol, for example, PCIe, is enabled.
  • FIGs. 4A - 4D are diagrams of computing systems capable of detecting a system configuration based on using a daughter card interface, according to various examples.
  • Computing system 400 includes a main PCA 402 that can include I/O controller 404 that includes a flexible port (not shown) that is connected to a first port connector 406 and a second port connector 408 via a multiplexer 410.
  • the first port connector 406 can be considered a board connector that connects to a circuit board, such as daughter PCA 412.
  • the connection of the daughter PCA 412 can change the state of the GPIO used to control the I/O controller 404.
  • the flexible port when the daughter PCA 412 is connected, the flexible port is configured for the first protocol, for example, a PCIe protocol associated with a PCIe port 414 on the daughter PCA 412. Similarly, if the daughter PCA 412 is not connected, the flexible port can be configured for the second port connector 408 using a second protocol, such as SATA.
  • a second protocol such as SATA.
  • Computing system 440 of FIG. 4C is a modification of FIG. 4B.
  • a second port connector 442 can be associated with a second daughter PCA 444.
  • the same port connector 406 can be used to transmit signal information of a second protocol. This can also be based on implementation. For example, when daughter PCA 412 is connected, the GPIO state can be driven to 0, indicating that flexible port and/or a multiplexer should be programmed for the PCIe port 414 to be active. When daughter PCA 444 is installed, the GPIO is at 1 .
  • the flexible port can be programmed to be associated with the second port connector 442 on the daughter PCA 444.
  • this port connector 442 can be configured to be associated with a SATA connection.
  • this port connector 442 can be configured to be associated with a USB protocol, Ethernet, Institute of Electrical and Electronics Engineers (IEEE) 1394, etc.
  • system 460 of FIG. 4D shows a configuration where a cable 462 is used to connect a device 464 via the first port connector 406.
  • the GPIO can be controlled based on the cable 462.
  • This example shows the cable 462 causing a GPIO of 1 , but it is noted that the cable 462 can be used to cause other states.
  • connecting the cable 462 tells a system configuration detection module that the intended configuration is to support the protocol associated with device 464.
  • one cable or multiple cables can be used to provide access to a port connector on a daughter PCA.
  • a connector cable for one type of interface may be used for connecting another type of interface on the daughter PCA if the specifications of the protocol are met.
  • one or more SATA connectors may be used to connect a PCIe port.
  • FIGs. 5A and 5B are diagrams of computing systems capable of detecting a system configuration based on the presence of a device, according to various examples.
  • Computing system 500 includes a PCA 502 that can include an I/O controller 504 with a flexible port that is connected to a first port connector 506 and a second port connector 508 via a multiplexer 510.
  • the first port connector 506 can use the ground plane of a card inserted into the first port connector 506 to determine a GPIO used to set a flexible port of the I/O controller 504.
  • the first port connector 506 can replace a ground pin associated with a card 512 that can be considered a peripheral device with the GPIO signal.
  • the ground plane connects the GPIO to ground.
  • the GPIO is set to 0, which can be a state that a system configuration detection module can associate with activating the flexible port and multiplexer 510 to work with the first port connector 506 using a first protocol. If the card 512 is not inserted, the GPIO can change state to 1 and the second port connector 508 associated with a second protocol can be activated.
  • FIGs. 6A and 6B are diagrams of computing systems that can be used to program a flexible port to provide an interface of a particular protocol or provide additional bandwidth to another interface, according to various examples.
  • Computing system 600 includes PCA 602 that can include an I/O controller 604 with a flexible port connected to a first port connector 606 and a PCIe port 608 via a multiplexer 610.
  • the first port connector 606 is associated with the SATA protocol; however, it is contemplated that other protocols can be used.
  • the computing system 600 shows that the GPIO includes a state that changes based on the coupling of an interface.
  • the GPIO is triggered using a switch 61 1 that is actuated when a SATA device 612 is inserted into a device bay, however, other methods of triggering the GPIO are contemplated.
  • the flexible port can be configured to use the first port connector 606 based on the GPIO.
  • the PCIe port 608 can be configured using a fixed port and/or another flexible port of the I/O controller 604.
  • the GPIO can be used to configure the flexible port to expand bandwidth capacity of the bus associated with the PCIe slot 608.
  • the PCIe slot 608 when the SATA device 612 is present, the PCIe slot 608 is an x1 slot, but when the SATA device 612 is not present, the PCIe slot 608 is an x2 slot. Similar bandwidth expansion may be used for other protocols and connectors.
  • FIGs. 7A and 7B are diagrams of computing systems capable of detecting a system configuration based on the presence of a chassis or power supply, according to various examples.
  • Computing system 700 includes a PCA 702 that includes an I/O controller 704 with a flexible port connected to a first port connector 706 and a second port connector 708 via a multiplexer 710.
  • a GPIO used to control the flexible port can be based, at least in part, on the chassis and/or power supply used for the computing system 700.
  • the PCA may also include a board connector 712 that can be connected to a chassis and/or power supply.
  • the board connector 712 can be connected via a chassis and/or power supply cable 714 to a first chassis and/or power supply 716.
  • the cable can include a loopback to connect a pin associated with the GPIO with a state, such as a ground state. As such, the loopback changes the state of the GPIO to 0.
  • This can provide information to a system configuration detection module about the chassis and/or power supply (PSU).
  • the GPIO can represent that the chassis has a slot to enable the second port connector 708.
  • the GPIO can represent that the power supply has enough power to enable the second port connector 708. This can be used to change default configuration parameters of the flexible port.
  • the first port connector to be looked at for a desired I/O configuration may be the second port connector 708 because of the GPIO.
  • the GPIO can be used to select the flexible port configuration and/or to disable one of the possible configurations for the flexible port configuration.
  • a chassis and/or PSU cable 718 is connected to a second chassis and/or power supply 720.
  • This chassis/PSU cable 718 does not have a loopback to connect the GPIO pin of the board connector 712 to ground.
  • the GPIO input is set to a state of one.
  • the state can tell a system configuration detection module about other information associated with the chassis and/or power supply.
  • the GPIO can represent that the chassis does not have a slot to enable the second port connector 708.
  • the GPIO can represent that the power supply does not have enough power to enable the second port connector 708.
  • this can be used to change default configuration parameters of the flexible port and/or multiplexer 710.
  • the system configuration detection module can determine a desired configuration based on a preference to a protocol associated with the first port connector 706 because of the information about the second port connector 708.
  • FIG. 8 is a flowchart of a method for configuring a flexible input/output port based on a detected configuration of a computing system, according to one example.
  • execution of method 800 is described below with reference to computing device 100, other suitable components for execution of method 800 can be utilized.
  • Method 800 may be implemented in the form of executable instructions stored on a machine-readable storage medium, such as storage medium 132, and/or in the form of electronic circuitry.
  • Method 800 may start at 802 and proceed to 804, where the computing device may be booted via a boot process.
  • a flexible port 140 or multiple flexible ports of an I/O controller 1 10 can be configured.
  • the method 800 can continue to 806 where, during the boot process, an I/O configuration of the computing device is detected based on a coupling of an interface to a flexible input/output port.
  • the detected I/O configuration can be a desired I/O configuration, for example, a configuration intended based on the system components at boot time.
  • the detected configuration can be based on a trial and error system of searching for connected peripheral devices or based on state information received from coupling information about the interface.
  • the coupling information received representing a first state shows that no device or component has been coupled to the interface while coupling information received representing a second state shows that a device or component has been coupled.
  • the states can represent particular desired system I/O configurations.
  • the state information can be used to determine whether the configuration is associated with a first daughter card or a second daughter card. Examples of methods to detect state information can be found in FIGs. 2A - 7B. Further, as noted above, multiple flexible I/O ports may be configured using these techniques.
  • the coupling information is based on the trial and error system.
  • a system configuration detection module 1 12 can set a multiplexer 1 16 connected to the flexible port 140 to communicate via a first interface.
  • the flexible port 140 can also be configured to communicate via the first interface.
  • a component discovery process can be performed on the first interface to determine if a peripheral device is connected. If a peripheral device is detected, the desired I/O configuration for the computing device 100 can be determined to use the first interface. If it is determined that a peripheral device is not detected via the first interface, the multiplexer 1 16 can be set to communicate with a second interface and the flexible port 140 can be set to work with the second interface.
  • this can be a default condition if the peripheral device was not found on the first interface.
  • a second component discovery process can be performed on the second interface. If a peripheral device is found on the second interface, the desired I/O configuration can be considered to use the second interface. In another embodiment, if the peripheral device is not found, other iterations of changing the multiplexer 1 16 and checking the connected interface can occur. Further, a default configuration (e.g., use the first interface, use the second interface, etc.) can be selected as the intended or desired configuration based on the lack of a peripheral device on the buses.
  • the flexible port 140 can be configured based on the detected desired I/O configuration.
  • the flexible port 140 can be configured to conform to a protocol associated with an interface associated with the detected configuration.
  • the desired I/O configuration can be based on GPIO, trial and error, or a combination thereof.
  • the method 800 can stop.
  • the computing device 100 can continue to perform other functionality.
  • the boot process can perform other startup features, such as handing off control of the computing device 100 to an operating system.
  • a manufacturer of a printed circuit assembly can use a flexible I/O port with various configurations.
  • I/O configuration can be performed by automatically detecting a system configuration at boot time instead of setting I/O configuration at PCA manufacture or using manual configuration. This can allow a PCA manufacturer to reuse the same PCA for varying systems. This implementation can also allow the manufacturer to reuse a PCB and/or PCA for various systems.

Abstract

Example embodiments disclosed herein relate to configuring a flexible port. The configuration of a computing device is detected based on a coupling of an interface to a flexible input/output port. The flexible input/output port is configured based on the detected configuration of the computing device.

Description

FLEXIBLE PORT CONFIGURATION BASED ON
INTERFACE COUPLING
BACKGROUND
[0001 ] Computing devices today are configured with various Input/Output interfaces. Examples of these interfaces include Peripheral Component Interconnect buses, Universal Serial Buses, and Serial Advanced Technology Attachment buses. An Input/Output Controller can be used to interface between these interfaces and a processor of a computing device.
BRIEF DESCRIPTION OF THE DRAWINGS
[0002] The following detailed description references the drawings, wherein:
[0003] FIGs. 1A and 1 B are block diagrams of computing devices capable of configuring a flexible port based on a detected system configuration, according to various examples;
[0004] FIGs. 2A and 2B are diagrams of computing systems capable of detecting a system configuration based on a physical detection device, according to various examples;
[0005] FIGs. 3A and 3B are diagrams of computing systems capable of detecting a system configuration based on cable detection, according to various examples;
[0006] FIGs. 4A - 4D are diagrams of computing systems capable of detecting a system configuration based on using a daughter card interface, according to various examples; [0007] FIGs. 5A and 5B are diagrams of computing systems capable of detecting a system configuration based on the presence of a device, according to various examples;
[0008] FIGs. 6A and 6B are diagrams of computing systems that can be used to program a flexible port to provide an interface of a particular protocol or provide additional bandwidth to another interface, according to various examples;
[0009] FIGs. 7A and 7B are diagrams of computing systems capable of detecting a system configuration based on the presence of a chassis or power supply, according to various examples; and
[0010] FIG. 8 is a flowchart of a method for configuring a flexible input/output port based on a detected configuration of a computing system, according to one example.
DETAILED DESCRIPTION
[001 1] Many computing systems today are configured to use various Input/Output (I/O) interfaces. Manufacturers use particular hardware, such as processors, I/O Controllers, etc. in their devices. Many of these I/O Controllers permanently define the I/O port types that can be used. Other I/O Controllers allow for flexible ports where one or more of the ports can be configured. In certain embodiments, a flexible port is a set of I/O connectors (e.g., pins, balls, etc.) of an I/O controller that can be used to provide a first I/O interface using a first protocol or a second I/O interface using a second protocol. Additional I/O connectors of the I/O controller can be used to implement the first I/O interface or the second I/O interface. In one example, some I/O Controllers may allow a set of pins associated with the hub to be used as a Universal Serial Bus (USB) port, a Peripheral Component Interconnect Express (PCIe) port, a Serial Advanced Technology Attachment (SATA) port, or other ports. This allows a chip manufacturer to reduce the variations of chips that it makes because another chip design need not be used to support the varying ports. [0012] Manufacturers develop printed circuit assemblies (PCAs), such as system boards, to work with I/O controllers and/or processors associated with the hubs. When a PCA is assembled, manufacturers may set the flexible ports to permanently define I/O port types to be used. This may be done because supporting hardware would be connected via a printed circuit board and this hardware and/or wire routing would be specialized for particular ports. However, this approach is not very expandable and can be difficult to customize for a particular user's or system's needs. Further, configuring the ports using user intervention can be time consuming and undesirable for a user.
[0013] Accordingly, various embodiments disclosed herein relate to detecting a desired I/O configuration of a computing device and configuring a flexible port. The detection of the configuration can include detection based on the coupling of an interface to the flexible port. In one embodiment, detection based on the coupling of an interface to the flexible port means that the connection of a component to at least the signals of the flexible port is used to detect the configuration. In one example, the coupling of the interface can also include a coupling of a general purpose input/output (GPIO) of the interface connection. In certain embodiments, a GPIO is a generic connector (e.g., a pin) on a chip whose behavior can be controlled using software executable by a controller. Further, in some embodiments, the interface is connected internal to the computing device, while in other embodiments, the interface is connected external to the computing device.
[0014] Referring now to the drawings, FIGs. 1A and 1 B are block diagrams of computing devices capable of configuring a flexible port based on a detected system configuration, according to various examples. Computing devices 100a, 100b include components that can be utilized to configure flexible ports based on a system configuration. The respective computing devices 100a, 100b may be a notebook computer, a desktop computer, a server, a workstation, or any other computing device that may use one or more flexible ports. In certain embodiments, computing device 100a may include an input/output controller 1 10, a system configuration detection module 1 12, and a port configuration module 1 14. In another embodiment, computing device 100b can also include a multiplexer 1 16, a processor 130, and a machine-readable storage medium 132. The input/output controller 1 10 can include a flexible port 140.
[0015] In certain embodiments, the input/output controller 1 10 is a chip that can connect peripheral components to a processor. In certain examples, the I/O controller 1 10 can be called a Southbridge, an I/O Controller Hub, a Fusion Controller Hub, etc. In other examples, the I/O controller 1 10 can be incorporated as part of a Northbridge or similar chip or chipset.
[0016] As noted, the I/O controller 1 10 can include a flexible port 140. More than one flexible port 140 can be included in the I/O controller 1 10. As noted, in certain examples, a flexible port 140 is a set of pins of the I/O controller 1 10 that can be used to provide a first I/O interface using a first protocol or a second I/O interface using a second protocol. Example interfaces include USB, PCIe, SATA, Small Computer System Interface (SCSI), Integrated Drive Electronics (IDE), PCI, etc. The flexible port 140 can be configured to use the first protocol or the second protocol. In certain examples, the port may be configured to be able to use additional protocols and/or interface. For example a single flexible port may be able to support three different types of interfaces.
[0017] The system configuration detection module 1 12 can be used to detect a desired input/output configuration of the computing device 100 based on a coupling of an interface to the flexible port 140. In certain examples, the detection of the desired I/O configuration of the computing device 100 based on the coupling of an interface to the flexible port 140 means that the connection of a component of the computing device 100 to at least the signals of the flexible port 140 associated with a protocol is used to detect the configuration. The configuration can be based on trial and error detection done by the computing device 100 (e.g., performed by a Basic Input Output System (BIOS) of the computing devices) or using a hardware configuration as further described in FIGs. 2A - 7B.
[0018] In one example, when the computing device 100 boots, the BIOS or other firmware causes the computing device to use trial and error detection. A multiplexer 1 16 can be used to split one or more signal connectors (e.g., wiring, connections of a Printed Circuit Board (PCB), etc.) of a bus associated with the flexible port 140 to two or more port connectors to avoid conflicts. However, in certain embodiments, the use of a multiplexer is not needed. In certain examples, the multiplexer 1 16 is external to the I/O controller 1 10. In other examples, the multiplexer 1 16 is internal to the I/O controller 1 10. The port connectors can be used to connect the flexible port 140 with a peripheral device or to another connector leading to the peripheral device. The port connectors can be different types of ports using different types of protocols. Examples of port connector types include SATA, PCIe, IDE, SCSI, and USB. The multiplexer 1 16 can be controlled using a selection signal to determine which of the port connectors to connect. The multiplexer 1 16 can also be implemented using one or more transistors that can be turned on/off using a selection signal. When the transistors are turned on, the individual lines of the flexible port 140 are connected to the respective port connector that should be on. The other port connectors connected to the multiplexer 1 16 and/or transistors to connect to the flexible port 140 can be turned off.
[0019] During the boot process, the system configuration detection module 1 12 can set the flexible port 140 to communicate using a first protocol (e.g., PCIe,
USB, SATA, etc.). The multiplexer 1 16 can also be set to associate the flexible port 140 with a port connector associated with the first protocol. The system configuration detection module 1 12 can then cause the flexible port 140 to perform a component discovery process based on the first protocol. This discovery process can learn if there is a peripheral device connected to the first port connector and/or is compatible with the first protocol. The port configuration module 1 14 can configure the flexible port 140 based on the component discovery process. In certain examples, the discovery of the peripheral device to the first port connector leads to an inference that this is the desired I/O configuration of a user/manufacturer of the computing device 100. Such inferences can be programmed into the system configuration detection module 1 12. In one example, if a peripheral device is found, the port configuration module 1 14 sets the flexible port 140 to work with the first port connector using the first protocol. In another example, if a peripheral device is not found, the port configuration module 1 14 can perform another task, for example, set the flexible port 140 to a default configuration and/or set the flexible port 140 based on further discovery.
[0020] In one example, the peripheral device is not found using the first protocol. As such, the component discovery process determines that there is an absence of a connected component to the first port. The system configuration detection module 1 12 configures the flexible port 140 to communicate using a second protocol and/or a second port connector. This can include setting the multiplexer 1 16 to connect the second port connector to the flexible port. The system configuration detection module 1 12 can then cause the flexible port 140 to perform a second component discovery process based on the second protocol. The port configuration module 1 14 can then select the second port connector to connect to the bus associated with the flexible port 140 based on the second component discovery process. For example, the selection of the second port connector can occur if a peripheral device is found on at the second port connector. If no peripheral device is found using the first and/or second port connector, a default condition can be set by the port configuration module 1 14 (e.g., a setting to the first port connector, a setting to the second port connector, a setting to another port connector, disabling the flexible port, etc.). An inference can be made that the default condition is the desired I/O configuration based on the lack of a peripheral device on the first port connector and/or the second port connector. Further, other iterations of the discovery process, for example, at a third and/or fourth port connector, can be performed. Moreover, multiple flexible ports can be set in this manner.
[0021 ] In certain examples, the system configuration detection module 1 12 can determine the intended/desired configuration of the flexible port 140 based on other hardware coupling of one or more interfaces to the flexible port 140 as further detailed in FIGs. 2A - 7B. Further, in certain embodiments, the system configuration detection module 1 12 and/or port configuration module 1 14 can be implemented as part of a Basic Input Output System (BIOS) or other firmware executed by the computing device 100. In some embodiments, the examples of FIGs. 2A - 7B can be implemented with the help of a multiplexer. In other embodiments, these examples can be implemented without a multiplexer. In certain examples, a multiplexer can be used to help maintain signal integrity. In other examples, a multiplexer can be used to prevent physical damage to/from a peripheral device connected to the flexible port to/from another peripheral device and/or the flexible port. This may occur, for example, if the electrical characteristics of a protocol associated with the flexible port are different from the electrical characteristics of a connected peripheral device.
[0022] A processor 130, such as a central processing unit (CPU) or a microprocessor suitable for retrieval and execution of instructions and/or electronic circuits can be configured to perform the functionality of any of the modules 1 12, 1 14 described herein. In certain scenarios, instructions and/or other information, such as port configuration information, can be included in machine-readable storage medium 132 or other memory. Input/output interfaces may additionally be provided by the computing device 100b. For example, input devices, such as a keyboard, a touch interface, a mouse, a microphone, etc. can be utilized to receive input from an environment surrounding the computing device 100b. Further, an output device, such as a display, can be utilized to present information to users. Examples of output devices include speakers, display devices, amplifiers, etc. These input and/or output devices can be configured to be connected via a non- flexible port and/or on the flexible port(s). Moreover, in certain embodiments, some components can be utilized to implement functionality of other components described herein.
[0023] Each of the modules 1 12, 1 14 may include, for example, hardware devices including electronic circuitry for implementing the functionality described herein. In addition or as an alternative, each module 1 12, 1 14 may be implemented as a series of instructions encoded on machine-readable storage medium 132 of computing device 100 and executable by processor 130. It should be noted that, in some embodiments, some modules are implemented as hardware devices, while other modules are implemented as executable instructions. [0024] Processor 130 may be, at least one central processing unit (CPU), at least one semiconductor-based microprocessor, at least one graphics processing unit (GPU), other hardware devices suitable for retrieval and execution of instructions stored in machine-readable storage medium 132, or combinations thereof. For example, the processor 130 may include multiple cores on a chip, include multiple cores across multiple chips, multiple cores across multiple devices (e.g., if the computing device 100 includes multiple node devices), or combinations thereof. Processor 130 may fetch, decode, and execute instructions to implement system detection, configuration, and implementation tasks. As an alternative or in addition to retrieving and executing instructions, processor 130 may include at least one integrated circuit (IC), other control logic, other electronic circuits, or combinations thereof that include a number of electronic components for performing the functionality of one or more modules.
[0025] Machine-readable storage medium 132 may be any electronic, magnetic, optical, or other physical storage device that contains or stores executable instructions. Thus, machine-readable storage medium 132 may be, for example, Random Access Memory (RAM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a storage drive, a Compact Disc Read Only Memory (CD-ROM), and the like. As such, the machine- readable storage medium 132 can be non-transitory. As described in detail herein, machine-readable storage medium 132 may be encoded with a series of executable instructions for performing various tasks, for example, the tasks of FIG. 8.
[0026] FIGs. 2A and 2B are diagrams of computing systems capable of detecting a system configuration based on a physical detection device, according to various examples. A main system board or PCA 200 can include an I/O controller 202 that has a flexible port (not shown) that is connected to a first port connector 204 and a second port connector 206 via a multiplexer 208. A general purpose input can be connected to a switch 210 that is actuated when hardware, such as a component 212 associated with a first protocol is installed in a computing system 214. In one example, the component 212 is a hard drive, an optical drive, a solid state drive, a hybrid drive, etc. When the component is installed in a drive bay, the switch is actuated, triggering a GPIO to a particular state. The state itself can change depending on implementation. In the example of FIG. 2A, the state is the GPIO = 1 . This corresponding GPIO can be used to control the flexible port to communicate via the first port connector 204 that has its interface coupled to the component 212. In certain scenarios, the switch 210 and GPIO can be considered as part as the coupling interface because both are physically connected simultaneously. In the example of FIG. 2B, the GPIO = 0, indicating that the second port connector 206 is the desired I/O configuration for flexible port. As such, the flexible port can be configured for the second port connector 206 using a second protocol. In one example, the first port connector 204 is a SATA connector and the second port connector 206 is a PCIe slot.
[0027] In certain examples, the GPIO can be used to directly control the flexible port on the I/O controller 202. In other examples, the GPIO can be connected to another component, such as a module controlled by a BIOS or other firmware to detect the desired configuration. The module can then be used to program the I/O controller 202. Further, for simplicity, the GPIO states here are shown as 0 and 1 , however, it is contemplated that other states (e.g., 00, 01 , 10, 1 1 , 000, etc.) can be used as GPIO. Moreover, other input mechanisms can be used. In one example, a multi-level coding can be used on the GPIO. For example, the input can be provided to an analog to digital converter to provide state information. The state information can be based on voltage levels of the input instead of being binary. This can be used to add expandability for PCAs. The diagrams shown in FIGs. 3A - 7B can also be implemented in this manner.
[0028] FIGs. 3A and 3B are diagrams of computing systems capable of detecting a system configuration based on cable detection, according to various examples. Computing system 300 includes a main system board or PCA 302 that can include an I/O controller 304 that includes a flexible port that is connected to a first port connector 306 and a second port connector 308 via a multiplexer 310. In this example, the first port connector 306 can be a header. The header can include pins that can be configured to drive a GPIO to a state when a cable 312 is connected. The cable 312 can include a loop back that connects at least two of the header pins together when the cable 312 is connected to the header. The cable coupling with the GPIO as well as the rest of the first port connector 306 can be used to determine the desired input/output configuration of the computing system 300. As noted above, the state of the GPIO used can vary based on implementation. In this example, when the cable 312 is used to connect a component 314 or connector on a chassis to the header, the flexible port is configured for the first protocol, for example, a USB protocol. If the cable 312 is not present, the first protocol and first port connector 306 is disabled and the second port connector 308 associated with a second protocol, for example, PCIe, is enabled.
[0029] FIGs. 4A - 4D are diagrams of computing systems capable of detecting a system configuration based on using a daughter card interface, according to various examples. Computing system 400 includes a main PCA 402 that can include I/O controller 404 that includes a flexible port (not shown) that is connected to a first port connector 406 and a second port connector 408 via a multiplexer 410. In this example, the first port connector 406 can be considered a board connector that connects to a circuit board, such as daughter PCA 412. The connection of the daughter PCA 412 can change the state of the GPIO used to control the I/O controller 404. As such, when the daughter PCA 412 is connected, the flexible port is configured for the first protocol, for example, a PCIe protocol associated with a PCIe port 414 on the daughter PCA 412. Similarly, if the daughter PCA 412 is not connected, the flexible port can be configured for the second port connector 408 using a second protocol, such as SATA.
[0030] Computing system 440 of FIG. 4C is a modification of FIG. 4B. In this scenario, instead of the second port connector 408 being associated with the main PCA 402, a second port connector 442 can be associated with a second daughter PCA 444. In this scenario, the same port connector 406 can be used to transmit signal information of a second protocol. This can also be based on implementation. For example, when daughter PCA 412 is connected, the GPIO state can be driven to 0, indicating that flexible port and/or a multiplexer should be programmed for the PCIe port 414 to be active. When daughter PCA 444 is installed, the GPIO is at 1 . As such, the flexible port can be programmed to be associated with the second port connector 442 on the daughter PCA 444. In one example, this port connector 442 can be configured to be associated with a SATA connection. In other examples, this port connector 442 can be configured to be associated with a USB protocol, Ethernet, Institute of Electrical and Electronics Engineers (IEEE) 1394, etc.
[0031 ] Similarly, system 460 of FIG. 4D shows a configuration where a cable 462 is used to connect a device 464 via the first port connector 406. The GPIO can be controlled based on the cable 462. This example shows the cable 462 causing a GPIO of 1 , but it is noted that the cable 462 can be used to cause other states. In this example, connecting the cable 462 tells a system configuration detection module that the intended configuration is to support the protocol associated with device 464. In some examples, one cable or multiple cables can be used to provide access to a port connector on a daughter PCA. Further, a connector cable for one type of interface may be used for connecting another type of interface on the daughter PCA if the specifications of the protocol are met. For example, one or more SATA connectors may be used to connect a PCIe port.
[0032] FIGs. 5A and 5B are diagrams of computing systems capable of detecting a system configuration based on the presence of a device, according to various examples. Computing system 500 includes a PCA 502 that can include an I/O controller 504 with a flexible port that is connected to a first port connector 506 and a second port connector 508 via a multiplexer 510. In this example, the first port connector 506 can use the ground plane of a card inserted into the first port connector 506 to determine a GPIO used to set a flexible port of the I/O controller 504. In this example, the first port connector 506 can replace a ground pin associated with a card 512 that can be considered a peripheral device with the GPIO signal. As such, when the card 512 is inserted, the ground plane connects the GPIO to ground. The GPIO is set to 0, which can be a state that a system configuration detection module can associate with activating the flexible port and multiplexer 510 to work with the first port connector 506 using a first protocol. If the card 512 is not inserted, the GPIO can change state to 1 and the second port connector 508 associated with a second protocol can be activated.
[0033] FIGs. 6A and 6B are diagrams of computing systems that can be used to program a flexible port to provide an interface of a particular protocol or provide additional bandwidth to another interface, according to various examples. Computing system 600 includes PCA 602 that can include an I/O controller 604 with a flexible port connected to a first port connector 606 and a PCIe port 608 via a multiplexer 610. In this example, the first port connector 606 is associated with the SATA protocol; however, it is contemplated that other protocols can be used. The computing system 600 shows that the GPIO includes a state that changes based on the coupling of an interface. In this example, the GPIO is triggered using a switch 61 1 that is actuated when a SATA device 612 is inserted into a device bay, however, other methods of triggering the GPIO are contemplated. When the SATA device 612 is present, the flexible port can be configured to use the first port connector 606 based on the GPIO. In this configuration, the PCIe port 608 can be configured using a fixed port and/or another flexible port of the I/O controller 604. When the SATA device 612 is not present, the GPIO can be used to configure the flexible port to expand bandwidth capacity of the bus associated with the PCIe slot 608. As such, in one example, when the SATA device 612 is present, the PCIe slot 608 is an x1 slot, but when the SATA device 612 is not present, the PCIe slot 608 is an x2 slot. Similar bandwidth expansion may be used for other protocols and connectors.
[0034] FIGs. 7A and 7B are diagrams of computing systems capable of detecting a system configuration based on the presence of a chassis or power supply, according to various examples. Computing system 700 includes a PCA 702 that includes an I/O controller 704 with a flexible port connected to a first port connector 706 and a second port connector 708 via a multiplexer 710. In this example, a GPIO used to control the flexible port can be based, at least in part, on the chassis and/or power supply used for the computing system 700. The PCA may also include a board connector 712 that can be connected to a chassis and/or power supply. [0035] In the example of FIG. 7A, the board connector 712 can be connected via a chassis and/or power supply cable 714 to a first chassis and/or power supply 716. The cable can include a loopback to connect a pin associated with the GPIO with a state, such as a ground state. As such, the loopback changes the state of the GPIO to 0. This can provide information to a system configuration detection module about the chassis and/or power supply (PSU). In one example, the GPIO can represent that the chassis has a slot to enable the second port connector 708. In another example, the GPIO can represent that the power supply has enough power to enable the second port connector 708. This can be used to change default configuration parameters of the flexible port. For example, the first port connector to be looked at for a desired I/O configuration may be the second port connector 708 because of the GPIO. In certain other examples, the GPIO can be used to select the flexible port configuration and/or to disable one of the possible configurations for the flexible port configuration.
[0036] In the example of FIG. 7B, a chassis and/or PSU cable 718 is connected to a second chassis and/or power supply 720. This chassis/PSU cable 718 does not have a loopback to connect the GPIO pin of the board connector 712 to ground. As such, the GPIO input is set to a state of one. The state can tell a system configuration detection module about other information associated with the chassis and/or power supply. In one example, the GPIO can represent that the chassis does not have a slot to enable the second port connector 708. In another example, the GPIO can represent that the power supply does not have enough power to enable the second port connector 708. Further, this can be used to change default configuration parameters of the flexible port and/or multiplexer 710. For example, the system configuration detection module can determine a desired configuration based on a preference to a protocol associated with the first port connector 706 because of the information about the second port connector 708.
[0037] FIG. 8 is a flowchart of a method for configuring a flexible input/output port based on a detected configuration of a computing system, according to one example. Although execution of method 800 is described below with reference to computing device 100, other suitable components for execution of method 800 can be utilized. Method 800 may be implemented in the form of executable instructions stored on a machine-readable storage medium, such as storage medium 132, and/or in the form of electronic circuitry.
[0038] Method 800 may start at 802 and proceed to 804, where the computing device may be booted via a boot process. During the boot process, a flexible port 140 or multiple flexible ports of an I/O controller 1 10 can be configured.
[0039] The method 800 can continue to 806 where, during the boot process, an I/O configuration of the computing device is detected based on a coupling of an interface to a flexible input/output port. The detected I/O configuration can be a desired I/O configuration, for example, a configuration intended based on the system components at boot time. As noted above, the detected configuration can be based on a trial and error system of searching for connected peripheral devices or based on state information received from coupling information about the interface.
[0040] In one example, the coupling information received representing a first state shows that no device or component has been coupled to the interface while coupling information received representing a second state shows that a device or component has been coupled. In certain embodiments, the states can represent particular desired system I/O configurations. In one example, the state information can be used to determine whether the configuration is associated with a first daughter card or a second daughter card. Examples of methods to detect state information can be found in FIGs. 2A - 7B. Further, as noted above, multiple flexible I/O ports may be configured using these techniques.
[0041 ] In another example, the coupling information is based on the trial and error system. As such, a system configuration detection module 1 12 can set a multiplexer 1 16 connected to the flexible port 140 to communicate via a first interface. The flexible port 140 can also be configured to communicate via the first interface. Then a component discovery process can be performed on the first interface to determine if a peripheral device is connected. If a peripheral device is detected, the desired I/O configuration for the computing device 100 can be determined to use the first interface. If it is determined that a peripheral device is not detected via the first interface, the multiplexer 1 16 can be set to communicate with a second interface and the flexible port 140 can be set to work with the second interface. In certain scenarios, this can be a default condition if the peripheral device was not found on the first interface. In other scenarios, a second component discovery process can be performed on the second interface. If a peripheral device is found on the second interface, the desired I/O configuration can be considered to use the second interface. In another embodiment, if the peripheral device is not found, other iterations of changing the multiplexer 1 16 and checking the connected interface can occur. Further, a default configuration (e.g., use the first interface, use the second interface, etc.) can be selected as the intended or desired configuration based on the lack of a peripheral device on the buses.
[0042] Then, at 808, the flexible port 140 can be configured based on the detected desired I/O configuration. As such, the flexible port 140 can be configured to conform to a protocol associated with an interface associated with the detected configuration. As noted, the desired I/O configuration can be based on GPIO, trial and error, or a combination thereof.
[0043] Then, at 810, the method 800 can stop. The computing device 100 can continue to perform other functionality. For example, the boot process can perform other startup features, such as handing off control of the computing device 100 to an operating system.
[0044] With the approaches above, a manufacturer of a printed circuit assembly can use a flexible I/O port with various configurations. As such, I/O configuration can be performed by automatically detecting a system configuration at boot time instead of setting I/O configuration at PCA manufacture or using manual configuration. This can allow a PCA manufacturer to reuse the same PCA for varying systems. This implementation can also allow the manufacturer to reuse a PCB and/or PCA for various systems.

Claims

CLAIMS What is claimed is:
1 . A computing device comprising:
an input/output controller including a flexible port;
a system configuration detection module to detect a desired input/output configuration of the computing device based on a coupling of an interface to the flexible port; and
a port configuration module to configure the flexible port based on the detected desired input/output configuration.
2. The computing device of claim 1 , further comprising:
a multiplexer, wherein a bus associated with the flexible port is connected to the multiplexer,
wherein the multiplexer is further connected to a first port connector and a second port connector,
wherein the port configuration module configures the flexible port to communicate using a first protocol,
wherein the system configuration detection module selects the first port connector to connect to the bus and causes the flexible port to perform a component discovery process based on the first protocol, and
wherein the port configuration module configures the flexible port based on the component discovery process.
3. The computing device of claim 2,
wherein the component discovery process determines an absence of a connected component,
wherein the system configuration detection module configures the flexible port to communicate using a second protocol and causes the flexible port to perform a second component discovery process based on the second protocol, and wherein the port configuration module selects the second port connector to connect to the bus based on the second component discovery process.
4. The computing device of claim 1 , further comprising:
a general purpose input connected to a switch that is actuated when hardware associated with a first protocol is installed,
wherein the detection of the desired input/output configuration is based on the general purpose input.
5. The computing device of claim 1 , further comprising:
a general purpose input connected to a pin associated with a header,
wherein when an interface cable associated with a first protocol is connected to the header, the general purpose input is pulled to a state, and
wherein the detection of the desired input/output configuration is based on the state.
6. The computing device of claim 1 , further comprising:
a general purpose input including a state that changes based on the coupling of the interface,
wherein if the state indicates that a component associated with a first protocol is not present, the port configuration module configures the flexible port to expand bandwidth capacity of a bus associated with a second protocol.
7. The computing device of claim 1 , further comprising:
a general purpose input connected to a pin associated with a board connector, wherein when a circuit board is connected via the board connector, the general purpose input is pulled to a state, and
wherein the detection of the desired input/output configuration is based on the state.
8. The computing device of claim 1 , further comprising:
a general purpose input connected to a pin associated with a board connector, wherein when at least one of a chassis and a power supply is connected via the board connector, the general purpose input is pulled to a state, and wherein the detection of the desired input/output configuration is further based on the state.
9. A method comprising:
booting a computing device via a boot process;
during the boot process, detecting an input/output configuration of the computing device based on a coupling of an interface to a flexible input/output port; and
configuring the flexible input/output port based on the detected input/output configuration.
10. The method of claim 9, further comprising:
setting a multiplexer connected to the flexible input/output port to communicate via a first interface; and
performing a component discovery process on the first interface,
wherein the configuration of the flexible input/output port is based on the component discovery process.
1 1 . The method of claim 10, further comprising:
determining that a component is not connected via the first interface;
setting the multiplexer connected to the flexible input/output port to communicate via a second interface; and
performing a second component discovery process on the second interface, wherein the configuration of the flexible input/output port is further based on the second component discovery process.
12. A non-transitory machine-readable storage medium storing instructions that, if executed by at least one processor of a device, cause the device to: initiate a boot process to boot the device;
during the boot process, detect a desired input/output configuration of the device based on coupling information of an interface to a flexible input/output port; and
configure the flexible input/output port to conform to a protocol associated with the detected desired input/output configuration.
13. The non-transitory machine-readable storage medium of claim 12, further comprising instructions that, if executed by the at least one processor, cause the device to:
receive state information of an input associated with the interface, wherein the detection of the input/output configuration is based on the state information.
14. The non-transitory machine-readable storage medium of claim 13, wherein the state information is based on a switch that is actuated when hardware associated with a first protocol is installed.
15. The non-transitory machine-readable storage medium of claim 12, further comprising instructions that, if executed by the at least one processor, cause the device to:
set a multiplexer connected to the flexible input/output port to communicate via a first interface;
initiate a component discovery process on the first interface,
wherein the flexible input/output port is configured to work with the first interface if a component is detected.
PCT/US2012/023347 2012-01-31 2012-01-31 Flexible port configuration based on interface coupling WO2013115798A1 (en)

Priority Applications (5)

Application Number Priority Date Filing Date Title
CN201280067226.2A CN104054064B (en) 2012-01-31 2012-01-31 Flexible port configuration based on interface coupling
US14/374,681 US10140231B2 (en) 2012-01-31 2012-01-31 Flexible port configuration based on interface coupling
EP12867016.3A EP2810173B1 (en) 2012-01-31 2012-01-31 Flexible port configuration based on interface coupling
PCT/US2012/023347 WO2013115798A1 (en) 2012-01-31 2012-01-31 Flexible port configuration based on interface coupling
TW102103093A TWI551994B (en) 2012-01-31 2013-01-28 Flexible port configuration based on interface coupling

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2012/023347 WO2013115798A1 (en) 2012-01-31 2012-01-31 Flexible port configuration based on interface coupling

Publications (1)

Publication Number Publication Date
WO2013115798A1 true WO2013115798A1 (en) 2013-08-08

Family

ID=48905655

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2012/023347 WO2013115798A1 (en) 2012-01-31 2012-01-31 Flexible port configuration based on interface coupling

Country Status (5)

Country Link
US (1) US10140231B2 (en)
EP (1) EP2810173B1 (en)
CN (1) CN104054064B (en)
TW (1) TWI551994B (en)
WO (1) WO2013115798A1 (en)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3198359A4 (en) * 2015-01-23 2018-05-30 Hewlett-Packard Development Company, L.P. Detecting orientation of a device docked to a docking station
US10210128B2 (en) 2015-01-28 2019-02-19 Hewlett-Packard Development Company, L.P. Redirection of lane resources
DE102016101796A1 (en) * 2016-02-02 2017-08-03 Fujitsu Technology Solutions Intellectual Property Gmbh Circuit for a mainboard of a computer system and method for a circuit
US10162910B2 (en) * 2016-11-03 2018-12-25 GM Global Technology Operations LLC Method and apparatus for configuring wiring
WO2018111867A1 (en) * 2016-12-12 2018-06-21 Franz Hoffmann Modular pluggable electronic processing component and distributed processing system formed thereof
US11119876B2 (en) * 2018-10-09 2021-09-14 Super Micro Computer, Inc. Device and method for testing computer system
CN111177055A (en) * 2020-01-02 2020-05-19 英业达科技有限公司 PCIE slot configuration setting method, system, medium and device
CN117407347B (en) * 2023-12-15 2024-03-12 成都电科星拓科技有限公司 PCIe switching chip, control method thereof and electronic equipment

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6298408B1 (en) * 1998-03-03 2001-10-02 Samsung Electronics Co., Ltd. Intelligent input and output controller for flexible interface
US20030229739A1 (en) 2002-06-06 2003-12-11 James Brewer Method and system for configuring a set of wire lines to communicate with AC or DC coupled protocols
US20080003845A1 (en) * 2006-06-29 2008-01-03 Hong C H Single System Board with Automatic Feature Selection Based on Installed Configuration Selection Unit
US20090228730A1 (en) * 2008-03-06 2009-09-10 Asustek Computer Inc. Computer System and Power Saving Method Thereof

Family Cites Families (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4296465A (en) * 1977-11-03 1981-10-20 Honeywell Information Systems Inc. Data mover
US4835737A (en) * 1986-07-21 1989-05-30 American Telephone And Telegraph Company, At&T Bell Laboratories Method and apparatus for controlled removal and insertion of circuit modules
US5317697A (en) * 1991-07-31 1994-05-31 Synernetics Inc. Method and apparatus for live insertion and removal of electronic sub-assemblies
US5418911A (en) * 1992-06-09 1995-05-23 Intel Corporation Data path switch method and apparatus that provides capacitive load isolation
US5467344A (en) * 1994-04-25 1995-11-14 Ascom Timeplex Trading Ag Packet data transmission with asynchronous bandwidth switching
US5619660A (en) * 1994-04-28 1997-04-08 Intel Corporation Keying notches for side contacts on a thin form factor computer card
US5627416A (en) * 1995-07-21 1997-05-06 Itt Corporation Multi-voltage IC card host
US6151647A (en) * 1998-03-26 2000-11-21 Gemplus Versatile interface smart card
US6138194A (en) * 1998-06-08 2000-10-24 Micron Electronics, Inc. Apparatus for sensing movement of a bus card and automatically removing power from the bus card
US6085260A (en) 1998-06-08 2000-07-04 Ford Motor Company Method and circuit for multiplexing an input port and an output port of a microprocessor into a single external interface
US7836236B2 (en) * 2004-02-12 2010-11-16 Super Talent Electronics, Inc. Extended secure-digital (SD) devices and hosts
US6718274B2 (en) * 1999-08-05 2004-04-06 2Micro International Limited Integrated PC Card host controller for the detection and operation of a plurality of expansion cards
US7493437B1 (en) * 2000-07-06 2009-02-17 Mcm Portfolio Llc Flashtoaster for reading several types of flash memory cards with or without a PC
DE10052620B4 (en) * 2000-10-24 2008-07-10 Abb Ag Method for initialization of a pluggable electrical unit
US7248597B2 (en) 2001-05-02 2007-07-24 Nvidia Corporation General purpose input/output controller
US6928504B2 (en) * 2002-01-02 2005-08-09 International Business Machines Corporation PC card motion detector
US6886057B2 (en) * 2002-06-06 2005-04-26 Dell Products L.P. Method and system for supporting multiple bus protocols on a set of wirelines
US7099969B2 (en) * 2003-11-06 2006-08-29 Dell Products L.P. Dynamic reconfiguration of PCI Express links
US7069369B2 (en) * 2004-02-12 2006-06-27 Super Talent Electronics, Inc. Extended-Secure-Digital interface using a second protocol for faster transfers
US7096310B2 (en) * 2004-03-16 2006-08-22 Hewlett-Packard Development, L.P. Switch configurable for a plurality of communication protocols
TWI271659B (en) * 2004-05-05 2007-01-21 Prolific Technology Inc Memory card equipped with a multi-interface function and method for choosing a compatible transmission mode
US20060114918A1 (en) * 2004-11-09 2006-06-01 Junichi Ikeda Data transfer system, data transfer method, and image apparatus system
TWI288346B (en) 2005-05-13 2007-10-11 Hon Hai Prec Ind Co Ltd A signal converting apparatus and a port automatically switching method
KR100589227B1 (en) * 2005-05-23 2006-06-19 엠텍비젼 주식회사 Apparatus capable of multi-interfacing memories and interfacing method of the same
KR100725981B1 (en) * 2005-08-01 2007-06-08 삼성전자주식회사 Multi-interface controller, memory card having the multi-interface controller, and method for setting interface
US8462628B2 (en) * 2006-12-20 2013-06-11 Integrated Device Technology, Inc. Method of improving over protocol-required scheduling tables while maintaining same
US20090006708A1 (en) * 2007-06-29 2009-01-01 Henry Lee Teck Lim Proportional control of pci express platforms
JP4438846B2 (en) 2007-09-14 2010-03-24 ソニー株式会社 Card type peripheral device
US8301822B2 (en) 2009-09-23 2012-10-30 Sandisk Il Ltd. Multi-protocol storage device bridge
TWI405085B (en) 2010-01-29 2013-08-11 Innostor Technology Corp Switching interface method for a multi-interface storage device
US8327042B2 (en) * 2010-09-03 2012-12-04 Plx Technology, Inc. Automatic port accumulation
TWM405104U (en) 2010-11-04 2011-06-01 Taiwin Electronics Co Ltd Model-switching device
US8874820B2 (en) * 2010-12-28 2014-10-28 Silicon Image, Inc. Mechanism for facilitating a configurable port-type peripheral component interconnect express/serial advanced technology attachment host controller architecture
US8756360B1 (en) * 2011-09-26 2014-06-17 Agilent Technologies, Inc. PCI-E compatible chassis having multi-host capability
US8996776B2 (en) * 2012-04-02 2015-03-31 Blackberry Limited Computing device and method for hot swapping media

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6298408B1 (en) * 1998-03-03 2001-10-02 Samsung Electronics Co., Ltd. Intelligent input and output controller for flexible interface
US20030229739A1 (en) 2002-06-06 2003-12-11 James Brewer Method and system for configuring a set of wire lines to communicate with AC or DC coupled protocols
US20080003845A1 (en) * 2006-06-29 2008-01-03 Hong C H Single System Board with Automatic Feature Selection Based on Installed Configuration Selection Unit
US20090228730A1 (en) * 2008-03-06 2009-09-10 Asustek Computer Inc. Computer System and Power Saving Method Thereof

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2810173A4

Also Published As

Publication number Publication date
CN104054064A (en) 2014-09-17
CN104054064B (en) 2017-06-20
EP2810173A4 (en) 2015-11-11
TWI551994B (en) 2016-10-01
TW201344443A (en) 2013-11-01
US10140231B2 (en) 2018-11-27
EP2810173B1 (en) 2018-10-31
US20150205740A1 (en) 2015-07-23
EP2810173A1 (en) 2014-12-10

Similar Documents

Publication Publication Date Title
US10140231B2 (en) Flexible port configuration based on interface coupling
TWI676895B (en) Configuring docks
US20170083470A1 (en) System and Method for Providing Personality Switching in a Solid State Drive Device
US7822964B2 (en) Booting apparatus for booting a computer and method therefor and computer with a booting apparatus
WO2012141743A1 (en) Apparatuses for configuring programmable logic devices from bios prom
US8880747B2 (en) Endpoint device discovery system
US10037170B2 (en) Motherboard and a method for boot-up
CN105814541A (en) Computer device and memory starting method for computer device
US20180210783A1 (en) Information processing apparatus, control method of the same, and storage medium
US20170091017A1 (en) Fault detecting device and method
CN109800032A (en) BOOTROM multicore loading method and device
US9946552B2 (en) System and method for detecting redundant array of independent disks (RAID) controller state from baseboard management controller (BMC)
US9043584B2 (en) Generating hardware events via the instruction stream for microprocessor verification
CN111026421A (en) Upgrading device
US20150186317A1 (en) Method and apparatus for detecting the initiator/target orientation of a smart bridge
KR100687925B1 (en) Computer System
US10198270B2 (en) Dynamic hardware configuration via firmware interface at computing device boot
EP2750030A1 (en) Method, apparatus and processor for reading BIOS
US20170269942A1 (en) Method for setting redundant array of independent disks
CN105446903A (en) Information processing method and electronic device
CN110333904B (en) Multi-hard-disk starting control method
TW201734800A (en) Method for setting redundant array of independent disks
US11341014B2 (en) System and method for generating a hotkey in a pre-boot environment
CN111176735B (en) Method for accelerating startup of electrocardiograph
US20210141627A1 (en) Power delivery controller updates

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12867016

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2012867016

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 14374681

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE