US20110289241A1 - Autodetection of a pci express device operating at a wireless rf mitigation frequency - Google Patents

Autodetection of a pci express device operating at a wireless rf mitigation frequency Download PDF

Info

Publication number
US20110289241A1
US20110289241A1 US13/198,528 US201113198528A US2011289241A1 US 20110289241 A1 US20110289241 A1 US 20110289241A1 US 201113198528 A US201113198528 A US 201113198528A US 2011289241 A1 US2011289241 A1 US 2011289241A1
Authority
US
United States
Prior art keywords
frequency
receive
endpoint device
physical layer
wireless extension
Prior art date
Legal status (The legal status 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 status listed.)
Abandoned
Application number
US13/198,528
Inventor
Mikal C. Hunsaker
Karthi Vadivelu
Andrew W. Martwick
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
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 Individual filed Critical Individual
Priority to US13/198,528 priority Critical patent/US20110289241A1/en
Publication of US20110289241A1 publication Critical patent/US20110289241A1/en
Abandoned legal-status Critical Current

Links

Images

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/42Bus transfer protocol, e.g. handshake; Synchronisation
    • G06F13/4282Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus
    • G06F13/4295Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus using an embedded synchronisation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2213/00Indexing scheme relating to interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F2213/0026PCI express
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L7/00Arrangements for synchronising receiver with transmitter
    • H04L7/04Speed or phase control by synchronisation signals
    • H04L7/10Arrangements for initial synchronisation

