# US 2014/0207981 A1 · Cached PHY register data access

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

- Number: US 2014/0207981 A1
- Document ID: US20140207981A1
- Status: Published application
- Kind: A1
- Application number: 13/745,828
- Filed: 2013-01-20
- Published: 2014-07-24
- Earliest claimed: 2013-01-20
- Assignees: International Business Machines Corporation
- Inventors: Anthony E. Baker
- Web page: https://patentgrep.com/patent/US20140207981A1

## CPC

- G06F 13/4027: {using bus bridges (G06F13/4022 takes precedence)}
- G06F 13/28: using burst mode transfer, e.g. direct memory access {DMA}, cycle steal (G06F13/32 takes precedence)
- G06F 13/385: {for adaptation of a particular data processing system to different peripheral devices}
- G06F 13/4282: {on a serial bus, e.g. I2C bus, SPI bus (on daisy chain buses G06F13/4247)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Ethernet physical sublayer (PHY) devices each provide PHY register data. One or more of the Ethernet PHY devices are connected to each of one or more management data input/output (MDIO)/management data clock (MDC) interfaces to which a number of MDIO/MDC controllers are connected. Each MDIO/MDC controller polls a corresponding MDIO/MDC interface to receive the PHY register data from the one or more Ethernet PHY devices connected thereto. The MDIO/MDC controllers store portions of the PHY register data received from the Ethernet PHY devices to a memory to which an interface is connected. A processor connected to the interface accesses the portions of the PHY register data stored to the memory. The processor can retrieve the portions of the PHY register data over the interface more quickly than the MDIO/MDC controllers can retrieve the PHY register data over the MDIO/MDC interfaces.

## Claims

### Claim 1

A device comprising:
a processor;
one or more management data input/output (MDIO)/management data clock (MDC) interfaces to which the processor are not directly connected;
a plurality of Ethernet physical sublayer (PHY) devices one or more Ethernet PHY devices of the Ethernet PHY devices connected to each MDIO/MDC interface, each Ethernet PHY device to provide PHY register data directly onto the MDIO/MDC interface to which the Ethernet PHY device is connected;
a plurality of MDIO/MDC controllers separate from the processor, each MDIO/MDC controller connected to and to poll a corresponding MDIO/MDC interface of the MDIO/MDC interfaces to receive the PHY register data from the one or more Ethernet PHY devices connected to the corresponding MDIO/MDC interface;
a memory to which the MDIO/MDC controllers are to store portions of the PHY register data received from the Ethernet PHY devices; and
an interface separate from the MDIO/MDC interfaces and connecting the memory to the processor, the processor accessing the portions of the PHY register data stored to the memory to retrieve the PHY register data without having to poll the Ethernet PHY devices itself via the MDIO/MDC interfaces.

### Claim 2 (depends on 1)

The device of claim 1, wherein each MDIO/MDC controller is to drive an MDC and MDIO signal on the corresponding MDIO/MDC interface in accordance with which the one or more Ethernet PHY devices connected thereto provide the PHY register data.

### Claim 3 (depends on 1)

The device of claim 1, wherein each MDIO/MDC controller is to, responsive to receiving the PHY register data from the one or more Ethernet PHY devices connected to the corresponding MDIO/MDC interface, extract management information regarding the one or more Ethernet PHY devices from the PHY register data, and is to store the management information on the memory as the portions of the PHY register data.

### Claim 4 (depends on 1)

The device of claim 1, wherein each MDIO/MDC interface is a single-bit, serial bus,
and wherein the interface is one of: a multiple-bit, parallel bus; a peripheral component interconnect (PCI) serial bus; a peripheral component interconnect express (PCIe) bus.

### Claim 5 (depends on 1)

The device of claim 1, wherein retrieval of the PHY register data by the MDIO/MDC controllers over the MDIO/MDC interfaces occurs more slowly than retrieval of the portions of the PHY register data by the processor over the interface.

### Claim 6 (depends on 1)

The device of claim 1, wherein each MDIO/MDC controller is separately configurable to operate according to one of a plurality of different MDIO/MDC protocols, each MDIO/MDC protocol having a different voltage level at which the MDIO/MDC interface is to operate.

### Claim 7 (depends on 6)

The device of claim 6, wherein at a given time, different of the MDIO/MDC controllers are operating according to different of the MDIO/MDC protocols.

### Claim 8 (depends on 1)

The device of claim 1, further comprising one of a field-programmable gate array (FPGA) and a complex programmable logic device (CPLD), within which the MDIO/MDC controllers and the memory are implemented.

### Claim 9 (depends on 1)

The device of claim 1, wherein the processor is to access the portions of the PHY register data stored to the memory for all the Ethernet PHY devices within a single access of the interface.

### Claim 10 (depends on 1)

The device of claim 1, wherein the processor is to access the portions of the PHY register data stored to the memory on an as-needed basis.

### Claim 11

An apparatus for a device including a processor, comprising:
a plurality of management data input/output (MDIO)/management data clock (MDC) controllers separate from the processor of the device, each MDIO/MDC controller connectable to a corresponding MDIO/MDC interface of one or more MDIO/MDC interfaces to which the processor are not directly connected to receive PHY register data from one or more Ethernet physical sublayer (PHY) devices connected to the corresponding MDIO/MDC interface by polling the corresponding MDIO/MDC interface so that the processor avoids having to poll the corresponding MDIO/MDC interface itself; and
a memory to which the MDIO/MDC controllers are to store portions of the PHY register data received from the Ethernet PHY devices, the memory connectable to an interface other than the MDIO/MDC interfaces and by which the processor is to access the portions of the PHY register data stored to the memory to retrieve the PHY register data without having to poll the Ethernet devices itself via the MDIO/MDC interfaces.

### Claim 12 (depends on 11)

The apparatus of claim 11, wherein each MDIO/MDC controller is to, responsive to receiving the PHY register data from the one or more Ethernet PHY devices connected to the corresponding MDIO/MDC interface, extract management information regarding the one or more Ethernet PHY devices from the PHY register data, and is to store the management information on the memory as the portions of the PHY register data.

### Claim 13 (depends on 11)

The apparatus of claim 11, wherein retrieval of the PHY register data by the MDIO/MDC controllers over the MDIO/MDC interfaces occurs more slowly than retrieval of the portions of the PHY register data by the processor from the memory.

### Claim 14 (depends on 11)

The apparatus of claim 11, wherein each MDIO/MDC controller is configurable to operate according to one of a plurality of different MDIO/MDC protocols, each MDIO/MDC protocol having a different voltage level at which the MDIO/MDC interface is to operate.

### Claim 15 (depends on 11)

The apparatus of claim 11, wherein the apparatus is implemented as one of a field-programmable gate array (FPGA) and a complex programmable logic device (CPLD).

### Claim 16

A method comprising:
polling, by each management data input/output (MDIO)/management data controller (MDC) controller of a plurality of MDIO/MDC controllers of an apparatus of a device also including a processor separate from the MDIO/MDC controllers, one or more Ethernet physical sublayer (PHY) devices over a corresponding MDIO/MDC interface of one or more MDIO/MDC interfaces to which the processor are not directly connected;
after polling the one or more Ethernet PHY devices, receiving, by each MDIO/MDC controller, PHY register data from the one or more Ethernet PHY devices connected to the corresponding MDIO/MDC interface; and
after receiving the PHY register data, storing, by each MDIO/MDC controller, portions of the PHY register data to a memory to which the MDIO/MDC controllers are connected and to which an interface is connected, for access by the processor connected to the interface to retrieve the PHY register data without having to poll the Ethernet PHY devices itself via the MDIO/MDC interfaces.

### Claim 17 (depends on 16)

The method of claim 16, further comprising:
driving, by each MDIO/MDC controller, an MDC and MDIO signal on the corresponding MDIO/MDC interface in accordance with which the one or more Ethernet PHY devices connected thereto provide the PHY register data.

### Claim 18 (depends on 16)

The method of claim 16, further comprising, after receiving the PHY register data and before storing the portions of the PHY register data to the memory:
extracting, by each MDIO/MDC controller, management information regarding the one or more Ethernet PHY devices from the PHY register data, as the portions of the PHY register data.

### Claim 19 (depends on 16)

The method of claim 16, further comprising, in response to being polled:
providing, by each Ethernet PHY device of the one or more Ethernet PHY devices, the PHY register data over the corresponding MDIO/MDC interface.

### Claim 20 (depends on 16)

The method of claim 16, further comprising:
accessing, by the processor, the portions of the PHY register data from the memory over the interface within a single access of the interface.
