From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Richard Fitzgerald <rf@opensource.cirrus.com>,
vkoul@kernel.org, yung-chuan.liao@linux.intel.com,
sanyog.r.kale@intel.com
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH v3 0/5] soundwire: Fixes for spurious and missing UNATTACH
Date: Wed, 14 Sep 2022 16:00:10 +0200 [thread overview]
Message-ID: <81fb961f-2629-fece-112b-4277d9e45d6c@linux.intel.com> (raw)
In-Reply-To: <20220914120949.747951-1-rf@opensource.cirrus.com>
On 9/14/22 14:09, Richard Fitzgerald wrote:
> The bus and cadence code has several bugs that cause UNATTACH notifications
> to either be sent spuriously or to be missed.
>
> These can be seen occasionally with a single peripheral on the bus, but are
> much more frequent with multiple peripherals, where several peripherals
> could change state and report in consecutive PINGs.
>
> The root of all of these bugs seems to be a code design flaw that assumed
> every PING status change would be handled separately. However, PINGs are
> handled by a workqueue function and there is no guarantee when that function
> will be scheduled to run or how much CPU time it will receive. PINGs will
> continue while the work function is handling a snapshot of a previous PING
> so the code must take account that (a) status could change during the
> work function and (b) there can be a backlog of changes before the IRQ work
> function runs again.
>
> Tested with 4 peripherals on 1 bus, and 8 peripherals on 2 buses.
I added my Reviewed-by tags for the last patches, there's only one typo
which could be dealt with a follow-up patch if that's easier
Thanks again for this contribution, much appreciated.
> CHANGES SINCE V2:
> #4 Add a comment explaining why INTMASK isn't cleared when going around
> the update_status loop.
>
> #5 Leave the existing error handling in sdw_program_device_num(),
> instead of suppressing the error return.
> Add a comment in sdw_handle_slave_status() explaining why the error
> is ignored.
> Re-word the explanation of why sdw_handle_slave_status() must only return
> early if it programmed a device ID.
>
> Richard Fitzgerald (4):
> soundwire: bus: Don't lose unattach notifications
> soundwire: bus: Don't re-enumerate before status is UNATTACHED
> soundwire: cadence: Fix lost ATTACHED interrupts when enumerating
> soundwire: bus: Don't exit early if no device IDs were programmed
>
> Simon Trimmer (1):
> soundwire: cadence: fix updating slave status when a bus has multiple
> peripherals
>
> drivers/soundwire/bus.c | 44 +++++++++++++---
> drivers/soundwire/cadence_master.c | 80 ++++++++++++++++--------------
> 2 files changed, 80 insertions(+), 44 deletions(-)
>
prev parent reply other threads:[~2022-09-14 14:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 12:09 [PATCH v3 0/5] soundwire: Fixes for spurious and missing UNATTACH Richard Fitzgerald
2022-09-14 12:09 ` [PATCH v3 1/5] soundwire: cadence: fix updating slave status when a bus has multiple peripherals Richard Fitzgerald
2022-09-14 12:09 ` [PATCH v3 2/5] soundwire: bus: Don't lose unattach notifications Richard Fitzgerald
2022-09-14 12:09 ` [PATCH v3 3/5] soundwire: bus: Don't re-enumerate before status is UNATTACHED Richard Fitzgerald
2022-09-14 12:09 ` [PATCH v3 4/5] soundwire: cadence: Fix lost ATTACHED interrupts when enumerating Richard Fitzgerald
2022-09-14 13:48 ` Pierre-Louis Bossart
2022-09-14 14:30 ` Richard Fitzgerald
2022-09-14 12:09 ` [PATCH v3 5/5] soundwire: bus: Don't exit early if no device IDs were programmed Richard Fitzgerald
2022-09-14 13:58 ` Pierre-Louis Bossart
2022-09-14 14:00 ` Pierre-Louis Bossart [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=81fb961f-2629-fece-112b-4277d9e45d6c@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--cc=sanyog.r.kale@intel.com \
--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