# US 10,372,657 B2 · Bimodal PHY for low latency in high speed interconnects

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 10,372,657 B2
- Document ID: US10372657B2
- Status: Granted
- Kind: B2
- Application number: 15/390,648
- Filed: 2016-12-26
- Published: 2018-06-28
- Granted: 2019-08-06
- Earliest claimed: 2016-12-26
- Assignees: Intel Corporation
- Applicants: Intel Corporation
- Inventors: Venkatraman Iyer; William R. Halleck; Rahul R. Shah; Eric Lee
- Web page: https://patentgrep.com/patent/US10372657B2

## CPC

- G06F 13/4068: {Electrical coupling}
- G06F 13/1673: {using buffers}
- G06F 13/1689: {Synchronisation and timing concerns (synchronisation on a memory bus G06F13/4234)}
- G06F 13/382: {using universal interface adapter}
- G06F 13/4282: {on a serial bus, e.g. I2C bus, SPI bus (on daisy chain buses G06F13/4247)}
- G06F 13/385: {for adaptation of a particular data processing system to different peripheral devices}
- G06F 2213/0026: PCI express
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems, methods, and apparatuses including a Physical layer (PHY) block coupled to a Media Access Control layer (MAC) block via a PHY/MAC interface. Each of the PHY and MAC blocks include a plurality of Physical Interface for PCI Express (PIPE) registers. The PHY/MAC interface includes a low pin count PIPE interface comprising a small set of wires coupled between the PHY block and the MAC block. The low pin count PIPE interface is configured to transfer register commands between the PHY and MAC blocks over the small set of wires in a time-multiplexed manner to support read and write access of the PHY and MAC PIPE registers. The PHY block may also be selectively configurable to implement a PIPE architecture when operating in a PIPE mode and a serialization and deserialization (SERDES) architecture when operating in a SERDES mode.

## Claims

### Claim 1

An apparatus comprising:
a Physical layer (PHY) block;
a Media Access Control layer (MAC) block; and
a PHY/MAC interface including,
a low pin count Physical Interface for PCI Express (PIPE) interface comprising,
a small set of wires coupled between the PHY and MAC blocks;
one or more PHY PIPE registers implemented in the PHY block; and
one or more MAC PIPE registers implemented in the MAC block,
wherein the low pin count PIPE interface is configured to transfer register commands between the PHY and MAC blocks over the small set of wires in a time-multiplexed manner.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the PHY/MAC interface further includes one or more signal lines dedicated for signals with critical timing requirements that are separate from the low pin count PIPE interface.

### Claim 3 (depends on 1)

The apparatus of claim 1, wherein the low pin count interface supports transmission from the PHY block to the MAC block in a first direction over a first data path and transmission from the MAC block to the PHY block in a second direction over a second data path, and each of the first and second data paths is 8-bits wide.

### Claim 4 (depends on 1)

The apparatus of claim 1, wherein the register commands includes a write request comprising an address and data to be written to a PHY PIPE register.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein the register commands includes a read request comprising an address of a PHY PIPE register to be read.

### Claim 6 (depends on 1)

The apparatus of claim 1, wherein the register commands includes a write request comprising an address and data to be written to a MAC PIPE register.

### Claim 7 (depends on 1)

The apparatus of claim 1, wherein the register commands includes a read request comprising an address of a MAC PIPE register to be read.

### Claim 8 (depends on 1)

The apparatus of claim 1, wherein the low pin count interface is further configured to implement a 12-bit address space into which PHY PIPE registers and MAC PIPE registers are mapped.

### Claim 9 (depends on 1)

The apparatus of claim 1, wherein the PHY block is selectively configurable to implement a PIPE architecture when operating in a PIPE mode and a serialization and deserialization (SERDES) architecture when operating in a SERDES mode.

### Claim 10 (depends on 1)

The apparatus of claim 1, wherein the MAC block comprises one of a PIPE compliant MAC or a serialization and deserialization (SERDES) compliant MAC.

### Claim 11

A Physical layer (PHY) chip, configured to interface with a Media Access Control layer (MAC) block, comprising:
a PHY block including circuitry to implement a Physical layer; and
a PHY/MAC interface including,
a low pin count Physical Interface for PCI Express (PIPE) interface comprising,
means for coupling the PHY block chip to a small number of wires to transmit signals to and receive signals from the MAC block; and
one or more PHY PIPE registers,
wherein the low pin count PIPE interface is configured to transfer register commands to the MAC block and receive register commands from the MAC block over the small number of wires in a time-multiplexed manner.

