[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210115053738.22630-1-yung-chuan.liao@linux.intel.com>
Date: Fri, 15 Jan 2021 13:37:33 +0800
From: Bard Liao <yung-chuan.liao@...ux.intel.com>
To: alsa-devel@...a-project.org, vkoul@...nel.org
Cc: vinod.koul@...aro.org, linux-kernel@...r.kernel.org,
gregkh@...uxfoundation.org, jank@...ence.com,
srinivas.kandagatla@...aro.org, rander.wang@...ux.intel.com,
hui.wang@...onical.com, pierre-louis.bossart@...ux.intel.com,
sanyog.r.kale@...el.com, bard.liao@...el.com
Subject: [PATCH 0/5] soundwire: fix ACK/NAK handling and improve log
The existing code reports a NAK only when ACK=0
This is not aligned with the SoundWire 1.x specifications.
Table 32 in the SoundWire 1.2 specification shows that a Device shall
not set NAK=1 if ACK=1. But Table 33 shows the Combined Response
may very well be NAK=1/ACK=1, e.g. if another Device than the one
addressed reports a parity error.
NAK=1 signals a 'Command_Aborted', regardless of the ACK bit value.
Move the tests for NAK so that the NAK=1/ACK=1 combination is properly
detected according to the specification.
Also, improve the demesg log to get more information for debugging.
Bard Liao (1):
soundwire: bus: add more details to track failed transfers
Pierre-Louis Bossart (4):
soundwire: use consistent format for Slave devID logs
soundwire: cadence: add status in dev_dbg 'State change' log
soundwire: cadence: fix ACK/NAK handling
soundwire: cadence: adjust verbosity in response handling
drivers/soundwire/bus.c | 11 ++++++-----
drivers/soundwire/cadence_master.c | 29 +++++++++++++++--------------
drivers/soundwire/slave.c | 10 ++++------
3 files changed, 25 insertions(+), 25 deletions(-)
--
2.17.1
Powered by blists - more mailing lists