From: Beleswar Padhi <b-padhi@ti.com>
To: <gregkh@linuxfoundation.org>, <rafael@kernel.org>,
<dakr@kernel.org>, <johan@kernel.org>, <pavel@kernel.org>,
<lenb@kernel.org>, <ulfh@kernel.org>
Cc: <sid9.karanam@gmail.com>, <afd@ti.com>, <nm@ti.com>,
<vigneshr@ti.com>, <u-kumar1@ti.com>, <b-padhi@ti.com>,
<driver-core@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<linux-pm@vger.kernel.org>
Subject: [RFC PATCH 0/2] Allow platform drivers to skip PM domain power-on at probe
Date: Tue, 27 Oct 2026 19:37:49 +0530 [thread overview]
Message-ID: <20261027140751.2465743-1-b-padhi@ti.com> (raw)
Some devices must be configured before their PM domain is powered on,
but on DT based platforms platform_probe() always powers it on first.
This series lets a platform driver opt out.
The user will be the TI K3 DSP/M4 remoteproc drivers which need to put
those remote cores in reset before powering on the pmdomain. A patch has
been posted to add "power-domains" DT property to these devices[0] which
is the motivation of this series as well.
[0]: https://lore.kernel.org/all/8cb23b44-027d-4d81-b342-7eaca0248f63@ti.com/
Please provide your comments.
Thanks,
Beleswar
Beleswar Padhi (2):
PM: domains: Honour PD_FLAG_ATTACH_POWER_ON for genpd
driver core: platform: Allow drivers to skip PM domain power-on at
probe
drivers/base/platform.c | 7 +++++--
drivers/base/power/common.c | 5 +++--
drivers/pmdomain/core.c | 5 +++--
include/linux/platform_device.h | 8 ++++++++
include/linux/pm_domain.h | 4 ++--
5 files changed, 21 insertions(+), 8 deletions(-)
--
2.34.1
next reply other threads:[~2026-10-27 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 14:07 Beleswar Padhi [this message]
2026-10-27 14:07 ` [RFC PATCH 1/2] PM: domains: Honour PD_FLAG_ATTACH_POWER_ON for genpd Beleswar Padhi
2026-10-27 14:07 ` [RFC PATCH 2/2] driver core: platform: Allow drivers to skip PM domain power-on at probe Beleswar Padhi
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=20261027140751.2465743-1-b-padhi@ti.com \
--to=b-padhi@ti.com \
--cc=afd@ti.com \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=pavel@kernel.org \
--cc=rafael@kernel.org \
--cc=sid9.karanam@gmail.com \
--cc=u-kumar1@ti.com \
--cc=ulfh@kernel.org \
--cc=vigneshr@ti.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®