Definitions

  • the present invention pertains to the field of computer system design. More particularly, the present invention relates to a root port that detects whether an attached device is operating at a PCI Express frequency or an alternative wireless extension frequency.
  • PCI Peripheral Component Interconnect
  • CPU central processing unit
  • PCI-X Peripheral Component Interconnect
  • PCI Express is the third generation of PCI architecture.
  • PCI Express offers higher input/output (I/O) bandwidth than its predecessors.
  • Traditional PCI attributes such as its usage model and software interfaces, are maintained.
  • the previous parallel bus implementation has been replaced by a link-to-link serial interface.
  • a split-transaction protocol is implemented with attributed packets that are prioritized and optimally delivered to their target.
  • FIG. 1 is an embodiment of a computer system that supports both PCI Express compliant devices and non-PCI Express compliant devices.
  • FIG. 2 is an embodiment of a flowchart to auto-detect a non-PCI Express compliant wireless extension device.
  • FIG. 3 is a block diagram of an embodiment of a device for detecting PCI Express compliant and non-PCI compliant devices.
  • the PCI Express architecture is typically composed of a plurality of layers. For example, a software layer generates PCI Express read and write requests. A transaction layer, coupled to the software layer, transports the software-generated requests to I/O devices using a packet-based, split-transaction protocol. A link layer coupled to the transaction layer adds sequence numbers and a cyclical redundancy check (CRC) number to the packets to create a highly reliable data transfer mechanism. Finally, a physical layer coupled to the link layer transports the packets to another PCI Express device.
  • CRC cyclical redundancy check
  • the PCI Express 1.0a specification supports a frequency of 2.5 gigahertz (GHz). This frequency may be referred to as the Gen1 frequency.
  • the Gen1 frequency is similar to the wireless 2.4 GHz spectrum. As a result, the Gen1 frequency potentially causes radio frequency (RF) interference with wireless communications.
  • RF radio frequency
  • a mechanism in a PCI Express port may reduce the data transfer rate.
  • the data transfer rate is reduced to 833 megahertz (MHz), or one-third the Gen1 frequency.
  • a mechanism to reduce the data transfer rate is described in more detail in co-pending application with Ser. No. 10/629,967 entitled, “RF Interference Mitigation by Spectral Shaping Using Adaptive Data Rate Adjustment for PCI Express Interconnect.”
  • the 833 MHz transfer rate is also known as the wireless extension frequency.
  • PCI Express 1.0a By definition of the PCI Express 1.0a specification, a computer system that communicates only with a device that operates at the wireless extension frequency is not PCI Express compliant. To maintain PCI Express compliance, a computer system that is able to communicate with non-PCI Express compliant devices also communicates with PCI Express compliant devices.
  • FIG. 1 depicts a PCI Express compliant computer system that is able to communicate with both a device operating at the Gen1 frequency and a device operating at the wireless extension frequency.
  • the computer system 100 of FIG. 1 comprises a processor 110 , a chipset 120 , and a memory 150 .
  • Computer system 100 which refers to processor 110 , chipset 120 , and memory 150 , is coupled to device 160 .
  • a computer system may include device 160 .
  • device 160 is either a PCI Express compliant or non-PCI Express compliant device. Coupling of device 160 to chipset 120 may comprise physically coupling device 160 to chipset 120 or wirelessly coupling device 160 to chipset 120 . As an example, chipset 120 has a transmitter to transmit data to and a receiver to receive data from coupled device 160 . Device 160 , as illustrated, further comprises port 170 , which is discussed in more detail below.
  • Chipset 120 is coupled to processor 110 , memory 150 , and device 160 .
  • Chipset 120 is illustrated as a single block; however, chipset 120 is not so limited. In fact, often chipset 120 comprises a plurality of controller hubs or integrated circuits.
  • chipset 120 comprises a memory controller hub (MCH) coupled to processor 110 and memory 150 , as well as a interconnect controller hub (ICH), also referred to as an input/output hub (IOH), coupled to the MCH and I/O devices through a bus, such as PCI Express.
  • MCH memory controller hub
  • ICH interconnect controller hub
  • IOH input/output hub
  • chipset 120 delivers data between the processor 110 and memory 150 .
  • PCI Express switch 130 adjusts a frequency of the data transmitted by a transmitter present in chipset 120 .
  • the PCI Express switch 130 may adjust the clock frequency of its receiver. For example, the switch 130 adjusts the receiver clock from the Gen1 frequency to the wireless extension frequency.
  • root port 140 attempts to establish communication with a connected device at the Gen1 frequency. If the communication is unsuccessful after N attempts, root port 140 auto-detects for a connected device operating at a wireless extension frequency.
  • the root port 140 and PCI Express switch 130 may be part of the physical layer or any other layer present in a PCI Express bus/protocol.
  • FIG. 2 depicts a flowchart of an algorithm for auto-detecting a connected device operating at a wireless extension frequency.
  • the algorithm is implemented by root port 140 .
  • root port 140 is illustrated in chipset 120 ; however, root port 140 is not so limited, as root port 140 may also be present in a separate controller hub, integrated circuit, switch, or bridge in the hierarchical connection of a peripheral bus.
  • root port 140 attempts to “train” a connected endpoint device at a first frequency.
  • data is transmitted at a first frequency.
  • the root port receiver is also clocked at the first frequency.
  • the first frequency is the Gen1 frequency.
  • Training may comprise a “bit-lock” and a “K-align lock” of the physical layers of each device.
  • Bit-lock refers to the ability of the receiver to properly lock onto specific bits within a bit-stream by identifying bit transition edges.
  • K-align lock refers to the ability of the receiver to determine symbol boundaries within a bit pattern.
  • the endpoint device is PCI Express compliant and the link negotiation is terminated in operation 270 .
  • the number of attempts, X may be a software programmable value with a hardware default. Furthermore, X may be an integer greater than or equal to one.
  • root port 140 is unable to train the endpoint device within X attempts, the receiver is clocked at a second frequency in operation 230 .
  • the receiver then attempts to K-align at the second frequency.
  • root port 140 continues to transport/transmit data at the first frequency.
  • the receiver may attempt to K-align at the second frequency for Y attempts in operation 240 .
  • the number of attempts, Y may be a software programmable value with a hardware default, as well as an integer equal to or greater than one. Both the number of attempts X and Y may also be a predetermined number of attempts in hardware or in software, as well as any combination of hardware and software.
  • the root port 140 returns to operation 210 and again attempts to train the endpoint device at the first frequency.
  • Root port 140 next attempts to train the endpoint device within Z attempts at the second frequency in operation 260 .
  • the receiver attempts to bit-lock, i.e. properly lock, onto specific bits within a bit-stream, and to K-align lock to determine symbol boundaries within a bit pattern.
  • Z may also be a predetermined or programmable integer implemented in hardware, software, or firmware.
  • the root port 140 returns to operation 210 and again attempts to train the endpoint device at the first frequency. Otherwise, if the receiver successfully trains at the second frequency within Z attempts, the link negotiation is terminated in operation 270 .
  • FIG. 3 depicts a block diagram of an embodiment of a device for detecting PCI Express compliant and non-PCI compliant devices.
  • FIG. 3 comprises a wireless extension state machine 305 , a receive circuit interface 310 , a receive physical interface 320 , a clock divider 330 , a multiplexer 335 , a link training and status state machine 340 , a transmit circuit interface 350 , a transmit physical layer 360 , a phase locked loop 365 , a clock divider 370 , and a multiplexer 375 .
  • Receive circuit interface 310 is coupled to receive physical layer 320 , clock divider 330 , and multiplexer 335 .
  • Clock divider 330 is coupled to multiplexer 335 .
  • Receive physical layer 320 is coupled to link training and status state machine 340 .
  • Link training and status state machine 340 and multiplexer 335 are coupled to wireless extension state machine 305 .
  • Phase locked loop 365 is coupled to clock divider 370 .
  • Clock divider 370 is coupled to multiplexer 375 .
  • Multiplexer 375 is coupled to link training and status state machine 340 .
  • receive circuit interface 310 receives a signal from a wireless extension endpoint. In another embodiment, receive circuit interface 310 receives a signal from a PCI Express endpoint. Receive circuit interface 310 may comprise an I/O buffer. The signal input to receive circuit interface 310 may comprise a clock and a data signal. In one embodiment the clock signal is extracted from the data signal. Receive circuit interface 310 may extract the clock from the signal and transmit the clock to clock divider 330 and multiplexer 335 . Receive circuit interface 310 transmits the data to receive physical layer 320 for processing. The data is subsequently passed from the receive physical layer 320 to link training and status state machine 340 and to the link layer.
  • the clock extracted from the signal received by the endpoint device may have a Gen1 frequency.
  • clock divider 330 divides the clock by three.
  • the inputs to the multiplexer 335 may be a Gen1 frequency and a wireless extension frequency.
  • the wireless extension state machine 305 transfers a signal to the multiplexer 335 to select whether the Gen1 frequency or the wireless extension frequency is output from the multiplexer 335 .
  • the wireless extension state machine 305 selects the Gen1 frequency, if the wireless extension state machine 305 determines that a PCI Express device is coupled to the receive circuit interface 310 and the transmit circuit interface 350 .
  • the wireless extension frequency may be selected by the wireless extension state machine 305 , if the wireless extension state machine 305 determines that a wireless extension device is coupled to the receive circuit interface 310 and the transmit circuit interface 350 .
  • the wireless extension state machine 305 also selects the transmitter clock. It is apparent that another state machine may select the transmitter clock. Wireless extension state machine 305 provides a select signal to multiplexer 375 . Multiplexer 375 receives a first clock and a second clock as inputs. A clock having a Gen1 frequency may be generated by phase locked loop 365 . The clock having a Gen1 frequency is provided to the first input of multiplexer 375 . The second input to multiplexer 375 is provided by the output of clock divider 370 .
  • the two inputs to multiplexer 335 are the Gen1 frequency and the wireless extension frequency, the Gen1 frequency generated by a PLL and the wireless extension frequency being based on the Gen1 frequency, i.e. the Gen1 frequency divided by 3.
  • the wireless extension state machine 305 initially selects the Gen1 frequency for both the receiver and the transmitter clocks. However, the wireless extension frequency or other frequency may be selected as the default for the receive and transmitter, as well as selecting the receiver and transmitter clocks individually.
  • Receive physical layer 320 receives a clock having a Gen1 frequency. Receive physical layer 320 also receives data from receive circuit interface 310 . The data is passed to link training and status state machine 340 at the selected frequency rate.
  • transmit physical layer 360 receives a clock having a Gen1 frequency.
  • Data is transmitted from the link layer to the physical layer, which may include status state machine 340 .
  • data is transmitted to the endpoint device at the Gen1 frequency.
  • data transmitted to the endpoint device is generated by the link layer.
  • Transmit circuit interface 350 may comprise an I/O buffer to transmit the data to the endpoint device.
  • receive physical layer 320 and link training and status state machine 340 After receiving data from the endpoint device, receive physical layer 320 and link training and status state machine 340 attempt to train the endpoint device at the Gen1 frequency. Training is initiated by link training and status state machine 340 . If the receive physical layer 320 and link training and status state machine 340 are successful in training the endpoint device at the Gen1 frequency, the link training and status state machine 340 provides a signal to the wireless extension state machine 305 to let the wireless extension state machine 305 know that the endpoint device is PCI Express compliant. As a result, wireless extension state machine 305 will continue to select clocks having Gen1 frequencies for multiplexers 335 and 375 .
  • wireless extension state machine 305 may select the wireless extension clock input for multiplexer 335 .
  • Receive physical layer 320 and link training and status state machine 340 may then attempt to K-align the data. For example, receive physical layer 320 may determine symbol boundaries within the bit pattern by looking for a COM symbol. The COM symbol may be a unique K-code character within a bit-sequence. If receive physical layer 320 and link training and status state machine 340 successfully K-align the data, the link training and status state machine 340 may select the wireless extension clock for multiplexer 375 and attempt to train the endpoint device at the wireless extension rate.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Small-Scale Networks (AREA)
  • Communication Control (AREA)

