diff options
| author | Andrey Golovko <andrey.golovko@gmail.com> | 2026-09-12 19:29:50 +0300 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2026-09-16 22:09:11 +0100 |
| commit | b2c5435300c815373a2112522eb38857313b5b96 (patch) | |
| tree | 5dbc1ad5dd2c60d52e1a10d282f36cb905db1638 /tools/perf/scripts/python/task-analyzer.py | |
| parent | 48ed992bfbe53537ad1cbc8ad68f7031e7ac0af3 (diff) | |
ASoC: tas2783-sdw: stop describing the Latency and XU ID/Version Controls
The read-only Control list and tas2783_sdca_mbq_size() still describe the
Latency Control of every Entity - twenty-one registers in all - and the
XU ID and XU Version of the Extension Unit. The driver never reads any
of them, and the platform firmware seen so far describes exactly one of
the Latencies (FU21, as a DisCo constant) and neither of the two XU
Controls. XU ID answers COMMAND_IGNORED on the bus in every power
state.
Since commit f4ffa3820949 ("ASoC: tas2783-sdw: do not cache read-only
Controls") they have no defaults and are marked volatile, so every
access goes to the bus. Remove them from both tables: the driver then
neither declares them readable nor sizes them, and the read-only list is
left with the readings the device actually reports - Clock Valid, the
actual power state, the protection status and the algorithm ready flags.
No functional change for the driver itself, which does not read any of
the removed registers.
Link: https://lore.kernel.org/all/70a91202-e801-4008-bec8-883b229f9f0f@linux.dev/
Signed-off-by: Andrey Golovko <andrey.golovko@gmail.com>
Link: https://patch.msgid.link/20260912163500.8412-1-andrey.golovko@gmail.com
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions
