All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ajay Agarwal <ajayagarwal@google.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Kevin Hilman <khilman@kernel.org>, Pavel Machek <pavel@ucw.cz>,
	Len Brown <len.brown@intel.com>,
	linux-pm@vger.kernel.org, manugautam@google.com,
	mshavit@google.com, quangh@google.com
Subject: Re: Prevent PM suspend from powering off the domain for non-wakeup in-use devices
Date: Mon, 10 Jul 2023 23:29:58 +0530	[thread overview]
Message-ID: <ZKxHHvBKvJeWiioc@google.com> (raw)
In-Reply-To: <20230707164149.GP6001@thinkpad>

Thanks Ulf and Mani for looking into this. I could not quite understand
your suggestions here. I believe you are talking about adding a new
helper API. What flag will this API update? Will it be
`dev->power.wakeup_path` itself? Or do we introduce a new boolean flag
in dev_pm_info structure for this?

Also, how about the genpd flag? Shall we re-use the
GENPD_FLAG_ACTIVE_WAKEUP flag? Or create a new one?

I feel that we should come up with a generic name for both the genpd
flag and the power flag to satisfy both the wakeup usecase and the
stay-on usecase. Let me know what you think.

Rafael, can you chime in as well?

  reply	other threads:[~2023-07-10 18:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06  3:06 Prevent PM suspend from powering off the domain for non-wakeup in-use devices Ajay Agarwal
2023-07-07 14:49 ` Ulf Hansson
2023-07-07 16:41   ` Manivannan Sadhasivam
2023-07-10 17:59     ` Ajay Agarwal [this message]
2023-07-13 14:30       ` Ulf Hansson
2023-07-31 12:27         ` Michael Shavit
2023-08-10 15:56           ` Ulf Hansson
2023-08-10 18:00             ` Michael Shavit
2023-08-11  8:33               ` Ulf Hansson

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=ZKxHHvBKvJeWiioc@google.com \
    --to=ajayagarwal@google.com \
    --cc=khilman@kernel.org \
    --cc=len.brown@intel.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=manugautam@google.com \
    --cc=mshavit@google.com \
    --cc=pavel@ucw.cz \
    --cc=quangh@google.com \
    --cc=rafael@kernel.org \
    --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.