From: Dhruva Gole <d-gole@ti.com>
To: Kevin Hilman <khilman@baylibre.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>, <linux-pm@vger.kernel.org>,
Nishanth Menon <nm@ti.com>, Akashdeep Kaur <a-kaur@ti.com>,
Sebin Francis <sebin.francis@ti.com>,
Markus Schneider-Pargmann <msp@baylibre.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 2/3] pmdomain: ti_sci: add wakeup constraint management
Date: Tue, 10 Dec 2024 16:24:41 +0530 [thread overview]
Message-ID: <20241210105441.wav23zfv25es2jld@lcpd911> (raw)
In-Reply-To: <20241206-lpm-v6-10-constraints-pmdomain-v6-2-833980158c68@baylibre.com>
On Dec 06, 2024 at 14:12:51 -0800, Kevin Hilman wrote:
> During system-wide suspend, check all devices connected to PM domain
> to see if they are wakeup-enabled. If so, set a TI SCI device
> constraint.
>
> Note: DM firmware clears all constraints on resume.
>
> Co-developed-by: Vibhore Vardhan <vibhore@ti.com>
> Signed-off-by: Vibhore Vardhan <vibhore@ti.com>
> Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
> Tested-by: Dhruva Gole <d-gole@ti.com>
> Signed-off-by: Kevin Hilman <khilman@baylibre.com>
> ---
Reviewed-by: Dhruva Gole <d-gole@ti.com>
--
Best regards,
Dhruva Gole
Texas Instruments Incorporated
next prev parent reply other threads:[~2024-12-10 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 22:12 [PATCH v6 0/3] pmdomain: ti_sci: collect and send low-power mode constraints Kevin Hilman
2024-12-06 22:12 ` [PATCH v6 1/3] pmdomain: ti_sci: add per-device latency constraint management Kevin Hilman
2024-12-10 10:47 ` Dhruva Gole
2024-12-06 22:12 ` [PATCH v6 2/3] pmdomain: ti_sci: add wakeup " Kevin Hilman
2024-12-10 10:54 ` Dhruva Gole [this message]
2024-12-06 22:12 ` [PATCH v6 3/3] pmdomain: ti_sci: handle wake IRQs for IO daisy chain wakeups Kevin Hilman
2024-12-10 10:55 ` Dhruva Gole
2024-12-10 14:02 ` [PATCH v6 0/3] pmdomain: ti_sci: collect and send low-power mode constraints Ulf Hansson
2024-12-11 15:41 ` Kevin Hilman
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=20241210105441.wav23zfv25es2jld@lcpd911 \
--to=d-gole@ti.com \
--cc=a-kaur@ti.com \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=msp@baylibre.com \
--cc=nm@ti.com \
--cc=sebin.francis@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox