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] [day] [month] [year] [list]

Date: Fri, 05 Jan 2024 18:48:18 +0000
From: Mark Brown <broonie@...nel.org>
To: conor+dt@...nel.org, krzysztof.kozlowski@...aro.org, 
 Shenghao Ding <shenghao-ding@...com>
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 Thu, 04 Jan 2024 22:57:16 +0800, 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.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/4] ASoC: dt-bindings: move tas2563 from tas2562.yaml to tas2781.yaml
      commit: 3dbb4e3602d217d7139b95a36077a6b7252dc290
[2/4] ASoC: tas2562: move tas2563 from tas2562 driver to tas2781 driver
      commit: 645994d21287a1ad2f637818d737f7a3d84e97d7
[3/4] ASoC: tas2781: Add tas2563 into header file for DSP mode
      commit: e9aa44736cb75e901d76ee59d80db1ae79d516f1
[4/4] ASoC: tas2781: Add tas2563 into driver
      commit: 9f1bcd16e2bd41d758438f1d74e5f2d35f1e8c8e

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark