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
| ||
|
Message-ID: <ZYxVuGwyw1ZA3XBv@smile.fi.intel.com> Date: Wed, 27 Dec 2023 18:50:00 +0200 From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com> To: Shenghao Ding <shenghao-ding@...com> Cc: broonie@...nel.org, conor+dt@...nel.org, krzysztof.kozlowski@...aro.org, robh+dt@...nel.org, 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 v3 2/5] ASoC: tas2562: move tas2563 from tas2562 driver to tas2781 driver On Mon, Dec 25, 2023 at 01:39:28PM +0800, Shenghao Ding wrote: > Move tas2563 from tas2562 driver to tas2781 driver, 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. I dunno if you got my emails, but my comments were completely ignored. You can't do this patch as after it the current users may have a regression. -- With Best Regards, Andy Shevchenko
Powered by blists - more mailing lists