[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84c4c331-54b6-4539-a8f2-880fd47ad97b@linaro.org>
Date: Tue, 12 Dec 2023 09:22:37 +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,
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 v1] ASoC: tas2562: remove tas2563 into driver
On 12/12/2023 06:08, Shenghao Ding wrote:
> Remove tas2563 from tas2562, it will be supported in separated driver code.
>
Why? I was not aware that you duplicate tas2563 in your other patch, so
that part need explanation. This part as well - why do we want to remove
its support from the Linux? What about users? After applying this code
they don't have support for their device!
Best regards,
Krzysztof
Powered by blists - more mailing lists