linux-kernel - Re: [PATCH v5 1/4] ASoC: dt-bindings: move tas2563 from tas2562.yaml to tas2781.yaml

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <015c913b-0462-4431-b716-ee45ac9fefe0@linaro.org>
Date: Thu, 4 Jan 2024 21:58:06 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Shenghao Ding <shenghao-ding@...com>, broonie@...nel.org,
 conor+dt@...nel.org
Cc: robh+dt@...nel.org, andriy.shevchenko@...ux.intel.com, kevin-lu@...com,
 baojun.xu@...com, devicetree@...r.kernel.org, lgirdwood@...il.com,
 perex@...ex.cz, pierre-louis.bossart@...ux.intel.com, 13916275206@....com,
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org,
 liam.r.girdwood@...el.com, soyer@....hu, tiwai@...e.de, peeyush@...com,
 navada@...com
Subject: Re: [PATCH v5 1/4] ASoC: dt-bindings: move tas2563 from tas2562.yaml
 to tas2781.yaml

On 04/01/2024 15:57, Shenghao Ding wrote:
> 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@...com>


Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>

Best regards,
Krzysztof