Abstract

A computer system that detects for a PCI Express compliant endpoint device is described. Specifically, the computer system clocks transmit and receive circuits at a first frequency and initiates a training sequence. If the endpoint device successfully trains at the first frequency, the endpoint device is PCI Express compliant. Otherwise, the computer system initiates another training sequence at a second frequency.

Description

    CROSS-REFERENCE TO RELATED APPLICATION
  • This application is a Continuation of U.S. patent application Ser. No. 11/026,968, filed on Dec. 29, 2004, and entitled “AUTODETECTION OF A PCI EXPRESS DEVICE OPERATING AT A WIRELESS RF MITIGATION FREQUENCY”. This application is incorporated herein by reference in its entirety.
  • FIELD
  • The present invention pertains to the field of computer system design. More particularly, the present invention relates to a root port that detects whether an attached device is operating at a PCI Express frequency or an alternative wireless extension frequency.
  • BACKGROUND
  • Peripheral Component Interconnect (PCI) is a computer bus design standard for connecting peripheral components to computers. A PCI bus typically routes signals between a central processing unit (CPU), various other chips on the motherboard, and cards that are plugged into PCI bus slot connectors. The PCI bus, however, is independent of the CPU chip implemented in a computer system. Thus, the PCI bus is adapted for use in many different kinds of computers or other high-tech hardware. Earlier versions of the PCI standard included PCI 2.2 and PCI-X.
  • PCI Express is the third generation of PCI architecture. PCI Express offers higher input/output (I/O) bandwidth than its predecessors. Traditional PCI attributes, such as its usage model and software interfaces, are maintained. However, the previous parallel bus implementation has been replaced by a link-to-link serial interface. Further, a split-transaction protocol is implemented with attributed packets that are prioritized and optimally delivered to their target.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is an embodiment of a computer system that supports both PCI Express compliant devices and non-PCI Express compliant devices.
  • FIG. 2 is an embodiment of a flowchart to auto-detect a non-PCI Express compliant wireless extension device.
  • FIG. 3 is a block diagram of an embodiment of a device for detecting PCI Express compliant and non-PCI compliant devices.
  • DETAILED DESCRIPTION
  • In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the present invention.
  • The PCI Express architecture is typically composed of a plurality of layers. For example, a software layer generates PCI Express read and write requests. A transaction layer, coupled to the software layer, transports the software-generated requests to I/O devices using a packet-based, split-transaction protocol. A link layer coupled to the transaction layer adds sequence numbers and a cyclical redundancy check (CRC) number to the packets to create a highly reliable data transfer mechanism. Finally, a physical layer coupled to the link layer transports the packets to another PCI Express device.
  • The PCI Express 1.0a specification supports a frequency of 2.5 gigahertz (GHz). This frequency may be referred to as the Gen1 frequency. The Gen1 frequency is similar to the wireless 2.4 GHz spectrum. As a result, the Gen1 frequency potentially causes radio frequency (RF) interference with wireless communications.
  • To reduce the RF interference of a wireless endpoint, a mechanism in a PCI Express port may reduce the data transfer rate. As an example, the data transfer rate is reduced to 833 megahertz (MHz), or one-third the Gen1 frequency. A mechanism to reduce the data transfer rate is described in more detail in co-pending application with Ser. No. 10/629,967 entitled, “RF Interference Mitigation by Spectral Shaping Using Adaptive Data Rate Adjustment for PCI Express Interconnect.” The 833 MHz transfer rate is also known as the wireless extension frequency.
  • By definition of the PCI Express 1.0a specification, a computer system that communicates only with a device that operates at the wireless extension frequency is not PCI Express compliant. To maintain PCI Express compliance, a computer system that is able to communicate with non-PCI Express compliant devices also communicates with PCI Express compliant devices.
  • FIG. 1 depicts a PCI Express compliant computer system that is able to communicate with both a device operating at the Gen1 frequency and a device operating at the wireless extension frequency. The computer system 100 of FIG. 1 comprises a processor 110, a chipset 120, and a memory 150. Computer system 100, which refers to processor 110, chipset 120, and memory 150, is coupled to device 160. However, a computer system may include device 160.
  • In one embodiment, device 160 is either a PCI Express compliant or non-PCI Express compliant device. Coupling of device 160 to chipset 120 may comprise physically coupling device 160 to chipset 120 or wirelessly coupling device 160 to chipset 120. As an example, chipset 120 has a transmitter to transmit data to and a receiver to receive data from coupled device 160. Device 160, as illustrated, further comprises port 170, which is discussed in more detail below.
  • Chipset 120 is coupled to processor 110, memory 150, and device 160. Chipset 120 is illustrated as a single block; however, chipset 120 is not so limited. In fact, often chipset 120 comprises a plurality of controller hubs or integrated circuits. As a specific example, chipset 120 comprises a memory controller hub (MCH) coupled to processor 110 and memory 150, as well as a interconnect controller hub (ICH), also referred to as an input/output hub (IOH), coupled to the MCH and I/O devices through a bus, such as PCI Express. Using typical memory bus protocols, chipset 120 delivers data between the processor 110 and memory 150.
  • Also shown in chipset 120 is PCI Express switch 130. In one embodiment, PCI Express switch 130 adjusts a frequency of the data transmitted by a transmitter present in chipset 120. Moreover, the PCI Express switch 130 may adjust the clock frequency of its receiver. For example, the switch 130 adjusts the receiver clock from the Gen1 frequency to the wireless extension frequency.
  • In one embodiment, root port 140, also illustrated in chipset 120, attempts to establish communication with a connected device at the Gen1 frequency. If the communication is unsuccessful after N attempts, root port 140 auto-detects for a connected device operating at a wireless extension frequency. The root port 140 and PCI Express switch 130 may be part of the physical layer or any other layer present in a PCI Express bus/protocol.
  • FIG. 2 depicts a flowchart of an algorithm for auto-detecting a connected device operating at a wireless extension frequency. In one embodiment, the algorithm is implemented by root port 140. As stated above root port 140 is illustrated in chipset 120; however, root port 140 is not so limited, as root port 140 may also be present in a separate controller hub, integrated circuit, switch, or bridge in the hierarchical connection of a peripheral bus.
  • In operation 210, root port 140 attempts to “train” a connected endpoint device at a first frequency. In a first embodiment, data is transmitted at a first frequency. As another example, in addition to transmitting data at the first frequency, the root port receiver is also clocked at the first frequency. As a specific example, the first frequency is the Gen1 frequency. Training may comprise a “bit-lock” and a “K-align lock” of the physical layers of each device. However training is not so limited. For example, training may also comprises exchanging training sequences. Bit-lock refers to the ability of the receiver to properly lock onto specific bits within a bit-stream by identifying bit transition edges. K-align lock refers to the ability of the receiver to determine symbol boundaries within a bit pattern.
  • If root port 140 is able to train the endpoint device within X attempts in operation 220, the endpoint device is PCI Express compliant and the link negotiation is terminated in operation 270. The number of attempts, X, may be a software programmable value with a hardware default. Furthermore, X may be an integer greater than or equal to one.
  • However, if root port 140 is unable to train the endpoint device within X attempts, the receiver is clocked at a second frequency in operation 230. The receiver then attempts to K-align at the second frequency. As a specific example, root port 140 continues to transport/transmit data at the first frequency. The receiver may attempt to K-align at the second frequency for Y attempts in operation 240. The number of attempts, Y, may be a software programmable value with a hardware default, as well as an integer equal to or greater than one. Both the number of attempts X and Y may also be a predetermined number of attempts in hardware or in software, as well as any combination of hardware and software.
  • Yet, if the receiver fails to K-align at the second frequency in operation 240, the root port 140 returns to operation 210 and again attempts to train the endpoint device at the first frequency.
  • On the other hand, if the receiver successfully K-aligns at the second frequency, the transmitter is adjusted to transmit data at the second frequency in operation 250. Root port 140 next attempts to train the endpoint device within Z attempts at the second frequency in operation 260. Thus, the receiver attempts to bit-lock, i.e. properly lock, onto specific bits within a bit-stream, and to K-align lock to determine symbol boundaries within a bit pattern. As stated above for X and Y, Z may also be a predetermined or programmable integer implemented in hardware, software, or firmware.
  • Nevertheless, if the receiver fails to train the endpoint device at the second frequency within Z attempts in operation 260, the root port 140 returns to operation 210 and again attempts to train the endpoint device at the first frequency. Otherwise, if the receiver successfully trains at the second frequency within Z attempts, the link negotiation is terminated in operation 270.
  • FIG. 3 depicts a block diagram of an embodiment of a device for detecting PCI Express compliant and non-PCI compliant devices. FIG. 3 comprises a wireless extension state machine 305, a receive circuit interface 310, a receive physical interface 320, a clock divider 330, a multiplexer 335, a link training and status state machine 340, a transmit circuit interface 350, a transmit physical layer 360, a phase locked loop 365, a clock divider 370, and a multiplexer 375.
  • Receive circuit interface 310 is coupled to receive physical layer 320, clock divider 330, and multiplexer 335. Clock divider 330 is coupled to multiplexer 335. Receive physical layer 320 is coupled to link training and status state machine 340. Link training and status state machine 340 and multiplexer 335 are coupled to wireless extension state machine 305. Phase locked loop 365 is coupled to clock divider 370. Clock divider 370 is coupled to multiplexer 375. Multiplexer 375 is coupled to link training and status state machine 340.
  • In one embodiment, receive circuit interface 310 receives a signal from a wireless extension endpoint. In another embodiment, receive circuit interface 310 receives a signal from a PCI Express endpoint. Receive circuit interface 310 may comprise an I/O buffer. The signal input to receive circuit interface 310 may comprise a clock and a data signal. In one embodiment the clock signal is extracted from the data signal. Receive circuit interface 310 may extract the clock from the signal and transmit the clock to clock divider 330 and multiplexer 335. Receive circuit interface 310 transmits the data to receive physical layer 320 for processing. The data is subsequently passed from the receive physical layer 320 to link training and status state machine 340 and to the link layer.
  • The clock extracted from the signal received by the endpoint device may have a Gen1 frequency. As a specific example, clock divider 330 divides the clock by three. Thus, the inputs to the multiplexer 335 may be a Gen1 frequency and a wireless extension frequency. The wireless extension state machine 305 transfers a signal to the multiplexer 335 to select whether the Gen1 frequency or the wireless extension frequency is output from the multiplexer 335. For one embodiment, the wireless extension state machine 305 selects the Gen1 frequency, if the wireless extension state machine 305 determines that a PCI Express device is coupled to the receive circuit interface 310 and the transmit circuit interface 350. However, the wireless extension frequency may be selected by the wireless extension state machine 305, if the wireless extension state machine 305 determines that a wireless extension device is coupled to the receive circuit interface 310 and the transmit circuit interface 350.
  • Besides selecting the receiver clock, in one embodiment, the wireless extension state machine 305 also selects the transmitter clock. It is apparent that another state machine may select the transmitter clock. Wireless extension state machine 305 provides a select signal to multiplexer 375. Multiplexer 375 receives a first clock and a second clock as inputs. A clock having a Gen1 frequency may be generated by phase locked loop 365. The clock having a Gen1 frequency is provided to the first input of multiplexer 375. The second input to multiplexer 375 is provided by the output of clock divider 370. Consequently, in a specific embodiment, the two inputs to multiplexer 335 are the Gen1 frequency and the wireless extension frequency, the Gen1 frequency generated by a PLL and the wireless extension frequency being based on the Gen1 frequency, i.e. the Gen1 frequency divided by 3.
  • In another embodiment, the wireless extension state machine 305 initially selects the Gen1 frequency for both the receiver and the transmitter clocks. However, the wireless extension frequency or other frequency may be selected as the default for the receive and transmitter, as well as selecting the receiver and transmitter clocks individually. Receive physical layer 320 receives a clock having a Gen1 frequency. Receive physical layer 320 also receives data from receive circuit interface 310. The data is passed to link training and status state machine 340 at the selected frequency rate.
  • Similarly, transmit physical layer 360 receives a clock having a Gen1 frequency. Data is transmitted from the link layer to the physical layer, which may include status state machine 340. Moreover, data is transmitted to the endpoint device at the Gen1 frequency. As an example, data transmitted to the endpoint device is generated by the link layer. Transmit circuit interface 350 may comprise an I/O buffer to transmit the data to the endpoint device.
  • After receiving data from the endpoint device, receive physical layer 320 and link training and status state machine 340 attempt to train the endpoint device at the Gen1 frequency. Training is initiated by link training and status state machine 340. If the receive physical layer 320 and link training and status state machine 340 are successful in training the endpoint device at the Gen1 frequency, the link training and status state machine 340 provides a signal to the wireless extension state machine 305 to let the wireless extension state machine 305 know that the endpoint device is PCI Express compliant. As a result, wireless extension state machine 305 will continue to select clocks having Gen1 frequencies for multiplexers 335 and 375.
  • However, if receive physical layer 320 and link training and status state machine 340 fail to train the endpoint device at the Gen1 rate, wireless extension state machine 305 may select the wireless extension clock input for multiplexer 335. Receive physical layer 320 and link training and status state machine 340 may then attempt to K-align the data. For example, receive physical layer 320 may determine symbol boundaries within the bit pattern by looking for a COM symbol. The COM symbol may be a unique K-code character within a bit-sequence. If receive physical layer 320 and link training and status state machine 340 successfully K-align the data, the link training and status state machine 340 may select the wireless extension clock for multiplexer 375 and attempt to train the endpoint device at the wireless extension rate.
  • In the foregoing specification the invention has been described with reference to specific exemplary embodiments thereof. It will, however, be evident that various modification and changes may be made thereto without departure from the broader spirit and scope of the invention as set forth in the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative rather than restrictive sense.

