diff options
| author | Jacky Chou <jacky_chou@aspeedtech.com> | 2025-12-11 14:24:58 +0800 |
|---|---|---|
| committer | Paolo Abeni <pabeni@redhat.com> | 2025-12-22 12:06:18 +0100 |
| commit | d1a1a4bade4b20c0858d0b2f81d2611de055f675 (patch) | |
| tree | ea19317d11c3d0919c8210de83558a9b8ec3ebcb /tools/perf/scripts/python/git@git.tavy.me:linux-stable.git | |
| parent | bf4172bd870c3a34d3065cbb39192c22cbd7b18d (diff) | |
net: mdio: aspeed: add dummy read to avoid read-after-write issue
The Aspeed MDIO controller may return incorrect data when a read operation
follows immediately after a write. Due to a controller bug, the subsequent
read can latch stale data, causing the polling logic to terminate earlier
than expected.
To work around this hardware issue, insert a dummy read after each write
operation. This ensures that the next actual read returns the correct
data and prevents premature polling exit.
This workaround has been verified to stabilize MDIO transactions on
affected Aspeed platforms.
Fixes: f160e99462c6 ("net: phy: Add mdio-aspeed")
Signed-off-by: Jacky Chou <jacky_chou@aspeedtech.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Link: https://patch.msgid.link/20251211-aspeed_mdio_add_dummy_read-v3-1-382868869004@aspeedtech.com
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/git@git.tavy.me:linux-stable.git')
0 files changed, 0 insertions, 0 deletions