From: Vinod Koul <vkoul@kernel.org>
To: "Liao, Bard" <bard.liao@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"ranjani.sridharan@linux.intel.com"
<ranjani.sridharan@linux.intel.com>,
"pierre-louis.bossart@linux.intel.com"
<pierre-louis.bossart@linux.intel.com>,
"hui.wang@canonical.com" <hui.wang@canonical.com>,
"srinivas.kandagatla@linaro.org" <srinivas.kandagatla@linaro.org>,
"jank@cadence.com" <jank@cadence.com>,
"Lin, Mengdong" <mengdong.lin@intel.com>,
"Kale, Sanyog R" <sanyog.r.kale@intel.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
"rander.wang@linux.intel.com" <rander.wang@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] soundwire: master: use pm_runtime_set_active() on add
Date: Fri, 27 Nov 2020 11:47:58 +0530 [thread overview]
Message-ID: <20201127061758.GK8403@vkoul-mobl> (raw)
In-Reply-To: <20201126042222.GG8403@vkoul-mobl>
On 26-11-20, 09:52, Vinod Koul wrote:
> > > > @@ -154,7 +163,12 @@ int sdw_master_device_add(struct sdw_bus *bus,
> > > struct device *parent,
> > > > bus->dev = &md->dev;
> > > > bus->md = md;
> > > >
> > > > + pm_runtime_set_autosuspend_delay(&bus->md->dev,
> > > SDW_MASTER_SUSPEND_DELAY_MS);
> > > > + pm_runtime_use_autosuspend(&bus->md->dev);
> > > > + pm_runtime_mark_last_busy(&bus->md->dev);
> > > > + pm_runtime_set_active(&bus->md->dev);
> > > > pm_runtime_enable(&bus->md->dev);
> > > > + pm_runtime_idle(&bus->md->dev);
> > >
> > > I understand that this needs to be done somewhere but is the core the right
> > > place. In intel case it maybe a dummy device but other controllers are real
> > > devices and may not support pm.
> > >
> > > I think better idea would be to do this in respective driver.. that way it
> > > would be an opt-in for device supporting pm.
> >
> > Should it be put in the same place as pm_runtime_enable?
> > IMHO, pm_runtime_enable is in the core already and it seems to be harmless
> > for devices which don't support pm. And pm can still be optional on md's
> > parent device.
>
> For intel case yes, but world is not only intel, there are md which do
> not have a parent like sof. they are real sdw controller devices
Sorry I confused md with real master device ;-) I guess this patch
should be okay then.. As the real parent will control.
Thanks
--
~Vinod
next prev parent reply other threads:[~2020-11-27 6:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 13:07 [PATCH] soundwire: master: use pm_runtime_set_active() on add Bard Liao
2020-11-25 5:05 ` Vinod Koul
2020-11-26 3:11 ` Liao, Bard
2020-11-26 4:22 ` Vinod Koul
2020-11-27 6:17 ` Vinod Koul [this message]
2020-12-02 7:19 ` 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=20201127061758.GK8403@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=jank@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mengdong.lin@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=srinivas.kandagatla@linaro.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;
as well as URLs for NNTP newsgroup(s).