From: Mark Brown <broonie@kernel.org>
To: alsa-devel@alsa-project.org, Cezary Rojewski <cezary.rojewski@intel.com>
Cc: rad@semihalf.com, upstream@semihalf.com, harshapriya.n@intel.com,
tiwai@suse.com, ranjani.sridharan@linux.intel.com,
pierre-louis.bossart@linux.intel.com, hdegoede@redhat.com,
amadeuszx.slawinski@linux.intel.com, cujomalainey@chromium.org,
lma@semihalf.com
Subject: Re: [PATCH v5 00/17] ASoC: Intel: AVS - Audio DSP for cAVS
Date: Fri, 11 Mar 2022 20:22:47 +0000 [thread overview]
Message-ID: <164703016723.264137.1929793280515599976.b4-ty@kernel.org> (raw)
In-Reply-To: <20220311153544.136854-1-cezary.rojewski@intel.com>
On Fri, 11 Mar 2022 16:35:27 +0100, Cezary Rojewski wrote:
> A continuation of cleanup work of Intel SST solutions found in
> sound/soc/intel/. With two major chapters released last year catpt [1]
> and removal of haswell solution [2], time has come for Skylake-driver.
>
> Througout 2019, 2020 and 2021 Skylake-driver has had many fixes applied
> and even attempts of refactors as seen in fundamental overhaul [3], IPC
> flow adjustments [4] and LARGE_CONFIG overhaul [5] series.
> Unfortunately, story repeats itself - problems are found within the core
> of a driver. Painting it with different colors does not change the fact
> that is it still a house of cards. As changes needed to address those
> issues would make Skylake solution incompatible with its previous
> revisions, a decision has been made to provide a new solution instead.
> In time it would deprecate and replace Skylake-driver.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[01/17] ALSA: hda: Add helper macros for DSP capable devices
commit: c19bd02e9029f0f75b58f4b8662527da74be8985
[02/17] ASoC: Export DAI register and widget ctor and dctor functions
commit: da0398099a83483014adc509a2845c88ccf672af
[03/17] ASoC: Intel: Introduce AVS driver
commit: 9fe51c559a862d6c884f6784de26c8f9463187b1
[04/17] ASoC: Intel: avs: Inter process communication
commit: 2879516fcd6d7ec5972762dbd94859d9221e70d8
[05/17] ASoC: Intel: avs: Add code loading requests
commit: cb1eb6b5be42799d23f81ffde84ee3537365b0ed
[06/17] ASoC: Intel: avs: Add pipeline management requests
commit: b956b27b477ae63e92240f813c1027de601df11f
[07/17] ASoC: Intel: avs: Add module management requests
commit: f14a1c5a9f830025dc8638303ddefd5f731ae4bc
[08/17] ASoC: Intel: avs: Add power management requests
commit: 469e87ca9a2029c325362496c7b589683a382505
[09/17] ASoC: Intel: avs: Add ROM requests
commit: 25f414fcdb875e4203ff43f42898367c32df4827
[10/17] ASoC: Intel: avs: Add basefw runtime-parameter requests
commit: 3322e1688953966da15fcd0ae3183a351e241ea3
[11/17] ASoC: Intel: avs: Firmware resources management utilities
commit: c1a427e8da9332a5832fd4a5429adede34bfa85f
[12/17] ASoC: Intel: avs: Declare module configuration types
commit: 580a5912d1fe774f9902b614fa33e1add92ca749
[13/17] ASoC: Intel: avs: Dynamic firmware resources management
commit: 215e67b2d2de1d8d34a53c440b9a19a732ee6fb0
[14/17] ASoC: Intel: avs: General code loading flow
commit: b27f452317236b0cbaa94c4498f8241e2ad871b1
[15/17] ASoC: Intel: avs: Implement CLDMA transfer
commit: 45864e49a05aa446b9d99c464c1a9f46956ed32c
[16/17] ASoC: Intel: avs: Code loading over CLDMA
commit: 65794fe1a5f6f5fb10fa7b71a762158332144855
[17/17] ASoC: Intel: avs: Code loading over HDA
commit: 092cf7b26a48a542d9aabfc0f517fa263102a4c1
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
next prev parent reply other threads:[~2022-03-11 20:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 15:35 [PATCH v5 00/17] ASoC: Intel: AVS - Audio DSP for cAVS Cezary Rojewski
2022-03-11 15:35 ` [PATCH v5 01/17] ALSA: hda: Add helper macros for DSP capable devices Cezary Rojewski
2022-03-11 15:31 ` Takashi Iwai
2022-03-11 15:35 ` [PATCH v5 02/17] ASoC: Export DAI register and widget ctor and dctor functions Cezary Rojewski
2022-03-11 15:35 ` [PATCH v5 03/17] ASoC: Intel: Introduce AVS driver Cezary Rojewski
2022-03-11 15:35 ` [PATCH v5 04/17] ASoC: Intel: avs: Inter process communication Cezary Rojewski
2022-03-11 15:35 ` [PATCH v5 05/17] ASoC: Intel: avs: Add code loading requests Cezary Rojewski
2022-03-11 15:35 ` [PATCH v5 06/17] ASoC: Intel: avs: Add pipeline management requests Cezary Rojewski
2022-03-11 15:35 ` [PATCH v5 07/17] ASoC: Intel: avs: Add module " Cezary Rojewski
2022-03-11 15:35 ` [PATCH v5 08/17] ASoC: Intel: avs: Add power " Cezary Rojewski
2022-03-11 15:35 ` [PATCH v5 09/17] ASoC: Intel: avs: Add ROM requests Cezary Rojewski
2022-03-11 15:35 ` [PATCH v5 10/17] ASoC: Intel: avs: Add basefw runtime-parameter requests Cezary Rojewski
2022-03-11 15:35 ` [PATCH v5 11/17] ASoC: Intel: avs: Firmware resources management utilities Cezary Rojewski
2022-03-11 15:35 ` [PATCH v5 12/17] ASoC: Intel: avs: Declare module configuration types Cezary Rojewski
2022-03-11 15:35 ` [PATCH v5 13/17] ASoC: Intel: avs: Dynamic firmware resources management Cezary Rojewski
2022-03-11 15:35 ` [PATCH v5 14/17] ASoC: Intel: avs: General code loading flow Cezary Rojewski
2022-03-11 15:35 ` [PATCH v5 15/17] ASoC: Intel: avs: Implement CLDMA transfer Cezary Rojewski
2022-03-11 15:35 ` [PATCH v5 16/17] ASoC: Intel: avs: Code loading over CLDMA Cezary Rojewski
2022-03-11 15:35 ` [PATCH v5 17/17] ASoC: Intel: avs: Code loading over HDA Cezary Rojewski
2022-03-11 20:22 ` Mark Brown [this message]
2022-03-11 20:24 ` [PATCH v5 00/17] ASoC: Intel: AVS - Audio DSP for cAVS Mark Brown
2022-03-14 18:00 ` 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=164703016723.264137.1929793280515599976.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=cezary.rojewski@intel.com \
--cc=cujomalainey@chromium.org \
--cc=harshapriya.n@intel.com \
--cc=hdegoede@redhat.com \
--cc=lma@semihalf.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rad@semihalf.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tiwai@suse.com \
--cc=upstream@semihalf.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.