PMBus™ – Coming To A Server Near YouComing …...2010/02/28  · PMBus – Coming To A Server Near YouComing To A Server Near You Bob White Chair, PMBus Specification Working Group

PMBus™ –Coming To A Server Near YouComing To A Server Near You

Bob WhiteChair, PMBus™ Specification Working Group

[email protected]

1

www.pmbus.org

Presentation Overview

• PMBus™ Specification And Application Profiles• PMBus In Today’s Servers• PMBus In Next Gen Servers

2

• New Energy Reading Commands• Clarification Of Status Bits And

SMBALERT# Signal• Other Coming Updates

DisclaimerAny Information About The Upcoming

3

Any Information About The Upcoming Revision Of The PMBus Specification And Application Profiles Is Preliminary And May

Change Without Notice.

The PMBus Specification

• Includes– How Devices

Communicate– Commands And Data

PMBus Spec

4

Commands And Data

• Does Not Include– Application Specific

Information– Required Commands– TolerancesRevision 1.2

Coming Soon

Application Profiles

• Includes– Required Commands– Required Data

FormatsApp Profile

5

Formats– Required Data Ranges– Tolerances

Application Profile For Server Power Coming

Soon After Specification Revision 1.2

Server Power Application Profile

• Addressing• Hardware• Data Formats

– Accuracy

• Status Commands• Limit Commands• Default Limits• Manufacturer

6

y– VOUT_MODE– Sensor– Formatting Tables

• Monitoring Power/Current/Voltage– Sensor Sampling

• Thermal Management

Manufacturer Controlled Limits

• Faults And Error Correction

• Capability And Inventory Reporting

• Write Protection• Interrupts

PMBus In A Server

MA

N

System ApplicationsNode Manger

Server Management

7

ServerMotherboard

BMC SubSystems

IPMI

PowerSupply

PowerSupply

WS-

M

PMBus In A Server

MA

N

System ApplicationsNode Manger

Server Management

BaseboardManagement

Controller

8

ServerMotherboard

BMC SubSystems

IPMI

PowerSupply

PowerSupply

WS-

M

PMBus In A Server

MA

N

System ApplicationsNode Manger

Server ManagementPMBus

9

ServerMotherboard

BMC SubSystems

IPMI

PowerSupply

PowerSupply

WS-

M

PMBus In A Server

MA

N

System ApplicationsNode Manger

Server Management

PMBus Is Not Used To Communicate Outside

The Server

10

ServerMotherboard

BMC SubSystems

IPMI

PowerSupply

PowerSupply

PMBus WS-

M

PMBus In Data Center

Data Center Applications

DMTFSMASH

11Server

Motherboard

BMC SubSystems

IPMI

PowerSupply

PowerSupply

PMBus

WS-

MANSystem Applications

SMASH

PMBus In Data Center

Data Center Applications

• Charge Back• Track Energy

Consumption• Thermal Mgt

• Protect Against Hot Spots

• Circuit Mgt

12Server

Motherboard

BMC SubSystems

IPMI

PowerSupply

PowerSupply

PMBus

WS-

MAN

• Circuit Mgt• Protect

Against Breaker Overload

System Applications

PMBus In A Next Gen Server

Val e Add

AdditionalSystem

ManagementFunctions

13

ServerMotherboard

BMC SubSystems

IPMI

PowerSupply

PowerSupply

PMBus

Value AddProcessor

PMBus In A Next Gen Server

Val e Add

MultipleMaster

Bus

14

ServerMotherboard

BMC SubSystems

IPMI

PowerSupply

PowerSupply

PMBus

Value AddProcessor

Multiple Output Power Supplies

15

Multiple Output Power Supplies

PAGECommandSets TheSwitch

16

Multiple Output Power SuppliesStep 1:Set The

Desired Output (PAGE)

Step 2:Send A

Command To That Output

17

Potential Conflict

Val e Add

1. VAP Sets PAGE

2. BMC Sets A Different PAGE

3. VAP Sends A Command –

To The Wrong Output!

18

ServerMotherboard

BMC SubSystems

IPMI

PowerSupply

PowerSupply

PMBus

Value AddProcessor

PAGEPLUS

• New Command: PAGE PLUS• Transmit In One Bus Transaction

– Device AddressS t Th PAGE

19

– Set The PAGE– Send A Command To That Page– Write Or Read Data Related To That Command

ADDRESS PAGE CMD COMMAND DATA (R/W)

Another Potential Conflict

Val e Add

1. BMC Reads Status

2. BMC ClearsStatus

3. VAP Can’t Know What Happened

20

ServerMotherboard

BMC SubSystems

IPMI

PowerSupply

PowerSupply

PMBus

Value AddProcessor

Another Potential Conflict

Val e Add

Why Can’t These Two Processors Talk To Each Other?

21

ServerMotherboard

BMC SubSystems

IPMI

PowerSupply

PowerSupply

PMBus

Value AddProcessor

Duplicate Status Information

STA

TUS

_x

PAG

E M

22

STA

TUS

