From: Vinod Koul <vkoul@kernel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: andersson@kernel.org, yung-chuan.liao@linux.intel.com,
pierre-louis.bossart@linux.intel.com, sanyog.r.kale@intel.com,
linux-arm-msm@vger.kernel.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] soundwire: qcom: stablity fixes
Date: Mon, 29 May 2023 10:43:54 +0530 [thread overview]
Message-ID: <ZHQ0kosUz15P8jo+@matsya> (raw)
In-Reply-To: <20230525133812.30841-1-srinivas.kandagatla@linaro.org>
On 25-05-23, 14:38, Srinivas Kandagatla wrote:
> During x13s audio testing we hit few corner cases due to issues
> in codec drivers and some obvious code bugs.
>
> Here are the fixes for those issues, mostly the issues are around
> devices loosing the sync in between runtime pm suspend resume path.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2023-05-29 5:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 13:38 [PATCH v2 0/4] soundwire: qcom: stablity fixes Srinivas Kandagatla
2023-05-25 13:38 ` [PATCH v2 1/4] soundwire: qcom: update status correctly with mask Srinivas Kandagatla
2023-07-10 8:17 ` Johan Hovold
2023-05-25 13:38 ` [PATCH v2 2/4] soundwire: qcom: wait for fifo to be empty before suspend Srinivas Kandagatla
2023-05-25 13:38 ` [PATCH v2 3/4] soundwire: qcom: add software workaround for bus clash interrupt assertion Srinivas Kandagatla
2023-05-25 13:38 ` [PATCH v2 4/4] soundwire: qcom: set clk stop need reset flag at runtime Srinivas Kandagatla
2023-05-29 5:13 ` Vinod Koul [this message]
2023-06-05 9:08 ` [PATCH v2 0/4] soundwire: qcom: stablity fixes Johan Hovold
2023-06-07 9:36 ` Srinivas Kandagatla
2023-06-08 10:11 ` Johan Hovold
2023-06-08 12:40 ` Johan Hovold
2023-06-08 12:45 ` Srinivas Kandagatla
2023-06-08 13:05 ` Johan Hovold
2023-06-08 14:23 ` Srinivas Kandagatla
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=ZHQ0kosUz15P8jo+@matsya \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=andersson@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--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.