-
Notifications
You must be signed in to change notification settings - Fork 475
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
Add mdio access type (clause 45/clause 22) attribute #1493
Conversation
Signed-off-by: Jiahua Wang <jiahua.wang@broadcom.com>
inc/saiswitch.h
Outdated
* FALSE - sai_switch_mdio_read_fn and sai_switch_mdio_write_fn use clasue 45 mdio access. | ||
* TRUE - sai_switch_mdio_read_fn and sai_switch_mdio_write_fn use clasue 22 mdio access. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could there be other clauses more in the future ? maybe this should be enum?, i think enum would be better here, since bool value should be used for something that is enabled or not, and here you have explicit types 22 and 45 to set
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
MDIO was originally defined in Clause 22 of IEEE RFC802.3. Clause 45 of the 802.3ae specification provided the ability to access 65,536 registers in 32 different devices on 32 different ports. 802.3ae is 20 years old. There is no new MDIO access mode in the last 20 years. MDIO frame format starts with 32 bits of logical 1 preamble and 2 bits of start of frame. The start of frame is 01 for clause 22 and 00 for clause 45. If the first bit of the start frame has to be logical 0, then no new MDIO frame format will be possible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i see, but it still would make sense to make it as enum, like for example you would have ipv4 and ipv6, it's better specify it as enum rather then bool, maybe lets ask community on this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed to attribute SAI_SWITCH_ATTR_MDIO_ACCESS_TYPE and enum sai_switch_mdio_clause_t
Signed-off-by: Jiahua Wang <jiahua.wang@broadcom.com>
@jiahua-wang , can you check why build is failing? |
@jiahua-wang failure is due to your change, check the error log in build:-
|
/** | ||
* @brief Switch MDIO access type | ||
* | ||
* set mdio access type (clause 22 or clause 45) before calling sai_switch_mdio_read_fn and sai_switch_mdio_write_fn |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why can't the platform decide to choose between cl22 or cl45 for the mdio r/w? why should a higher SAI layer tell which one to choose? i am not able to understand the usecase. Can you add more to the PR description?
attr should be named SAI_SWITCH_ATTR_SWITCH_MDIO_CLAUSE or SAI_SWITCH_ATTR_MDIO_CLAUSE, 2nd preffered |
With PR #1507 replacing this PR, I will close this PR. |
Signed-off-by: Jiahua Wang jiahua.wang@broadcom.com