Skip to content
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

[action] [PR:19473] [Mellanox] implement state machine for always firmware control ports (#19473) #19688

Merged
merged 1 commit into from
Jul 25, 2024

Conversation

mssonicbld
Copy link
Collaborator

  • Why I did it
    When module host management is enabled, all modules are managed by the same state machine which initializes all modules/ports. However, on 5600 and 5400, there is a type of port which we called "service port". Those ports are always under firmware control. In that case, those ports should be managed by a different state machine. This PR is to implement the state machine for always firmware control ports.

  • How I did it
    Implement a state machine for always firmware control ports.

  • How to verify it
    Manual test
    unit test

…onic-net#19473)

- Why I did it
When module host management is enabled, all modules are managed by the same state machine which initializes all modules/ports. However, on 5600 and 5400, there is a type of port which we called "service port". Those ports are always under firmware control. In that case, those ports should be managed by a different state machine. This PR is to implement the state machine for always firmware control ports.

- How I did it
Implement a state machine for always firmware control ports.

- How to verify it
Manual test
unit test
@mssonicbld
Copy link
Collaborator Author

Original PR: #19473

@mssonicbld mssonicbld merged commit 239ae3d into sonic-net:202311 Jul 25, 2024
11 checks passed
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.

2 participants