_x

PAG

E N

Bits Set Together/Cleared Individually

STA

TUS

_x

PAG

E M Cleared By One Master

23

STA

TUS

_x

PAG

E N Cleared By The Other Master

Reading Input And Output Power

• PMBus Has READ_POUT And READ_PIN Commands

• But…G tti G d V l F P I P bl ti

24

• Getting Good Values For Power Is Problematic• Issues

– Averaging Time– Data Age– Averaging Calculation Methods

• OEMS Are Looking For Accuracy Of 1-2%

Reading Input And Output Power

• PMBus Has READ_POUT And READ_PIN Commands

• But…G tti G d V l F P I P bl ti

25

• Getting Good Values For Power Is Problematic• Issues

– Averaging Time– Data Age– Averaging Calculation Methods

• OEMS Are Looking For Accuracy Of 1-2%

“Sampling And Averaging Considerations For Measuring

AC Input Power”APEC 2009

READ_EIN And READ_EOUT

• Revision 1.2 Will Have Two New Commands:READ_EIN And READ_EOUT

• Attempt Is To Make Reporting Of PowerI d d t Of PMB D i Ch t i ti

26

– Independent Of PMBus Device Characteristics– Put Computation Burden On Host– Put Time Keeping Burden On Host

• Commands Will Return Two Values– An Accumulated Energy Reading (“Watt-Samples”)– Current Number Of Power Samples

Discrete Time Power Calculation

Power Calculation

27

• Discrete Time Power Calculation

1 1

1 1[ ] [ ] [ ]N N

AVEn n

P p n v n i nN N

Power Calculation

• Host Keeps At Least The Last Values Returned– With Time Stamp Information If Needed– Rollover Tracking Are The Host’s Responsibility

Host Retrieves Accumulator And Sample Count

28

• Host Retrieves Accumulator And Sample Count When It Wants

• Host Calculates The Average Power Since The Last Reading By:

Latest Accumulator Count – Previous Accumulator CountLatest Sample Count – Previous Sample CountAVERAGEP

Conceptual Implementation

Vin

Clock Multiplier

A/D

Scale ByLSB_V &

LSB_I

Accumulator(40 Bits?)

DataFormatter

Packet

29

Iin

Clock

A/D

SampleCounter(24 Bits)

Maker/Bus

Interface

Clock

Clarify Status Bits/SMBALERT#

• Comments Received That Specification Is Not Clear On How Status Bits Are:– Set

Cleared

30

– Cleared– Interact With SMBALERT# Signal

LATCHSET Q

Bit In STATUS_BYTE/STATUS_WORD Register

Bit In STATUS_X Register

Event Detector Output

Other Status BitsThat Can Set The

Same Bit In STATUS_BYTE/STATUS_WORD

Conceptual SchematicLooking At

Using A Conceptual

Schematic To Convey

F nctionalit

31

CLR

SMBALERT#Circuit

SMBALERT_MASK Bit

CLEAR_FAULTS

Write 1 To Status Register Bit

Device Address Sent In Response To Receiving A Read To The Alert Response

Address While SMBALERT# Asserted

Other Status BitsThat Can Cause

SMBALET# To Be Asserted

CLR

SMBALERT#

PAGE Selected

Functionality

LATCHSET Q

Bit In STATUS_BYTE/STATUS_WORD Register

Bit In STATUS_X Register

Event Detector Output

Other Status BitsThat Can Set The

Same Bit In STATUS_BYTE/STATUS_WORD

Conceptual Schematic

NewClear Individual Status Bits

And Registers

32

CLR

SMBALERT#Circuit

SMBALERT_MASK Bit

CLEAR_FAULTS

Write 1 To Status Register Bit

Device Address Sent In Response To Receiving A Read To The Alert Response

Address While SMBALERT# Asserted

Other Status BitsThat Can Cause

SMBALET# To Be Asserted

CLR

SMBALERT#

PAGE Selected

LATCHSET Q

Bit In STATUS_BYTE/STATUS_WORD Register

Bit In STATUS_X Register

Event Detector Output

Other Status BitsThat Can Set The

Same Bit In STATUS_BYTE/STATUS_WORD

Conceptual SchematicNewSMBALERT_MASK

33

CLR

SMBALERT#Circuit

SMBALERT_MASK Bit

CLEAR_FAULTS

Write 1 To Status Register Bit

Device Address Sent In Response To Receiving A Read To The Alert Response

Address While SMBALERT# Asserted

Other Status BitsThat Can Cause

SMBALET# To Be Asserted

CLR

SMBALERT#

PAGE Selected

Other Changes

• Now Based On SMBus V2.0• Bus I/O High Impedance When Device Is Off• Group Protocol PEC Clarified

34

• IOUT_CAL_GAIN Updated• MFR_MAX_TEMP_1,2,3 Command

Not The Complete List!

Acknowledgment

Thanks To Brian Griffith Of Intel Corporation

35

pFor Contributions On “PMBus In A Server”,

“PMBus In the Data Center” And Server Power Application Profile

36