From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Brady Norander <bradynorander@gmail.com>,
Takashi Iwai <tiwai@suse.com>, Mark Brown <broonie@kernel.org>,
<alsa-devel@alsa-project.org>
Cc: <linux-kernel@vger.kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Subject: Re: [PATCH v2] ALSA: hda: intel-dsp-cfg: Use AVS driver on SKL/KBL/APL Chromebooks
Date: Mon, 30 Oct 2023 20:23:44 +0100 [thread overview]
Message-ID: <754f3c29-cfac-243c-d280-0cc84ed36ccb@intel.com> (raw)
In-Reply-To: <2f5ffc3b-01be-413d-843e-8654d953f56f@gmail.com>
On 2023-10-30 7:58 PM, Brady Norander wrote:
> The legacy SKL driver no longer works properly on these Chromebook
> platforms. Use the new AVS driver by default instead.
Hello,
Thank you for the patch. The code looks fine but it will cause backward
compatibility problems on driver <-> topology line which I'd like to avoid.
There's an ongoing discussion regarding 24/32 format support for HDAudio
drivers which is currently incorrect for all Intel AudioDSP drivers.
Until the discussion is finished I'd like to avoid switching. While the
avs-driver deprecates the skylake-driver since v5.4, the topology file
package is not yet part of any official distro release.
I've high hopes to finish the process by the end of November. That
means: driver code gets updated to properly represent 24/32 format AND
the avs-topology-xml repo [1] receives equivalent update making it a
candidate for distro integration. I'll bump this patch once the process
concludes.
[1]: https://github.com/thesofproject/avs-topology-xml
Czarek
next prev parent reply other threads:[~2023-10-30 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 18:58 [PATCH v2] ALSA: hda: intel-dsp-cfg: Use AVS driver on SKL/KBL/APL Chromebooks Brady Norander
2023-10-30 19:23 ` Cezary Rojewski [this message]
2023-10-31 8:07 ` Takashi Iwai
2023-10-31 9:47 ` Cezary Rojewski
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=754f3c29-cfac-243c-d280-0cc84ed36ccb@intel.com \
--to=cezary.rojewski@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bradynorander@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--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