From: Takashi Iwai <tiwai@suse.de>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: tiwai@suse.com, broonie@kernel.org, perex@perex.cz,
amadeuszx.slawinski@linux.intel.com, linux-sound@vger.kernel.org
Subject: Re: [PATCH v4] ALSA: hda: Transfer firmware in two chunks
Date: Wed, 15 Jan 2025 08:58:12 +0100 [thread overview]
Message-ID: <87a5bsld9n.wl-tiwai@suse.de> (raw)
In-Reply-To: <20250114184239.120002-1-cezary.rojewski@intel.com>
On Tue, 14 Jan 2025 19:42:39 +0100,
Cezary Rojewski wrote:
>
> As per specification, SDxLVI shall be at least 1 i.e.: two chunks to
> perform a valid transfer. This is true for the PCM transfer code but
> not firmware-transfer one.
>
> Technical background:
> - the LVI > 0 rule shall be obeyed in PCM transfer
> - HW permits LVI == 0 when transfer is SW-controlled (SPIB)
> - FW download is not a PCM transfer and is SW-controlled (SPIB)
>
> The above is the fundament which AudioDSP firmware loading functions
> have been built upon and worked since 2016. The presented changes are to
> align the loading flows and avoid rising more questions in the future.
>
> Achieve the goal by splitting snd_hdac_stream_setup_periods() into
> substream-dependent and -independent part. Let snd_hdac_dsp_prepare()
> utilize the latter so that both DSP-loading and PCM flows utilize same
> BLDE setup loop which already takes care of cutting the buffer based on
> azx_dev->period_bytes.
>
> Signed-off-by: Cezary Rojewski <cezary.rojewski@intel.com>
Applied now. Thanks.
Takashi
prev parent reply other threads:[~2025-01-15 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 18:42 [PATCH v4] ALSA: hda: Transfer firmware in two chunks Cezary Rojewski
2025-01-15 7:58 ` Takashi Iwai [this message]
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=87a5bsld9n.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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