From: Vinod Koul <vkoul@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
tiwai@suse.de, broonie@kernel.org, gregkh@linuxfoundation.org,
jank@cadence.com, srinivas.kandagatla@linaro.org,
slawomir.blauciak@intel.com,
Bard liao <yung-chuan.liao@linux.intel.com>,
Rander Wang <rander.wang@linux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Subject: Re: [PATCH v2 0/5] soundwire: stream: fix state machines and transitions
Date: Thu, 13 Feb 2020 15:59:11 +0530 [thread overview]
Message-ID: <20200213102911.GE2618@vkoul-mobl> (raw)
In-Reply-To: <20200114235227.14502-1-pierre-louis.bossart@linux.intel.com>
On 14-01-20, 17:52, Pierre-Louis Bossart wrote:
> The existing stream support works fine with simple cases, but does not
> map well with ALSA transitions for underflows/resume where prepare()
> can be called multiple times. Concurrency with multiple devices per
> links or multiple streams enabled on the same link also needs to be
> fixed.
>
> These patches are the result of hours of validation on the Intel side
> and should benefit other implementations since there is nothing
> hardware-specific. The Intel-specific changes being reviewed do depend
> on those stream changes though to be functional.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2020-02-13 10:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 23:52 [PATCH v2 0/5] soundwire: stream: fix state machines and transitions Pierre-Louis Bossart
2020-01-14 23:52 ` [PATCH v2 1/5] soundwire: stream: update state machine and add state checks Pierre-Louis Bossart
2020-01-14 23:52 ` [PATCH v2 2/5] soundwire: stream: only prepare stream when it is configured Pierre-Louis Bossart
2020-01-14 23:52 ` [PATCH v2 3/5] soundwire: stream: do not update parameters during DISABLED-PREPARED transition Pierre-Louis Bossart
2020-01-14 23:52 ` [PATCH v2 4/5] soundwire: stream: fix support for multiple Slaves on the same link Pierre-Louis Bossart
2020-01-14 23:52 ` [PATCH v2 5/5] soundwire: stream: don't program ports when a stream that has not been prepared Pierre-Louis Bossart
2020-02-10 14:27 ` [PATCH v2 0/5] soundwire: stream: fix state machines and transitions Pierre-Louis Bossart
2020-02-13 10:29 ` Vinod Koul [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=20200213102911.GE2618@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jank@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=slawomir.blauciak@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox