All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@kernel.org>
To: Souvik Chakravarty <souvik.chakravarty@arm.com>,
	Peng Fan <peng.fan@oss.nxp.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Vincent Guittot <vincent.guittot@linaro.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>, Peng Fan <peng.fan@nxp.com>,
	"cristian.marussi@arm.com" <cristian.marussi@arm.com>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	"arm-scmi@vger.kernel.org" <arm-scmi@vger.kernel.org>,
	Chuck Cannon <chuck.cannon@nxp.com>
Subject: Re: POWER_DOMAIN_ATTRIBUTES in SCMI
Date: Mon, 07 Apr 2025 17:23:17 -0700	[thread overview]
Message-ID: <7h7c3vh56y.fsf@baylibre.com> (raw)
In-Reply-To: <81580b24-e11c-40c4-a709-5ad0feab8841@arm.com>

Souvik Chakravarty <souvik.chakravarty@arm.com> writes:

> Some quick thoughts below to keep this architecturally consistent.

[...]

> There are 2 ways to wakeup a device:
> a) The device is powered by one or more PDs, one or more of which needs
> to be kept ON to trigger the wakeup.
> b) The device is powered by one or more PDs, but none of them are
> required to trigger a wakeup. The device wake is derived from an out of
> band logic which is kept powered ON (either transparently to OS, or via
> another PD which does NOT belong to the device).

In the case of TI SoCs, it's (b).  In fact, most of the IO pads on the
SoC can be enabled as wakeup capable when the SoC hits certain low-power
states.  The bits to control this are part of the pinctrl settings for
the each driver on these SoCs.  So technically it's neither the device
nor its power domain that cause the wakeup, but the external pad, aided
by some dedicated, always-on hardware, called "IO daisy chain" in the TI
documentation[1].

Kevin

[1] c.f Section 6.2.3.11 I/O Power Management and Daisy Chaining
    in the AM62L TRM for b bit more details: https://www.ti.com/lit/pdf/sprujb4





  reply	other threads:[~2025-04-08  0:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14  9:20 POWER_DOMAIN_ATTRIBUTES in SCMI Peng Fan
2025-02-18 10:41 ` Sudeep Holla
2025-02-18 13:08   ` Peng Fan
2025-02-18 13:57     ` Vincent Guittot
2025-02-18 15:02       ` Ulf Hansson
2025-02-18 15:26         ` Sudeep Holla
2025-02-18 16:31         ` Peng Fan
2025-02-20  2:53           ` Peng Fan
2025-02-20  9:59             ` Souvik Chakravarty
2025-04-08  0:23               ` Kevin Hilman [this message]
2025-02-18 16:20       ` Peng Fan

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=7h7c3vh56y.fsf@baylibre.com \
    --to=khilman@kernel.org \
    --cc=arm-scmi@vger.kernel.org \
    --cc=chuck.cannon@nxp.com \
    --cc=cristian.marussi@arm.com \
    --cc=dan.carpenter@linaro.org \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=souvik.chakravarty@arm.com \
    --cc=sudeep.holla@arm.com \
    --cc=ulf.hansson@linaro.org \
    --cc=vincent.guittot@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.