From: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
To: lgirdwood@gmail.com, broonie@kernel.org, tiwai@suse.de,
bhelgaas@google.com
Cc: linux-sound@vger.kernel.org, kai.vehmanen@linux.intel.com,
ranjani.sridharan@linux.intel.com,
yung-chuan.liao@linux.intel.com, pierre-louis.bossart@linux.dev,
linux-kernel@vger.kernel.org, kw@linux.com,
linux-pci@vger.kernel.org
Subject: [PATCH v2 0/4] ASoC/SOF/PCI/Intel: Support for Nova Lake
Date: Tue, 20 Jan 2026 21:35:03 +0200 [thread overview]
Message-ID: <20260120193507.14019-1-peter.ujfalusi@linux.intel.com> (raw)
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
next reply other threads:[~2026-01-20 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 19:35 Peter Ujfalusi [this message]
2026-01-20 19:35 ` [PATCH v2 1/4] PCI: Add Intel Nova Lake audio Device ID Peter Ujfalusi
2026-01-20 19:35 ` [PATCH v2 2/4] ASoC: SOF: Intel: add support for Nova Lake NVL Peter Ujfalusi
2026-01-20 19:35 ` [PATCH v2 3/4] ALSA: hda: core: intel-dsp-config: Add support for NVL Peter Ujfalusi
2026-01-20 19:35 ` [PATCH v2 4/4] ALSA: hda: controllers: intel: add support for Nova Lake Peter Ujfalusi
2026-01-22 13:26 ` [PATCH v2 0/4] ASoC/SOF/PCI/Intel: Support " Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260120193507.14019-1-peter.ujfalusi@linux.intel.com \
--to=peter.ujfalusi@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=kw@linux.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=pierre-louis.bossart@linux.dev \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tiwai@suse.de \
--cc=yung-chuan.liao@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox