From: Vinod Koul <vkoul@kernel.org>
To: Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: broonie@kernel.org, tiwai@suse.de, linux-kernel@vger.kernel.org,
linux-sound@vger.kernel.org, pierre-louis.bossart@linux.dev,
bard.liao@intel.com, ranjani.sridharan@linux.intel.com
Subject: Re: [PATCH 3/4] soundwire: intel_ace2x: Send PDI stream number during prepare
Date: Thu, 17 Oct 2024 12:07:09 +0530 [thread overview]
Message-ID: <ZxCwlYBP4OUFhXR5@vaman> (raw)
In-Reply-To: <20241016032910.14601-4-yung-chuan.liao@linux.intel.com>
On 16-10-24, 11:29, Bard Liao wrote:
> From: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
>
> In the case of a prepare callback after an xrun or when the PCM is
> restarted after a call to snd_pcm_drain/snd_pcm_drop, avoid
> reprogramming the SHIM registers but send the PDI stream number so that
> the link DMA data can be set. This is needed for the case that the DMA
> data is cleared when the PCM is stopped and restarted without being
> closed.
Acked-by: Vinod Koul <vkoul@kernel.org>
--
~Vinod
next prev parent reply other threads:[~2024-10-17 6:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 3:29 [PATCH 0/4] ASoC/SoundWire: clean up link DMA during stop for IPC4 Bard Liao
2024-10-16 3:29 ` [PATCH 1/4] ASoC: SOF: ipc4-topology: Do not set ALH node_id for aggregated DAIs Bard Liao
2024-10-16 3:29 ` [PATCH 2/4] ASoC: SOF: Intel: hda: Handle prepare without close for non-HDA DAI's Bard Liao
2024-10-16 3:29 ` [PATCH 3/4] soundwire: intel_ace2x: Send PDI stream number during prepare Bard Liao
2024-10-17 6:37 ` Vinod Koul [this message]
2024-10-16 3:29 ` [PATCH 4/4] ASoC: SOF: Intel: hda: Always clean up link DMA during stop Bard Liao
2024-10-16 13:58 ` [PATCH 0/4] ASoC/SoundWire: clean up link DMA during stop for IPC4 Liao, Bard
2024-10-18 21:30 ` Mark Brown
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=ZxCwlYBP4OUFhXR5@vaman \
--to=vkoul@kernel.org \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=pierre-louis.bossart@linux.dev \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tiwai@suse.de \
--cc=yung-chuan.liao@linux.intel.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.