Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vitor Soares <ivitro@gmail.com>
To: Kendall Willis <k-willis@ti.com>, Nishanth Menon <nm@ti.com>,
	Tero Kristo <kristo@kernel.org>,
	Santosh Shilimkar <ssantosh@kernel.org>,
	Ulf Hansson <ulfh@kernel.org>,
	Kevin Hilman <khilman@baylibre.com>, Dhruva Gole <d-gole@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
	 linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	 tomi.valkeinen@ideasonboard.com, sebin.francis@ti.com,
	devarsht@ti.com,  vigneshr@ti.com, vishalm@ti.com,
	vitor.soares@toradex.com
Subject: Re: [PATCH] pmdomain: ti_sci: add wakeup constraint to parent devices of wakeup source
Date: Mon, 11 May 2026 17:51:29 +0100	[thread overview]
Message-ID: <becb54adc0bea88578c8fe4c7c1b7b68bf5cc6d4.camel@gmail.com> (raw)
In-Reply-To: <20260506-wkup-constraint-v1-1-0a4bce791b29@ti.com>

Hi Kendall,

On Wed, 2026-05-06 at 22:16 -0500, Kendall Willis wrote:
> Set wakeup constraint for any device in a wakeup path. All parent devices
> of a wakeup device should not be turned off during suspend. This ensures
> the wakeup device is kept on while the system is suspended.
> 

Thanks for the patch.

I tested it on our Verdin AM62P. As expected, suspend now fails cleanly with "-
19" when an SDIO WiFi module is registered as a wakeup source, instead of
crashing on resume:

ti-sci 44043000.system-controller: PM: failed to suspend: error -19

I did not test the IO daisy chain wakeup path, since that is out of scope for
this patch.

Best regards,
Vitor Soares




  reply	other threads:[~2026-05-11 16:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07  3:16 [PATCH] pmdomain: ti_sci: add wakeup constraint to parent devices of wakeup source Kendall Willis
2026-05-11 16:51 ` Vitor Soares [this message]
2026-05-12 16:17   ` Kendall Willis

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=becb54adc0bea88578c8fe4c7c1b7b68bf5cc6d4.camel@gmail.com \
    --to=ivitro@gmail.com \
    --cc=d-gole@ti.com \
    --cc=devarsht@ti.com \
    --cc=k-willis@ti.com \
    --cc=khilman@baylibre.com \
    --cc=kristo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=sebin.francis@ti.com \
    --cc=ssantosh@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tomi.valkeinen@ideasonboard.com \
    --cc=ulfh@kernel.org \
    --cc=vigneshr@ti.com \
    --cc=vishalm@ti.com \
    --cc=vitor.soares@toradex.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