Claims (5)

1. An apparatus, comprising:
a receive circuit interface adapted to receive data from an endpoint device;
a transmit circuit interface adapted to transmit data to the endpoint device based on a transmit interface clock signal;
a receive physical layer coupled to the receive circuit interface, the receive physical layer adapted to look for bit patterns in the data received by the receive circuit interface based on a receive interface clock signal;
link training logic coupled to the receive physical layer, the link training logic adapted to detect if the endpoint device is a first endpoint device operating at a first frequency or a second endpoint device operating at a second frequency; and
wireless extension logic coupled to the link training logic, the wireless extension logic adapted to select either the first or the second frequency independently for the receive interface clock signal and the transmit interface clock signal.
2. The apparatus of claim 1, wherein the link training logic adapted to detect if the endpoint device is a first endpoint device operating at a first frequency or a second endpoint device operating at a second frequency comprises: detecting the endpoint device is a first endpoint device operating at a first frequency in response to the receive physical layer successfully finding the bit patterns in the data received by the receive circuit interface when wireless extension logic selects the first frequency for the receive interface clock signal; and detecting the endpoint device is a second endpoint device operating at a second frequency in response to the receive physical layer successfully finding the bit patterns in the data received by the receive circuit interface when wireless extension logic selects the second frequency for the receive interface clock signal.
3. The apparatus of claim 1, wherein the first endpoint device is PCI Express compliant and the second endpoint device is a wireless extension device that is not PCI Express compliant.
4. The apparatus of claim 1, wherein the wireless extension logic is adapted to select the first frequency for the receive interface clock signal by default, the receive physical layer is adapted to look for bit patterns in the data received by the receive circuit interface based on the receive interface clock signal being at the first frequency in response to the wireless extension logic selecting the first frequency for the receive interface clock signal by default, and the link training logic detecting the endpoint device is a first endpoint device operating at the first frequency in response to the receive physical layer indicating the bit patterns are found at the first frequency.
5. The apparatus of claim 4, wherein the wireless extension logic is adapted to select the second frequency for the receive interface clock signal in response to the receive physical layer indicating the bit patterns are not found at the first frequency after N attempts, the receive physical layer is adapted to look for bit patterns in the data received by the receive circuit interface based on the receive interface clock signal being at the second frequency in response to the wireless extension logic selecting the second frequency, and the link training logic detecting the endpoint device is a second endpoint device operating at the second frequency in response to the receive physical layer indicating the bit patterns are found at the second frequency.
US13/198,528 2004-12-29 2011-08-04 Autodetection of a pci express device operating at a wireless rf mitigation frequency Abandoned US20110289241A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US13/198,528 US20110289241A1 (en) 2004-12-29 2011-08-04 Autodetection of a pci express device operating at a wireless rf mitigation frequency

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/026,968 US8041844B2 (en) 2004-12-29 2004-12-29 Autodetection of a PCI express device operating at a wireless RF mitigation frequency
US13/198,528 US20110289241A1 (en) 2004-12-29 2011-08-04 Autodetection of a pci express device operating at a wireless rf mitigation frequency

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/026,968 Continuation US8041844B2 (en) 2004-12-29 2004-12-29 Autodetection of a PCI express device operating at a wireless RF mitigation frequency

