summaryrefslogtreecommitdiffstats
path: root/sound/soc/codecs
diff options
context:
space:
mode:
authorShenghao Ding <shenghao-ding@ti.com>2024-01-04 22:57:16 +0800
committerMark Brown <broonie@kernel.org>2024-01-05 13:27:15 +0000
commit3dbb4e3602d217d7139b95a36077a6b7252dc290 (patch)
tree1e6517cd016bbe98c64c057544ccaa1783c9120e /sound/soc/codecs
parent67508b874844b80ac49f70b78d67036c28b9fe7e (diff)
downloadlinux-stable-3dbb4e3602d217d7139b95a36077a6b7252dc290.tar.gz
linux-stable-3dbb4e3602d217d7139b95a36077a6b7252dc290.tar.bz2
linux-stable-3dbb4e3602d217d7139b95a36077a6b7252dc290.zip
ASoC: dt-bindings: move tas2563 from tas2562.yaml to tas2781.yaml
Move tas2563 from tas2562.yaml to tas2781.yaml to unbind tas2563 from tas2562 driver code and bind it to tas2781 driver code, because tas2563 only work in bypass-DSP mode with tas2562 driver. In order to enable DSP mode for tas2563, it has been moved to tas2781 driver. As to the hardware part, such as register setting and DSP firmware, all these are stored in the binary firmware. What tas2781 drivder does is to parse the firmware and download it to the chip, then power on the chip. So, tas2781 driver can be resued as tas2563 driver. Only attention will be paid to downloading corresponding firmware. Signed-off-by: Shenghao Ding <shenghao-ding@ti.com> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Link: https://msgid.link/r/20240104145721.1398-1-shenghao-ding@ti.com Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'sound/soc/codecs')
0 files changed, 0 insertions, 0 deletions