diff options
| author | Maxime Chevallier <maxime.chevallier@bootlin.com> | 2026-08-26 16:04:53 +0200 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-08-27 10:53:27 -0700 |
| commit | d29b399150b07796dfa81d8778d4804c08c2a41d (patch) | |
| tree | 55c37e7d2d0de46824b950032dac05041f8c48d6 /tools/perf/scripts/python | |
| parent | e2a6641e3bfde58f2284f9859c2b0fdcc6d1c0da (diff) | |
| download | linux-d29b399150b07796dfa81d8778d4804c08c2a41d.tar.gz linux-d29b399150b07796dfa81d8778d4804c08c2a41d.zip | |
net: stmmac: selftests: Check multiple MMC counters
The MMC counters report MAC statistics. Multiple counters can be
enabled when the IP is integrated, however there's no way to know
exactly which ones. Un-implemented counters seem to report 0.
It was found that on StarFive JH7110 and Amlogic SM1, the counter that's
used by the selftest (mmc_tx_framecount_g) isn't implemented, triggering
an MMC selftest failure.
Both the above SoCs seem to implement mmc_rx_framecount_gb, let's use
this counter as well for MMC counter validation.
Note that this doesn't guarantee that we won't encounter the same issue
again if another IP implements yet another set of counters that don't
include that new one.
If the game of whack-a-mole with implemented counters becomes too hard to
maintain, we may simply consider removing the MMC selftest entirely.
Fixes: 091810dbded9 ("net: stmmac: Introduce selftests support")
Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Link: https://patch.msgid.link/20260826140500.616466-2-maxime.chevallier@bootlin.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
