From: Vinod Koul <vkoul@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
gregkh@linuxfoundation.org, broonie@kernel.org,
srinivas.kandagatla@linaro.org,
Bard liao <yung-chuan.liao@linux.intel.com>
Subject: Re: [PATCH 0/3] soundwire: revisit peripheral driver bind/unbind
Date: Wed, 6 Jul 2022 10:41:02 +0530 [thread overview]
Message-ID: <YsUZZmQsz25YNfM/@matsya> (raw)
In-Reply-To: <20220621225641.221170-1-pierre-louis.bossart@linux.intel.com>
On 21-06-22, 17:56, Pierre-Louis Bossart wrote:
> This patchset fixes the driver bind/unbind cases which are not
> well-supported today. I initially reported a race condition in March
> 2022 [1] and the more tests I ran the more timing assumptions crept to
> the surface.
>
> With this patchset, I've been able to bind the drivers in any order,
> and when all dependencies were available the card is
> created/registered. Likewise I was able to remove codec drivers while
> the bus was still running. The initial suggestion to use
> device_lock()/unlock() led to system hangs in suspend-resume that I
> was unable to root-cause after weeks of tests, hence this patchset
> relies on a SoundWire-specific lock doesn't interfere with other core
> device locking.
Applied, thanks for this cleanup.
--
~Vinod
prev parent reply other threads:[~2022-07-06 5:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 22:56 [PATCH 0/3] soundwire: revisit peripheral driver bind/unbind Pierre-Louis Bossart
2022-06-21 22:56 ` [PATCH 1/3] soundwire: revisit driver bind/unbind and callbacks Pierre-Louis Bossart
2022-06-21 22:56 ` Pierre-Louis Bossart
2022-06-21 22:56 ` [PATCH 2/3] soundwire: peripheral: remove useless ops pointer Pierre-Louis Bossart
2022-06-21 22:56 ` Pierre-Louis Bossart
2022-06-21 22:56 ` [PATCH 3/3] soundwire: intel: use pm_runtime_resume() on component probe Pierre-Louis Bossart
2022-06-21 22:56 ` Pierre-Louis Bossart
2022-07-06 5:11 ` Vinod Koul [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=YsUZZmQsz25YNfM/@matsya \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--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.