[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <41d1aad9-2381-4d7b-b247-9d114c5c517f@opensource.cirrus.com>
Date: Mon, 1 Apr 2024 09:32:49 +0000
From: Richard Fitzgerald <rf@...nsource.cirrus.com>
To: Takashi Iwai <tiwai@...e.de>
CC: <broonie@...nel.org>, <tiwai@...e.com>, <linux-sound@...r.kernel.org>,
<alsa-devel@...a-project.org>, <linux-kernel@...r.kernel.org>,
<patches@...nsource.cirrus.com>
Subject: Re: [PATCH 0/5] ALSA: cirrus: Tidy up of firmware control read/write
On 30/03/2024 08:40, Takashi Iwai wrote:
> On Mon, 25 Mar 2024 12:31:22 +0100,
> Richard Fitzgerald wrote:
>>
>> This set of patches factors out some repeated code to clean up
>> firmware control read/write functions, and removes some redundant
>> control notification code.
>>
>> Simon Trimmer (5):
>> firmware: cs_dsp: Add locked wrappers for coeff read and write
>> ASoC: wm_adsp: Use cs_dsp_coeff_lock_and_[read|write]_ctrl()
>> ALSA: hda: hda_cs_dsp_ctl: Use
>> cs_dsp_coeff_lock_and_[read|write]_ctrl()
>> ASoC: wm_adsp: Remove notification of driver write
>> ALSA: hda: hda_cs_dsp_ctl: Remove notification of driver write
>
> The patch 4 doesn't look cleanly applicable to my tree.
> Should it be applied via Mark's tree?
>
Yes, it will need to go through Mark's tree.
Mark's for-next has one extra patch to wm_adsp.c that changes
the same function:
f193957b0fbb ("ASoC: wm_adsp: Fix missing mutex_lock in
wm_adsp_write_ctl()")
Powered by blists - more mailing lists