- List of Tables
- Revision
- Definition
- References
- About This Manual
- 1 Introduction and Scope
- 2 Requirements
- 3 Architecture Design
- 4 High-Level Design
- 5 SAI API
- 6 Configuration and management
- 7 Warmboot and Fastboot Design Impact
- 8 Restrictions or Limitations
- 9 Unit Test cases
| Rev | Date | Author | Change Description |
|---|---|---|---|
| 0.1 | 05/05/2023 | Anoop Kamath | Initial version |
| Term | Definition |
|---|---|
| xcvrd | Transceiver Daemon |
| CMIS | Common Management Interface Specification |
| DP | Data Path |
| DPInit | Data-Path Initialization |
| QSFP-DD | QSFP-Double Density (i.e. 400G) optical module |
| SI | Signal Integrity |
| EC | Explicit Control |
| TX | Transmit |
| RX | Recieve |
| EQ | Equalizer |
| Document | Location |
|---|---|
| CMIS v5 | CMIS5p0.pdf |
This is a high-level design document describing the way to apply custom SI settings for CMIS supported modules.
Certain high-speed QSFP_DD, OSFP and QSFP modules require Signal Integrity (SI) settings to match platform media settings in order to achieve link stability, right tunning and optimal performance.
Excerpt from CMIS5.0 spec providing definition of Signal Integrity:
These SI settings can vary based on combination of the module vendor plus platform vendor. The module will have default TX/RX SI settings programmed in its EEPROM by module vendor, but platform vendor has provision to overwrite these settings to match their platform requirements. The host can apply new TX SI settings when TX Input Adaptive EQ is disabled for all TX Data Path lanes but RX SI settings can be applied directly. These TX/RX setting should be applied with Explicit Control bit is set to 1.
Excerpt from CMIS5.0 spec providing definition of Explicit Control:
This feature would be enabled per platform basis. If platform wants to use this feature, they would need to provide optics_si_setting.json file during init for XCVRD to parse it. The SI parameters can be vendor and module specific. The vendor can populate desired SI param values in a JSON file. Provide an approach in the CMIS state machine to generate and apply host defined SI parameters to module eeprom. The Modules that do not support CMIS and not part of CMIS state machine are not in the scope of this document.
The SI media setting file optics_si_setting.json needs to be defined by each platform_vendor that will need SI settings. All SKUs of the platform will share the same optics_si_setting.json file. If no file is found, then this mechanism will be ignored.
This file will have two blocks: the first is global level setting and the next is port level setting. These blocks will contain subblocks of range or indiviual ports. Inside this port block, there will be subblocks for different lane speeds which will eventuall have per-lane SI parameter setting values based on the type of vendor that are expected to be programmed. The SI settings will not depend on cable length.
TX EQ (TX input equalizer control) setting can be FIXED or ADAPTIVE. Only adaptive EQ should be used for TX input, and it's enabled as the default setting in module. Fixed EQ is not recommended for TX direction and will not work until the SI/Hardware team explicitly recommends it.
If the TxInputEqFixedManualControlSupported flag is set, then the TX SI params will be applied and we need to disable AdaptiveInputEqEnableTx.
TX SI Control Advertisement: Page 01h Byte 161 - Bit 2 - TxInputEqFixedManualControlSupported Bit 3 - TxInputAdaptiveEqSupported
TX Input EQ register control: Page 10h Byte 153 – 159
| Byte | Field Name |
|---|---|
| 153 | AdaptiveInputEqEnableTx1..8 (lane 1-8) |
| 154 - 155 | AdaptiveInputEqRecallTx1..8 (lane 1-8) |
| 156 - 159 | FixedInputEqTargetTx1..8 (lane 1-8) |
The RX_SETTING SI settings can be directly written and applied for RX output equalization if RX Output Controls are Supported.
TX SI Control Advertisement: Page 01h Byte 162 - Bit 2 - RxOutputAmplitudeControlSupported Bit 3-4 - RxOutputEqControlSupported
The RX Output EQ register control: Page 10h Byte 162 – 173
| Byte | Field Name |
|---|---|
| 162 - 165 | OutputEqPreCursorTargetRx1..8 (lane 1-8) |
| 166 - 169 | OutputEqPostCursorTargetRx1..8 (lane 1-8) |
| 170 - 173 | OutputAmplitudeTargetRx1..8 (lane 1-8) |
This block's first level of identification will be the range of port numbers. The ports can be defined as a range of 0-31 or a list of multiple ports: 1, 2, 3, or a list of ports in the range of 5–10, 25–31, matching the index number in the port_config.ini file. This port range will have a unique defined lane speed, which will have unique vendor and vendor part number entries supporting this speed. Module key will be created based on speed and vendor details.
Each vendor will have per-lane SI param attribute entries applicable for the identified port + speed for the platform vendor. This value will be searched through the module key.
The entries in this block will be unique single port numbers. The control of SI attribute list generation search will reach the PORT_MEDIA_SETTINGS block only when no attribute list is generated in the GLOBAL_MEDIA_SETTINGS block.
There will be unique speed and vendor/vendor_PN entries in each identified port block.
Default values can be platform defaults for multiple vendors in each section.
- FixedInputEqTargetTx
- OutputEqPreCursorTargetRx
- OutputEqPostCursorTargetRx
- OutputAmplitudeTargetRx
{
"GLOBAL_MEDIA_SETTINGS": {
"0-17,19-24": {
"100G_SPEED": {
"CREDO-CAC82X321MXYXYHW": {
"OutputEqPreCursorTargetRx": {
"OutputEqPreCursorTargetRx1": 5,
"OutputEqPreCursorTargetRx2": 5,
"OutputEqPreCursorTargetRx3": 5,
"OutputEqPreCursorTargetRx4": 5,
"OutputEqPreCursorTargetRx5": 5,
"OutputEqPreCursorTargetRx6": 5,
"OutputEqPreCursorTargetRx7": 5,
"OutputEqPreCursorTargetRx8": 5
}
},
"CISCO-INNOLIGHT-T-DXXNT-NCI": {
"OutputEqPostCursorTargetRx": {
"OutputEqPostCursorTargetRx1": 8,
"OutputEqPostCursorTargetRx2": 8,
"OutputEqPostCursorTargetRx3": 8,
"OutputEqPostCursorTargetRx4": 8,
"OutputEqPostCursorTargetRx5": 8,
"OutputEqPostCursorTargetRx6": 8,
"OutputEqPostCursorTargetRx7": 8,
"OutputEqPostCursorTargetRx8": 8
}
}
}
},
"25,28,30": {
"100G_SPEED": {
"Default": {
"OutputAmplitudeTargetRx": {
"OutputAmplitudeTargetRx1": 7,
"OutputAmplitudeTargetRx2": 7,
"OutputAmplitudeTargetRx3": 7,
"OutputAmplitudeTargetRx4": 7,
"OutputAmplitudeTargetRx5": 7,
"OutputAmplitudeTargetRx6": 7,
"OutputAmplitudeTargetRx7": 7,
"OutputAmplitudeTargetRx8": 7
}
}
}
}
},
"PORT_MEDIA_SETTINGS": {
"18": {
"100G_SPEED": {
"Default": {
"OutputEqPostCursorTargetRx": {
"OutputEqPostCursorTargetRx1": 5,
"OutputEqPostCursorTargetRx2": 5,
"OutputEqPostCursorTargetRx3": 5,
"OutputEqPostCursorTargetRx4": 5,
"OutputEqPostCursorTargetRx5": 5,
"OutputEqPostCursorTargetRx6": 5,
"OutputEqPostCursorTargetRx7": 5,
"OutputEqPostCursorTargetRx8": 5
}
}
}
}
}
}
Please refer below points in line with flow diagram.
-
When CMIS-supported module insertion happens in XCVRD, the module will progress to the AP_CONFIG state (after DP_DEINIT state applying app code, EC = 0)) in the CMIS state machine. During which, when the module is in DataPathDeactivated or Disabled state, the desired AppSel code is applied. When the Config Success is validated and before DP_INIT state, check if the optics_si_setting.json file is parsed successfully and if lane speed needs special Signal Integrity (SI) settings. The lane speed is generated based on the module speed and the host lane count.
-
If both of the above conditions are met, then proceed to generate the key (module key) and retrieve the SI attribute list.
2.1. Generate module key based on Data Path(DP) lane speed + module vendor name, + module vendor part number.
2.2. Using this module key (2.1), the search begins for the detected port in the GLOBAL_MEDIA_SETTINGS section. If the module key matches any entries or any search that matches for (2.3) to (2.5) sections, then SI attributes from this section are copied to the SI param attribute list (2.7).
2.3. If no match happens in 2.2, reduce the search to module default + speed of the detected port in GLOBAL_MEDIA_SETTINGS
2.4. If no match happens in 2.3, reduce the search to the speed of the detected port in GLOBAL_MEDIA_SETTINGS
2.5. If no match happens in the GLOBAL_MEDIA_SETTINGS block, the search now begins in the PORT_MEDIA_SETTINGS block for the detected port. If no match happens in the PORT_MEDIA_SETTINGS block, the final search for the default block is done.
2.6. If no match happens to the default block, then an empty attribute list (2.8) is returned. -
Get the attribute list and validate if the list is not empty, then proceed to process the SI setting param list. If the list is empty, continue with the DP_INIT state in the CMIS state machine.
-
After applying the application code to the configuration with Explicit Control (EC) = 0, and committed to the activate state, now read and cache the default or active TX/RX SI settings. We need to cache the default values of the module. It's possible that we may not modify all the parameters. In such cases, we need to apply new SI values along with the default values that were already present. If we only apply the new values in Staged Control Set, the other values will be set to 0 in the Active Control Set.
Reference Register: Upper Page 10h bytes 145 –152 (desired ApSel Code)
Reference Register: Upper Page 11h bytes 214 to 234 -
Update the new values from the attribute list (3) to the cached SI list (5).
-
Write new EQ settings to Staged Control Set 0. EQ settings include: new SI attribute list from (5) - Validate this against SI Controls Advertisement, disabling adaptive TX input EQ settings if applicable. Apply application code to config with EC = 1 and commit to the active set.
Reference Register: Upper Page 01h bytes 161 - 162 (TX/RX SI Controls Advertisement)
Reference Register: Upper Page 10h bytes 143 (Applying APSel Config using ApplyDPInit, Copying from Staged Control Set to Active Control Set)
Reference Register: Upper Page 10h bytes 145 – 152 (desired ApSel Code)
Reference Register: Upper page 10h byte 153 - 173 (desired Host defined SI settings for EC=1 mode) -
Validate the config_status code, if the status is not config success, then force CMIS to reinit and retry. If the configuration fails after 3 retry attempts, print an error message and exit from initializing this port. If config_status is successful, then continue with the DP_INIT state in the CMIS state machine.
Reference Register: Upper Page 11h Byte 202-205 (config_status register)
CMIS FSM change:
SI attribute generation flow:
There are no changes to SAI API
There are no changes to any CLI/YANG model or Config DB enhancements.
There is no impact to Warmboot and Fastboot design. This feature is invoked as part of exisiting CMIS manager flow only
If transceiver is not present:
- All the workflows mentioned above will not invoke Modules that do not support CMIS and not part of CMIS state machine are not in the scope of this document.
- Check XCVRD/CMIS log if optics SI settings are succesfully applied for module which expect the SI settings.
- Check XCVRD/CMIS log if optics SI settings are ignored for modules that dont expect the SI settings.
- Validate no link flaps or link down once SI settings are applied