| Message ID | 20240814083929.1217319-1-cezary.rojewski@intel.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | ASoC: Intel: Remove skylake driver | expand |
On Wed, Aug 14, 2024 at 10:39:15AM +0200, Cezary Rojewski wrote: > A spiritual successor to haswell/baytrail removal series [1]. > > The avs-driver found in sound/soc/intel/avs is a direct replacement to > the existing skylake-driver. It covers all features supported by it and > more and aligns with the recommended flows and requirements based on > Windows driver equivalent. > > The skylake-driver related UAPI has been removed with "ASoC: Drop > soc-topology ABI v4 support" [2]. > > For the official kernel tree the deprecation begun with v6.0. Most > skylake-drivers users moved to avs- or SOF-driver when AudioDSP > capabilities are available on the platform or to snd-hda-intel > (sound/pci/hda) when such capabilities are not. > > For the supported trees the deprecation begun with v5.4 with v5.15 being > the first where the skylake-driver is disabled entirely. > > All machine board drivers that consume this DSP driver have their > replacements present within sound/soc/intel/avs/boards/ directory. > Changes in v2: > - added two new patches (leading the series) > - the first moves all device entries previously under the skylake-driver > dependency under the avs-driver > - the second patch drops struct skl_machine_pdata usage to fix > compilation errors as pointed out by IKP > - no further changes, retained Acked-by tags for these Hmm... Have you received my tag for the v1? Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
On 2024-08-14 4:42 PM, Andy Shevchenko wrote: > On Wed, Aug 14, 2024 at 10:39:15AM +0200, Cezary Rojewski wrote: >> A spiritual successor to haswell/baytrail removal series [1]. >> >> The avs-driver found in sound/soc/intel/avs is a direct replacement to >> the existing skylake-driver. It covers all features supported by it and >> more and aligns with the recommended flows and requirements based on >> Windows driver equivalent. >> >> The skylake-driver related UAPI has been removed with "ASoC: Drop >> soc-topology ABI v4 support" [2]. >> >> For the official kernel tree the deprecation begun with v6.0. Most >> skylake-drivers users moved to avs- or SOF-driver when AudioDSP >> capabilities are available on the platform or to snd-hda-intel >> (sound/pci/hda) when such capabilities are not. >> >> For the supported trees the deprecation begun with v5.4 with v5.15 being >> the first where the skylake-driver is disabled entirely. >> >> All machine board drivers that consume this DSP driver have their >> replacements present within sound/soc/intel/avs/boards/ directory. > >> Changes in v2: >> - added two new patches (leading the series) >> - the first moves all device entries previously under the skylake-driver >> dependency under the avs-driver >> - the second patch drops struct skl_machine_pdata usage to fix >> compilation errors as pointed out by IKP >> - no further changes, retained Acked-by tags for these > > Hmm... Have you received my tag for the v1? > > Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Yeah, I've left the tags alone for patches 3-14 but for the newly added two I did not as that would be inappropriate. The first two patches address the problems reported by IKP bot - I've not been dealing with sound/soc/intel/common/ for a while and have forgotten about its existence. Thank you for reviewing the series! Kind regards, Czarek
On Wed, 14 Aug 2024 10:39:15 +0200, Cezary Rojewski wrote: > A spiritual successor to haswell/baytrail removal series [1]. > > The avs-driver found in sound/soc/intel/avs is a direct replacement to > the existing skylake-driver. It covers all features supported by it and > more and aligns with the recommended flows and requirements based on > Windows driver equivalent. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [01/14] ALSA: hda: Move SST device entries to AVS commit: ec7bccd770b628a465458194aeac4408cdcc5ccd [02/14] ASoC: Intel: Drop skl_machine_pdata usage commit: cd5c4dd97f35cd7cf772fc8c12738bd971cbb58e [03/14] ASoC: Intel: Remove bxt_rt298 board driver commit: 4d61ed7609d8b8fef71f78db6a8ac3221a46ea17 [04/14] ASoC: Intel: Remove bxt_da7219_max98357a board driver commit: fa07502e01569b39265008bac783a1202a7560e5 [05/14] ASoC: Intel: Remove kbl_rt5663_rt5514_max98927 board driver commit: a08b5fde945ef8b427d2d29515a806fe571d7639 [06/14] ASoC: Intel: Remove kbl_rt5663_max98927 board driver commit: 1af24289751253e58850ba572c584f7e6b1caa87 [07/14] ASoC: Intel: Remove kbl_rt5660 board driver commit: 1a40ef882fee37006243ebf0b4848c7811672fe2 [08/14] ASoC: Intel: Remove kbl_da7219_max98927 board driver commit: 1daa8dce04619f39d4d8ee43ae2a0cec9ab31897 [09/14] ASoC: Intel: Remove kbl_da7219_max98357a board driver commit: 15d6966580f3e40fe2f4ecfcde2edd69cc5508e9 [10/14] ASoC: Intel: Remove skl_rt286 board driver commit: 51d8e9b20db840e78e0d1ff585cf4c8eb4e091b0 [11/14] ASoC: Intel: Remove skl_nau88l25_ssm4567 board driver commit: 4dbf2f9a725d1370d67f9a3bce2f33e913b57e52 [12/14] ASoC: Intel: Remove skl_nau88l25_max98357a board driver commit: 6de8dddc56b0577df996212b634f82f6f1fb013c [13/14] ASoC: Intel: Remove skylake driver commit: 46e211411113932be1fd31580a03502466648f91 [14/14] ASoC: Intel: avs: Enable by default for all SST configurations commit: 526139aff1d14c5a2cc0a769c063f439444c61c2 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