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,
pierre-louis.bossart@linux.intel.com, bard.liao@intel.com
Subject: [PATCH 0/2] soundwire: improve pm_runtime handling
Date: Thu, 3 Aug 2023 14:52:18 +0800 [thread overview]
Message-ID: <20230803065220.3823269-1-yung-chuan.liao@linux.intel.com> (raw)
This patchset improves the pm_runtime behavior in rare corner cases
identified by the Intel CI in the last 6 months.
a) in stress-tests, it's not uncommon to see the following type of
warnings when the codec reports as ATTACHED
"rt711 sdw:0:025d:0711:00: runtime PM trying to activate child device
sdw:0:025d:0711:00 but parent (sdw-master-0) is not active"
This warning was not correlated with any functional issue, but it
exposed a design issue on when to enable pm_runtime. The recommended
practice in the pm_runtime documentation is to keep the devices in
'suspended' mode and mark them as 'active' when they are really
functional.
Pierre-Louis Bossart (2):
soundwire: intel_auxdevice: enable pm_runtime earlier on startup
soundWire: intel_auxdevice: resume 'sdw-master' on startup and system
resume
drivers/soundwire/intel_auxdevice.c | 27 +++++++++++++++++++--------
1 file changed, 19 insertions(+), 8 deletions(-)
--
2.25.1
next reply other threads:[~2023-08-03 6:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 6:52 Bard Liao [this message]
2023-08-03 6:52 ` [PATCH 1/2] soundwire: intel_auxdevice: enable pm_runtime earlier on startup Bard Liao
2023-08-04 9:44 ` Charles Keepax
2023-08-03 6:52 ` [PATCH 2/2] soundWire: intel_auxdevice: resume 'sdw-master' on startup and system resume Bard Liao
2023-08-04 9:44 ` Charles Keepax
2023-08-11 7:06 ` [PATCH 0/2] soundwire: improve pm_runtime 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=20230803065220.3823269-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=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--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®