Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Takashi Iwai <tiwai@suse.de>, <alsa-devel@alsa-project.org>
Cc: Mark Brown <broonie@kernel.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [PATCH 3/3] ASoC: intel: skylake: Set max DMA segment size
Date: Tue, 15 Feb 2022 15:37:55 +0100	[thread overview]
Message-ID: <af117b20-15d0-1392-b6aa-36f082eee0e0@intel.com> (raw)
In-Reply-To: <20220215132756.31236-4-tiwai@suse.de>

On 2022-02-15 2:27 PM, Takashi Iwai wrote:
> The recent code refactoring to use the standard DMA helper requires
> the max DMA segment size setup for SG list management.  Without it,
> the kernel may spew warnings when a large buffer is allocated.
> 
> This patch sets up dma_set_max_seg_size() for avoiding spurious
> warnings.


Thanks for accounting for skylake-driver when providing fixes.

Acked-by: Cezary Rojewski <cezary.rojewski@intel.com>

> Fixes: 2c95b92ecd92 ("ALSA: memalloc: Unify x86 SG-buffer handling (take#3)")
> Cc: <stable@vger.kernel.org>
> BugLink: https://github.com/thesofproject/linux/issues/3430
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
> ---
>   sound/soc/intel/skylake/skl.c | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/sound/soc/intel/skylake/skl.c b/sound/soc/intel/skylake/skl.c
> index 148ddf4cace0..aeca58246fc7 100644
> --- a/sound/soc/intel/skylake/skl.c
> +++ b/sound/soc/intel/skylake/skl.c
> @@ -952,6 +952,7 @@ static int skl_first_init(struct hdac_bus *bus)
>   	/* allow 64bit DMA address if supported by H/W */
>   	if (dma_set_mask_and_coherent(bus->dev, DMA_BIT_MASK(64)))
>   		dma_set_mask_and_coherent(bus->dev, DMA_BIT_MASK(32));
> +	dma_set_max_seg_size(bus->dev, UINT_MAX);
>   
>   	/* initialize streams */
>   	snd_hdac_ext_stream_init_all

  reply	other threads:[~2022-02-15 14:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 13:27 [PATCH 0/3] ALSA: Set max DMA segment size Takashi Iwai
2022-02-15 13:27 ` [PATCH 1/3] ALSA: hda: " Takashi Iwai
2022-02-15 13:27 ` [PATCH 2/3] ASoC: SOF: " Takashi Iwai
2022-02-16 16:31   ` Mark Brown
2022-02-15 13:27 ` [PATCH 3/3] ASoC: intel: skylake: " Takashi Iwai
2022-02-15 14:37   ` Cezary Rojewski [this message]
2022-02-16 16:31   ` Mark Brown
2022-02-17  8:48 ` [PATCH 0/3] ALSA: " Takashi Iwai

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=af117b20-15d0-1392-b6aa-36f082eee0e0@intel.com \
    --to=cezary.rojewski@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.de \
    /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