From: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
To: lgirdwood@gmail.com, broonie@kernel.org, tiwai@suse.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,
bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/4] ASoC/SOF/PCI/Intel: add PantherLake H support
Date: Mon, 10 Feb 2025 10:17:26 +0200 [thread overview]
Message-ID: <20250210081730.22916-1-peter.ujfalusi@linux.intel.com> (raw)
Hi,
Changes since v1:
- Updated the commit messages
- added the Acked-by from Bjorn and Mark
The audio IP in PTL-H is identical to the already supported PTL but the
PCI-ID has been changes due to the differences in the product's
configuration outside of audio.
To support PTL-H we really just need to wire up the new ID.
Regards,
Peter
---
Peter Ujfalusi (1):
ASoC: SOF: Intel: pci-ptl: Add support for PTL-H
Pierre-Louis Bossart (3):
PCI: pci_ids: add INTEL_HDA_PTL_H
ALSA: hda: intel-dsp-config: Add PTL-H support
ALSA: hda: hda-intel: add Panther Lake-H support
include/linux/pci_ids.h | 1 +
sound/hda/intel-dsp-config.c | 5 +++++
sound/pci/hda/hda_intel.c | 2 ++
sound/soc/sof/intel/pci-ptl.c | 1 +
4 files changed, 9 insertions(+)
--
2.48.1
next reply other threads:[~2025-02-10 8:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 8:17 Peter Ujfalusi [this message]
2025-02-10 8:17 ` [PATCH v2 1/4] PCI: pci_ids: add INTEL_HDA_PTL_H Peter Ujfalusi
2025-02-10 8:17 ` [PATCH v2 2/4] ALSA: hda: intel-dsp-config: Add PTL-H support Peter Ujfalusi
2025-02-10 8:17 ` [PATCH v2 3/4] ASoC: SOF: Intel: pci-ptl: Add support for PTL-H Peter Ujfalusi
2025-02-10 8:17 ` [PATCH v2 4/4] ALSA: hda: hda-intel: add Panther Lake-H support Peter Ujfalusi
2025-02-10 17:14 ` [PATCH v2 0/4] ASoC/SOF/PCI/Intel: add PantherLake H support Takashi Iwai
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=20250210081730.22916-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=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.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