linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-pm@vger.kernel.org, Nishanth Menon <nm@ti.com>,
	Vibhore Vardhan <vibhore@ti.com>, Dhruva Gole <d-gole@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 v2 2/3] pmdomain: ti_sci: add wakeup constraint management
Date: Thu, 05 Sep 2024 14:58:09 -0700	[thread overview]
Message-ID: <7hseudahla.fsf@baylibre.com> (raw)
In-Reply-To: <CAPDyKFpH9TQ3P75CXxHmgo+y8z-C_iYCzFzqR93w1Mt9jhFBBw@mail.gmail.com>

Ulf Hansson <ulf.hansson@linaro.org> writes:

> On Tue, 20 Aug 2024 at 02:00, Kevin Hilman <khilman@baylibre.com> 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>
>> Signed-off-by: Kevin Hilman <khilman@baylibre.com>
>> Signed-off-by: Dhruva Gole <d-gole@ti.com>
>> ---
>>  drivers/pmdomain/ti/ti_sci_pm_domains.c | 19 +++++++++++++++++++
>>  1 file changed, 19 insertions(+)
>>
>> diff --git a/drivers/pmdomain/ti/ti_sci_pm_domains.c b/drivers/pmdomain/ti/ti_sci_pm_domains.c
>> index 963272fa387b..8af907579152 100644
>> --- a/drivers/pmdomain/ti/ti_sci_pm_domains.c
>> +++ b/drivers/pmdomain/ti/ti_sci_pm_domains.c
>> @@ -76,6 +76,23 @@ static int ti_sci_pd_set_lat_constraint(struct device *dev, s32 val)
>>         return ret;
>>  }
>>
>> +static inline bool ti_sci_pd_set_wkup_constraint(struct device *dev)
>> +{
>
> Similar comment as for patch1, should this be a static void intstead?
>

Yes, will do in v3.

Kevin




  reply	other threads:[~2024-09-05 22:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20  0:00 [PATCH v2 0/3] pmdomain: ti_sci: collect and send low-power mode constraints Kevin Hilman
2024-08-20  0:00 ` [PATCH v2 1/3] pmdomain: ti_sci: add per-device latency constraint management Kevin Hilman
2024-09-05 11:30   ` Ulf Hansson
2024-09-05 21:57     ` Kevin Hilman
2024-08-20  0:00 ` [PATCH v2 2/3] pmdomain: ti_sci: add wakeup " Kevin Hilman
2024-09-05 11:31   ` Ulf Hansson
2024-09-05 21:58     ` Kevin Hilman [this message]
2024-08-20  0:00 ` [PATCH v2 3/3] pmdomain: ti_sci: handle wake IRQs for IO daisy chain wakeups Kevin Hilman
2024-08-20 10:07 ` [PATCH v2 0/3] pmdomain: ti_sci: collect and send low-power mode constraints Dhruva Gole
2024-09-05 11:38 ` Ulf Hansson
2024-09-05 22:07   ` Kevin Hilman
2024-09-06  9:00     ` 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=7hseudahla.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=a-kaur@ti.com \
    --cc=d-gole@ti.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 \
    --cc=vibhore@ti.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;
as well as URLs for NNTP newsgroup(s).