All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Lina Iyer <ilina@codeaurora.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Linux PM <linux-pm@vger.kernel.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH v6 0/3] Better domain idle from device wakeup patterns
Date: Tue, 8 Dec 2020 18:26:13 +0100	[thread overview]
Message-ID: <CAJZ5v0g+nK+jV+Gy+BKEALRtsXDK0HnDbz07Nv3KPK5L3V3OKg@mail.gmail.com> (raw)
In-Reply-To: <20201130225039.15981-1-ilina@codeaurora.org>

On Mon, Nov 30, 2020 at 11:51 PM Lina Iyer <ilina@codeaurora.org> wrote:
>
> Hi,
>
> The v5[1] of the series brought out some interesting discussions. The
> most important being is it worth adding the additional expense to all PM
> domains even if no wakeup pattern is available. It seems like
> maintaining a domain specific flag that the governor could check is a
> generic enough option. That should disable additional overhead for
> domains that do not need this feature.
>
> Ulf suggested that we could allow wakeups only if any of the domain idle
> state specifies a residency. However, we don't want to check for next
> wakeup everytime the domain enters idle just because the domain
> specifies an idle state with residency. This is also not desired.
>
> Also, if the domain checks for next wakeup, should the parent domains of
> the domain also check for next wakeup? And when do we set that up? These
> are questions that we don't know the answers yet. So, let's enable the
> domain governor only if the domain sets up the flag or when the device
> in the domain specifies the next wakeup.
>
> The previous post of the series explaining why this is a useful feature
> is v5[1]. Please let me know what you think.

Ulf had comments on the previous versions, so waiting for him to
respond here, thanks!

  parent reply	other threads:[~2020-12-08 17:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30 22:50 [PATCH v6 0/3] Better domain idle from device wakeup patterns Lina Iyer
2020-11-30 22:50 ` [PATCH v6 1/3] PM / Domains: add domain feature flag for next wakeup Lina Iyer
2020-12-22 13:06   ` Ulf Hansson
2021-01-04 15:54     ` Lina Iyer
2020-11-30 22:50 ` [PATCH v6 2/3] PM / domains: inform PM domain of a device's " Lina Iyer
2020-12-22 13:09   ` Ulf Hansson
2021-01-04 15:43     ` Lina Iyer
2021-01-08 10:07       ` Ulf Hansson
2020-11-30 22:50 ` [PATCH v6 3/3] PM / Domains: use device's next wakeup to determine domain idle state Lina Iyer
2020-12-22 14:41   ` Ulf Hansson
2020-12-08 17:26 ` Rafael J. Wysocki [this message]
2020-12-09 10:36   ` [PATCH v6 0/3] Better domain idle from device wakeup patterns Ulf Hansson
2020-12-09 15:18     ` Lina Iyer

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=CAJZ5v0g+nK+jV+Gy+BKEALRtsXDK0HnDbz07Nv3KPK5L3V3OKg@mail.gmail.com \
    --to=rafael@kernel.org \
    --cc=ilina@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=ulf.hansson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.