From: Bard Liao <yung-chuan.liao@linux.intel.com>
To: alsa-devel@alsa-project.org, vkoul@kernel.org
Cc: vinod.koul@linaro.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, srinivas.kandagatla@linaro.org,
rander.wang@linux.intel.com, hui.wang@canonical.com,
pierre-louis.bossart@linux.intel.com, sanyog.r.kale@intel.com,
bard.liao@intel.com
Subject: [PATCH 0/2] soundwire: bus: handle errors in clock stop/start sequences
Date: Wed, 31 Mar 2021 09:13:53 +0800 [thread overview]
Message-ID: <20210331011355.14313-1-yung-chuan.liao@linux.intel.com> (raw)
If a device lost sync and can no longer ACK a command, it may not be
able to enter a lower-power state but it will still be able to resync
when the clock restarts. In those cases, we want to continue with the
clock stop sequence.
This patch modifies the behavior when -ENODATA is received, with the
error level demoted to a dev_dbg() since it's a recoverable issue.
For consistency the log messages are also modified to be unique and
self-explanatory, and missing logs are also added on clock stop exit.
Pierre-Louis Bossart (2):
soundwire: add macro to selectively change error levels
soundwire: bus: handle errors in clock stop/start sequences
drivers/soundwire/bus.c | 70 +++++++++++++++++++----------------------
drivers/soundwire/bus.h | 8 +++++
2 files changed, 40 insertions(+), 38 deletions(-)
--
2.17.1
next reply other threads:[~2021-03-31 1:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 1:13 Bard Liao [this message]
2021-03-31 1:13 ` [PATCH 1/2] soundwire: add macro to selectively change error levels Bard Liao
2021-04-01 7:24 ` Vinod Koul
2021-04-01 14:30 ` Pierre-Louis Bossart
2021-04-01 16:46 ` Greg KH
2021-04-01 18:07 ` Pierre-Louis Bossart
2021-04-01 18:25 ` Greg KH
2021-04-01 18:43 ` Pierre-Louis Bossart
2021-04-01 20:56 ` Greg KH
2021-04-01 22:05 ` Pierre-Louis Bossart
2021-03-31 1:13 ` [PATCH 2/2] soundwire: bus: handle errors in clock stop/start sequences Bard Liao
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=20210331011355.14313-1-yung-chuan.liao@linux.intel.com \
--to=yung-chuan.liao@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=vinod.koul@linaro.org \
--cc=vkoul@kernel.org \
/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
all inboxes | Powered by JetHome®