diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2026-08-03 17:40:56 -0700 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-08-03 17:40:56 -0700 |
| commit | ef26a42b07d59bdc4d6b0727554a9366ab708d1a (patch) | |
| tree | 7d5662339cca4422d74663d19f73ff72d6f3ced0 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 958f2f4b1dc784c80b47c7778c305c955af0ca06 (diff) | |
| parent | 48806dbee0c256406a7998fa16edb9a4c6da9982 (diff) | |
Merge branch 'net-stmmac-only-use-mac-loopback-for-selftests'
Maxime Chevallier says:
====================
net: stmmac: only use MAC loopback for selftests
stmmac selftests currently use PHY loopback when a PHY is attached, and
fallback to MAC loopback otherwise. PHY loopback however isn't ideal nor
necessary for the tests we are running, that only stress the internal
stmmac features.
Some PHYs bring the carrier state down when in loopback mode, which will
prevent any packet transmission even for ourselves, making selftests
fail for non-stmmac related reasons.
Let's rely only on MAC-side loopback for selftests, making it clear that
any problem found with stmmac selftests are indeed caused by the stmmac
driver, and not external factors.
This was tested on :
- Cyclone V with RGMII link to KSZ9031
- Cyclone V with 1000BaseX
- imx8mp with RGMII link to KSZ9131
- stm32mp157& with RGMII link to RTL8211F
- Allwinner H2+ with an internal PHY
====================
Link: https://patch.msgid.link/20260728155728.1193169-1-maxime.chevallier@bootlin.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions
