All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Hans de Goede <hdegoede@redhat.com>, alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: intel: atom: Fix breakage for PCM buffer address setup
Date: Thu, 19 Aug 2021 17:35:18 +0200	[thread overview]
Message-ID: <s5hwnoh8n2h.wl-tiwai@suse.de> (raw)
In-Reply-To: <20210819152945.8510-1-tiwai@suse.de>

On Thu, 19 Aug 2021 17:29:45 +0200,
Takashi Iwai wrote:
> 
> The commit 2e6b836312a4 ("ASoC: intel: atom: Fix reference to PCM
> buffer address") changed the reference of PCM buffer address to
> substream->runtime->dma_addr as the buffer address may change
> dynamically.  However, I forgot that the dma_addr field is still not
> set up for the CONTINUOUS buffer type (that this driver uses) yet in
> 5.14 and earlier kernels, and it resulted in garbage I/O.  The problem
> will be fixed in 5.15, but we need to address it quickly for now.
> 
> The fix is to deduce the address again from the DMA pointer with
> virt_to_phys(), but from the right one, substream->runtime->dma_area.
> 
> Fixes: 2e6b836312a4 ("ASoC: intel: atom: Fix reference to PCM buffer address")
> Reported-and-tested-by: Hans de Goede <hdegoede@redhat.com>
> Cc: <stable@vger.kernel.org>
> Link: https://lore.kernel.org/r/2048c6aa-2187-46bd-6772-36a4fb3c5aeb@redhat.com
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
> ---

Mark, as it's close to the 5.14 final, exceptionally I'd like to merge
this into my tree directly now, so that it can be certainly included
in the next PR to Linus.
(Also because the commit will be reverted on for-next again, too.)

After the merge, feel free to pull my for-linus branch into yours.


thanks,

Takashi

  reply	other threads:[~2021-08-19 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19 15:29 [PATCH] ASoC: intel: atom: Fix breakage for PCM buffer address setup Takashi Iwai
2021-08-19 15:35 ` Takashi Iwai [this message]
2021-08-19 15:40   ` Mark Brown
2021-08-19 16:59     ` 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=s5hwnoh8n2h.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=hdegoede@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.