Message ID | 20231221101346.429-1-shenghao-ding@ti.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel+bounces-8188-ouuuleilei=gmail.com@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:7300:2483:b0:fb:cd0c:d3e with SMTP id q3csp311232dyi; Thu, 21 Dec 2023 02:19:49 -0800 (PST) X-Google-Smtp-Source: AGHT+IHYstLiHmCpXOA5WptZAB/94/wjD+DtOyrfWqn1i2s2mBv7lj0UfXkO1cVCrXHkA18f9i3o X-Received: by 2002:a05:6808:1998:b0:3b9:de63:f514 with SMTP id bj24-20020a056808199800b003b9de63f514mr26853889oib.12.1703153988862; Thu, 21 Dec 2023 02:19:48 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1703153988; cv=none; d=google.com; s=arc-20160816; b=zcsz3z8Piz3YlbFBxfTANvUUmqkhY/z6pDQve/7N4p0C2fd0tgqD4ynHwHKJxvAZfN SzUuabGkmhwZSzEibZ9Cvq1e8J0kMzY1fNJm1ZuGNjZ6gSSCMDPEqx3CVDyN5YQDy4WR PsE65lHa9AkRdApzTaqm1E1HILiXYbVOf85uohqHgxe18SDLFriY53ruotLWOPIsQR0p jbw7OY95m1RPH4TDFAWl2WqQONagVyyskA3lLLIUz2Qm4mVmCLAiJlGzGvL+XMmrsi3J xIq/W7epqFforai6iK6mNyd/28cYH1G1AmdQUrMLBUSymVRD1UuHPFihkmXpXKWt0eyr wvlA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:message-id:date:subject:cc:to :from:dkim-signature; bh=sLdFXnpxFlQqoK1p8Vg4Etqv0GZzsWvE6eYx5Q11kJs=; fh=nmpqriIAxzz9z4/piqOabUsFkiEK8VDv7G5j+pvfHas=; b=LRdEDXLMN9gnK5vq/1bv50sTRc4qa+pRqRbbfrHBLske3QezTAkkEujbKbGe7dbpNx 2DHwyRb7xsYFZfSmrXvIb9JeF4tIs9ZGZ4MIC+jSMZd4/2I0sUfjR0hXOolhR4UKL7PJ AkfUQyd4iEze8t30zJf+2vPv0DWKpraEgd4SOj49wrK80fc9dOVK4X86IGOmrN2sjlzZ FWaBjKUHltgJoTgTl5f2i9hH+08Xtt3lJgcl/DlhEw4zHYAxcyWaqQVQE2ILhQ0xMxDn HqECeDTpQnLqlXLDPBND8oQzbcuk/oDgneVOAc9vvayrTXV862rgFmtYAyTi60NOvOt1 sAhw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=Fne4aXwm; spf=pass (google.com: domain of linux-kernel+bounces-8188-ouuuleilei=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) smtp.mailfrom="linux-kernel+bounces-8188-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: from sy.mirrors.kernel.org (sy.mirrors.kernel.org. [147.75.48.161]) by mx.google.com with ESMTPS id z65-20020a633344000000b005bd04873387si1362649pgz.105.2023.12.21.02.19.48 for <ouuuleilei@gmail.com> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 21 Dec 2023 02:19:48 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-8188-ouuuleilei=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=Fne4aXwm; spf=pass (google.com: domain of linux-kernel+bounces-8188-ouuuleilei=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) smtp.mailfrom="linux-kernel+bounces-8188-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sy.mirrors.kernel.org (Postfix) with ESMTPS id AF41EB230C3 for <ouuuleilei@gmail.com>; Thu, 21 Dec 2023 10:15:58 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id C8667524A9; Thu, 21 Dec 2023 10:15:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="Fne4aXwm" X-Original-To: linux-kernel@vger.kernel.org Received: from lelv0143.ext.ti.com (lelv0143.ext.ti.com [198.47.23.248]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AA81B51C25; Thu, 21 Dec 2023 10:15:22 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ti.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ti.com Received: from fllv0035.itg.ti.com ([10.64.41.0]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id 3BLADv1h012631; Thu, 21 Dec 2023 04:13:57 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1703153637; bh=sLdFXnpxFlQqoK1p8Vg4Etqv0GZzsWvE6eYx5Q11kJs=; h=From:To:CC:Subject:Date; b=Fne4aXwmBn5dkqpqqFw+7R70drLMXfF1yxXg1kAffa/M4/hJk+qR2eP/AFxxfzls2 r5w+WzMMNOAjL+6aUXm4OBt72RJTx3481WiYorsaZtSicVRp/85TDKb8d8C/HeiXbl JL3IT4IpZGut2koWzEOW5kN6000OxrXmwSfiHN6M= Received: from DLEE102.ent.ti.com (dlee102.ent.ti.com [157.170.170.32]) by fllv0035.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 3BLADvhN017220 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 21 Dec 2023 04:13:57 -0600 Received: from DLEE109.ent.ti.com (157.170.170.41) by DLEE102.ent.ti.com (157.170.170.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Thu, 21 Dec 2023 04:13:57 -0600 Received: from lelvsmtp5.itg.ti.com (10.180.75.250) by DLEE109.ent.ti.com (157.170.170.41) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Thu, 21 Dec 2023 04:13:56 -0600 Received: from LT5CG31242FY.dhcp.ti.com (lt5cg31242fy.dhcp.ti.com [10.85.14.210]) by lelvsmtp5.itg.ti.com (8.15.2/8.15.2) with ESMTP id 3BLADoQc069419; Thu, 21 Dec 2023 04:13:51 -0600 From: Shenghao Ding <shenghao-ding@ti.com> To: <broonie@kernel.org>, <conor+dt@kernel.org>, <krzysztof.kozlowski@linaro.org> CC: <robh+dt@kernel.org>, <andriy.shevchenko@linux.intel.com>, <kevin-lu@ti.com>, <baojun.xu@ti.com>, <devicetree@vger.kernel.org>, <lgirdwood@gmail.com>, <perex@perex.cz>, <pierre-louis.bossart@linux.intel.com>, <13916275206@139.com>, <linux-sound@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <liam.r.girdwood@intel.com>, <soyer@irl.hu>, <tiwai@suse.de>, <peeyush@ti.com>, <navada@ti.com>, Shenghao Ding <shenghao-ding@ti.com> Subject: [PATCH v2 1/5] ASoC: dt-bindings: remove tas2563 from yaml Date: Thu, 21 Dec 2023 18:13:41 +0800 Message-ID: <20231221101346.429-1-shenghao-ding@ti.com> X-Mailer: git-send-email 2.33.0.windows.2 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: <linux-kernel.vger.kernel.org> List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org> List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1785886397033417511 X-GMAIL-MSGID: 1785886397033417511 |
Series |
[v2,1/5] ASoC: dt-bindings: remove tas2563 from yaml
|
|
Commit Message
Ding, Shenghao
Dec. 21, 2023, 10:13 a.m. UTC
Remove tas2563 from tas2562, it will be supported in tas2781 to better
support dsp mode.
Signed-off-by: Shenghao Ding <shenghao-ding@ti.com>
---
Change in v2:
- remove tas2563, which will be move to tas2781 driver
---
Documentation/devicetree/bindings/sound/tas2562.yaml | 2 --
1 file changed, 2 deletions(-)
Comments
On Thu, Dec 21, 2023 at 06:13:41PM +0800, Shenghao Ding wrote: > Remove tas2563 from tas2562, it will be supported in tas2781 to better > support dsp mode. DSP Shouldn't this patch go after the actual change happen? I don't know the answer myself, I would like to hear DT people on this.
On 21/12/2023 11:13, Shenghao Ding wrote: > Remove tas2563 from tas2562, it will be supported in tas2781 to better > support dsp mode. Please provide rationale in terms of bindings and hardware, not in terms of driver. Or at least not only. For example "supported in tas2781" does not fit hardware part, so you sure must be talking about drivers thus why driver change would affect bindings? Best regards, Krzysztof
On 21/12/2023 16:50, Andy Shevchenko wrote: > On Thu, Dec 21, 2023 at 06:13:41PM +0800, Shenghao Ding wrote: >> Remove tas2563 from tas2562, it will be supported in tas2781 to better >> support dsp mode. > > DSP > > Shouldn't this patch go after the actual change happen? I would squash both, so device documentation does not disappear. Best regards, Krzysztof
> -----Original Message----- > From: Andy Shevchenko <andriy.shevchenko@linux.intel.com> > Sent: Thursday, December 21, 2023 11:51 PM > To: Ding, Shenghao <shenghao-ding@ti.com> > Cc: broonie@kernel.org; conor+dt@kernel.org; > krzysztof.kozlowski@linaro.org; robh+dt@kernel.org; Lu, Kevin <kevin- > lu@ti.com>; Xu, Baojun <baojun.xu@ti.com>; devicetree@vger.kernel.org; > lgirdwood@gmail.com; perex@perex.cz; pierre-louis.bossart@linux.intel.com; > 13916275206@139.com; linux-sound@vger.kernel.org; linux- > kernel@vger.kernel.org; liam.r.girdwood@intel.com; soyer@irl.hu; > tiwai@suse.de; Gupta, Peeyush <peeyush@ti.com>; Navada Kanyana, > Mukund <navada@ti.com> > Subject: [EXTERNAL] Re: [PATCH v2 1/5] ASoC: dt-bindings: remove tas2563 > from yaml > > On Thu, Dec 21, 2023 at 06:13:41PM +0800, Shenghao Ding wrote: > > Remove tas2563 from tas2562, it will be supported in tas2781 to better > > support dsp mode. > > DSP > > Shouldn't this patch go after the actual change happen? > I don't know the answer myself, I would like to hear DT people on this. > tas2781 driver can be reused as tas2563 driver, except for the DSP firmware file, and both DSP firmware files complied with TI SmartAMP DSP spec 3.0. > > -- > With Best Regards, > Andy Shevchenko > >
> -----Original Message----- > From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > Sent: Friday, December 22, 2023 1:32 AM > To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>; Ding, Shenghao > <shenghao-ding@ti.com> > Cc: broonie@kernel.org; conor+dt@kernel.org; robh+dt@kernel.org; Lu, > Kevin <kevin-lu@ti.com>; Xu, Baojun <baojun.xu@ti.com>; > devicetree@vger.kernel.org; lgirdwood@gmail.com; perex@perex.cz; pierre- > louis.bossart@linux.intel.com; 13916275206@139.com; linux- > sound@vger.kernel.org; linux-kernel@vger.kernel.org; > liam.r.girdwood@intel.com; soyer@irl.hu; tiwai@suse.de; Gupta, Peeyush > <peeyush@ti.com>; Navada Kanyana, Mukund <navada@ti.com> > Subject: [EXTERNAL] Re: [PATCH v2 1/5] ASoC: dt-bindings: remove tas2563 > from yaml > > On 21/12/2023 16:50, Andy Shevchenko wrote: > > On Thu, Dec 21, 2023 at 06:13:41PM +0800, Shenghao Ding wrote: > >> Remove tas2563 from tas2562, it will be supported in tas2781 to > >> better support dsp mode. > > > > DSP > > > > Shouldn't this patch go after the actual change happen? > > I would squash both, so device documentation does not disappear. I do not fully understand "squash both", do you mean still to keep ti,tas2563 in tas2562.yaml? > > Best regards, > Krzysztof
> -----Original Message----- > From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > Sent: Friday, December 22, 2023 1:31 AM > To: Ding, Shenghao <shenghao-ding@ti.com>; broonie@kernel.org; > conor+dt@kernel.org > Cc: robh+dt@kernel.org; andriy.shevchenko@linux.intel.com; Lu, Kevin > <kevin-lu@ti.com>; Xu, Baojun <baojun.xu@ti.com>; > devicetree@vger.kernel.org; lgirdwood@gmail.com; perex@perex.cz; pierre- > louis.bossart@linux.intel.com; 13916275206@139.com; linux- > sound@vger.kernel.org; linux-kernel@vger.kernel.org; > liam.r.girdwood@intel.com; soyer@irl.hu; tiwai@suse.de; Gupta, Peeyush > <peeyush@ti.com>; Navada Kanyana, Mukund <navada@ti.com> > Subject: [EXTERNAL] Re: [PATCH v2 1/5] ASoC: dt-bindings: remove tas2563 > from yaml > > On 21/12/2023 11:13, Shenghao Ding wrote: > > Remove tas2563 from tas2562, it will be supported in tas2781 to better > > support dsp mode. > > Please provide rationale in terms of bindings and hardware, not in terms of > driver. Or at least not only. For example "supported in tas2781" does not fit > hardware part, so you sure must be talking about drivers thus why driver > change would affect bindings? This patch mainly change the binding, not the driver code. Tas2563 is unbound to tas2562 driver, and bound to tas2781 driver. > > > > Best regards, > Krzysztof
On 27/12/2023 08:04, Ding, Shenghao wrote: > > >> -----Original Message----- >> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> >> Sent: Friday, December 22, 2023 1:32 AM >> To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>; Ding, Shenghao >> <shenghao-ding@ti.com> >> Cc: broonie@kernel.org; conor+dt@kernel.org; robh+dt@kernel.org; Lu, >> Kevin <kevin-lu@ti.com>; Xu, Baojun <baojun.xu@ti.com>; >> devicetree@vger.kernel.org; lgirdwood@gmail.com; perex@perex.cz; pierre- >> louis.bossart@linux.intel.com; 13916275206@139.com; linux- >> sound@vger.kernel.org; linux-kernel@vger.kernel.org; >> liam.r.girdwood@intel.com; soyer@irl.hu; tiwai@suse.de; Gupta, Peeyush >> <peeyush@ti.com>; Navada Kanyana, Mukund <navada@ti.com> >> Subject: [EXTERNAL] Re: [PATCH v2 1/5] ASoC: dt-bindings: remove tas2563 >> from yaml >> >> On 21/12/2023 16:50, Andy Shevchenko wrote: >>> On Thu, Dec 21, 2023 at 06:13:41PM +0800, Shenghao Ding wrote: >>>> Remove tas2563 from tas2562, it will be supported in tas2781 to >>>> better support dsp mode. >>> >>> DSP >>> >>> Shouldn't this patch go after the actual change happen? >> >> I would squash both, so device documentation does not disappear. > I do not fully understand "squash both", do you mean still to keep ti,tas2563 in tas2562.yaml? I meant to squash both binding patches (git help rebase). Best regards, Krzysztof
On 27/12/2023 08:07, Ding, Shenghao wrote: > > >> -----Original Message----- >> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> >> Sent: Friday, December 22, 2023 1:31 AM >> To: Ding, Shenghao <shenghao-ding@ti.com>; broonie@kernel.org; >> conor+dt@kernel.org >> Cc: robh+dt@kernel.org; andriy.shevchenko@linux.intel.com; Lu, Kevin >> <kevin-lu@ti.com>; Xu, Baojun <baojun.xu@ti.com>; >> devicetree@vger.kernel.org; lgirdwood@gmail.com; perex@perex.cz; pierre- >> louis.bossart@linux.intel.com; 13916275206@139.com; linux- >> sound@vger.kernel.org; linux-kernel@vger.kernel.org; >> liam.r.girdwood@intel.com; soyer@irl.hu; tiwai@suse.de; Gupta, Peeyush >> <peeyush@ti.com>; Navada Kanyana, Mukund <navada@ti.com> >> Subject: [EXTERNAL] Re: [PATCH v2 1/5] ASoC: dt-bindings: remove tas2563 >> from yaml >> >> On 21/12/2023 11:13, Shenghao Ding wrote: >>> Remove tas2563 from tas2562, it will be supported in tas2781 to better >>> support dsp mode. >> >> Please provide rationale in terms of bindings and hardware, not in terms of >> driver. Or at least not only. For example "supported in tas2781" does not fit >> hardware part, so you sure must be talking about drivers thus why driver >> change would affect bindings? > This patch mainly change the binding, not the driver code. Tas2563 is unbound > to tas2562 driver, and bound to tas2781 driver. Then why do you reference driver "tas2781" here? Best regards, Krzysztof
> -----Original Message----- > From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > Sent: Wednesday, December 27, 2023 6:56 PM > To: Ding, Shenghao <shenghao-ding@ti.com> > Cc: robh+dt@kernel.org; andriy.shevchenko@linux.intel.com; Lu, Kevin > <kevin-lu@ti.com>; Xu, Baojun <baojun.xu@ti.com>; > devicetree@vger.kernel.org; lgirdwood@gmail.com; perex@perex.cz; pierre- > louis.bossart@linux.intel.com; 13916275206@139.com; linux- > sound@vger.kernel.org; linux-kernel@vger.kernel.org; > liam.r.girdwood@intel.com; soyer@irl.hu; tiwai@suse.de; Gupta, Peeyush > <peeyush@ti.com>; Navada Kanyana, Mukund <navada@ti.com>; > broonie@kernel.org; conor+dt@kernel.org > Subject: Re: [EXTERNAL] Re: [PATCH v2 1/5] ASoC: dt-bindings: remove > tas2563 from yaml > > On 27/12/2023 08:07, Ding, Shenghao wrote: > > > > > >> -----Original Message----- > >> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > >> Sent: Friday, December 22, 2023 1:31 AM > >> To: Ding, Shenghao <shenghao-ding@ti.com>; broonie@kernel.org; > >> conor+dt@kernel.org > >> Cc: robh+dt@kernel.org; andriy.shevchenko@linux.intel.com; Lu, Kevin > >> <kevin-lu@ti.com>; Xu, Baojun <baojun.xu@ti.com>; > >> devicetree@vger.kernel.org; lgirdwood@gmail.com; perex@perex.cz; > >> pierre- louis.bossart@linux.intel.com; 13916275206@139.com; linux- > >> sound@vger.kernel.org; linux-kernel@vger.kernel.org; > >> liam.r.girdwood@intel.com; soyer@irl.hu; tiwai@suse.de; Gupta, > >> Peeyush <peeyush@ti.com>; Navada Kanyana, Mukund <navada@ti.com> > >> Subject: [EXTERNAL] Re: [PATCH v2 1/5] ASoC: dt-bindings: remove > >> tas2563 from yaml > >> > >> On 21/12/2023 11:13, Shenghao Ding wrote: > >>> Remove tas2563 from tas2562, it will be supported in tas2781 to > >>> better support dsp mode. > >> > >> Please provide rationale in terms of bindings and hardware, not in > >> terms of driver. Or at least not only. For example "supported in > >> tas2781" does not fit hardware part, so you sure must be talking > >> about drivers thus why driver change would affect bindings? > > This patch mainly change the binding, not the driver code. Tas2563 is > > unbound to tas2562 driver, and bound to tas2781 driver. > > Then why do you reference driver "tas2781" here? Both tas2563 and tas2781 are dsp-inside audio amplifier, tas2781 driver is designed for dsp-inside series chips, not only for tas2781. > > Best regards, > Krzysztof
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