From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Felipe Balbi <balbi@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:ULTRA-WIDEBAND (UWB) SUBSYSTEM:"
<linux-usb@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCHv2 1/3] software node: Power management operations for software nodes
Date: Fri, 30 Oct 2020 12:27:02 +0200 [thread overview]
Message-ID: <20201030102702.GA2333887@kuha.fi.intel.com> (raw)
In-Reply-To: <CAJZ5v0gc6ihoNuh5eR4MW+uf9CBH=qoRjGeeOHxgvjmUnorPCg@mail.gmail.com>
Hi Rafael,
On Thu, Oct 29, 2020 at 06:10:59PM +0100, Rafael J. Wysocki wrote:
> Well, this basically implements a wrapper PM domain that is somewhat
> more generic, as a concept, then software nodes PM.
>
> At least it is not specific to software nodes, so I'd prefer it to be
> defined generically.
I don't think we should generalize it like that. I do not think the
power domains should have any links between each other at the general
level (just like we probable should not link fwnodes together anymore
like we do now with the "secondary" fwnode). That is why I have
confined this to software nodes only for now.
I think ideally devices could belong to multiple power domains. That
would be the general solution. I did not think that trying to figure
out how to do that would be reasonable as the first approach (maybe I
should have done exactly that?). But would it be acceptable to allow
devices to belong to multiple power domains?
> Moreover, IIUC, this breaks if the "primary" PM domain callbacks try
> to get to the original PM domain via the dev->pm_domain pointer, which
> the genpd callbacks do.
Ouch, that is true.
> Do we want to wrap the ACPI PM domain only, by any chance? If so, it
> may be more straightforward to invoke swnode callbacks directly from
> there, if any.
The software node can still be the only "primary" fwnode. I don't
think we should limit this to only platforms (and kernels) that
support ACPI.
thanks,
--
heikki
next prev parent reply other threads:[~2020-10-30 10:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 10:59 [PATCHv2 0/3] PM operations for software nodes Heikki Krogerus
2020-10-29 10:59 ` [PATCHv2 1/3] software node: Power management " Heikki Krogerus
2020-10-29 11:13 ` Sakari Ailus
2020-10-29 11:51 ` Heikki Krogerus
2020-10-29 12:17 ` Andy Shevchenko
2020-10-29 13:01 ` Sakari Ailus
2020-10-29 17:10 ` Rafael J. Wysocki
2020-10-30 10:27 ` Heikki Krogerus [this message]
2022-03-25 16:42 ` Lukas Wunner
2022-03-28 8:15 ` Heikki Krogerus
2020-10-29 10:59 ` [PATCHv2 2/3] software node: Introduce device_add_software_node() Heikki Krogerus
2020-10-29 10:59 ` [PATCHv2 3/3] usb: dwc3: pci: Register a software node for the dwc3 platform device Heikki Krogerus
2020-10-29 12:18 ` [PATCHv2 0/3] PM operations for software nodes Andy Shevchenko
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=20201030102702.GA2333887@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=balbi@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sakari.ailus@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