Hot-Insertion of I2C Devices
Permalink
Bookmark
Share
Twitter
Digg
Reddit
Facebook
Stumbleupon
Del.icio.us| IP.com Number | IPCOM000015956D |
|
|
|---|---|---|---|
| Dated | May 8, 2002 UTC | ||
| Size | 1 page(s) (34.4 KB) | ||
| Disclosed by |
|
||
Publication Summary
In today's server systems hot plugging of adapter cards, system components, memory, etc. has become a wide spread function. Often I2C devices reside on these hot-plug or hot-added devices to provide VPD or other system monitoring functions. It is not possible to instruct every I2C agent that may reside on the shared bus to stop "talking" before a hot-plug event occurs. If a hot-plug event were to occur while the I2C bus was not IDLE, the I2C bus could possibly become corrupted. When hot-plugging an I2C device, this invention will ensure that the I2C bus is in an IDLE state before connecting/disconnecting the bus thus preventing I2C bus corruption. The invention consists of a FET switch, circuitry to detect an I2C IDLE condition, and circuitry to communicate with the user/system. For a hot-remove event, the invention first detects that the user/system wants to hot-remove an I2C device. The invention will then monitor the I2C bus for an IDLE state. Once IDLE is detected, the invention will disconnect the I2C device from the bus using a FET switch and then signal to the system/user that the device can be removed. The same basic events occur for a hot-add. The invention hold the FET switch in the off position. The user hot-adds the I2C device and the system supplies power to the device. The invention waits for an IDLE cycle to be detected on the I2C bus and closes the FET switch. Completion of the close can then be communicated to the user/system. 1| Country | United States |
|---|---|
| Language | English (United States) |
About this Publication
This document was submitted to IP.com's Prior Art Database and this preview is designed to provide you with information regarding the contents of this document by displaying up to the first four pages of the document as scaled page renderings and displaying a limited amount of text which was extracted from the document on the Text Preview Tab.
To find out more on how to obtain the entire document, click the Download tab. There is a charge for downloading some Prior Art Database documents; please examine carefully whether you believe this document fills your needs before purchasing.
For more information about the Prior Art Database, visit the Learn section of this website. Thank you for visiting IP.com's Prior Art Database! You may wish to check out our Global Patent Search website before you leave.
Hot-Insertion of I2C Devices
In today's server systems hot plugging of adapter cards, system components, memory, etc. has become a wide spread function. Often I2C devices reside on these hot-plug or hot-added devices to provide VPD or other system monitoring functions. It is not possible to instruct every I2C agent that may reside on the shared bus to stop "talking" before a hot-plug event occurs. If a hot-plug event were to occur while the I2C bus was not IDLE, the I2C bus could possibly become corrupted. When hot-plugging an I2C device, this invention will ensure that the I2C bus is in an IDLE state before connecting/disconnecting the bus thus preventing I2C bus corruption. The invention consists of a FET switch, circuitry to detect an I2C IDLE condition, and circuitry to communicate with the user/system.
For a hot-remove event, the invention first detects that the user/system wants to hot-remove an I2C device. The invention will then monitor the I2C bus for an IDLE state. Once IDLE is detected, the invention will disconnect the I2C device from the bus using a FET switch and then signal to the system/user that the device can be removed. The same basic events occur for a hot-add. The invention hold the FET switch in the off position. The user hot-adds the I2C device and the system supplies power to the device. The invention waits for an IDLE cycle to be detected on the I2C bus and closes the FET switch. Completion of the close can then be communicated to the use...