linux-kernel - [PATCH v3 1/5] 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-next>] [day] [month] [year] [list]

Message-ID: <20231225053932.1138-1-shenghao-ding@ti.com>
Date: Mon, 25 Dec 2023 13:39:27 +0800
From: Shenghao Ding <shenghao-ding@...com>
To: <broonie@...nel.org>, <conor+dt@...nel.org>,
        <krzysztof.kozlowski@...aro.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>,
        Shenghao Ding <shenghao-ding@...com>
Subject: [PATCH v3 1/5] ASoC: dt-bindings: move tas2563 from tas2562.yaml to tas2781.yaml

Move tas2563 from tas2562.yaml to tas2781.yaml, because tas2563 only work
in bypass-DSP mode with tas2562 driver. In oder 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 dooes is to parse the firmware and
download them to the tas2781 or tas2563, then power on tas2781 or tas2563.
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>

---
Change in v3:
 - remove tas2563, which will be move to tas2781 driver
 - Add more comments on why move tas2563 to tas2781 driver
 - provide rationale in terms of bindings and hardware, not in terms of driver.
   Or at least not only.
---
 Documentation/devicetree/bindings/sound/tas2562.yaml | 2 --
 1 file changed, 2 deletions(-)

diff --git a/Documentation/devicetree/bindings/sound/tas2562.yaml b/Documentation/devicetree/bindings/sound/tas2562.yaml
index f01c0dde0cf7..d28c102c0ce7 100644
--- a/Documentation/devicetree/bindings/sound/tas2562.yaml
+++ b/Documentation/devicetree/bindings/sound/tas2562.yaml
@@ -18,7 +18,6 @@ description: |
 
   Specifications about the audio amplifier can be found at:
     https://www.ti.com/lit/gpn/tas2562
-    https://www.ti.com/lit/gpn/tas2563
     https://www.ti.com/lit/gpn/tas2564
     https://www.ti.com/lit/gpn/tas2110
 
@@ -29,7 +28,6 @@ properties:
   compatible:
     enum:
       - ti,tas2562
-      - ti,tas2563
       - ti,tas2564
       - ti,tas2110
 
-- 
2.34.1