Public bug reported:
SRU Justification:
[Impact]
Once the BF3 MDIO clock is enabled by software it is expected and intended
for it to keep toggling. BF3 has a hardware GPIO bug where constant
toggling at "high frequencies" will lead to GPIO degradation.
[Fix]
* A workaround is to lower down the clock frequency.
* That will increase the "life expectation" of the GPIO.
* The lowest possible frequency we can achieve is 1.09Mhz by setting
mdio_period = 0xFF.
[Test Case]
* Check if the gige driver is loaded
* Check that the oob_net0 interface is up and operational
* Check that the OOB gets an ip
* Do SW reset and powercycle and check the oon_net0 interface again
[Regression Potential]
* Lowering the frequency shouldn't have any impact but it controls the access
to the PHY registers.
So do the usual OOB tests to verify that there is indeed no impact.
** Affects: linux-bluefield (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2086791
Title:
mlxbf-gige: Support workaround for MDIO GPIO degradation bug
Status in linux-bluefield package in Ubuntu:
New
Bug description:
SRU Justification:
[Impact]
Once the BF3 MDIO clock is enabled by software it is expected and intended
for it to keep toggling. BF3 has a hardware GPIO bug where constant
toggling at "high frequencies" will lead to GPIO degradation.
[Fix]
* A workaround is to lower down the clock frequency.
* That will increase the "life expectation" of the GPIO.
* The lowest possible frequency we can achieve is 1.09Mhz by setting
mdio_period = 0xFF.
[Test Case]
* Check if the gige driver is loaded
* Check that the oob_net0 interface is up and operational
* Check that the OOB gets an ip
* Do SW reset and powercycle and check the oon_net0 interface again
[Regression Potential]
* Lowering the frequency shouldn't have any impact but it controls the access
to the PHY registers.
So do the usual OOB tests to verify that there is indeed no impact.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2086791/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
