diff options
author | Nicolas Frattaroli <frattaroli.nicolas@gmail.com> | 2021-10-16 13:53:50 +0300 |
---|---|---|
committer | Mark Brown <broonie@kernel.org> | 2021-10-17 02:16:43 +0300 |
commit | d6365d0f0a03c1feb28d86dfd192972ddc647013 (patch) | |
tree | e28870f5f484ce627622f9654a169f2bf899acd0 /drivers | |
parent | 9a61277af7fb90e58bfd2608f0e28bb0649c4128 (diff) | |
download | linux-d6365d0f0a03c1feb28d86dfd192972ddc647013.tar.xz |
ASoC: rockchip: i2s-tdm: Strip out direct CRU use
In cases where both rx and tx lrck are synced to the same source,
the resets for rx and tx need to be triggered simultaneously,
according to the downstream driver.
As there is no reset API to atomically bulk (de)assert two resets
at once, what the driver did was implement half a reset controller
specific to Rockchip, which tried to write the registers for the
resets within one write ideally or several writes within an irqsave
section.
This of course violates abstractions quite badly. The driver should
not write to the CRU's registers directly.
In practice, for the cases I tested the driver with, which is audio
playback, replacing the synchronised asserts with just individual
ones does not seem to make any difference.
If it turns out that this breaks something in the future, it should
be fixed through the specification and implementation of an atomic
bulk reset API, not with a CRU hack.
Signed-off-by: Nicolas Frattaroli <frattaroli.nicolas@gmail.com>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
Message-Id: <20211016105354.116513-2-frattaroli.nicolas@gmail.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions