From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: alsa-devel@alsa-project.org
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
tiwai@suse.de, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
vkoul@kernel.org, broonie@kernel.org,
srinivas.kandagatla@linaro.org, jank@cadence.com,
slawomir.blauciak@intel.com,
Bard liao <yung-chuan.liao@linux.intel.com>,
Rander Wang <rander.wang@linux.intel.com>
Subject: [alsa-devel] [PATCH 0/6] soundwire: cadence: better logs and error handling
Date: Fri, 10 Jan 2020 15:57:25 -0600 [thread overview]
Message-ID: <20200110215731.30747-1-pierre-louis.bossart@linux.intel.com> (raw)
This is a stand-alone set of patches to improve error handling and
provide better information to the platform integrator.
As suggested by Vinod, these patches are shared first - with the risk
that they are separated from the actual steps where they are needed.
For reference, the complete set of 100+ patches required for SoundWire
on Intel platforms is available here:
https://github.com/thesofproject/linux/pull/1692
Pierre-Louis Bossart (4):
soundwire: cadence_master: filter out bad interrupts
soundwire: cadence_master: log more useful information during timeouts
soundwire: cadence_master: handle multiple status reports per Slave
soundwire: bus: check first if Slaves become UNATTACHED
Rander Wang (2):
soundwire: cadence_master: clear interrupt status before enabling
interrupt
soundwire: cadence_master: remove config update for interrupt setting
drivers/soundwire/bus.c | 18 +++++++++
drivers/soundwire/cadence_master.c | 60 +++++++++++++++++++++++++-----
2 files changed, 68 insertions(+), 10 deletions(-)
base-commit: b637124800a157c4df3699d1137d8533394f7678
--
2.20.1
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next reply other threads:[~2020-01-10 21:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 21:57 Pierre-Louis Bossart [this message]
2020-01-10 21:57 ` [alsa-devel] [PATCH 1/6] soundwire: cadence_master: filter out bad interrupts Pierre-Louis Bossart
2020-01-10 21:57 ` [alsa-devel] [PATCH 2/6] soundwire: cadence_master: clear interrupt status before enabling interrupt Pierre-Louis Bossart
2020-01-10 21:57 ` [alsa-devel] [PATCH 3/6] soundwire: cadence_master: log more useful information during timeouts Pierre-Louis Bossart
2020-01-10 21:57 ` [alsa-devel] [PATCH 4/6] soundwire: cadence_master: remove config update for interrupt setting Pierre-Louis Bossart
2020-01-10 21:57 ` [alsa-devel] [PATCH 5/6] soundwire: cadence_master: handle multiple status reports per Slave Pierre-Louis Bossart
2020-01-10 21:57 ` [alsa-devel] [PATCH 6/6] soundwire: bus: check first if Slaves become UNATTACHED Pierre-Louis Bossart
2020-01-14 6:24 ` [alsa-devel] [PATCH 0/6] soundwire: cadence: better logs and error handling Vinod Koul
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=20200110215731.30747-1-pierre-louis.bossart@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--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=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=vkoul@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).