Hi,

Changes since v1:
- commit message/subject fixes suggested by Bjorn
- Acked-by tags added.

this series adds audio support for the NVL variant of the
Nova Lake family.
NVL also based on ACE4 audio subsystem, but with higher clock
rate, more DSP memory and more DSP cores (4 vs 2) compared to
NVL-S.

Regards,
Peter
---
Peter Ujfalusi (4):
  PCI: Add Intel Nova Lake audio Device ID
  ASoC: SOF: Intel: add support for Nova Lake NVL
  ALSA: hda: core: intel-dsp-config: Add support for NVL
  ALSA: hda: controllers: intel: add support for Nova Lake

 include/linux/pci_ids.h           |  1 +
 sound/hda/controllers/intel.c     |  1 +
 sound/hda/core/intel-dsp-config.c |  4 ++++
 sound/soc/sof/intel/hda.h         |  1 +
 sound/soc/sof/intel/nvl.c         | 24 ++++++++++++++++++++++++
 sound/soc/sof/intel/pci-nvl.c     | 31 +++++++++++++++++++++++++++++++
 6 files changed, 62 insertions(+)

-- 
2.52.0

On Tue, 20 Jan 2026 21:35:03 +0200, Peter Ujfalusi wrote:
> Changes since v1:
> - commit message/subject fixes suggested by Bjorn
> - Acked-by tags added.
> 
> this series adds audio support for the NVL variant of the
> Nova Lake family.
> NVL also based on ACE4 audio subsystem, but with higher clock
> rate, more DSP memory and more DSP cores (4 vs 2) compared to
> NVL-S.
> 
> [...]

Applied to

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

Thanks!

[1/4] PCI: Add Intel Nova Lake audio Device ID
      commit: b190870e0e0cfb375c0d4da02761c32083f3644d
[2/4] ASoC: SOF: Intel: add support for Nova Lake NVL
      commit: 1800bcdc68ead7209451085431d80aa95ea7cd03
[3/4] ALSA: hda: core: intel-dsp-config: Add support for NVL
      commit: a094d8a50679356fbf045af274ccab85c9a644fb
[4/4] ALSA: hda: controllers: intel: add support for Nova Lake
      commit: 7f428282fde34f06f3ab898b8a9081bf93a41f22

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