mbox series

[0/2] ASoC: SOF: Intel: split Baytrail and Merrifield

Message ID 20210505170235.306797-1-pierre-louis.bossart@linux.intel.com
Headers show
Series ASoC: SOF: Intel: split Baytrail and Merrifield | expand

Message

Pierre-Louis Bossart May 5, 2021, 5:02 p.m. UTC 
We've had recurring randconfig issues with the two platforms relying
on ACPI and PCI. I think it's time to split the two and introduce a
common 'atom' module, so that dependencies are better handled.

I chose not to add a Fixes tag since the changes are rather invasive,
and the randconfig issues only happen in non-functional cases.

There should be no functional changes with this patchset, only code
moved and renamed.

Pierre-Louis Bossart (2):
  ASoC: SOF: Intel: byt: prepare split between Baytrail and Merrifield
  ASoC: SOF: Intel: move common ATOM stuff to module

 sound/soc/sof/intel/Makefile  |   5 +-
 sound/soc/sof/intel/atom.c    | 463 ++++++++++++++++++++
 sound/soc/sof/intel/atom.h    |  74 ++++
 sound/soc/sof/intel/byt.c     | 768 ++++------------------------------
 sound/soc/sof/intel/pci-tng.c | 171 +++++++-
 5 files changed, 783 insertions(+), 698 deletions(-)
 create mode 100644 sound/soc/sof/intel/atom.c
 create mode 100644 sound/soc/sof/intel/atom.h

Comments

Mark Brown May 11, 2021, 8:25 a.m. UTC | #1 
On Wed, 5 May 2021 12:02:33 -0500, Pierre-Louis Bossart wrote:
> We've had recurring randconfig issues with the two platforms relying
> on ACPI and PCI. I think it's time to split the two and introduce a
> common 'atom' module, so that dependencies are better handled.
> 
> I chose not to add a Fixes tag since the changes are rather invasive,
> and the randconfig issues only happen in non-functional cases.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: SOF: Intel: byt: prepare split between Baytrail and Merrifield
      commit: 1c5ab2dc752fcd02264e8dca8bde55ca479aa684
[2/2] ASoC: SOF: Intel: move common ATOM stuff to module
      commit: 47fad2393b0446229883f95e373067441794e22f

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