-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
arch/risc-v/mpfs ethernet improvements #15979
arch/risc-v/mpfs ethernet improvements #15979
Conversation
- Use LPWORK by default if CONFIG_MPFS_ETHMAC_HPWORK is not defined - Always use LPWORK for timeouts; this makes very lengthy operations such as re-initializing PHY. Signed-off-by: Jukka Laitinen <jukka.laitinen@tii.ae>
…roken PHYs If the interface is UP, and no packets are received in 30s, re-initialize the interface by calling the already implemented mpfs_txtimeout_expiry. This is a workaround for a bug where IF might be UP and working but packets can only be transmitted. Receive side just doesn't work at all. The bug manifests at least in older LAN8742A (rev A and B), for which also a silicon errata exists. The original issue can be re-produced easily by disconnecting and reconnecting the ethernet cable while the IF is up. Signed-off-by: Jukka Laitinen <jukka.laitinen@tii.ae>
…UG_NET - Fix compilation failure "error: 'mpfs_phydump' defined but not used [-Werror=unused-function]" - Add debug dump of phy registers. Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>
mpfs_phyinit() was called twice during ifup(). Signed-off-by: Jani Paalijarvi <jani.paalijarvi@unikie.com>
[Experimental Bot, please feedback here] Yes, this PR appears to meet the basic NuttX requirements, but could be improved. While it provides a summary of the changes and testing information, it lacks detail in the Impact section. Specifically, it needs to address most of the "NO/YES" questions with more than a single sentence. For example, even though the impact is stated as "only MPFS ethernet," the PR should explicitly state NO for impacts like user changes, build process changes, documentation updates, security implications, etc. If any of these are YES, then a detailed explanation is required. The testing section also needs to include actual logs, not just a description of the test environment. |
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.
for 64d2953 please change the title to
arch/risc-v/mpfd: set GMAC_RX_UNITSIZE to max gmac frame len
64d2953
to
0c06e37
Compare
I believe I have addressed all the review comments, is this good to go in? |
Verify that GMAC RX/TX buffers are 64 byte aligned Signed-off-by: Jukka Laitinen <jukka.laitinen@tii.ae>
0c06e37
to
7985c55
Compare
Summary
This updates the mpfs_ethernet driver by picking the following corrections from TII/SSRC branches:
Impact
Impacts only MPFS ethernet, improves reliability.
user changes: NO
build process changes: NO
documentation updates: NO
security implications: NO
Testing
Build Host: Ubuntu 22.04
Target: icicle:hwtest & 3 custom HW designs.