From: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
To: lgirdwood@gmail.com, broonie@kernel.org
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,
bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, kw@linux.com
Subject: [PATCH 0/7] ASoC/SOF/PCI/Intel: Support for Nova Lake S
Date: Thu, 2 Oct 2025 11:42:45 +0300 [thread overview]
Message-ID: <20251002084252.7305-1-peter.ujfalusi@linux.intel.com> (raw)
Hi,
this series adds initial support for NVL-S from the Nova Lake family.
NVL-S includes ACE4 audio subsystem, it has 2 DSP cores.
Regards,
Peter
---
Bard Liao (1):
ASoC: Intel: soc-acpi-intel-nvl-match: add rt722 l3 support
Peter Ujfalusi (6):
PCI: Add Intel Nova Lake S audio Device ID
ALSA: hda/hdmi: intelhdmi: add HDMI codec ID for Intel NVL
ASoC: Intel: soc-acpi: add NVL match tables
ASoC: SOF: Intel: add initial support for NVL-S
ALSA: hda: core: intel-dsp-config: Add support for NVL-S
ALSA: hda: controllers: intel: add support for Nova Lake S
include/linux/pci_ids.h | 1 +
include/sound/soc-acpi-intel-match.h | 2 +
sound/hda/codecs/hdmi/intelhdmi.c | 1 +
sound/hda/controllers/intel.c | 2 +
sound/hda/core/intel-dsp-config.c | 8 ++
sound/soc/intel/common/Makefile | 1 +
.../intel/common/soc-acpi-intel-nvl-match.c | 90 +++++++++++++++++++
sound/soc/sof/intel/Kconfig | 17 ++++
sound/soc/sof/intel/Makefile | 2 +
sound/soc/sof/intel/hda-dsp.c | 1 +
sound/soc/sof/intel/hda.h | 1 +
sound/soc/sof/intel/nvl.c | 55 ++++++++++++
sound/soc/sof/intel/nvl.h | 14 +++
sound/soc/sof/intel/pci-nvl.c | 82 +++++++++++++++++
sound/soc/sof/intel/shim.h | 1 +
15 files changed, 278 insertions(+)
create mode 100644 sound/soc/intel/common/soc-acpi-intel-nvl-match.c
create mode 100644 sound/soc/sof/intel/nvl.c
create mode 100644 sound/soc/sof/intel/nvl.h
create mode 100644 sound/soc/sof/intel/pci-nvl.c
--
2.51.0
next reply other threads:[~2025-10-02 8:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 8:42 Peter Ujfalusi [this message]
2025-10-02 8:42 ` [PATCH 1/7] PCI: Add Intel Nova Lake S audio Device ID Peter Ujfalusi
2025-11-03 12:43 ` Péter Ujfalusi
2025-11-03 16:02 ` Bjorn Helgaas
2025-11-03 16:27 ` Péter Ujfalusi
2025-11-03 17:33 ` Bjorn Helgaas
2025-11-04 6:14 ` Péter Ujfalusi
2025-10-02 8:42 ` [PATCH 2/7] ALSA: hda/hdmi: intelhdmi: add HDMI codec ID for Intel NVL Peter Ujfalusi
2025-10-02 8:42 ` [PATCH 3/7] ASoC: Intel: soc-acpi: add NVL match tables Peter Ujfalusi
2025-10-03 11:08 ` Mark Brown
2025-10-02 8:42 ` [PATCH 4/7] ASoC: Intel: soc-acpi-intel-nvl-match: add rt722 l3 support Peter Ujfalusi
2025-10-03 11:10 ` Mark Brown
2025-10-02 8:42 ` [PATCH 5/7] ASoC: SOF: Intel: add initial support for NVL-S Peter Ujfalusi
2025-10-03 11:10 ` Mark Brown
2025-10-02 8:42 ` [PATCH 6/7] ALSA: hda: core: intel-dsp-config: Add " Peter Ujfalusi
2025-10-02 8:42 ` [PATCH 7/7] ALSA: hda: controllers: intel: add support for Nova Lake S Peter Ujfalusi
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=20251002084252.7305-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=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