Re: [PATCH 0/9] ASoC: SOF/amd: ACP7.B support and ASP carveout firmware loading
From: Mukunda,Vijendar
Date: Thu Oct 15 2026 - 07:59:54 EST
On 14/10/26 00:39, Mark Brown wrote:
> On Tue, 13 Oct 2026 21:11:32 +0530, Vijendar Mukunda wrote:
>> ASoC: SOF/amd: ACP7.B support and ASP carveout firmware loading
>>
>> This series adds ACP7.B platform support to the AMD SOF driver stack
>> and implements the ASP-authenticated firmware load path required by
>> both ACP7.B and ACP7.F.
>>
>> Patches 1-2 are preparatory renames and restructuring. The existing
>> acp7x machine table and chip descriptor are renamed to acp7f to
>> accurately reflect the hardware they target (ACP7.F). The probe
>> callback is restructured to select the per-revision descriptor via a
>> dedicated static pci_device_id entry rather than encoding it in
>> driver_data of the shared ID table.
>>
>> [...]
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.4
>
> Thanks!
>
> [1/9] ASoC: SOF: amd: rename acp7x machine table and descriptor to acp7f
> https://git.kernel.org/broonie/misc/c/929e433b8cbc
> [2/9] ASoC: SOF: amd: select descriptor per PCI revision in acp7x probe
> https://git.kernel.org/broonie/misc/c/f84363861e44
> [3/9] ASoC: amd: add I2S machine table for ACP7.B
> https://git.kernel.org/broonie/misc/c/9246ac5b5c99
> [4/9] ASoC: SOF: amd: add ACP7.B chip descriptor and wire per-revision probe
> https://git.kernel.org/broonie/misc/c/44f8d28191f1
> [5/9] ASoC: SOF: amd: Propagate PCI subsystem Vendor and Device IDs
> https://git.kernel.org/broonie/misc/c/b2dc10ee0b51
> [6/9] ASoC: SOF: amd: consolidate local variable declarations
> https://git.kernel.org/broonie/misc/c/b23e9b1f3b4c
> [7/9] ASoC: amd: acp: add acp-mach-common.h for shared machine driver types
> https://git.kernel.org/broonie/misc/c/0e4c4081169b
> [8/9] ASoC: SOF: amd: propagate pdm_sel to SDW machine driver via mach->pdata
> https://git.kernel.org/broonie/misc/c/439c43d9628e
> [9/9] ASoC: SOF: amd: add ASP carveout firmware loading for ACP7.B/7.F
> https://git.kernel.org/broonie/misc/c/cec3598305a6
>
> 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.
Hi Mark,
I noticed that the incremental patches sent as replies to the v1 series were
not included in the applied changes.
https://lore.kernel.org/alsa-devel/20261014114446.1476489-1-Vijendar.Mukunda@xxxxxxx/T/#u
Please let me know if you would prefer the incremental patches to be resent?
Thanks,
Vijendar
> Thanks,
> Mark