mbox series

[0/3] ASoC: SOF: minor updates for 5.20

Message ID 20220725195343.145603-1-pierre-louis.bossart@linux.intel.com
Headers show
Series ASoC: SOF: minor updates for 5.20 | expand

Message

Pierre-Louis Bossart July 25, 2022, 7:53 p.m. UTC
One sanity check for SSP index reported by NHLT/BIOS and two updates for
Mediatek and Intel Chromebooks related to already-merged firmware
changes.

Ideally this should go in 5.20, time-permitting.

Brent Lu (1):
  ASoC: SOF: dai-intel: add SOF_DAI_INTEL_SSP_CLKCTRL_MCLK_AON bit

Pierre-Louis Bossart (1):
  ASoC: SOF: Intel: hda: add sanity check on SSP index reported by NHLT

YC Hung (1):
  ASoC: SOF: Add cont_update_posn to platform parameters

 include/sound/sof/dai-intel.h | 2 ++
 include/uapi/sound/sof/abi.h  | 2 +-
 sound/soc/sof/intel/hda.c     | 7 +++++++
 sound/soc/sof/ipc3-pcm.c      | 3 +++
 sound/soc/sof/sof-priv.h      | 1 +
 5 files changed, 14 insertions(+), 1 deletion(-)

Comments

Mark Brown July 26, 2022, 11:30 a.m. UTC | #1
On Mon, 25 Jul 2022 14:53:40 -0500, Pierre-Louis Bossart wrote:
> One sanity check for SSP index reported by NHLT/BIOS and two updates for
> Mediatek and Intel Chromebooks related to already-merged firmware
> changes.
> 
> Ideally this should go in 5.20, time-permitting.
> 
> Brent Lu (1):
>   ASoC: SOF: dai-intel: add SOF_DAI_INTEL_SSP_CLKCTRL_MCLK_AON bit
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: SOF: Intel: hda: add sanity check on SSP index reported by NHLT
      commit: e51699505042fb365df3a0ce68b850ccd9ad0108
[2/3] ASoC: SOF: Add cont_update_posn to platform parameters
      commit: d95610a1832993c539be22f0ec3ea8e34a29acff
[3/3] ASoC: SOF: dai-intel: add SOF_DAI_INTEL_SSP_CLKCTRL_MCLK_AON bit
      commit: af468aadf00485a2f5e804fe97db4731bc7a9c24

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