Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Cezary Rojewski <cezary.rojewski@intel.com>
To: "Girdwood, Liam R" <liam.r.girdwood@intel.com>
Cc: "hdegoede@redhat.com" <hdegoede@redhat.com>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"perex@perex.cz" <perex@perex.cz>,
	"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
	"amadeuszx.slawinski@linux.intel.com"
	<amadeuszx.slawinski@linux.intel.com>,
	"tiwai@suse.com" <tiwai@suse.com>
Subject: Re: [PATCH 00/12] ASoC: Intel: avs: Add support for MTL-FCL platforms
Date: Mon, 7 Apr 2025 10:04:41 +0200	[thread overview]
Message-ID: <01eecf3e-36a5-430b-8e2b-ef53edbcf703@intel.com> (raw)
In-Reply-To: <b8fa998839daa544acf868e6260fce59f863cf5d.camel@intel.com>

On 2025-04-04 3:28 PM, Girdwood, Liam R wrote:
> On Fri, 2025-04-04 at 15:09 +0200, Cezary Rojewski wrote:
>> On 2025-04-04 2:52 PM, Girdwood, Liam R wrote:
>>> On Fri, 2025-04-04 at 11:49 +0200, Cezary Rojewski wrote:
>>>> Cezary Rojewski (11):
>>>>     ALSA: hda: Allow to fetch hlink by ID
>>>>     ASoC: Intel: avs: Ignore Vendor-space manipulation for ACE
>>>>     ASoC: Intel: avs: Read HW capabilities when possible
>>>>     ASoC: Intel: avs: Relocate DSP status registers
>>>>     ASoC: Intel: avs: MTL-based platforms support
>>>>     ASoC: Intel: avs: LNL-based platforms support
>>>>     ASoC: Intel: avs: PTL-based platforms support
>>>>     ASoC: Intel: avs: PCM operations for LNL-based platforms
>>>>
>>> Sorry - AVS is not officially supported for MTL, LNL and PTL on
>>> Linux.
>>>
>>> NAK.
>>
>>
>> FCL is a PTL-A, PTL-based platform. The driver is officially
>> supported
>> on the ACE architecture with clients utilizing it on distributions
>> such
>> as Android and Yocto. As software needs little to no changes to cover
>> PTL alone it is preferable to have clear division: ace1.0 <- ace2.0
>> <-
>> ace3.0. The code is maintainable and readable this way.
> 
> No argument with FCL or any non client devices.

I see. So we're talking about pci_ids and their attached descriptors, 
and _not_ removing the functional code that enables avs-driver on ACE 
architecture?

The filenames/prefixes shall remain as-is given the driver's design - 
platform that starts given arch, becomes its namesake.

Kind regards,
Czarek

  reply	other threads:[~2025-04-07  8:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04  9:49 [PATCH 00/12] ASoC: Intel: avs: Add support for MTL-FCL platforms Cezary Rojewski
2025-04-04  9:49 ` [PATCH 01/12] ALSA: hda: Allow to fetch hlink by ID Cezary Rojewski
2025-04-04  9:49 ` [PATCH 02/12] ASoC: Intel: avs: Ignore Vendor-space manipulation for ACE Cezary Rojewski
2025-04-04  9:49 ` [PATCH 03/12] ASoC: Intel: avs: Read HW capabilities when possible Cezary Rojewski
2025-04-04  9:49 ` [PATCH 04/12] ASoC: Intel: avs: Relocate DSP status registers Cezary Rojewski
2025-04-04  9:49 ` [PATCH 05/12] ASoC: Intel: avs: MTL-based platforms support Cezary Rojewski
2025-04-04  9:49 ` [PATCH 06/12] ASoC: Intel: avs: LNL-based " Cezary Rojewski
2025-04-04  9:49 ` [PATCH 07/12] ASoC: Intel: avs: PTL-based " Cezary Rojewski
2025-04-04  9:49 ` [PATCH 08/12] ASoC: Intel: avs: PCM operations for LNL-based platforms Cezary Rojewski
2025-04-04  9:49 ` [PATCH 09/12] ASoC: Intel: avs: Dynamically assign ops for non-HDAudio DAIs Cezary Rojewski
2025-04-04  9:49 ` [PATCH 10/12] ASoC: Intel: avs: Conditionally add DMA config when creating Copier Cezary Rojewski
2025-04-04  9:49 ` [PATCH 11/12] ASoC: Intel: avs: Add boards definitions for ACE platforms Cezary Rojewski
2025-04-04  9:49 ` [PATCH 12/12] ALSA: hda: Select avs-driver by default on FCL Cezary Rojewski
2025-04-04 12:52 ` [PATCH 00/12] ASoC: Intel: avs: Add support for MTL-FCL platforms Girdwood, Liam R
2025-04-04 13:09   ` Cezary Rojewski
2025-04-04 13:28     ` Girdwood, Liam R
2025-04-07  8:04       ` Cezary Rojewski [this message]
2025-04-07  9:36         ` Girdwood, Liam R
2025-04-07  9:45           ` Cezary Rojewski
2025-04-07 10:15             ` Girdwood, Liam R

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=01eecf3e-36a5-430b-8e2b-ef53edbcf703@intel.com \
    --to=cezary.rojewski@intel.com \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=liam.r.girdwood@intel.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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