[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0b01a3ae-4766-490e-939d-1d16c2748644@linux.dev>
Date: Mon, 12 May 2025 14:59:44 +0200
From: Pierre-Louis Bossart <pierre-louis.bossart@...ux.dev>
To: Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>, lgirdwood@...il.com,
broonie@...nel.org
Cc: linux-sound@...r.kernel.org, kai.vehmanen@...ux.intel.com,
ranjani.sridharan@...ux.intel.com, yung-chuan.liao@...ux.intel.com,
guennadi.liakhovetski@...ux.intel.com, bhelgaas@...gle.com,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] ASoC/SOF/PCI/Intel: add Wildcat Lake support
> The audio IP in Wildcat Lake (WCL) is largely identical to the one in
> Panther Lake, the main difference is the number of DSP cores, memory
> and clocking.
> It is based on the same ACE3 architecture.
>
> In SOF the PTL topologies can be re-used for WCL to reduce duplication
> of code and topology files.
Is this really true? I thought topology files are precisely the place where a specific pipeline is assigned to a specific core. If the number of cores is lower, then a PTL topology could fail when used on a WCL DSP, no?
Powered by blists - more mailing lists