From: Takashi Iwai <tiwai@suse.de>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: tiwai@suse.com, linux-sound@vger.kernel.org, broonie@kernel.org,
perex@perex.cz, amadeuszx.slawinski@linux.intel.com
Subject: Re: [PATCH 2/3] ALSA: hda: Transfer firmware in two chunks
Date: Thu, 09 Jan 2025 15:29:26 +0100 [thread overview]
Message-ID: <87y0zk5ad5.wl-tiwai@suse.de> (raw)
In-Reply-To: <20250109125204.3668961-3-cezary.rojewski@intel.com>
On Thu, 09 Jan 2025 13:52:03 +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.
>
> Signed-off-by: Cezary Rojewski <cezary.rojewski@intel.com>
> ---
> sound/hda/hdac_stream.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/sound/hda/hdac_stream.c b/sound/hda/hdac_stream.c
> index 2670792f43b4..18d74a28a246 100644
> --- a/sound/hda/hdac_stream.c
> +++ b/sound/hda/hdac_stream.c
> @@ -455,6 +455,7 @@ static int setup_bdle(struct hdac_bus *bus,
> struct hdac_stream *azx_dev, __le32 **bdlp,
> int ofs, int size, int with_ioc)
> {
> + u32 bdle_size = size / 2;
> __le32 *bdl = *bdlp;
>
> while (size > 0) {
> @@ -469,7 +470,7 @@ static int setup_bdle(struct hdac_bus *bus,
> bdl[0] = cpu_to_le32((u32)addr);
> bdl[1] = cpu_to_le32(upper_32_bits(addr));
> /* program the size field of the BDL entry */
> - chunk = snd_sgbuf_get_chunk_size(dmab, ofs, size);
> + chunk = snd_sgbuf_get_chunk_size(dmab, ofs, bdle_size);
> /* one BDLE cannot cross 4K boundary on CTHDA chips */
> if (bus->align_bdle_4k) {
> u32 remain = 0x1000 - (ofs & 0xfff);
Note that we set up BDLE also for the fragment for pos_adj correction
at the beginning of the buffer. With your patch, this small BDLE
would be split again. I don't think it's the desired outcome.
The requirement is to have at least two BDL entries?
thanks,
Takashi
next prev parent reply other threads:[~2025-01-09 14:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 12:52 [PATCH 0/3] ALSA: hda: Compilation and firmware-loading fixes Cezary Rojewski
2025-01-09 12:52 ` [PATCH 1/3] ALSA: hda: Fix compilation of snd_hdac_adsp_xxx() helpers Cezary Rojewski
2025-01-09 12:42 ` Jaroslav Kysela
2025-01-09 14:20 ` Takashi Iwai
2025-01-09 14:41 ` Cezary Rojewski
2025-01-09 14:52 ` Takashi Iwai
2025-01-09 12:52 ` [PATCH 2/3] ALSA: hda: Transfer firmware in two chunks Cezary Rojewski
2025-01-09 14:29 ` Takashi Iwai [this message]
2025-01-09 17:13 ` Cezary Rojewski
2025-01-09 12:52 ` [PATCH 3/3] ALSA: control: Fix argument type mismatch Cezary Rojewski
2025-01-09 14:31 ` Takashi Iwai
2025-01-09 14:47 ` 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=87y0zk5ad5.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