Publications (1)

Publication Number Publication Date
US20110289241A1 true US20110289241A1 (en) 2011-11-24

Family

ID=36168378

Family Applications (2)

Application Number Title Priority Date Filing Date
US11/026,968 Expired - Fee Related US8041844B2 (en) 2004-12-29 2004-12-29 Autodetection of a PCI express device operating at a wireless RF mitigation frequency
US13/198,528 Abandoned US20110289241A1 (en) 2004-12-29 2011-08-04 Autodetection of a pci express device operating at a wireless rf mitigation frequency

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US11/026,968 Expired - Fee Related US8041844B2 (en) 2004-12-29 2004-12-29 Autodetection of a PCI express device operating at a wireless RF mitigation frequency

Country Status (5)

Country Link
US (2) US8041844B2 (en)
CN (1) CN100592278C (en)
DE (1) DE112005003286B4 (en)
TW (1) TWI313816B (en)
WO (1) WO2006071665A2 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120324139A1 (en) * 2011-06-14 2012-12-20 Advanced Micro Devices, Inc. Wireless communication for point-to-point serial link protocol
US9891653B2 (en) 2015-06-15 2018-02-13 Altera Corporation Techniques for clock rate changes during data rate changes in an integrated circuit (IC)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8041844B2 (en) 2004-12-29 2011-10-18 Intel Corporation Autodetection of a PCI express device operating at a wireless RF mitigation frequency
US8050290B2 (en) * 2007-05-16 2011-11-01 Wilocity, Ltd. Wireless peripheral interconnect bus
US9075926B2 (en) 2007-07-19 2015-07-07 Qualcomm Incorporated Distributed interconnect bus apparatus
WO2010041093A1 (en) * 2008-10-09 2010-04-15 Federico Tiziani Virtualized ecc nand
CN102129762B (en) * 2010-12-23 2012-12-26 泉州市明佳电子科技有限公司 Debugging device for bidirectional host radio frequency board of vehicle remote control system
US20170280385A1 (en) * 2016-03-23 2017-09-28 Qualcomm Incorporated Link speed control systems for power optimization
EP3507675A4 (en) * 2017-01-28 2020-02-12 Hewlett-Packard Development Company, L.P. Adaptable connector with external i/o port
CN109213268A (en) * 2017-07-04 2019-01-15 佛山市顺德区顺达电脑厂有限公司 Server cabinet system and its signal transmission frequency method of adjustment
US12072831B2 (en) 2022-01-20 2024-08-27 Mediatek Inc. Dynamic PCIE speed-adjusting method and wireless device and user equipment thereof

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4409687A (en) * 1978-10-30 1983-10-11 General Electric Company Arrangement and method for establishing radio communication in a system
US5483676A (en) * 1988-08-04 1996-01-09 Norand Corporation Mobile radio data communication system and method
US5490209A (en) * 1994-02-09 1996-02-06 Harris Corporation Autobaud rate detection mechanism
EP0759055B1 (en) * 1994-04-18 1998-07-22 International Business Machines Corporation Wireless optical communication system with adaptive data rate
US5729557A (en) * 1995-10-12 1998-03-17 Pacific Communication Systems, Inc. Cellular communication system with multiple code rates
US5914959A (en) * 1996-10-31 1999-06-22 Glenayre Electronics, Inc. Digital communications system having an automatically selectable transmission rate
US6081700A (en) * 1996-12-17 2000-06-27 Motorola, Inc. Radio having a self-tuning antenna and method thereof
US5764111A (en) * 1997-02-18 1998-06-09 Motorola Inc. Voltage controlled ring oscillator frequency multiplier
US6295563B1 (en) * 1998-01-30 2001-09-25 Unisys Corporation Control system for recreating of data output clock frequency which matches data input clock frequency during data transferring
US6175752B1 (en) * 1998-04-30 2001-01-16 Therasense, Inc. Analyte monitoring device and methods of use
US6442628B1 (en) * 1998-05-01 2002-08-27 Adaptec, Inc. Method and system for automatically determining maximum data throughput over a bus
US6438159B1 (en) * 1999-02-16 2002-08-20 Maxtor Corporation Method and apparatus for margining error rate of multi-drop data buses
US6690949B1 (en) * 1999-09-30 2004-02-10 Skyworks Solutions, Inc. System and process for supporting multiple wireless standards with a single circuit architecture
US6680970B1 (en) 2000-05-23 2004-01-20 Hewlett-Packard Development Company, L.P. Statistical methods and systems for data rate detection for multi-speed embedded clock serial receivers
US6708239B1 (en) * 2000-12-08 2004-03-16 The Boeing Company Network device interface for digitally interfacing data channels to a controller via a network
US6901265B2 (en) * 2001-04-25 2005-05-31 Parthus (Uk) Limited Mobile communication apparatus
US7227891B2 (en) * 2001-11-05 2007-06-05 Agere Systems Inc. Transceiver employing training-while-working mode
US7346012B2 (en) * 2002-12-13 2008-03-18 Tioga Technologies Ltd. Transceiver with accelerated echo canceller convergence
US7076033B2 (en) * 2003-03-31 2006-07-11 Research In Motion Limited Bit rate matching system and method
US6798869B1 (en) 2003-03-31 2004-09-28 Research In Motion Limited Bit rate matching system and method
US7373498B2 (en) * 2003-12-23 2008-05-13 Intel Corporation Method and apparatus for updating a system configuration through an active or passive update
US7395363B2 (en) * 2004-09-09 2008-07-01 Intel Corporation Methods and apparatus for multiple bit rate serial communication
US7191255B2 (en) 2004-10-27 2007-03-13 Intel Corporation Transaction layer link down handling for PCI express
US7580696B2 (en) * 2004-12-14 2009-08-25 Lear Corporation Self-aligning vehicular transmitter system
US8041844B2 (en) 2004-12-29 2011-10-18 Intel Corporation Autodetection of a PCI express device operating at a wireless RF mitigation frequency

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120324139A1 (en) * 2011-06-14 2012-12-20 Advanced Micro Devices, Inc. Wireless communication for point-to-point serial link protocol
US9891653B2 (en) 2015-06-15 2018-02-13 Altera Corporation Techniques for clock rate changes during data rate changes in an integrated circuit (IC)

