All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@kernel.org>
Cc: Dhruva Gole <d-gole@ti.com>, Andrew Davis <afd@ti.com>,
	Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
	Santosh Shilimkar <ssantosh@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Praneeth Bajjuri <praneeth@ti.com>,
	Dave Gerlach <d-gerlach@ti.com>, Vibhore Vardhan <vibhore@ti.com>,
	Georgi Vlaev <g-vlaev@ti.com>
Subject: Re: [PATCH V6 4/4] firmware: ti_sci: Introduce system suspend resume support
Date: Wed, 9 Aug 2023 10:23:30 +0300	[thread overview]
Message-ID: <20230809072330.GB11676@atomide.com> (raw)
In-Reply-To: <7httt9dq2x.fsf@baylibre.com>

* Kevin Hilman <khilman@kernel.org> [230809 00:20]:
> To me, it sounds like you might want to use ->resume_early() or maybe
> ->resume_noirq() in the pinctrl driver for this so that IO isolation can
> be disabled sooner?

For calls that need to happen just before the SoC is disabled or first
thing on resume path, cpu_cluster_pm_enter() and cpu_cluster_pm_exit()
notifiers work nice and allow distributing the code across the related
SoC specific code and device drivers. See for example the usage in
drivers/irqchip/irq-gic.c for CPU_CLUSTER_PM_ENTER.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@kernel.org>
Cc: Dhruva Gole <d-gole@ti.com>, Andrew Davis <afd@ti.com>,
	Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
	Santosh Shilimkar <ssantosh@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Praneeth Bajjuri <praneeth@ti.com>,
	Dave Gerlach <d-gerlach@ti.com>, Vibhore Vardhan <vibhore@ti.com>,
	Georgi Vlaev <g-vlaev@ti.com>
Subject: Re: [PATCH V6 4/4] firmware: ti_sci: Introduce system suspend resume support
Date: Wed, 9 Aug 2023 10:23:30 +0300	[thread overview]
Message-ID: <20230809072330.GB11676@atomide.com> (raw)
In-Reply-To: <7httt9dq2x.fsf@baylibre.com>

* Kevin Hilman <khilman@kernel.org> [230809 00:20]:
> To me, it sounds like you might want to use ->resume_early() or maybe
> ->resume_noirq() in the pinctrl driver for this so that IO isolation can
> be disabled sooner?

For calls that need to happen just before the SoC is disabled or first
thing on resume path, cpu_cluster_pm_enter() and cpu_cluster_pm_exit()
notifiers work nice and allow distributing the code across the related
SoC specific code and device drivers. See for example the usage in
drivers/irqchip/irq-gic.c for CPU_CLUSTER_PM_ENTER.

Regards,

Tony

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-08-09  7:23 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03  6:42 [PATCH V6 0/4] firmware: ti_sci: Introduce system suspend support Dhruva Gole
2023-08-03  6:42 ` Dhruva Gole
2023-08-03  6:42 ` [PATCH V6 1/4] firmware: ti_sci: Introduce Power Management Ops Dhruva Gole
2023-08-03  6:42   ` Dhruva Gole
2023-08-03 15:14   ` Andrew Davis
2023-08-03 15:14     ` Andrew Davis
2023-08-03 15:42     ` Dhruva Gole
2023-08-03 15:42       ` Dhruva Gole
2023-08-03 15:57       ` Andrew Davis
2023-08-03 15:57         ` Andrew Davis
2023-08-03  6:42 ` [PATCH V6 2/4] firmware: ti_sci: Add support for querying the firmware caps Dhruva Gole
2023-08-03  6:42   ` Dhruva Gole
2023-08-03 15:21   ` Andrew Davis
2023-08-03 15:21     ` Andrew Davis
2023-08-03  6:42 ` [PATCH V6 3/4] firmware: ti_sci: Allocate memory for Low Power Modes Dhruva Gole
2023-08-03  6:42   ` Dhruva Gole
2023-08-03 15:23   ` Andrew Davis
2023-08-03 15:23     ` Andrew Davis
2023-08-03 15:57     ` Dhruva Gole
2023-08-03 15:57       ` Dhruva Gole
2023-08-03  6:42 ` [PATCH V6 4/4] firmware: ti_sci: Introduce system suspend resume support Dhruva Gole
2023-08-03  6:42   ` Dhruva Gole
2023-08-03 15:26   ` Andrew Davis
2023-08-03 15:26     ` Andrew Davis
2023-08-03 15:55     ` Dhruva Gole
2023-08-03 15:55       ` Dhruva Gole
2023-08-03 16:00       ` Andrew Davis
2023-08-03 16:00         ` Andrew Davis
2023-08-03 16:08         ` Dhruva Gole
2023-08-03 16:08           ` Dhruva Gole
2023-08-07 21:57           ` Kevin Hilman
2023-08-07 21:57             ` Kevin Hilman
2023-08-08 11:54             ` Dhruva Gole
2023-08-08 11:54               ` Dhruva Gole
2023-08-09  0:20               ` Kevin Hilman
2023-08-09  0:20                 ` Kevin Hilman
2023-08-09  7:23                 ` Tony Lindgren [this message]
2023-08-09  7:23                   ` Tony Lindgren
2023-08-09 17:37                   ` Kevin Hilman
2023-08-09 17:37                     ` Kevin Hilman
2023-08-03 15:18 ` [PATCH V6 0/4] firmware: ti_sci: Introduce system suspend support Andrew Davis
2023-08-03 15:18   ` Andrew Davis

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=20230809072330.GB11676@atomide.com \
    --to=tony@atomide.com \
    --cc=afd@ti.com \
    --cc=d-gerlach@ti.com \
    --cc=d-gole@ti.com \
    --cc=g-vlaev@ti.com \
    --cc=khilman@kernel.org \
    --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=praneeth@ti.com \
    --cc=ssantosh@kernel.org \
    --cc=vibhore@ti.com \
    --cc=viresh.kumar@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.