mbox series

[00/13] ASoC: topology: kcontrol registration cleanup

Message ID 20240627101850.2191513-1-amadeuszx.slawinski@linux.intel.com (mailing list archive)
Headers show
Series ASoC: topology: kcontrol registration cleanup | expand

Message

Amadeusz Sławiński June 27, 2024, 10:18 a.m. UTC
Code used to create standalone and widget controls is mostly same, with
with exception that in standalone case dynamic object needs to be
registered and control created directly.

Following patches clean up and unify kcontrol creation code in topology
code.

Amadeusz Sławiński (13):
  ASoC: topology: Simplify code
  ASoC: topology: Do not do unnecessary dobj management
  ASoC: topology: Properly initialize soc_enum values
  ASoC: topology: Cleanup soc_tplg_dapm_widget_dbytes_create
  ASoC: topology: Cleanup soc_tplg_dapm_widget_dmixer_create
  ASoC: topology: Cleanup soc_tplg_dapm_widget_denum_create
  ASoC: topology: Correctly set shift_r in soc_tplg_denum_create()
  ASoC: topology: Align dynamic object initialization for controls
  ASoC: topology: Rename function creating widget kcontrol
  ASoC: topology: Reshuffle function placement
  ASoC: topology: Unify code for creating standalone and widget bytes
    control
  ASoC: topology: Unify code for creating standalone and widget mixer
    control
  ASoC: topology: Unify code for creating standalone and widget enum
    control

 sound/soc/soc-topology.c | 568 +++++++++++++--------------------------
 1 file changed, 194 insertions(+), 374 deletions(-)


base-commit: 2b1281d6ae7b47c654f5be68e0d270f76f7accd2

Comments

Mark Brown July 3, 2024, 2:07 p.m. UTC | #1
On Thu, 27 Jun 2024 12:18:37 +0200, Amadeusz Sławiński wrote:
> Code used to create standalone and widget controls is mostly same, with
> with exception that in standalone case dynamic object needs to be
> registered and control created directly.
> 
> Following patches clean up and unify kcontrol creation code in topology
> code.
> 
> [...]

Applied to

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

Thanks!

[01/13] ASoC: topology: Simplify code
        commit: 97a05cb4ab12f55e19cf28f6ceca47bb6ed8fea4
[02/13] ASoC: topology: Do not do unnecessary dobj management
        commit: 7aa129706b4d6f7a2c649b359eea0336eb640feb
[03/13] ASoC: topology: Properly initialize soc_enum values
        commit: 8ec2a2643544ce352f012ad3d248163199d05dfc
[04/13] ASoC: topology: Cleanup soc_tplg_dapm_widget_dbytes_create
        commit: 52f4f7272c92d5be3988839a33be41b180bbc28e
[05/13] ASoC: topology: Cleanup soc_tplg_dapm_widget_dmixer_create
        commit: 40a16442a048c5f2b4336edd4d202f1930fb9df5
[06/13] ASoC: topology: Cleanup soc_tplg_dapm_widget_denum_create
        commit: d1d0262a1f5c7a543271bd5899cdb4b3ddfe054b
[07/13] ASoC: topology: Correctly set shift_r in soc_tplg_denum_create()
        commit: 963942f73b02b053f97e079ed6dae5f3602cc4b1
[08/13] ASoC: topology: Align dynamic object initialization for controls
        commit: f14a33fcadbacc1d9728e9c75253145ae6e09bbf
[09/13] ASoC: topology: Rename function creating widget kcontrol
        commit: 76d8aa0f727e327a0ba9bcb904865c40d256c292
[10/13] ASoC: topology: Reshuffle function placement
        commit: c2dad0db01fcacd44616e9d4c7263b187c4ff530
[11/13] ASoC: topology: Unify code for creating standalone and widget bytes control
        commit: 0867278200f787817036419fc87b56fb04a448e4
[12/13] ASoC: topology: Unify code for creating standalone and widget mixer control
        commit: 4654ca7cc8d6b57c77436dd44b347cc7dd3f5f08
[13/13] ASoC: topology: Unify code for creating standalone and widget enum control
        commit: 8f2942b9198c935862bc2400602780844b352667

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