From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: <alsa-devel@alsa-project.org>, <vkoul@kernel.org>,
<vinod.koul@linaro.org>, <linux-kernel@vger.kernel.org>,
<pierre-louis.bossart@linux.intel.com>, <bard.liao@intel.com>
Subject: Re: [PATCH 1/2] soundwire: intel_auxdevice: enable pm_runtime earlier on startup
Date: Fri, 4 Aug 2023 09:44:41 +0000 [thread overview]
Message-ID: <20230804094441.GR103419@ediswmail.ad.cirrus.com> (raw)
In-Reply-To: <20230803065220.3823269-2-yung-chuan.liao@linux.intel.com>
On Thu, Aug 03, 2023 at 02:52:19PM +0800, Bard Liao wrote:
> From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
>
> As soon as the bus starts, physical peripheral devices may report as
> ATTACHED and set their status with pm_runtime_set_active() in their
> update_status()/io_init().
>
> This is problematic with the existing code, since the parent
> pm_runtime status is changed to "active" after starting the bus. This
> creates a time window where the pm_runtime framework can report an
> issue, e.g.
>
> "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 patch enables runtime_pm earlier to make sure the auxiliary
> device is pm_runtime active after powering-up, but before starting the
> bus.
>
> This problem was exposed by recent changes in the timing of the bus
> reset, but was present in this driver since we introduced pm_runtime
> support.
>
> Closes: https://github.com/thesofproject/linux/issues/4328
> Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
> Reviewed-by: Rander Wang <rander.wang@intel.com>
> Signed-off-by: Bard Liao <yung-chuan.liao@linux.intel.com>
> ---
Doesn't seem to cause any problems on my SoundWire devices, so
very loosely:
Tested-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Thanks,
Charles
next prev parent reply other threads:[~2023-08-04 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 6:52 [PATCH 0/2] soundwire: improve pm_runtime handling Bard Liao
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 [this message]
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=20230804094441.GR103419@ediswmail.ad.cirrus.com \
--to=ckeepax@opensource.cirrus.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 \
--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
all inboxes | Powered by JetHome®