Also Published As

Publication number Publication date
DE112005003286B4 (en) 2012-01-05
TW200636489A (en) 2006-10-16
TWI313816B (en) 2009-08-21
CN100592278C (en) 2010-02-24
WO2006071665A2 (en) 2006-07-06
WO2006071665A3 (en) 2006-09-28
US20060143338A1 (en) 2006-06-29
US8041844B2 (en) 2011-10-18
DE112005003286T5 (en) 2007-11-22
CN101091171A (en) 2007-12-19

Similar Documents

Publication Publication Date Title
US20110289241A1 (en) Autodetection of a pci express device operating at a wireless rf mitigation frequency
CN108702358B (en) Scalable efficient high-speed serialized interconnect
CN106796563B (en) System and method for chip-to-chip communication
US9979432B2 (en) Programmable distributed data processing in a serial link
CN106209695B (en) Providing low power physical units for load/store communication protocols
US8006008B2 (en) Apparatus and method for data processing having an on-chip or off-chip interconnect between two or more devices
US20040120353A1 (en) Method and apparatus for double data rate serial ATA phy interface
US8135872B2 (en) USB controller and a testing method of the USB controller
CN104322033A (en) Controlling a physical link of a first protocol using an extended capability structure of a second protocol
US9524265B2 (en) Providing a serial protocol for a bidirectional serial interconnect
US11726947B2 (en) Interface device and method of operating the same
US20240248819A1 (en) Peripheral component interconnect express device and operating method thereof
US20240241569A1 (en) Method for adaptively adjusting state transition time in peripheral component interconnect express system to enhance overall performance, and associated apparatus
JP2011114625A (en) Communication system and communication device
US10333565B2 (en) Safe communication mode for a high speed link
US20140035633A1 (en) Autonomous initialization method of facing port of semiconductor integrated circuit and semiconductor integrated circuit

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION