Slave Identifier Scanning on CCIe Bus for Hot-Plug Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current I2C bus systems face challenges in efficiently identifying and managing slave devices, particularly in scenarios involving hot-plugging and high-speed data transmission, where existing methods are inadequate for dynamic protocol switching and device detection.
Innovation Solution
The implementation of a method for scanning slave identifiers (SIDs) on a CCIe bus, which involves transmitting inquiries with specific configurations of bits, modifying masks to expose additional bits, and using both lines of the bus for data transmission, allowing for efficient identification and management of slave devices, including support for hot-plugging and high-speed operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional I2C bus methods are used for device identification, then compatibility with legacy devices is maintained, but the efficiency of slave device identification and hot-plug capability deteriorates
Solution Approach 1:
The slave identifier is divided into multiple bits that are scanned sequentially through multiple inquiry transactions. Each inquiry targets specific bit positions, allowing the master device to efficiently determine the complete identifier by combining results from segmented transactions rather than using a single lengthy detection process.
Solution Approach 2:
The master device performs preliminary scanning of slave identifier bits during initialization and before hot-plug events. By proactively querying slave devices and storing their identifiers in advance, the system reduces detection time when devices are added or removed, as the identification framework is already established.
2Measurement precision
If iterative inquiry method is used to scan all slave identifier bits, then complete device identification is achieved, but the number of bus transactions increases
Solution Approach 1:
Multiple slave identifier bits are combined into a single comprehensive identifier value once all bits are scanned. The master device merges the individual bit results from multiple inquiries to form the complete slave identifier, reducing the overall complexity by consolidating the segmented information into a unified device identification.
Solution Approach 2:
The slave device creates a copy of its identifier that has been masked by applying a mask received in the inquiry. This copying mechanism allows the slave to efficiently compare its identifier against the inquiry parameters without directly manipulating the full identifier, simplifying the matching process while maintaining accuracy.
3Speed
If both lines of the bus are used for data transmission, then high-speed data transmission is enabled, but compatibility with single-ended I2C devices deteriorates
Solution Approach 1:
The CCIe bus interface is designed to universally support both differential and single-ended communication modes. The same physical bus infrastructure can operate in high-speed differential mode when both lines are utilized, or fall back to single-ended mode for compatibility with legacy I2C devices, making the system adaptable to different device types and speed requirements.
Solution Approach 2:
The bus operating mode is dynamically selected based on device capabilities and requirements. The system can switch between using both lines for high-speed transmission and single-line mode for legacy device compatibility, allowing the communication protocol to adapt its behavior to match the connected devices rather than requiring a fixed configuration.
Data Source
AI summary
System, methods and apparatus are described that facilitate transmission of data, particularly between two or more devices within an electronic apparatus. Embodiments disclosed herein relate to scanning for slave identifiers (SIDs) on a CCIe bus. A disclosed method includes transmitting a first inquiry on a control data bus, where the first inquiry includes a first configuration of bits, determining presence of a slave device that has a slave identifier that includes a second configuration of bits that matches the first configuration of bits, and repetitively transmitting additional inquiries on the control data bus with different configurations of bits until all bits of the slave identifier are determined. The slave device may assert a response to each inquiry that includes a configuration of bits that matches a corresponding configuration of bits in the slave identifier.