### Claim 12 (depends on 11)

The PHY chip of claim 11, wherein the PHY/MAC interface further includes means for coupling to one or more signal lines dedicated for signals with critical timing requirements that are separate from the low pin count PIPE interface.

### Claim 13 (depends on 11)

The PHY chip of claim 11, wherein the low pin count PIPE interface supports transmission of signals from the PHY block to the MAC block over a data transmission path in a first direction and reception of signals transmitted from the MAC block to the PHY block over a data reception path in a second direction, and each of the first and second data transmission path and data reception path is 8-bits wide.

### Claim 14 (depends on 11)

The PHY chip of claim 11, wherein the register commands includes a write request comprising an address and data to be written to a PHY PIPE register.

### Claim 15 (depends on 11)

The PHY chip of claim 11, wherein the register commands includes a read request comprising an address of a PHY PIPE register to be read.

### Claim 16 (depends on 11)

The PHY chip of claim 11, wherein the MAC block includes one or more MAC PIPE registers and the register commands includes a write request comprising an address and data to be written to a MAC PIPE register.

### Claim 17 (depends on 11)

The PHY chip of claim 11, wherein the MAC block includes one or more MAC PIPE registers and the register commands includes a read request comprising an address of a MAC PIPE register to be read.

### Claim 18 (depends on 11)

The PHY chip of claim 11, wherein the low pin count PIPE interface is further configured to implement a 12-bit address space into which PHY PIPE registers are mapped.

### Claim 19 (depends on 11)

The PHY chip of claim 11, wherein the MAC block includes one or more MAC PIPE registers and the low pin count PIPE interface is further configured to implement a 12-bit address space into which the one or more MAC PIPE registers are mapped.

### Claim 20 (depends on 11)

The PHY chip of claim 11, wherein the PHY block is selectively configurable to implement a PIPE architecture when operating in a PIPE mode and a serialization and deserialization (SERDES) architecture when operating in a SERDES mode.

### Claim 21

A Media Access Control layer (MAC) block, configured to interface with a Physical layer (PHY) block, comprising:
means for implementing a MAC layer; and
a PHY/MAC interface including,
a low pin count Physical Interface for PCI Express (PIPE) interface comprising,
means for coupling the MAC block to a small number of wires to transmit signals to and receive signals from the PHY block; and
one or more MAC PIPE registers,
wherein the low pin count PIPE interface is configured to transfer register commands to the PHY block and receive register commands from the PHY block over the small number of wires in a time-multiplexed manner.

### Claim 22 (depends on 21)

The MAC block of claim 21, wherein the PHY/MAC interface further includes means for coupling to one or more signal lines dedicated for signals with critical timing requirements that are separate from the low pin count PIPE interface.

### Claim 23 (depends on 21)

The MAC block of claim 21, wherein the low pin count PIPE interface supports transmission of signals from the MAC block to the PHY block over a data transmission path in a first direction and reception of signals transmitted from the PHY block to the MAC block over a data reception path in a second direction, and each of the first and second data transmission path and data reception path is 8-bits wide.

### Claim 24 (depends on 21)

The MAC block of claim 21, wherein the register commands includes a write request comprising an address and data to be written to a MAC PIPE register.

### Claim 25 (depends on 21)

The MAC block of claim 21, wherein the register commands includes a read request comprising an address of a MAC PIPE register to be read.

### Claim 26 (depends on 21)

The MAC block of claim 21, wherein the PHY block includes one or more PHY PIPE registers and the register commands includes a write request comprising an address and data to be written to a PHY PIPE register.

### Claim 27 (depends on 21)

The MAC block of claim 21, wherein the PHY block includes one or more PHY PIPE registers and the register commands includes a read request comprising an address of a PHY PIPE register to be read.

### Claim 28 (depends on 21)

The MAC block of claim 21, wherein the low pin count PIPE interface is further configured to implement a 12-bit address space into which MAC PIPE registers are mapped.

### Claim 29 (depends on 21)

The MAC block of claim 21, wherein the PHY block includes one or more PHY PIPE registers and the low pin count PIPE interface is further configured to implement a 12-bit address space into which the one or more PHY PIPE registers are mapped.

### Claim 30 (depends on 21)

The MAC block of claim 21, wherein the PHY block is selectively configurable to implement a PIPE architecture when operating in a PIPE mode and a serialization and deserialization (SERDES) architecture when operating in a SERDES mode.