Skip to content

Dynamic transceiver tuning support #26

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 10 commits into from
Jun 6, 2019
Merged

Conversation

dgsudharsan
Copy link
Collaborator

@dgsudharsan dgsudharsan commented Mar 28, 2019

- What I did
Dynamic transceiver tuning support
- How I did it
Dynamically program pre-emphasis and other settings based on media detected in xcvrd. The various supported media are defined in media_settings.json

- How to verify it
Perform OIR of different media types. Dump the pre-emphasis values from hardware and verify that they got reflected

- Description for the changelog

Support for dynamically programming pre-emphasis

- A picture of a cute animal (not mandatory but encouraged)

UT fixes

UT fixes

Addressing code review comments

Addressing review comments

Adding media key values in global section

Adding media key values in port section

Fixing for SR4 case
@dgsudharsan dgsudharsan changed the title Preemphasis related changes Dynamic transceiver tuning support Mar 28, 2019
@lguohan lguohan requested a review from jleveque March 28, 2019 15:31
# Connect to ASIC_DB to notify Media notifications
asic_db = daemon_base.db_connect(swsscommon.ASIC_DB)
media_notifier = swsscommon.NotificationProducer(asic_db,
"MEDIANOTIFICATION")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be app db.

Copy link

@stevenlu99 stevenlu99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a corner case that user might insert a SFP during warmboot, In such case that function post_port_sfp_dom_info_to_db seems will skip programming serdes tuning value to asic and will never be programmed for this newly plugged SFP until OIR again.
Could you consider such case even is a very rare case?

@dgsudharsan
Copy link
Collaborator Author

There is a corner case that user might insert a SFP during warmboot, In such case that function post_port_sfp_dom_info_to_db seems will skip programming serdes tuning value to asic and will never be programmed for this newly plugged SFP until OIR again.
Could you consider such case even is a very rare case?

Hi @stevenlu99 Yes I think that event will be very rare case and is it worth to handle such a case? I am not sure if someone might do a warm reboot and in parallel change cabling (It defeats the purpose of warm reboot)

dgsudharsan added 4 commits May 14, 2019 12:13
Support for multiple ranges

Added logic to have default values at global level incase multiple ports have same defaults
@lguohan lguohan merged commit 366ac0e into sonic-net:master Jun 6, 2019
@dgsudharsan dgsudharsan deleted the dgpreemp branch October 8, 2019 05:38
@jleveque jleveque added the xcvrd label Jul 10, 2020
vdahiya12 pushed a commit to vdahiya12/sonic-platform-daemons that referenced this pull request Apr 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants